9066690daf
Fix an issue with qcow-bundle naming that was causing docker registry info to be dropped. Dropped redundant "qcow" prefix for qcow-bundle subdirectories. Use qcow-bundle subdirectory as image name. Rename "config" directory as "manifests" per offline review request. Change-Id: Ie110923b3c8d5a825dd7a199658722b853018d97
Directory structure:
|-- manifests
|-- iso
+-- network_data.json
+-- user_data
|-- qcow-bundle
|-- control-plane
+-- osconfig-vars.yaml
+-- qcow-vars.yaml
|-- data-plane
+-- osconfig-vars.yaml
+-- qcow-vars.yaml
The generate_iso and package_qcow make target can be used to build ISO and
QCOW artifacts respectively, after the shared image-builder container is
built (built with the build target).
The ISO always builds out of the manifests/iso directory, because this is only
used for local testing. It is not an artifact that is promoted or published.
QCOWs are grouped into publishable "bundles", i.e. a container image where all
QCOWs needed for a given deployment are stored. A bundle will be built for each
manifests/qcow-bundle* directory. Each manifests/qcow-bundle* directory contains
one subdirectory per QCOW that is part of that bundle, where overrides for
those images can be placed.
The following items are expected in the iso directory:
user_data- YAML file containing cloud-init user-datanetwork_data.json- JSON file containing cloud-init network data
QCOWs expect the following files to be present in their directory:
osconfig-vars.yaml- YAML file containingosconfigplaybook overridesqcow-vars.yaml- YAML file containingqcowplayboook overrides