2274dfb942
Previous release contains attribute ’encrypted-fs’ in the ’platform config’ service parameter, which is used to enable and disable the luks file system. Upgrade activity need to delete this unused attribute from the database. This change adds a new migration script to delete 'encrypted-fs' attribute. The script will run only when from release is 22.12 and during upgrade-activate. Test Plan: PASS: build-pkgs -c controllerconfig PASS: build-image PASS: AIO-SX upgrade to 24.xx from previous release with luks file system disabled. After upgrade activate encrypted-fs attribute should be deleted from DB. PASS: AIO-SX upgrade to 24.xx from previous release with luks file system enabled. After upgrade activate encrypted-fs attribute should be deleted from DB. PASS: AIO-DX upgrade to 24.xx from previous release with luks file system disabled. After upgrading controller-1(upgraded/ active controller), script execution should delete encrypted-fs attribute from the DB. Story: 2010873 Task: 49663 Change-Id: I96ed9bf572f20e64419763eb285f4997c37ddf9b Signed-off-by: Jagatguru Prasad Mishra <jagatguruprasad.mishra@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.