History

Yuxing Jiang bff2f0aa2f Check vim strategy before updating network It is risky to update a subcloud's network if there is an existing vim strategy: the on-going vim strategy triggers lock/unlock/swact can interrupt the ansible-playbook, leaving the subcloud in an un-recoverable state. To prevent this issue, this commit checks the on-going vim strategy, and blocks the further operation if it exists. Test plan: 1. Passed - deploy a DC with this change. 2. Passed - create a kube-rootca-update orchestration against a subcloud, verify the subcloud update with network reconfiguration is blocked by the ongoing strategy, verify the network reconfiguration is not blocked after the strategy applied. 3. Passed - create a system-config-update strategy by updating the addresspool on the subcloud, verify the subcloud update with network reconfiguration is blocked when applying this strategy, verify this operation is not blocked after the strategy applied. Story: 2010722 Task: 49414 Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com> Change-Id: I2c3b824ebbd6766996f3422c681f16d03b6063fa		2024-02-08 16:48:12 -05:00
..
v1	Check vim strategy before updating network	2024-02-08 16:48:12 -05:00
README.rst	Move content to subdir to support relocated packaging	2019-11-04 13:57:02 -05:00
__init__.py	Move content to subdir to support relocated packaging	2019-11-04 13:57:02 -05:00
restcomm.py	Fix subcloud-group endpoint routing conflict	2022-12-06 13:21:14 +00:00
root.py	Update tox pylint/pep8 for dcmanager	2024-01-18 21:51:25 +00:00

README.rst

controllers

API request processing

root.py:: API root request
subclouds.py: Controller for all the subcloud related requests
restcomm.py:: common functionality used in API