Uplifts the Promenade image as well as other modifications required
because of recent changes to Promenade, namely:
* HostSystem schema changes for new image and new key under packages
* New chart configuration to utilize new source for hyperkube
* Refactoring names to make more sense and added new monitoring_image
By specifying exact ubuntu release as a tag for `updater.py` script, it prevents
downloading ubuntu with a higher release, for example, ubuntu bionic.
Changing bionic to xenial for armada chart.
Lint site manifests for Airship in a Bottle when publishing
and merging patches.
The patch adds a pre-run step that generates a new set of
certificates that is required for the validation.
Make aiab scripts to use relative paths, this fixes a problem
when the user runs the script from a different from `/root/deploy`
directory, or runs it from outside of `tools/deployment/aiab`.
`dev_single_node` directory is inherited from an old
aiab repo and does not have much meaning in the current
directories layout, move all the scripts to aiab directory.
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.
This adds new variables to the 005-clone-dependencies script in
Airskiff to be able to turn off cloning for the Airship repositories.
The intended use case of this is so the Airskiff gate can avoid cloning
the repository it is currently testing.
The UID:GID under which commands from within containers are run does not
necessarily match UID:GID set in container. This patch enforces run of
containers with process UID:GID matching current user's UID:GID.
Creation of directories is documented, so that user's wouldn't get
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.
Note: all scripts in tools/deployment/aiab directory have been
moved into this repository as is (except a few changes to make
them work), they require a heavy refactoring that will be done
in separate patch-sets.
* Add a virtual single node manifests that are based on a sloop type.
* Use NFS provisioner instead of Ceph.
* Update tools/openstack to be non-seaworthy specific, use a default
region name and auth url.
* Make type/sloop/config/common-software-config.yaml to be site specific,
to allow to configure custom region_name.
* Remove max-pods-per-cpu parameter for kubelet, treasuremap needs
to support a diverse set of environments, without constraints
on the number of available cores. Max pods configuration parameter
is still present and helps to mitigate problems when kubernetes
unexpectedly starts a large number of pods.
Currently the manifest targeted by armada in the
030-armada-bootstrap.sh script is hard-coded to "ucp-bootstrap". This
patch set updates the 030 script to make drive the target manifest
off of a new environment variable "TARGET_MANIFEST". By default
"ucp-bootstrap" is still used, and existing functionality should not
The motivation behind this, is it allows us to use the armada
bootstrap script to do more than just bootstrap the ucp components,
which may prove useful in zuul gate jobs that use treasuremap.
One of the first things the tools/airship utility script does is run
dpkg and apt. Because these commands were not being ran with sudo,
the airship script could only be ran as the root user. Adding sudo
so any user can run the tools/airship script.
When running the 020-setup-client.sh script on a new ubuntu 16.04 VM,
the gcc, python-dev, and python-setuptools apt packages are required
for pip to install the cmd2 package.
Previously, airskiff's 000-install-packages script added the docker
repo, then deleted stale docker packages, then updated the apt database.
This change moves the apt update before the delete, so that apt-get
knows about the packages it's being asked to delete. Without this in
place it'll fail on a fresh VM that doesn't know about the docker repo.
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.