starlingx/docs
Code Issues Proposed changes

Clarify subcloud requirement to update "--install-values " for future restoration (dsr10)

Browse Source 
Change-Id: Id8db07261401b1673203a517d8437affc5bfa3db
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
(cherry picked from commit ea1dc59305b54718dfecf63b12888c0391111a13)
This commit is contained in:
Ngairangbam Mili 2025-05-02 05:25:16 +00:00
parent 720d8f1ddb
commit 950f2ead1f
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/dist_cloud/kubernetes/deploy-software-releases-using-the-cli-1ea02eb230e5.rst
View File

@ -31,14 +31,15 @@ The System Controller is now ready for new subcloud deployment.
.. note::
Starting release |prod-ver|, low-latency configuration via remote install
is no longer supported.
is no longer supported.
For new subcloud deployments that involve remote install using Redfish,
avoid using ``install_type`` of 4 and 5 in ``install-values.yaml``.
avoid using ``install_type`` of 4 and 5 in ``install-values.yaml``.
For existing subclouds that were originally deployed with remote install,
use :command:`dcmanager subcloud update --install-values` to update the
``install_type`` so they can be restored in the future.
use :command:`dcmanager subcloud update --install-values` to update
``install_type`` so they can be restored in the future. Ensure that the
software version in ``install_values`` matches the new version.
Orchestrate the Deployment of a Software Release Across the Subclouds
---------------------------------------------------------------------
@ -340,4 +341,4 @@ If a failure occurs, follow the general steps below:
#. Resolve the condition that caused the failure.
#. Retry the orchestration by deleting the failed strategy and create a new
one for the failed subcloud(s).
one for the failed subcloud(s).