| Table of Contents |
|---|
Introduction
...
Deployment Configuration and Strategy
| Parameter | Sub-Category-1 | Description | Example 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:
...
| 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 | ||
...
PKI-Catalog
Secrets
Actions
| Parameter | Sub-Category-1 | sub-category-2 | Description | Example 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 |
...