Table of Contents |
---|
...
Parameter | Description | Example-Value |
---|---|---|
vendor | Vendor of the server chassis | Intel |
generation | Generation of the chassis model | '4' |
hw_version | Version of the chassis model within its generation | '3' |
bios_version | The certified version of the chassis BIOS | 'SE5C .... |
boot_mode | Mode of the default boot of hardware - bios, uefi | bios |
bootstrap_protocol | Protocol of boot of the hardware - pxe, usb, hdd | 'pxe |
pxe_interface | Which interface to use for network booting within the OOB manager, not OS device | 0 |
Device-Aliases:
NICs:
User can categorize the NICs in the hardware as control-plane nics or dataplane nics. In each category he can have one or more NICs. For example, he can define ctrl_nic1, ctrl_nic2, ctrl_nic3, and data_nic1, data_nic2, data_nic3, etc. It is better to use names that are self-explanatory - for example, if you have a separate NIC for PXE, name it as pxe_nic. This categorization will be referred in the host-profiles. For every NIC defined, the below information can be configured.
...
Parameter | Description | Example Value |
---|---|---|
address | The PCI address of the NIC | 0000:04:00.0 |
dev_type | Description of the NIC | 'I350 Gigabit Network Connection' |
bus_type | The bus supported | 'pci' |
...
Parameter | Description | Example Value |
---|---|---|
address | The bus address of the Disk | 0:2.0.0 |
dev_type | Description of the disk. | 'INTEL SSDSC2BB48' |
bus_type | The bus supported | 'scsi' |
...
Parameter | Sub-category-1 | Sub-category-2 | Description | Example Value |
---|---|---|---|---|
cpu_set | ||||
kvm | '4-43,48-87' | |||
huge_pages | ||||
dpdk | ||||
size | '1G' | |||
count | 32 |
Host Profiles
The host profiles Following things are covered:
...
Parameter Category | Sub-Category-1 | Sub-Category-2 | Description | Example Value 1 | Example Value 2 |
---|---|---|---|---|---|
hardware_profile | NA | NA | The hardware profile used by the host | intel_2600.yaml | |
primary_network | NA | NA | The main network used for administration | dmz | |
Interfaces | NA | NA | Define each and every interfaces of the host in detail. | ||
Name | NA | Name of the Interface | dmz | data1 | |
device_link | The name of the network link. | dmz | data1 | ||
slaves | NIC Aliases | ctrl_nic1 | data_nic1 | ||
networks | The networks this interface belongs to. | dmz | - private - management | ||
...
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.
...