ef5ec3e4c0
Send a different extra variable to the restore playbook so it only
attempts to mount the seed ISO when restoring a pre-installed subcloud.
This fixes an issue where the seed ISO would also be mounted for
auto-restore with install and factory restore, where the subcloud is
reinstalled by the install playbook.
Test Plan:
01. PASS – Run standard subcloud restore. Verify it works as expected
without calling the RVMC script to mount the seed ISO.
02. PASS – Run subcloud auto-restore on a pre-installed subcloud
(without --with-install). Verify that the seed ISO is mounted by
the RVMC script.
03. PASS – Run subcloud auto-restore with --with-install. Verify that
the subcloud is remote installed by the install playbook and that
the restore playbook does not mount the seed ISO.
04. PASS – Run subcloud factory restore. Verify that the subcloud is
remote installed by the install playbook and that the restore
playbook does not mount the seed ISO.
Depends-On: https://review.opendev.org/c/starlingx/ansible-playbooks/+/964504
Closes-Bug: 2129547
Change-Id: Ief1b060838dccaeac90eae09e82811e6e0f88ac1
Signed-off-by: Gustavo Herzmann <gustavo.herzmann@windriver.com>
Service
- DC Manager Service has responsibility for:
-
Main subcloud state machine as well as all operations on subclouds including creation, deletion and update.
- service.py:
-
run DC Manager service in multi-worker mode, and establish RPC server
- subcloud_manager.py:
-
Manages all subcloud related activities such as creation, deletion, availability status, management state
- audit_manager.py:
-
A Periodic audit to contact each subcloud and ensure that at least one of each service group is up and active, which is a pre-requisite for declaring a subcloud as online.
- scheduler.py:
-
Thread group manager, also responsible for periodic timer tasks - ie. audit.