2fb32cf88d
This change allows the management and admin network reconfig at same time in an AIO-DX subcloud. Currently, it is necessary to lock and unlock the controller in order to reconfigure the management network from AIO-SX. If the customer changes the management network fist, the new mgmt network will be in the database but the changes will jsut be applied during the unlock / reboot of the system. But the admin network changes are applied in runtime, if the admin network is changed after the management network reconfig, the admin will apply the changes on the system and some of them will apply the new mgmt network values before the system is updated with the new mgmt ip range, it will cause a puppet error and the system will not be correctly configured. Tests done: IPv4 AIO-SX subcloud mgmt network reconfig IPv4 AIO-SX subcloud admin network reconfig IPv4 AIO-SX subcloud admin and mgmt network reconfig IPv4 AIO-SX subcloud mgmt and admin network reconfig Story: 2010722 Task: 49724 Change-Id: I113eab2618f34b305cb7c4ee9bb129597f3898bb Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com> |
||
---|---|---|
api-ref/source | ||
config-gate | ||
controllerconfig | ||
devstack | ||
doc | ||
releasenotes | ||
storageconfig | ||
sysinv | ||
tmp/patch-scripts/EXAMPLE_SYSINV/scripts | ||
tools/docker/images | ||
tsconfig | ||
workerconfig | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
centos_build_layer.cfg | ||
centos_dev_wheels.inc | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_pkg_dirs_containers | ||
centos_stable_wheels.inc | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
debian_stable_wheels.inc | ||
test-requirements.txt | ||
tox.ini |
README.rst
config
The starlingx/config repository handles the StarlingX configuration management services.
Its key component is the System Inventory Service (Sysinv), which provides the system command-line interface (CLI)1.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.