
Fix bullets with older command and replace by correct command. Closes-bug: 2103741 Change-Id: I94739424e7fab43241079434e7c8867174871b09 Signed-off-by: Elisamara Aoki Gonçalves <elisamaraaoki.goncalves@windriver.com>
2.2 KiB
Manage Subcloud Groups
Subclouds can be organized into subcloud groups. These subcloud groups can control how subclouds are updated.
When a subcloud is created it is automatically added to the 'Default'
subcloud group, unless the group is specified. Subclouds can be
associated with a particular group when they are created, and that
association can be changed to a different subcloud group, if required.
To create a subcloud group, see, create-edit-and-delete-subcloud-groups-using-the-cli
.
For example, while creating a strategy, if several subclouds can be
upgraded or updated in parallel, they can be grouped together in a
subcloud group that supports parallel upgrades or updates. In this case,
the max_parallel_subclouds
, and subcloud_apply_type
are
not specified when the strategy is created, so that the
settings in the subcloud group are used.
Alternatively, if several subclouds should be upgraded or updated
individually, they can be grouped together in a subcloud group that
supports serial updates. In this case, the max_parallel_subclouds
,
andsubcloud_apply_type
are not
specified when creating the strategy, and the subcloud group settings
for max_parallel_subclouds
(not applicable), and the
subcloud_apply_type
(serial) associated with that subcloud group are used.
For more information on creating a strategy for orchestration upgrades, updates or firmware updates, see:
To create a software deploy orchestration strategy, use the
dcmanager sw-deploy-strategy create
command.For more information see
deploy-software-releases-using-the-cli-1ea02eb230e5
.To create a firmware update orchestration strategy use the
dcmanager fw-update-strategy create
command.
create-edit-and-delete-subcloud-groups-using-the-cli
orchestration-strategy-using-subcloud-groups