Announcing end of support for Neuron Conda packages in Deep Learning AMI

{"value":"We are changing the way [AWS Neuron](https://aws.amazon.com/machine-learning/neuron/) the SDK of [Inf1 instances](https://aws.amazon.com/ec2/instance-types/inf1/) is installed and upgraded in Deep Learning AMI (DLAMI). Starting with Neuron SDK 1.14.0, we will no longer support conda packages to install Neuron SDK framework in DLAMI and we will no longer update conda packages used to install Neuron SDK framework (Neuron conda packages) with new versions.\n\nStarting with Neuron SDK 1.14.0, pip packages (Neuron pip packages) will be used to install Neuron SDK framework in DLAMI conda environment. To upgrade Neuron SDK framework DLAMI users should use pip upgrade commands instead of conda update commands. Instructions are available in this blog and in [Neuron SDK documentation](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/neuron-intro/neuron-install-guide.html#deep-learning-ami-dlami).\n\n#### **Why are we making the change?**\n\n- To solve upgrade issues related to Neuron conda packages that were reported by users. For example, in some cases the upgrade using ```conda update <framework>```\n cannot be used even though newer versions existed in known conda channel. By moving to pip upgrade flow we expect those issues to be solved.\n- To maintain consistency with the way software packages are installed in DLAMI where pip packages are used in most cases.\n\n#### **How does this impact me?**\n\nStarting with Neuron SDK 1.14.0, do not use ```conda update <framework>``` inside the conda environment to upgrade Neuron SDK framework to latest Neuron SDK releases. Instead, run one of the following commands to upgrade to latest Neuron framework of your choice:\n\n- To upgrade Neuron PyTorch:\n```\nsource activate aws_neuron_pytorch_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade torch-neuron neuron-cc[tensorflow] torchvision\n```\n\n- To upgrade Neuron TensorFlow:\n```\nsource activate aws_neuron_tensorflow_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade tensorflow-neuron tensorboard-neuron neuron-cc\n```\n\n- To upgrade Neuron MXNet:\n```\nsource activate aws_neuron_mxnet_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade mxnet-neuron neuron-cc\n```\n\n##### **How do I upgrade to latest Neuron SDK version if I am using versions before 1.14.0 ?**\n\nIf you are using Neuron SDK versions before 1.14.0 and want to upgrade to latest Neuron SDK version you should use pip upgrade commands described above instead of conda update commands.\n\n##### **How do I know what Neuron SDK version included in what DLAMI version ?**\n\nSee “[Deep Learning AMI (DLAMI) and Neuron SDK versions Matrix](https://awsdocs-neuron-staging.readthedocs-hosted.com/en/mxnet-branding/neuron-intro/dlami/dlami-neuron-matrix.html)” in Neuron documentation.\n\n##### **Do the pip upgrade commands upgrade all Neuron packages ?**\n\nThe pip upgrade commands applies to Neuron framework (in addition to the Neuron compiler). To upgrade Neuron runtime and tools, see [Neuron SDK documentation](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/neuron-intro/neuron-install-guide.html#deep-learning-ami-dlami).\n\n##### **What happens if I try to do ```conda update <framework>```?**\nAttempting to do ```conda update <framework>``` in newer versions of DLAMI would result in “PackageNotInstalledError: Package is not installed in prefix.” error:\n\n```\n(aws_neuron_tensorflow_36) ubuntu@ip-xxx-xx-xx-xx:~$ conda update tensorflow-neuron\nPackageNotInstalledError: Package is not installed in prefix.\nprefix: /home/ubuntu/anaconda3/envs/aws_neuron_tensorflow\npackage name: tensorflow-neuron\n```\n\n#### **Next steps**\n\nStarting with Neuron SDK 1.14.0, Neuron conda packages used to install Neuron SDK framework in DLAMI will no longer be supported. Instead, pip packages will be used to install Neuron SDK in DLAMI. Moving to pip packages will solve installation and upgrade issues reported by users and will be consistent with how other packages are installed in DLAMI.\nTo upgrade Neuron SDK framework, DLAMI users should use pip upgrade commands instead of conda update commands as explained above. If you have any questions or concerns about this change or if you are facing issues please open\n[Github issue](https://github.com/aws/aws-neuron-sdk/issues), or post a question in [Neuron AWS forums](https://forums.aws.amazon.com/forum.jspa?forumID=355).","render":"<p>We are changing the way <a href=\"https://aws.amazon.com/machine-learning/neuron/\" target=\"_blank\">AWS Neuron</a> the SDK of <a href=\"https://aws.amazon.com/ec2/instance-types/inf1/\" target=\"_blank\">Inf1 instances</a> is installed and upgraded in Deep Learning AMI (DLAMI). Starting with Neuron SDK 1.14.0, we will no longer support conda packages to install Neuron SDK framework in DLAMI and we will no longer update conda packages used to install Neuron SDK framework (Neuron conda packages) with new versions.</p>\n<p>Starting with Neuron SDK 1.14.0, pip packages (Neuron pip packages) will be used to install Neuron SDK framework in DLAMI conda environment. To upgrade Neuron SDK framework DLAMI users should use pip upgrade commands instead of conda update commands. Instructions are available in this blog and in <a href=\"https://awsdocs-neuron.readthedocs-hosted.com/en/latest/neuron-intro/neuron-install-guide.html#deep-learning-ami-dlami\" target=\"_blank\">Neuron SDK documentation</a>.</p>\n<h4><a id=\"Why_are_we_making_the_change_4\"></a><strong>Why are we making the change?</strong></h4>\n<ul>\n<li>To solve upgrade issues related to Neuron conda packages that were reported by users. For example, in some cases the upgrade using <code>conda update &lt;framework&gt;</code><br />\ncannot be used even though newer versions existed in known conda channel. By moving to pip upgrade flow we expect those issues to be solved.</li>\n<li>To maintain consistency with the way software packages are installed in DLAMI where pip packages are used in most cases.</li>\n</ul>\n<h4><a id=\"How_does_this_impact_me_10\"></a><strong>How does this impact me?</strong></h4>\n<p>Starting with Neuron SDK 1.14.0, do not use <code>conda update &lt;framework&gt;</code> inside the conda environment to upgrade Neuron SDK framework to latest Neuron SDK releases. Instead, run one of the following commands to upgrade to latest Neuron framework of your choice:</p>\n<ul>\n<li>To upgrade Neuron PyTorch:</li>\n</ul>\n<pre><code class=\"lang-\">source activate aws_neuron_pytorch_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade torch-neuron neuron-cc[tensorflow] torchvision\n</code></pre>\n<ul>\n<li>To upgrade Neuron TensorFlow:</li>\n</ul>\n<pre><code class=\"lang-\">source activate aws_neuron_tensorflow_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade tensorflow-neuron tensorboard-neuron neuron-cc\n</code></pre>\n<ul>\n<li>To upgrade Neuron MXNet:</li>\n</ul>\n<pre><code class=\"lang-\">source activate aws_neuron_mxnet_p36\npip config set global.extra-index-url https://pip.repos.neuron.amazonaws.com\npip install --upgrade mxnet-neuron neuron-cc\n</code></pre>\n<h5><a id=\"How_do_I_upgrade_to_latest_Neuron_SDK_version_if_I_am_using_versions_before_1140__35\"></a><strong>How do I upgrade to latest Neuron SDK version if I am using versions before 1.14.0 ?</strong></h5>\n<p>If you are using Neuron SDK versions before 1.14.0 and want to upgrade to latest Neuron SDK version you should use pip upgrade commands described above instead of conda update commands.</p>\n<h5><a id=\"How_do_I_know_what_Neuron_SDK_version_included_in_what_DLAMI_version__39\"></a><strong>How do I know what Neuron SDK version included in what DLAMI version ?</strong></h5>\n<p>See “<a href=\"https://awsdocs-neuron-staging.readthedocs-hosted.com/en/mxnet-branding/neuron-intro/dlami/dlami-neuron-matrix.html\" target=\"_blank\">Deep Learning AMI (DLAMI) and Neuron SDK versions Matrix</a>” in Neuron documentation.</p>\n<h5><a id=\"Do_the_pip_upgrade_commands_upgrade_all_Neuron_packages__43\"></a><strong>Do the pip upgrade commands upgrade all Neuron packages ?</strong></h5>\n<p>The pip upgrade commands applies to Neuron framework (in addition to the Neuron compiler). To upgrade Neuron runtime and tools, see <a href=\"https://awsdocs-neuron.readthedocs-hosted.com/en/latest/neuron-intro/neuron-install-guide.html#deep-learning-ami-dlami\" target=\"_blank\">Neuron SDK documentation</a>.</p>\n<h5><a id=\"What_happens_if_I_try_to_do_conda_update_ltframeworkgt_47\"></a><strong>What happens if I try to do <code>conda update &lt;framework&gt;</code>?</strong></h5>\n<p>Attempting to do <code>conda update &lt;framework&gt;</code> in newer versions of DLAMI would result in “PackageNotInstalledError: Package is not installed in prefix.” error:</p>\n<pre><code class=\"lang-\">(aws_neuron_tensorflow_36) ubuntu@ip-xxx-xx-xx-xx:~$ conda update tensorflow-neuron\nPackageNotInstalledError: Package is not installed in prefix.\nprefix: /home/ubuntu/anaconda3/envs/aws_neuron_tensorflow\npackage name: tensorflow-neuron\n</code></pre>\n<h4><a id=\"Next_steps_57\"></a><strong>Next steps</strong></h4>\n<p>Starting with Neuron SDK 1.14.0, Neuron conda packages used to install Neuron SDK framework in DLAMI will no longer be supported. Instead, pip packages will be used to install Neuron SDK in DLAMI. Moving to pip packages will solve installation and upgrade issues reported by users and will be consistent with how other packages are installed in DLAMI.<br />\nTo upgrade Neuron SDK framework, DLAMI users should use pip upgrade commands instead of conda update commands as explained above. If you have any questions or concerns about this change or if you are facing issues please open<br />\n<a href=\"https://github.com/aws/aws-neuron-sdk/issues\" target=\"_blank\">Github issue</a>, or post a question in <a href=\"https://forums.aws.amazon.com/forum.jspa?forumID=355\" target=\"_blank\">Neuron AWS forums</a>.</p>\n"}