| Table of Contents |
|---|
Introduction
Assumptions
- All the hardware are Uniform
- Same number of NICs with same PCI ids
- Same number of disks with same addresses.
- 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
...
| Table of Contents |
|---|
Introduction
Assumptions
- All the hardware are Uniform
- Same number of NICs with same PCI ids
- Same number of disks with same addresses.
- 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
| Parameter | Sub-Category-1 | Sub-Category-2 | Description | Example Value |
| physical_provisioner | ||||
| deployment_strategy | Name of the strategy to use. User can use the one that is defined in airshipit/treasuremap/global/deployment See below. | 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 | ||||
| Deployment-Strategy | ||||
| groups | named sets of nodes that will be deployed together. | |||
| name | name of the group | masters | ||
| critical | if this group is required to continue to additional phases of deployment | true | ||
| depends_on | Group names that must be successful before this group can be processed | [] | ||
| selectors | A list of identifying information to indicate the nodes that are members of this group | |||
| node_names | node01 | |||
| node_labels | ucp_control_plane: enabled | |||
| node_tags | control | |||
| rack_names | rack01 | |||
| success_criteria | A list of identifying information to indicate the nodes that are members of this group. When no criteria are specified, it means that no checks are done - processing continues as if nothing is wrong | |||
| percent_successful_nodes | The calculated success rate of nodes completing the deployment phase. | 75 would mean that 3 of 4 nodes must complete the phase successfully | ||
| minimum_successful_nodes | An integer indicating how many nodes must complete the phase to be considered successful | 3 | ||
| maximum_failed_nodes | An integer indicating a number of nodes that are allowed to have failed the deployment phase and still consider that group successful. | 0 | ||
Typical Ordering of groups:
__________ __________________
| ntp-node | | monitoring-nodes | ---------- ------------------ | ____V__________ | control-nodes | --------------- |_________________________ | | ______V__________ ______V__________ | compute-nodes-1 | | compute-nodes-2 | ----------------- -----------------
Profiles
There are two important categories of profiles that the user should create to match their environment:
...
| 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 | ||
...
Source (as mentioned in commonaddress.yaml) | Destination |
|---|---|
| .genesis.hostname | .values.nodes[0].name |
| .masters[0].hostname | .values.nodes[1].name |
| .masters[1].hostname | .values.nodes[2].name |
Source | Destination |
|---|---|
| certificate of calico-etcd-<podname>-node1 | .values.nodes[0].tls.client.cert |
| certificate-key calico-etcd-<podname>-node1 | .values.nodes[0].tls.client.key |
| certificate of calico-etcd-<podname>-node1-peer | .values.nodes[0].tls.peer.cert |
| certificate-key of calico-etcd-<podname>-node1-peer | .values.nodes[0].tls.peer.key |
| certificate of calico-etcd-<podname>-node2 | .values.nodes[1].tls.client.cert |
| certificate-key calico-etcd-<podname>-node2 | .values.nodes[1].tls.client.key |
| certificate of calico-etcd-<podname>-node2-peer | .values.nodes[1].tls.peer.cert |
| certificate-key of calico-etcd-<podname>-node2-peer | .values.nodes[1].tls.peer.key |
| certificate of calico-etcd-<podname>-node3 | .values.nodes[2].tls.client.cert |
| certificate-key calico-etcd-<podname>-node3 | .values.nodes[2].tls.client.key |
| certificate of calico-etcd-<podname>-node3-peer | .values.nodes[2].tls.peer.cert |
| certificate-key of calico-etcd-<podname>-node3-peer | .values.nodes[2].tls.peer.key |
Undercloud Platform
Ceph
Openstack helm Infra
...
| 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 |
...