Airship utility CLI access
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Dodda, Prateek Dodda 9f9d8d39be upgarding Openstack Utility client version to stein. 3 hafta önce
charts upgarding Openstack Utility client version to stein. 3 hafta önce
docs Editorial changes to documentation files 2 ay önce
images upgarding Openstack Utility client version to stein. 3 hafta önce
jmphost Enforce the use of the correct kubectl client version 1 ay önce
tools Fix postgresql utility 1 ay önce
zuul.d Postgresql UC Python and Ubuntu upgrade. 2 ay önce
.gitignore Chart/Dockerfile for Ceph Utility Container 1 yıl önce
.gitreview Add .gitreview 6 ay önce
LICENSE Initial commit 1 yıl önce
Makefile Pass extra build args to Docker image builds 3 ay önce Editorial changes to files 2 ay önce

Utility Containers

Utility containers give Operations staff an interface to an Airship environment that enables them to perform routine operations and troubleshooting activities. Utility containers support Airship environments without exposing secrets and credentials while at the same time restricting access to the actual containers.


Deploy OSH-AIO.

System Requirements

The recommended minimum system requirements for a full deployment are:

  • 16 GB RAM
  • 8 Cores
  • 48 GB HDD


  1. Add the below to /etc/sudoers.

    root    ALL=(ALL) NOPASSWD: ALL
    ubuntu  ALL=(ALL) NOPASSWD: ALL
  2. Install the latest versions of Git, CA Certs, and Make if necessary.

    sudo apt-get update
    sudo apt-get dist-upgrade -y
    sudo apt-get install --no-install-recommends -y \
        ca-certificates \
        git \
        make \
        jq \
        nmap \
        curl \
        uuid-runtime \
  3. Clone the OpenStack-Helm repositories.

    git clone git clone

  4. Configure proxies.

In order to deploy OpenStack-Helm behind corporate proxy servers, add the following entries to openstack-helm-infra/tools/gate/devel/local-vars.yaml.

        http: http://username:password@host:port
        https: https://username:password@host:port

Add the address of the Kubernetes API,, and .svc.cluster.local to your no_proxy and NO_PROXY environment variables.

    export no_proxy=${no_proxy},,.svc.cluster.local
    export NO_PROXY=${NO_PROXY},,.svc.cluster.local
  1. Deploy Kubernetes and Helm.

    cd openstack-helm

Edit /etc/resolv.conf and remove the DNS nameserver entry (nameserver The Python setup client fails if this nameserver entry is present.

  1. Setup clients on the host, and assemble the charts.


Re-add DNS nameservers back to /etc/resolv.conf so that the Keystone URLs DNS will resolve.

  1. Deploy the ingress controller.

  2. Deploy Ceph.

  3. Activate the namespace to be able to use Ceph.

  4. Deploy Keystone.

  5. Deploy Heat.

  6. Deploy Horizon.

  7. Deploy Glance.

  8. Deploy Cinder.

  9. Deploy LibVirt.

  10. Deploy the compute kit (Nova and Neutron).

  11. To run further commands from the CLI manually, execute the following to set up authentication credentials.

    export OS_CLOUD=openstack_helm
  12. Clone the Porthole repository to the openstack-helm project.

    git clone

To deploy utility pods

  1. Add and make the chart:

    cd porthole
    helm repo add <chartname> http://localhost:8879/charts
    make all
  2. Deploy Ceph-utility.

  3. Deploy Compute-utility.

  4. Deploy Etcdctl-utility.

  5. Deploy Mysqlclient-utility.

  6. Deploy Openstack-utility.



The PostgreSQL utility container is deployed as a part of Airship-in-a-Bottle (AIAB). To deploy and test postgresql-utility, see the PostgreSQL README.