...
| Parameter | Sub-Category | Description | Example Value |
|---|---|---|---|
| bonding | |||
| mode | |||
| hash | |||
| peer_rate | |||
| mon_rate | |||
| up_delay | |||
| down_delay | |||
| mtu | |||
| linkspeed | |||
| trunking | |||
| mode | |||
| default_network | |||
| allowed_networks* | |||
| labels |
Software
Recently openstack services are deployed as containers, and to manage these containers various container management platforms such as Kubernetes are used.
Airship too uses the approach of openstack on Kubernetes (OOK). For deployment/configuration of services/applications/pods (in this case Openstack, monitoring, etc.) on Kubernetes, users have two options (a) Kolla-Kubernetes (b) Openstack Helm. Both the options uses helm for packaging the Kubernetes definitions for each service. However, openstack helm uses helm charts, whereas kolla-kubernetes uses uses ansible for deployment/orchestration. Airship uses the former option - helm charts. Accordingly, under software, user configurations will fall under two important categories - Charts and Configurations.
Charts
Kubernetes
Undercloud Platform
Ceph
Openstack helm Infra
Open Stack Helm
Tenant-Ceph
Config
Under this configuration, user can only set the region name for openstack helm.
| Parameter | sub-category | Description | Example-Value |
|---|---|---|---|
| osh | |||
| region_name | The region name to use. Typically Site name is provided. | intel-pod10 |
PKI-Catalog
| Parameter | sub-category-1 | sub-category-2 | Description | Example Value |
| certificate_authorities | ||||
| description | ||||
| certificates | ||||
| document_name | ||||
| description | ||||
| common_name | ||||
| hosts | ||||
| groups | ||||
| keypairs | ||||
| name | ||||
| description |
Secrets
Publickeys of the Users.
...