Versions Compared

Key

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

Table of Contents

...

  1. All the hardware are Uniform
    1. Same number of NICs with same PCI ids
    2. Same number of disks with same addresses.
  2. Everything is named and their names are used for reference - In Airship, the name if the filename is not important, but the name in the 'schema' (found in schema/metadata/name) is important.

Deployment Configuration and Strategy

ParameterSub-Category-1DescriptionExample Value
physical_provisioner



deployment_strategy


deploy_interval


deploy_timeout


destroy_interval


destroy_timeout


join_wait


prepare_node_interval


prepare_node_timeout


prepare_site_interval


prepare_site_timeout


verify_interval


verify_timeout

kubernetes



node_status_interval


node_status_timeout

kubernetes_provisioner



drain_timeout


drain_grace_period


clear_labels_timeout


remove_etcd_timeout


etcd_ready_timeout

armada+



get_releases_timeout


get_status_timeout


manifest+


post_apply_timeout


validate_design_timeout

Profiles

There are two important categories of profiles that the user should create to match their environment:

...

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













...

PKI-Catalog


Secrets


Actions

ParameterSub-Category-1sub-category-2DescriptionExample Value
signaling



assets




items




path



location



type
'unit','file', 'pkg_list


data



location_pipeline
template


data_pipeline
base64_encode', 'template', 'base64_decode', 'utf8_encode','utf8_decode'


permissions

node_filter




filter_set_type



filter_set items




filter_type



node_names



node_tags



node_labels



rack_names



rack_labels


Rack


ParameterSub-CategoryDescriptionExample Value
tor_switches



mgmt_ip


sdn_api_uri

location



clli


grid

local_networks*


labels


...