Configure Airship Seaworthy site specific parameters
when running tests. This would allow to make required
changes to default values in ./tools/openstack script
which are currently Seaworthy specific.
Currently, Airskiff deploys a custom manifest defined in
tools/deployment/airskiff/manifests/airship.yaml to boostrap Airship
components. This exempts Airskiff from the daily version uplift process
and causes a divergence from the global UCP charts. This commit updates
the Airskiff bootstrap process to use the existing UCP charts at the
Since  updated the Airskiff CI jobs to clone dependent projects, the
relative OSH-infra path for the airskiff job no longer exists. This
change removes it so that the CI can use the cloned path as specified in
the airskiff deployment scripts.
On April 19, OpenStack completed the migration from openstack.org to
opendev.org . During this migration, Airship projects moved from the
"openstack" namespace to the "airship" namespace. This commit makes
preliminary updates to gate and developer scripts to account for the
migration and fix broken integration gates.
This commit adds a site linting gate for the new airsloop site.
Additionally, this change aims to standardize the names of all gates and
creates a parent job for site linting gates.
This commit replaces the kubeadm Kubernetes deployment script with the
new OpenStack-Helm infra minikube deployment script.
Currently, Airskiff deployment scripts build images of the Airship
components locally so that local changes can be deployed with ease;
however, pulling images with the latest tag has the same effect because
locally built images take precedence over pulling images from the
internet. Therefore, a developer can still build the images locally and
deploy them using the Airskiff deployment scripts.
Currently, the Airskiff gate does not recognize failures because the
gate script only verifies that an action lifecycle enters a COMPLETE
state; however, a lifecycle in COMPLETE status is not always an
indication of a successful deployment. This commit updates the
wait_for_shipyard script to check the status of each action step and
results in exit_code 1 if any steps failed.
This commit moves the installation and enablement of AppArmor to the
package installation script. Previously, it was in an additional script
where its usage was undocumented, causing confusing deployment errors.
This change introduces a Zuul gate that deploys a limited number of
components from the Airskiff site (i.e. memcached) using the Airskiff
site documents. The purpose of the job is to gate all patches against
an integration of several Airship components (i.e. Armada, Deckhand,
Pegleg, and Shipyard), and exercise their capabilities by deploying
software. This change also creates a framework to allow for future,
robust gates that include other projects (e.g. OpenStack-Helm).
With the integration of the airskiff site in Treasuremap, there is a
need for Zuul site linting gates to ensure that all sites are still
syntactically valid when changes are made to global documents. This
change introduces linting gates for both treasuremap sites, airskiff and
- use redfish library to manage bare-metal power state
- fixup pipeline triggers and defaults
- add log rotation for old builds
- fix minor re-try issues
- add job build/display name
- use generic ssh lib