Fix disk size issue for latest multinode-gate
PODs are being evicted due reduced disk size (30 from 64G). The issue is constantly appearing around MAAS image deployment. Change-Id: If8a0717a7f57d77d0c91a6798c774dc9cc06ecb6
|23 hours ago|
|deployment_files||6 days ago|
|doc||3 months ago|
|manifests||2 months ago|
|tools||23 hours ago|
|.gitignore||7 months ago|
|.gitreview||3 months ago|
|.zuul.yaml||3 days ago|
|LICENSE||2 years ago|
|Makefile||1 year ago|
|README.md||3 months ago|
|Vagrantfile||3 months ago|
|tox.ini||1 year ago|
Airship is a broad integration of several components enabling an automated, resilient Kubernetes-based infrastructure for hosting Helm-deployed containerized workloads.
Airship is the name for the project formerly known as UCP or the Undercloud Platform.
Find more documentation for Airship in a Bottle on Read the Docs.
To get started, run the following in a fresh Ubuntu 16.04 VM (minimum 4vCPU/20GB RAM/32GB disk). This will deploy Airship and Openstack Helm (OSH):
sudo -i mkdir -p /root/deploy && cd "$_" git clone https://opendev.org/airship/airship-in-a-bottle cd /root/deploy/airship-in-a-bottle/manifests/dev_single_node ./airship-in-a-bottle.sh
Or, alternatively, if you have Vagrant installed, just run the following (only libvirt/kvm hypervisor is tested, but vagrant box supports VMware Desktop/Workstation/Fusion, Parallels, and Hyper-V):
curl -O https://opendev.org/airship/airship-in-a-bottle/raw/branch/master/Vagrantfile vagrant up
Platform orchestrator for initial deployment, platform updates, and server redeployments
The bootstrapper for the Kubernetes control plane - both on an initial genesis node to get a working Kubernetes cluster and for adding additional nodes to the existing Kubernetes cluster.
Provisioner for Helm charts. Provides the capability to override chart values.yaml items.
The orchestrator for physical asset provisioning (e.g. server deployment).
YAML design data manager.