airshipctl is using upstream ensure-docker role instead of
docker-install. correcting this in treasuremap
Signed-off-by: Sreejith Punnapuzha <Sreejith.Punnapuzha@outlook.com>
Change-Id: Ideea1d9f641d6abad1d9f7c37698f7c09f778fce
* Align treasuremap virtual-airship-core site to recent changes of
airshipctl
* This PS takes care of only the "airship-core" type and all other
sites will fail validate docs untill the secrets are aligned.
* So the validate_docs is invoked with parameter "virtual-airship-core"
to run document validation just for virtual-airship-core
reference airshipctl commit: e2c56108eef38dd83df52fcfd1fa6844e5376a56
Change-Id: I2e6149951beca570a3cadeecbc05366325c80286
* updated the syntax for enable plugins with recent uplift
of kustomize version
* Had to uplift the airshipctl version as well
Change-Id: I0c637603013adc2594c39cbea7cc07f3937cf3ee
* After dex is added, it is observed that almost all gate runner
builds are failing.
* So trying to adjust the disk size to check if it resolves the
issue.
Change-Id: Ie33bc32e49e00d225599c9de5ff7917fb527b8ef
Uplift airshipctl to version with new phases.
Add phases from zuul job in deploy-airship-core-gating.
Relates-To: #166
Change-Id: I98b605d16940fab2a728e4646e52c7d1ad992c2d
This change restructures the deployment script directory to support
type-specific deployment scripts. As sub-clusters are added, those
scripts will only be relevant to the multi-tenant type. The distinction
between which scripts should be used for each type will prevent
unexpected deployment errors.
Co-authored-by: Drew Walters <andrew.walters@att.com>
Change-Id: Ic14d4536bc9e593ab81c94b5c1dcec063a93ed18
* This playbook is used in thrid party gates and
it is failing at verify hwcc stage which is removed recently.
Change-Id: I7266a81d87886f7ca4d04fe1f9e360f948dd54a9
* BOT will be configured to listen for treasuremap repo changes and
add/update comments and issues status ( close ) as applicable.
Change-Id: I2e2070461e60fc75dd2066432c4f5cd48023c5e3
These scripts allow one to stand up a treasuremap test-site
note: Removing the phase lma-infra-target from script 31, since
it causes a wait to fail later on in the pipeline
Change-Id: I43374a874c110ab32d6158975c50fd4b89693479
* Treasuremap is dependant on airshipctl repo. So pinning the last
good tested version of airshipctl in treasuremap
Change-Id: I6923da9871b946134fbdc285c38bcb8f967aa804
Relates-To: #100
The Ironic Deployment init container was recently updated in airshipctl
[0], and the update requires more disk space on nodes deployed by the
baremetal operator. This change updates the target and worker node
specifications to match the new values in airshipctl.
[0] https://review.opendev.org/c/airship/airshipctl/+/765376
Change-Id: Ifa75fd49d97502bb1b638f9ee58cd30af7d27482
To facilitate catalogue-driven generation of BareMetalHost resources,
airship splits the work into two pieces:
1. <phasename>/hostgenerator/ is responsible for substituting
catalogue variables into a host generation template
2. <phasename>/ invokes its hostgenerator/ as a Kustomize generator:,
leveraging the results of 1. to generate BMH.
However, a weird side-effect of this setup is that the catalogues used
in step 1. above are still hanging around in step 2., and Kustomize
tries to interpret them as generator: plugin configs,
resulting in a rendering error.
Previously, we'd worked around this by having a pass-through plugin
implementation, which performs a no-op generation for the spent catalogues.
However, with the change below, airshipctl migrated to container-based KRM
functions for its kustomize plugins, and also adopted a
strategic-patch-delete mechanism to clean up the spent catalogues,
so that they aren't still hanging around by the time the generation occurs.
https://review.opendev.org/#/c/759279/
Change-Id: I50a9bd2fcc37b70f50b8ded88f152775aff928bc
Closes: #48
This change introduces airshipctl's document pull functionality to the
Treasuremap gate runner job. This enables Treasuremap maintainers to pin
to a version of airshipctl deployment scripts and manifests that are
known to be compatible with Treasuremap's v2 branch.
In order to ensure that the deployment scripts and manifests come from
the same version of airshipctl, this change introduces a playbook that
checks out the referenced version of airhsipctl after it is cloned by
Zuul. It also checks out the known version a second time in the
deployment scripts for operators invoking the scripts in a non-Zuul
environment.
To update the pinned version of Treasuremap using Zuul, change the Zuul
variable airshipctl_ref. To update the pinned version in a non-Zuul
environment, use the environment variable AIRSHIPCTL_REF.
Change-Id: I300f545efcdd024b689a96ee99e502de7fdd1b83
Signed-off-by: Drew Walters <andrew.walters@att.com>
* missed to update the playbook to use token in
previous commit (https://review.opendev.org/#/c/759453/)
Change-Id: Ibc1a8ad7787e39b0879a1703f0b0518417daeff5
Closes: #44
A recent refactor of the Kustomize config command [0] changed the config
subcommand to cfg. Since airshipctl has introduced a version of
Kustomize with the new subcommand, cfg, Treasuremap jobs are failing
because they still use Kustomize config.
This change updates kustomize config commands to kustomize cfg.
[0] 701c217791 (diff-73e268a15f17741962365907345f2ea7b20d8e2d19ec57efacb6067281b19b68)
Change-Id: I9eaac604c9eafdb6791e49716ea109906ddfe9f6
Jobs in airshipctl have recently started timing out due to drift between
the roles in airshipctl and playbooks in treasuremap. This change
updates playbooks that have recently changed in airshipctl to resolve
the job timeouts [0].
[0] https://review.opendev.org/747027
Change-Id: I4a39471dcd27eb323aa2c6aad7b4df570ef809d6
This adds airshipctl as a testing, and calls its deployment
scripts to launch a VM-based test. This will be used to validate
treasuremap deployment manifests.
Change-Id: If4fa60f896211d2f6b63271b58b96541c399694c
Zuul