...
Airship is a declarative way of automating the deployment of a site. Therefore, all the deployment details are defined in the configuration files and manifests.
The manifests are divided into three layers: global, type, and site. They are hierarchical and meant as overrides from one layer to another. This means that global is baseline for all sites, type is a subset of common overrides for a number of sites with common configuration patterns (such as similar hardware, specific feature settings, and so on), and finally the site is the last layer of site-specific overrides and configuration (such as specific IP addresses, hostnames, and so on). See Deckhand documentation for more details on layering.
...
- Airship Site Authoring and Deployment Guide
- Code comments in the manifests themselves, for example common-addresses.yaml
- As well as each individual chart of components, for example, Deckhand chart values.yaml
Global
Global manifests contain base configuration including the , defined in Airship Treasuremap, contain base configurations common to all sites. The versions of all Helm charts and Docker images, for example, which are specified in versions.yaml.
...
data:
site_type: cntt
repositories:
global:
revision: v1.47
url: https://opendev.org/airship/treasuremap.git
...
You will need to export environment variables that correspond to the new site (keystone URL, node IPs, and so on). See the beginning of the deploy script for details on the required variables.
...
https://build.opnfv.org/ci/view/airship/
OpenStack
...
The treasuremap repository contains a wrapper script for running OpenStack clients tools/openstack. The wrapper uses heat image that already has openstack client installed.
Clone latest treasuremap code
$ git clone https://github.com/airshipit/treasuremap.git
Setup the needed environment variables, and execute the script as openstack CLI
$ export OSH_KEYSTONE_URL='http://identity-airship.intel-pod17.opnfv.org/v3'
$ export OS_REGION_NAME=intel-pod17
$ treasuremap/tools/openstack image list