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.
Profiles
There are two important categories of profiles that the user should create to match their environment:
- Hardware ( site/<site_name>/profiles/hardware/<profile_name>.yaml)
- Host site/<site_name>/profiles/host/<profile_name(s)>.yaml
Hardware Profile
Under the hardware profile, user can provide details about the server, and few device (n/w and disk) aliases. User can contact the administrator to obtain this information - else, one has to obtain this information from the 'lshw' command. For example: sudo lshw -c network -businfo - to know the NIC names and PCI Ids. Once the user has the hardware information, it can be configure following parameters:
Server:
| 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' |
Disks:
The Disks can be either bootdisk or datadisk(s). Similar to NICs, the self-explanatory names should be choosen. For example, cephjournal1 can be the name for one of the disks use as one the ceph journals.
For every disk defined, the below information can be configured:
| 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' |
Host Profiles
The host profiles Following things are covered:
- Mapping NICs of the host the Networks it would belong to. NOTE: For definition of network please refer to Networks section below.
- How the Bootdisk is partitioned.
- What all software components are enabled on the particular host.
- What hardware profile that host is using.
- Platform specific configuration for the host.
For majority of the cases, you only need two host profiles - Dataplane and Control Plane. Of course, the user can create more than 2 and use it accordingly. The below table summarizes the configurable parameters for the host profiles.
| Parameter Category | Sub-Category-1 | Sub-Category-2 | Description | Example Value |
|---|---|---|---|---|
| hardware_profile | NA | NA | The hardware profile used by the host | intel_2600.yaml |
| Interfaces | Name | NA | ||