Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

ParameterDescriptionExample-Value
vendorVendor of the server chassisIntel
generationGeneration of the chassis model'4'
hw_versionVersion of the chassis model within its generation'3'
bios_versionThe certified version of the chassis BIOS'SE5C ....
boot_modeMode of the default boot of hardware - bios, uefibios
bootstrap_protocolProtocol of boot of the hardware - pxe, usb, hdd'pxe
pxe_interfaceWhich interface to use for network booting within the OOB manager, not OS device0

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. 

...

ParameterDescriptionExample Value
addressThe PCI address of the NIC0000:04:00.0
dev_typeDescription of the NIC'I350 Gigabit Network Connection'
bus_typeThe bus supported'pci'

...

ParameterDescriptionExample Value
addressThe bus address of the Disk0:2.0.0
dev_type

Description of the disk.

'INTEL SSDSC2BB48'
bus_typeThe bus supported'scsi'

...

ParameterSub-category-1Sub-category-2DescriptionExample 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 CategorySub-Category-1Sub-Category-2DescriptionExample Value 1Example Value 2
hardware_profileNANAThe hardware profile used by the hostintel_2600.yaml
primary_networkNANAThe main network used for administrationdmz
Interfaces



NANADefine each and every interfaces of the host in detail.

Name


NAName of the Interfacedmzdata1
device_linkThe name of the network link.dmzdata1
slavesNIC Aliases ctrl_nic1data_nic1
networksThe networks this interface belongs to.dmz

- private

- management













...

ParameterSub-CategoryDescriptionExample 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.

Parametersub-categoryDescriptionExample-Value
osh



region_nameThe region name to use. Typically Site name is provided.intel-pod10



PKI-Catalog

Parametersub-category-1sub-category-2DescriptionExample Value
certificate_authorities




description



certificates




document_name



description



common_name



hosts



groups

keypairs




name



description



Secrets

Publickeys of the Users.

...