...
| Parameter Category | Sub Category 1 | Sub Category 2 | Sub-Category-2 | Sub-Category-2 | Description | Example Value 1 |
|---|---|---|---|---|---|---|
| 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 networkLink that will be attached to this interface. NetworkLink definition includes part of the interface configuration such as bonding(see below) | dmz, data1 | ||||
| slaves | NIC Aliases. The list of hardware interfaces used for creating this interface. This value can be a device alias defined in the HardwareProfile or the kernel name of the hardware interface. For bonded interfaces, this would list all the slaves. For non-bonded interfaces, this should list the single hardware interface used | ctrl_nic1, data_nic1 | ||||
| networks | This is the list of networks to enable on this interface. If multiple networks are listed, the NetworkLink attached to this interface must have trunking enabled or the design validation will fail.. | dmz, private, management | ||||
| storage | Either in a HostProfile or BaremetalNode document. The storage configuration can describe the creation of partitions on physical disks, the assignment of physical disks and/or partitions to volume groups, and the creation of logical volumes. | |||||
physical_devices* | A physical device can either be carved up in partitions (including a single partition consuming the entire device) or added to a volume group as a physical volume. Each key in the physical_devices mapping represents a device on a node. The key should either be a device alias defined in the HardwareProfile or the name of the device published by the OS. The value of each key must be a mapping with the following keys | |||||
| labels | A mapping of key/value strings providing generic labels for the device | bootdrive: true | ||||
| volume_group | A volume group name to add the device to as a physical volume. Incompatible with the partitions specification | |||||
| partitions* | A sequence of mappings listing the partitions to be created on the device. Incompatible with volume_group specification | |||||
| name | Metadata describing the partition in the topology | 'root | ||||
| size | The size of the partition. | '30g' | ||||
| part_uuid | A UUID4 formatted UUID to assign to the partition. If not specified one will be generated | |||||
| volume_group | name assigned to a volume group | |||||
| labels | ||||||
| bootable | Boolean whether this partition should be the bootable device | true | ||||
| filesystem | An optional mapping describing how the partition should be formatted and mounted | |||||
| mountpoint | Where the filesystem should be mounted. If not specified the partition will be left as a raw device | '/' | ||||
| fstype | The format of the filesystem. Defaults to ext4 | 'ext4' | ||||
| mount_options | fstab style mount options. Default is ‘defaults’ | 'defaults' | ||||
| fs_uuid | A UUID4 formatted UUID to assign to the filesystem. If not specified one will be generated | |||||
| fs_label | A filesystem label to assign to the filesystem. Optional. | |||||
| volume_groups | ||||||
| vg_uuid | A UUID4 format uuid applied to the volume group. If not specified, one is generated | |||||
| logical_volumes* | A sequence of mappings listing the logical volumes to be created in the volume | |||||
| name | Used as the logical volume name | |||||
| lv_uuid | A UUID4 format uuid applied to the logical volume: If not specified, one is generated | |||||
| size | The logical volume size | |||||
| filesystem | A mapping specifying how the logical volume should be formatted and mounted | |||||
| mountpoint | Same as above. | |||||
| fstype | ||||||
| mount_options | ||||||
| fs_uuid | ||||||
| fs_label | ||||||
| platform | define the operating system image and kernel to use as well as customize the kernel configuration | |||||
| image | Image name | 'xenial' | ||||
| kernel | Kernel Version | 'hwe-16.04' | ||||
| kernel_params | A mapping. Each key should either be a string or boolean value. For boolean true values, the key will be added to the kernel parameter list as a flag. For string values, the key:value pair will be added to the kernel parameter list as key=value | kernel_package: 'linux-image-4.15.0-46-generic' | ||||
| oob | The ipmi OOB type requires additional configuration to allow OOB management | |||||
| network | which node network is used for OOB access. | oop | ||||
| account | valid account that can access the BMC via IPMI over LAN | root | ||||
| credential | valid password for the account that can access the BMC via IPMI over LAN | root | ||||
| spec | host_profile | Name of the HostProfile that this profile adopts and overrides values from. | defaults | |||
| metadata | ||||||
| owner_data | ||||||
| <software-component-name> enabled/disabled | openstack-l3-agent: enabled |
...
This is defined under Baremetal. Node network attachment can be described in a HostProfile or a BaremetalNode document. Node addressing is allowed only in a BaremetalNode document.
Hence, this focuses mostly on addressing. Nodes adopts all values from the profile that it is mapped to and can then again override or append any configuration that is specific to that node.
...
| Parameter | Sub-Category | Description | Example Value | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cidr | classless inter-domain routing address for the network | 172.16.3.0/24 | ||||||||||||||||
| ranges* | defines a sequence of IP addresses within the defined cidr. Ranges cannot overlap. | |||||||||||||||||
| type | start | end | dns | domain | servers | dhcp_relay | self_ip | upstream_target | mtu | vlan | routedomain | routes* | subnet | gateway | metric | routedomain | labels |
Network Link
| The type of address range (static, dhcp, reserved) | static | ||
| start | The starting IP of the range, inclusive. | 172.16.3.15 | |
| end | The last IP of the range, inclusive | 172.16.3.200 | |
| dns | used for specifying the list of DNS servers to use if this network is the primary network for the node. | ||
| domain | A domain that can be used for automated registration of IP addresses assigned from this Network | opnfv.org | |
| servers | A comma-separated list of IP addresses to use for DNS resolution | 8.8.8.8 | |
| dhcp_relay | DHCP relaying is used when a DHCP server is not attached to the same layer 2 broadcast domain as nodes that are being PXE booted. The DHCP requests from the node are consumed by the relay (generally configured on a top-of-rack switch) which then encapsulates the request in layer 3 routing and sends it to an upstream DHCP server. The Network spec supports a dhcp_relay key for Networks that should relay DHCP requests. | ||
| self_ip | |||
| upstream_target | IP address must be a host IP address for a MaaS rack controller. The upstream target network must have a defined DHCP address range | ||
| mtu | maximum transmission unit for this Network. Must be equal or less than the mtu defined for the hosting NetworkLink. | 1500 | |
| vlan | If a Network is accessible over a NetworkLink using 802.1q VLAN tagging, the vlan attribute specified the VLAN tag for this Network. It should be omitted for non-tagged Networks | '102' | |
| routedomain | logical grouping of L3 networks such that a network that describes a static route for accessing the route domain will yield a list of static routes for all the networks in the routedomain. See the description of routes below for more information | storage | |
| routes* | defines a list of static routes to be configured on nodes attached to this network. The routes can defined in one of two ways: an explicit destination subnet where the route will be configured exactly as described or a destination routedomain where Installer will calculate all the destination L3 subnets for the routedomain and add routes for each of them using the gateway and metric defined. | ||
| subnet | Destination CIDR for the route | 0.0.0.0/0 | |
| gateway | The gateway IP on this Network to use for accessing the destination | 172.16.3.1 | |
| metric | The metric or weight for this route | 10 | |
| routedomain | Use this route’s gateway and metric for accessing networks in thedefined routedomain. | storage |
Network Link
The NetworkLink defines layer 1 and layer 2 attributes that should be in-sync between the node and the switch. Each link can support a single untagged VLAN and 0 or more tagged VLANs
| Parameter | Sub-Category | Description | Example Value | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bonding | Describes combining multiple physical links into a single logical link | |||||||||||||
| mode | What bonding mode to configure
| 802.3ad | ||||||||||||
| hash | The link selection hash. Supported values are layer3+4, layer2+3, layer2. | layer3+4 | ||||||||||||
| peer_rate | How frequently to send LACP control frames. Supported values are fast and slow. | fast | ||||||||||||
| mon_rate | Interval between checking link state in milliseconds. | 100 | ||||||||||||
| up_delay | Delay in milliseconds between a link coming up and being marked up in the bond. > mon_rate | 200 | ||||||||||||
| down_delay | Delay in milliseconds between a link going down and being marked down in the bond. > mon_rate | 200 | ||||||||||||
| mtu | maximum transmission unit for the link. It must be equal or greater than the MTU of any VLAN interfaces using the link. | 9000 | ||||||||||||
| linkspeed | physical layer speed and duplex. | auto | ||||||||||||
| trunking | how multiple layer 2 networks will be multiplexed on the link | |||||||||||||
| mode | Can be disabled for no trunking or 802.1q for standard VLAN tagging | 802.1q | ||||||||||||
| default_network | For mode: disabled, this is the single network on the link. For mode: 802.1q this is optionally the network accessed by untagged frames. | |||||||||||||
| allowed_networks* | is a sequence of network names listing all networks allowed on this link. Each Network can be listed on one and only one NetworkLink | |||||||||||||
| Parameter | Sub-Category | Description | Example 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.
...