- Adds PV for local caching. This allows us to also use PV
in other clusters like AKS.
- Moves artifacts and caching files into /opt/aiap-files/artifacts
and /opt/aiap-files/caching so we only have one PV
Relates-To: #645
Change-Id: I84172778df66bee8a833b13d5b740a6cf45220c2
This adds the `status-checker` container, which aggregates the statuses
of the task containers. This is useful for quickly checking whether AIAP
is in a failed or successful state, allowing for early exit during
gating or testing. This also prevents the containers from stopping for
any reason, allowing for easy debugging.
Change-Id: I1571d006fb3c856e4d2bedee0befdccae6082a66
This change aims to clarify the differentiation between deploying AIAP
to Azure and deploying to a native Linux environment.
Change-Id: I3e014589dc02cce1bac5ff32a69c29ef6fc5b9f3
This updates the documentation for working with AIAP. This includes
changes to the README as well as adding all configurable values to the
examples (having their default values).
Change-Id: I7c1b92d6a324b0fbd07f27ec0607fc62765c4fa2
This adds a script that a developer can use to run airship in a pod
in a dynamically created AKS cluster. By default a resource group is
created and then cleaned up following the test.
Further work needs to be done to surface some indication of a failed
test out of the pod, and watch for that condition in this script.
Change-Id: I29f462b9becd6d1de0a9e0e1d7877c6019cbd6ee
Introduces Airship in pod. This includes:
* A base image which sets up common requirements
* An image for the libvirt service
* An image for building a specified instance of airshipctl
* An image for initializing the various libvirt infrastructure required
for a deployment
* An image which runs the deployment scripts
Closes: #313
Change-Id: Ib1114350190b0fe0c0761ff67b38b3eca783161a