Deploy Airship and OpenStack¶

To deploy SUSE OpenStack cloud using Airship, run:
./run.sh deploy
This script takes several minutes to finish.
Track Deployment Progress¶
Using kubectl¶
To check the deployment progress of the Airship UCP services:
kubectl get po -n ucp
To check the deployment progress of the Openstack services:
kubectl get po -n openstack
OpenStack Services¶
SUSE Containerized OpenStack deploys OpenStack Cinder, Glance, Heat, Horizon, Keystone, Neutron, Nova.
SUSE Containerized OpenStack deployment will automatically add the following host rules to the /etc/hosts file on the deployer:
10.10.10.10 identity.openstack.svc.cluster.local
10.10.10.10 image.openstack.svc.cluster.local
10.10.10.10 volume.openstack.svc.cluster.local
10.10.10.10 compute.openstack.svc.cluster.local
10.10.10.10 network.openstack.svc.cluster.local
10.10.10.10 dashboard.openstack.svc.cluster.local
10.10.10.10 nova-novncproxy.openstack.svc.cluster.local
10.10.10.10 orchestration.openstack.svc.cluster.local
You can access OpenStack service public endpoints using the host names listed in the /etc/hosts directory. For example, access OpenStack Horizon (dashboard) at http://dashboard.openstack.svc.cluster.local.
You can access Horizon and other OpenStack service APIs from a different system by adding the entries above to DNS or /etc/hosts on that system.
Using Kubernetes Dashboard¶
Deploy the Kubernetes Dashboard UI with the instructions at https://github.com/kubernetes/dashboard.
Using Shipyard CLI¶
Airship Shipyard CLI allows you to retrieve the progress and status of deployment actions.
To use the CLI, you must set up two environment variables:
export OS_CLOUD=airship
export OS_PASSWORD=PEdLb_RgyDXJUJ7VgeRy
The OS_PASSWORD is the Shipyard service password in the UCP keystone. It can be found in the secrets/ucp_shipyard_keystone_password file in your workspace on the deployer node.
To check the workflow status of the deployment action, run:
/opt/airship-shipyard/tools/shipyard.sh describe action/01D821AZ27H6NCSPV01RXQPDST
The last argument is the action key in Shipyard. Its value is stored in the soc-keys.yaml file in your workspace, for example,
Site:
name: soc
action_key: action/01D963GH0B621TBQHZAH8MW9JE
Here is a sample output of the Shipyard describe command:
Name: update_software
Action: action/01D963GH0B621TBQHZAH8MW9JE
Lifecycle: Complete
Parameters: {}
Datetime: 2019-04-23 22:01:57.003504+00:00
Dag Status: success
Context Marker: b2157815-e993-4333-b881-4937084441dd
User: shipyard
Steps Index State Footnotes
step/01D963GH0B621TBQHZAH8MW9JE/action_xcom 1 success
step/01D963GH0B621TBQHZAH8MW9JE/dag_concurrency_check 2 success
step/01D963GH0B621TBQHZAH8MW9JE/deployment_configuration 3 success
step/01D963GH0B621TBQHZAH8MW9JE/validate_site_design 4 success
step/01D963GH0B621TBQHZAH8MW9JE/armada_build 5 success
step/01D963GH0B621TBQHZAH8MW9JE/decide_airflow_upgrade 6 success
step/01D963GH0B621TBQHZAH8MW9JE/armada_get_status 7 success
step/01D963GH0B621TBQHZAH8MW9JE/armada_post_apply 8 success
step/01D963GH0B621TBQHZAH8MW9JE/upgrade_airflow 9 skipped
step/01D963GH0B621TBQHZAH8MW9JE/skip_upgrade_airflow 10 success
step/01D963GH0B621TBQHZAH8MW9JE/deckhand_validate_site_design 11 success
step/01D963GH0B621TBQHZAH8MW9JE/armada_validate_site_design 12 success
step/01D963GH0B621TBQHZAH8MW9JE/armada_get_releases 13 success
step/01D963GH0B621TBQHZAH8MW9JE/create_action_tag 14 success
Commands User Datetime
invoke shipyard 2019-04-23 22:01:57.752593+00:00
Validations: None
Action Notes:
> action metadata:01D963GH0B621TBQHZAH8MW9JE(2019-04-23 22:01:57.736165+00:00): Configdoc revision 1
Logs¶
To check Airship logs, run the Shipyard logs CLI command, for example:
/opt/airship-shipyard/tools/shipyard.sh logs step/01D963GH0B621TBQHZAH8MW9JE/armada_build
To check logs from a running container, use the kubectl logs command. For example, to retrieve the test output from the Keystone Rally test, run:
kubectl logs airship-keystone-test -n openstack
Run Developer Mode¶
If you want to patch upstream Helm charts or build your own container images, you need to set the following environment variables before deployment:
export SOCOK8S_DEVELOPER_MODE='True'
export AIRSHIP_BUILD_LOCAL_IMAGES='true'
./run.sh deploy
Alternatively, you can add the following two lines to the env/extravars file:
SOCOK8S_DEVELOPER_MODE: true
AIRSHIP_BUILD_LOCAL_IMAGES: true