Integration of Deployment Manager (ds8)
Story: 2010718 Task: 48735 Change-Id: I328095360526cfcd546ff795cbd4082995c08992 Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
parent
591824df28
commit
deda1c4e86
@ -1,4 +1,7 @@
|
||||
|
||||
|
||||
.. Orchupgradecli-begin
|
||||
.. Orchupgradecli-end
|
||||
.. Orchupgradecli-end
|
||||
|
||||
.. deploymentmanager-begin
|
||||
.. deploymentmanager-end
|
@ -1,4 +1,7 @@
|
||||
|
||||
|
||||
.. upgradeDX-begin
|
||||
.. upgradeDX-end
|
||||
.. upgradeDX-end
|
||||
|
||||
.. deploymentmanager-begin
|
||||
.. deploymentmanager-end
|
@ -1,4 +1,7 @@
|
||||
|
||||
|
||||
.. upgradeAIO-begin
|
||||
.. upgradeAIO-end
|
||||
.. upgradeAIO-end
|
||||
|
||||
.. deploymentmanager-begin
|
||||
.. deploymentmanager-end
|
@ -9,4 +9,8 @@
|
||||
.. wrsend
|
||||
|
||||
.. DMupgrades-begin
|
||||
.. DMupgrades-end
|
||||
.. DMupgrades-end
|
||||
|
||||
.. deploymentmanager-begin
|
||||
.. deploymentmanager-end
|
||||
|
||||
|
@ -295,7 +295,7 @@ subcloud, the subcloud installation process has two phases:
|
||||
|
||||
~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
|
||||
|
||||
.. include:: /_includes/installing-a-subcloud-without-redfish-platform-management-service.rest
|
||||
.. pre-include:: /_includes/installing-a-subcloud-without-redfish-platform-management-service.rest
|
||||
:start-after: begin-prepare-files-to-copy-deployment-config
|
||||
:end-before: end-prepare-files-to-copy-deployment-config
|
||||
|
||||
|
@ -466,6 +466,12 @@ Follow the steps below to manually upgrade the system controller:
|
||||
configuration is applied. The upgrade state goes from **activating** to
|
||||
**activation-complete** once this is done.
|
||||
|
||||
.. only:: partner
|
||||
|
||||
.. include:: /_includes/upgrading-the-systemcontroller-using-the-cli.rest
|
||||
:start-after: deploymentmanager-begin
|
||||
:end-before: deploymentmanager-end
|
||||
|
||||
The following states apply when this command is executed.
|
||||
|
||||
**activation-requested**
|
||||
|
@ -258,6 +258,12 @@ described below to upgrade the remaining nodes of the |prod|.
|
||||
configuration is applied. The upgrade state goes from **activating** to
|
||||
**activation-complete** once this is done.
|
||||
|
||||
.. only:: partner
|
||||
|
||||
.. include:: /_includes/performing-an-orchestrated-upgrade-using-the-cli.rest
|
||||
:start-after: deploymentmanager-begin
|
||||
:end-before: deploymentmanager-end
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ system upgrade-activate
|
||||
|
@ -484,6 +484,12 @@ of |prod| software.
|
||||
configuration is applied. The upgrade state goes from ``activating`` to
|
||||
``activation-complete`` once this is done.
|
||||
|
||||
.. only:: partner
|
||||
|
||||
.. include:: /_includes/upgrading-all-in-one-duplex-or-standard.rest
|
||||
:start-after: deploymentmanager-begin
|
||||
:end-before: deploymentmanager-end
|
||||
|
||||
The following states apply when this command is executed.
|
||||
|
||||
``activation-requested``
|
||||
|
@ -371,6 +371,12 @@ For more details, see :ref:`Contents of System Backup
|
||||
configuration is applied. The upgrade state goes from *activating* to
|
||||
*activation-complete* once this is done.
|
||||
|
||||
.. only:: partner
|
||||
|
||||
.. include:: /_includes/upgrading-all-in-one-simplex.rest
|
||||
:start-after: deploymentmanager-begin
|
||||
:end-before: deploymentmanager-end
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ system upgrade-activate
|
||||
|
Loading…
x
Reference in New Issue
Block a user