d0c8907104
Because the management network and its parameters are embedded in many parts of the system, having a separate admin network makes it much easier to change the parameters of this network (subnet, gateway, etc) after a subcloud has been provisioned. The admin network will take precedence over the existing management network for communication between the subcloud and system controller if it is defined. The management network will still exist on the subcloud, but will be a private network. This commit contains logic to choose the most appropriate keystone auth url and admin endpoint required for subcloud administration depending on whether the admin network is present or not. Note: Corresponding puppet review: https://review.opendev.org/c/starlingx/stx-puppet/+/865288 Test Plan: - Bootstrap and install DC subcloud with admin network defined. PASS: Ensure the openstack admin endpoints on both the subcloud and system controller for the affected services use the admin subnet of the subcloud PASS: Ensure the subcloud can become online and in-sync using the admin network. Regression: - AIO-SX: On a non-DC system, ensure the openstack endpoints for the various services are not impacted by the change. - Bootstrap and install DC subcloud with no admin network defined. PASS: Ensure the openstack admin endpoints on both the subcloud and system controller for the affected services use the management subnet of the subcloud (no impact) PASS: Ensure the subcloud can become online and in-sync with the management network (no impact). Depends-On: https://review.opendev.org/c/starlingx/config/+/863033 Story: 2010319 Task: 46910 Signed-off-by: Steven Webster <steven.webster@windriver.com> Change-Id: Icf4c7c97ed69c74e6827c63614cb44abca28e38a |
||
|---|---|---|
| .. | ||
| cert-alarm | ||
| cert-mon | ||
| cgts-client | ||
| sysinv | ||
| sysinv-agent | ||