9e5b12cae9
Story: 2010676 Task: 51423 Change-Id: I2e15fd4645c7661ab838a4ed0e69f7167a1cce79 Signed-off-by: Elisamara Aoki Gonçalves <elisamaraaoki.goncalves@windriver.com>
24 lines
901 B
ReStructuredText
24 lines
901 B
ReStructuredText
.. afr1600186951848
|
|
.. _orchestration-strategy-using-subcloud-groups:
|
|
|
|
============================================
|
|
Orchestration Strategy Using Subcloud Groups
|
|
============================================
|
|
|
|
When an upgrade, update, or firmware update orchestration strategy is created,
|
|
the strategy ensures that the application of software upgrades, and updates are
|
|
done in the following order for the subclouds.
|
|
|
|
The order in which :command:`dcmanager subcloud-group list` displays the
|
|
subcloud groups, is the order they are processed by orchestration.
|
|
|
|
|
|
.. _ochestration-strategy-using-subcloud-groups-ol-hzg-q2v-ymb:
|
|
|
|
#. First, all subclouds in the default group.
|
|
|
|
#. All subclouds in the first, second, and third group, etc.
|
|
|
|
#. Subclouds from different groups will never be included in the same stage of
|
|
the strategy to ensure they are not upgraded, updated (patched) at the
|
|
same time. |