Added migration for deployment #10800

ilya-lavrenov · 2022-03-04T15:41:03Z

Details:

item1
...

Tickets:

ticket-id

ilyachur · 2022-03-05T03:05:49Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+
+"Easy to use" is one of the main points for OpenVINO 2.0 concept. This includes not only simplification of migration from frameworks to OpenVINO Toolkit, but also how OpenVINO is organized, how the development tools are used, how to develop and deploy OpenVINO-based applications.
+
+Starting from OpenVINO 2.0, Model Optimizer, Post Training Optimization tool, Open Model Zoo tools and other Python-based Development tools are distributed via [PyPI](https://pypi.org/project/openvino-dev/) only. This simplifies user experience, because in older versions of OpenVINO development tools should be installed and used differently dependning on distribution type (debian packages vs. PyPi).


I think will be good to provide an example, how openvino-dev package can be installed.
pip install openvino-dev

yury-gorbachev

Generally good document

yury-gorbachev · 2022-03-05T06:43:05Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+
+## Introduction
+
+"Easy to use" is one of the main points for OpenVINO 2.0 concept. This includes not only simplification of migration from frameworks to OpenVINO Toolkit, but also how OpenVINO is organized, how the development tools are used, how to develop and deploy OpenVINO-based applications.


We cannot write OpenVINO 2.0, we can say OpenVINO API 2.0 or OpenVINO 22.1 release per marketing requirement. In this case I think OpenVINO API 2.0 makes more sense, in next paragraph I suggest to replace with 22.1 release...

Hi there, yes we have some guidelines from marketing:

For any features that require a designated version (e.g. API & IR format), please use v2 and so on, for example, OpenVINO API v2.

2.0 is ok to use when there is clearly a distinction between release number and feature version, i.e. OpenVINO 2022.1 now supports API 2.0.

Do no use 2.0 as it relates to OpenVINO release, as it confuses the market around our product naming convention. So "OpenVINO 2.0" is not allowed.

For any reference to actual release, please use the full release number. So use OpenVINO 2022.1 only.

yury-gorbachev · 2022-03-05T06:44:52Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+
+"Easy to use" is one of the main points for OpenVINO 2.0 concept. This includes not only simplification of migration from frameworks to OpenVINO Toolkit, but also how OpenVINO is organized, how the development tools are used, how to develop and deploy OpenVINO-based applications.
+
+Starting from OpenVINO 2.0, Model Optimizer, Post Training Optimization tool, Open Model Zoo tools and other Python-based Development tools are distributed via [PyPI](https://pypi.org/project/openvino-dev/) only. This simplifies user experience, because in older versions of OpenVINO development tools should be installed and used differently dependning on distribution type (debian packages vs. PyPi).


This not only simplifies due to different installation, but also ensures that dependencies are handled properly via PyPi as well as supports virtual environments for development tools.

yury-gorbachev · 2022-03-05T06:45:49Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+
+Starting from OpenVINO 2.0, Model Optimizer, Post Training Optimization tool, Open Model Zoo tools and other Python-based Development tools are distributed via [PyPI](https://pypi.org/project/openvino-dev/) only. This simplifies user experience, because in older versions of OpenVINO development tools should be installed and used differently dependning on distribution type (debian packages vs. PyPi).
+
+Moreover, we have tried further to reorganize package structure to have it in a good shape:


Here, it is a little bit unclear shift from general description to IRC package. So, maybe I would clarify that it is applicable to installer package. Or am I missing something?

yury-gorbachev · 2022-03-05T06:47:12Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+Moreover, we have tried further to reorganize package structure to have it in a good shape:
+
+- `runtime` folder with OpenVINO Runtime include headers, libraries and CMake interfaces.
+- `tools` folder with [compile_tool](../../../tools/compile_tool/README.md), [deployment manager](../../install_guides/deployment-manager-tool.md), `requirement.txt` files with `openvino-dev` package.


requirement.txt file with link to corresponding version of openvino-dev package.

yury-gorbachev · 2022-03-05T06:47:45Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+$ mo.py -h
+```
+
+In OpenVINO 2.0 users can install development tools only from [PyPI](https://pypi.org/project/openvino-dev/) repository:


Starting with OpenVINO 22.1...

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

yury-gorbachev · 2022-03-05T06:58:04Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+target_link_libraries(ie_ngraph_app PRIVATE ${InferenceEngine_LIBRARIES} ${NGRAPH_LIBRARIES})
+```
+
+OpenVINO Runtine 2.0:


yury-gorbachev · 2022-03-05T06:59:26Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+ - `openvino_onnx_frontend` to read ONNX models
+ - `openvino_paddle_frontend` to read Paddle models
+
+So, to perform deployment steps - just take only required functionality: `openvino` or `openvino_c` depending on derired language plus plugins which are needed to solve your task. For example, `openvino_intel_cpu_plugin` and `openvino_ir_frontend` plugins to be able to load OpenVINO IRs and perform inference on CPU device.


yury-gorbachev · 2022-03-05T07:00:27Z

docs/OV_Runtime_UG/migration_ov_2_0/intro.md

@@ -77,5 +78,6 @@ Please look at next transition guides to understand how migrate Inference Engine
 - [Preprocess your model](./preprocessing.md)
 - [Configure device](./configure_devices.md)
 - [OpenVINO™ Model Creation](graph_construction.md)
+ - [Install & deployment](deployment_migration.md)


I'm wondering if we should set this as first doc in list? Given that logically this is the first thing you do (aligned with Get Started)

xu-yuan1 · 2022-03-10T09:22:04Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

@@ -0,0 +1,156 @@
+# Install & Deployment {#openvino_2_0_deployment}


Updates on Installation & Deployment

xu-yuan1 · 2022-03-10T09:45:14Z

docs/OV_Runtime_UG/migration_ov_2_0/deployment_migration.md

+
+- `runtime` folder with OpenVINO Runtime include headers, libraries and CMake interfaces.
+- `tools` folder with [compile_tool](../../../tools/compile_tool/README.md), [deployment manager](../../install_guides/deployment-manager-tool.md), `requirement.txt` files with link to corresponding version of `openvino-dev` package.
+- `python` folder with OpenVINO Python Runtime.


What is "OpenVINO Python Runtime"? I think it's a kind of incorporating the OpenVINO brand, which is not allowed. Is it "the Python version for OpenVINO Runtime"?

the Python version for OpenVINO Runtime - yes

* Added migration for deployment * Addressed comments

* Added migration for deployment (#10800) * Added migration for deployment * Addressed comments * more info after the What's new Sessions' questions (#10803) * more info after the What's new Sessions' questions * generalizing the optimal_batch_size vs explicit value message * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Update docs/OV_Runtime_UG/automatic_batching.md Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Perf Hints docs and General Opt Guide refactoring (#10815) * Brushed the general optimization page * Opt GUIDE, WIP * perf hints doc placeholder * WIP * WIP2 * WIP 3 * added streams and few other details * fixed titles, misprints etc * Perf hints * movin the runtime optimizations intro * fixed link * Apply suggestions from code review Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * some details on the FIL and other means when pure inference time is not the only factor * shuffled according to general->use-case->device-specifics flow, minor brushing * next iter * section on optimizing for tput and latency * couple of links to the features support matrix * Links, brushing, dedicated subsections for Latency/FIL/Tput * had to make the link less specific (otherwise docs compilations fails) * removing the Temp/Should be moved to the Opt Guide * shuffled the tput/latency/etc info into separated documents. also the following docs moved from the temp into specific feature, general product desc or corresponding plugins - openvino_docs_IE_DG_Model_caching_overview - openvino_docs_IE_DG_Int8Inference - openvino_docs_IE_DG_Bfloat16Inference - openvino_docs_OV_UG_NoDynamicShapes * fixed toc for ov_dynamic_shapes.md * referring the openvino_docs_IE_DG_Bfloat16Inference to avoid docs compilation errors * fixed main product TOC, removed ref from the second-level items * reviewers remarks * reverted the openvino_docs_OV_UG_NoDynamicShapes * reverting openvino_docs_IE_DG_Bfloat16Inference and openvino_docs_IE_DG_Int8Inference * "No dynamic shapes" to the "Dynamic shapes" as TOC * removed duplication * minor brushing * Caching to the next level in TOC * brushing * more on the perf counters ( for latency and dynamic cases) Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> * Updated common IE pipeline infer-request section (#10844) * Updated common IE pipeline infer-reqest section * Update ov_infer_request.md * Apply suggestions from code review Co-authored-by: Karol Blaszczak <karol.blaszczak@intel.com> Co-authored-by: Maxim Shevtsov <maxim.y.shevtsov@intel.com> Co-authored-by: Karol Blaszczak <karol.blaszczak@intel.com> * DOCS: Removed useless 4 spaces in snippets (#10870) * Updated snippets * Added link to encryption * [DOCS] ARM CPU plugin docs (#10885) * initial commit ARM_CPU.md added ARM CPU is added to the list of supported devices * Update the list of supported properties * Update Device_Plugins.md * Update CODEOWNERS * Removed quotes in limitations section * NVIDIA and Android are added to the list of supported devices * Added See Also section and reg sign to arm * Added Preprocessing acceleration section * Update the list of supported layers * updated list of supported layers * fix typos * Added support disclaimer * update trade and reg symbols * fixed typos * fix typos * reg fix * add reg symbol back Co-authored-by: Vitaly Tuzov <vitaly.tuzov@intel.com> * Try to fix visualization (#10896) * Try to fix visualization * New try * Update Install&Deployment for migration guide to 22/1 (#10933) * updates * update * Getting started improvements (#10948) * Onnx updates (#10962) * onnx changes * onnx updates * onnx updates * fix broken anchors api reference (#10976) * add ote repo (#10979) * DOCS: Increase content width (#10995) * fixes * fix * Fixed compilation Co-authored-by: Maxim Shevtsov <maxim.y.shevtsov@intel.com> Co-authored-by: Tatiana Savina <tatiana.savina@intel.com> Co-authored-by: Karol Blaszczak <karol.blaszczak@intel.com> Co-authored-by: Aleksandr Voron <aleksandr.voron@intel.com> Co-authored-by: Vitaly Tuzov <vitaly.tuzov@intel.com> Co-authored-by: Ilya Churaev <ilya.churaev@intel.com> Co-authored-by: Yuan Xu <yuan1.xu@intel.com> Co-authored-by: Victoria Yashina <victoria.yashina@intel.com> Co-authored-by: Nikolay Tyukaev <nikolay.tyukaev@intel.com>

ilya-lavrenov force-pushed the deployment-migration branch 4 times, most recently from a2b8199 to 3efc22d Compare March 4, 2022 16:38

ilya-lavrenov requested a review from xu-yuan1 March 4, 2022 16:39

ilya-lavrenov added this to the 2022.1 milestone Mar 4, 2022

ilya-lavrenov added the category: docs OpenVINO documentation label Mar 4, 2022

Added migration for deployment

ba58a5e

ilya-lavrenov force-pushed the deployment-migration branch from 3efc22d to ba58a5e Compare March 4, 2022 16:42

ilyachur reviewed Mar 5, 2022

View reviewed changes

yury-gorbachev approved these changes Mar 5, 2022

View reviewed changes

ilya-lavrenov marked this pull request as ready for review March 5, 2022 11:28

ilya-lavrenov requested a review from a team as a code owner March 5, 2022 11:28

ilya-lavrenov requested review from avladimi and removed request for a team March 5, 2022 11:28

ilya-lavrenov added the port to master Required port to master from 2022.3 LTS label Mar 5, 2022

ilya-lavrenov requested review from a team March 5, 2022 11:28

ilya-lavrenov requested review from a team as code owners March 5, 2022 11:28

ilya-lavrenov requested review from a team March 5, 2022 11:28

Addressed comments

faa8168

ilya-lavrenov force-pushed the deployment-migration branch 2 times, most recently from 41dc109 to faa8168 Compare March 5, 2022 11:31

azhogov merged commit db05e54 into openvinotoolkit:releases/2022/1 Mar 5, 2022

ilya-lavrenov deleted the deployment-migration branch March 5, 2022 12:18

xu-yuan1 reviewed Mar 10, 2022

View reviewed changes

ilya-lavrenov added a commit to ilya-lavrenov/openvino that referenced this pull request Mar 18, 2022

Added migration for deployment (openvinotoolkit#10800)

018497e

* Added migration for deployment * Addressed comments

ilya-lavrenov added ported to master Ported from 2022.x branches to master and removed port to master Required port to master from 2022.3 LTS labels Mar 18, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added migration for deployment #10800

Added migration for deployment #10800

ilya-lavrenov commented Mar 4, 2022

ilyachur Mar 5, 2022

yury-gorbachev left a comment

yury-gorbachev Mar 5, 2022

xu-yuan1 Mar 10, 2022 •

edited

Loading

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

yury-gorbachev Mar 5, 2022

xu-yuan1 Mar 10, 2022 •

edited

Loading

xu-yuan1 Mar 10, 2022

ilya-lavrenov Mar 10, 2022


		"Easy to use" is one of the main points for OpenVINO 2.0 concept. This includes not only simplification of migration from frameworks to OpenVINO Toolkit, but also how OpenVINO is organized, how the development tools are used, how to develop and deploy OpenVINO-based applications.

		Starting from OpenVINO 2.0, Model Optimizer, Post Training Optimization tool, Open Model Zoo tools and other Python-based Development tools are distributed via [PyPI](https://pypi.org/project/openvino-dev/) only. This simplifies user experience, because in older versions of OpenVINO development tools should be installed and used differently dependning on distribution type (debian packages vs. PyPi).


		## Introduction

		"Easy to use" is one of the main points for OpenVINO 2.0 concept. This includes not only simplification of migration from frameworks to OpenVINO Toolkit, but also how OpenVINO is organized, how the development tools are used, how to develop and deploy OpenVINO-based applications.


		Starting from OpenVINO 2.0, Model Optimizer, Post Training Optimization tool, Open Model Zoo tools and other Python-based Development tools are distributed via [PyPI](https://pypi.org/project/openvino-dev/) only. This simplifies user experience, because in older versions of OpenVINO development tools should be installed and used differently dependning on distribution type (debian packages vs. PyPi).

		Moreover, we have tried further to reorganize package structure to have it in a good shape:

		@@ -0,0 +1,156 @@
		# Install & Deployment {#openvino_2_0_deployment}

Added migration for deployment #10800

Added migration for deployment #10800

Conversation

ilya-lavrenov commented Mar 4, 2022

Details:

Tickets:

Choose a reason for hiding this comment

yury-gorbachev left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xu-yuan1 Mar 10, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xu-yuan1 Mar 10, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

xu-yuan1 Mar 10, 2022 •

edited

Loading

xu-yuan1 Mar 10, 2022 •

edited

Loading