...
The Airship installer is delivered in a form of site and type manifests, as well as deployment script. This helps automating and adjusting the Airship to the OPNFV reference lab Intel POD17.
Manifests
Airship is a declarative way of automating the deployment of a site and therefor all the deployment details are defined in a the configuration files/manifests.
All the manifests are All site configuration is divided in 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 patters (e.g. similar hardware, or need of enabled features), and finally the site is the last layer of site specific overrides and configuration (such as specific IP addresses, hostnames, etc). See Deckhand documentation for more details on layering.
The global and type manifests can be used as is, unless any major differences from a reference deployment are required. In the later case, this may introduce a new type, or even contributions to the global manifests.
The site manifests are specific for each site and are required to be customized for each new deployment. The specific documentation how to customize these documents are described at
- Airship Site Authoring and Deployment Guide
- Code comments in the manifests themselves, for example common-addresses.yaml
- As well as each individual charts of components, for exmaple Deckhand chart values.yaml
Global
Global manifests contain base configuration including version to all the Helm charts and Docker images specified in versions.yaml.
...