8196e7f946
Group of the current managed subclouds which are supposed
to be duplicated in a peer site as secondary subclouds.
This commit add subcloud-peer-group APIs of
create/delete/update/show/list/
list-subclouds of a subcloud-peer-group
Update setting peer-group for subcloud, Using DB of subclouds'
'peer_group_id' Column.
Update subcloud update API, add peer_group parameter
Usage:
Add a subcloud to peer-group:
dcmanager subcloud update SUBCLOUD --peer-group PEER_GROUP
Remove a subcloud from peer-group:
dcmanager subcloud update SUBCLOUD --peer-group none
Test Plan:
1. PASS - Create a subcloud-peer-group
2. PASS - Update an existing subcloud's peer-group to a existing
subcloud-peer-group successfully;
3. PASS - Verify subcloud-peer-group list-subclouds can get the expected
Subcloud above successfully;
4. PASS - Update group_priority/group_state/max_subcloud_rehoming/
system_leader_id/system_leader_name
of a subcloud-peer-group successfully;
5. PASS - Check can get subcloud status of a subcloud-peer-group
successfully;
6. PASS - Delete a subcloud-peer-group completes successfully.
7. PASS - Delete a subcloud-peer-group while it still has subclouds
associated to it. the subclouds' peer-group-id is auto
set to None successfully;
8. PASS - Add a subcloud, update the peer-group-id as a non-existing
subcloud-peer-group, get error message successfully;
9. PASS - Update subcloud peer group with invalid
group_priority/group_state/max_subcloud_rehoming/
system_leader_id/system_leader_name
Story: 2010852
Task: 48485
Change-Id: I93d0808b8cf02eba0e6f687007df42e2d2ea1848
Signed-off-by: Wang Tao <tao.wang@windriver.com>
8 lines
214 B
JSON
8 lines
214 B
JSON
{
|
|
"peer_group_name": "pg-name",
|
|
"group_priority": 0,
|
|
"group_state": "enabled",
|
|
"max_subcloud_rehoming": 10,
|
|
"system_leader_id": "ac62f555-9386-42f1-b3a1-51ecb709409d",
|
|
"system_leader_name": "dc1-name"
|
|
} |