The Deployment Manager of Intel® Distribution of OpenVINO™ creates a deployment package by assembling the model, IR files, your application, and associated dependencies into a runtime package for your target device.
The Deployment Manager is a Python* command-line tool that is delivered within the Intel® Distribution of OpenVINO™ toolkit for Linux* and Windows* release packages and available after installation in the <INSTALL_DIR>/deployment_tools/tools/deployment_manager
directory.
IMPORTANT: The operating system on the target host must be the same as the development system on which you are creating the package. For example, if the target system is Ubuntu 18.04, the deployment package must be created from the OpenVINO™ toolkit installed on Ubuntu 18.04.
There are two ways to create a deployment package that includes inference-related components of the OpenVINO™ toolkit:
You can run the Deployment Manager tool in either Interactive or Standard CLI mode.
Click to expand/collapse
Interactive mode provides a user-friendly command-line interface that will guide you through the process with text prompts.
Use the options provided on the screen to complete selection of the target devices and press Enter to proceed to the package generation dialog. if you want to interrupt the generation process and exit the program, type q and press Enter.
The script successfully completes and the deployment package is generated in the output directory specified.
Click to expand/collapse
Alternatively, you can run the Deployment Manager tool in the standard CLI mode. In this mode, you specify the target devices and other parameters as command-line arguments of the Deployment Manager Python script. This mode facilitates integrating the tool in an automation pipeline.
To launch the Deployment Manager tool in the standard mode, open a new terminal window, go to the Deployment Manager tool directory and run the tool command with the following syntax:
The following options are available:
<--targets>
— (Mandatory) List of target devices to run inference. To specify more than one target, separate them with spaces. For example: --targets cpu gpu vpu
. You can get a list of currently available targets running the tool's help: [--output_dir]
— (Optional) Path to the output directory. By default, it set to your home directory.[--archive_name]
— (Optional) Deployment archive name without extension. By default, it set to openvino_deployment_package
.[--user_data]
— (Optional) Path to a directory with user data (IRs, models, datasets, etc.) required for inference. By default, it's set to None
, which means that the user data are already present on the target host machine.The script successfully completes and the deployment package is generated in the output directory specified.
After the Deployment Manager has successfully completed, you can find the generated .tar.gz
(for Linux) or .zip
(for Windows) package in the output directory you specified.
To deploy the Inference Engine components from the development machine to the target host, perform the following steps:
Unpack the archive into the destination directory on the target host (if your archive name is different from the default shown below, replace the openvino_deployment_package
with the name you use).
The package is unpacked to the destination directory and the following subdirectories are created:
bin
— Snapshot of the bin
directory from the OpenVINO installation directory.deployment_tools/inference_engine
— Contains the Inference Engine binary files.install_dependencies
— Snapshot of the install_dependencies
directory from the OpenVINO installation directory.<user_data>
— The directory with the user data (IRs, datasets, etc.) you specified while configuring the package.install_openvino_dependencies.sh
script: Congratulations, you have finished the deployment of the Inference Engine components to the target host.