The script must wait for Processing actions if they exist,
it also needs to fail if it failed to retrieve a list of
actions from Shipyard.
Change-Id: I806a2c5c2e05fa768c6c3434c5c6d9bd102c6c92
Wait-for-shipyard sctipt was just checking actions that are
in "Processing" state, but if some actions are "Complete",
it comes to infinity loop.
Change-Id: I9c007a60227159af561f5ceacf5fc3dd469fce0c
Refactor Airship in a bottle scripts to use `airship`
command line tool instead of relying on hardcoded values
with the versions of images and repositories.
The patch includes additional fixes:
1. Allow to specify credentials for wait-for-shipyard
script without assuming some specific set of creds.
2. Fix a path to common-addresses file.
Change-Id: I59d0a0e1758a6575a84abb22045e08437aa51466
Using Airship CLI script allows us to use pegleg
image configured in versions.yaml, which will be
updated during regular uplift procedure.
Change-Id: I68a6e5477fc72fb52dfc893b6eef69dd64320ded
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
global layer.
Change-Id: I68dc405fda3cb1dbf5865104b657bdd75812e9bc
On April 19, OpenStack completed the migration from openstack.org to
opendev.org [0]. 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.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005011.html
Change-Id: I88c4d96a756c59dd68ce8c3b801eba9ca8a6f8db
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.
Change-Id: If5117c4638652b8d5b91fe73ede0f5e19a1e2cc1
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).
Story: 2004351
Change-Id: I953e0c809d7fe112fd84458a4c6eec6ecadaf010
Dmitry Ukov