...
| 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 | 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 |
...
Put a passphrase for the user as 'data'.
Boot Actions
Boot actions can be more accurately described as post-deployment file placement. This file placement can be leveraged to install actions for servers to take after the permanent OS is installed and the server is rebooted. Including custom or vendor scripts and a SystemD service to run the scripts on first boot or on all boots allows almost any action to be configured.
| Parameter | Sub-Category-1 | sub-category-2 | Description | Example Value | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| signaling | assets | items | path | whether to expect a signal at the completion of this boot action. If set to true for a boot action that does not send a signal, it will elongate the deployment step and consider the boot action failed. | true | ||||||
| assets | A list of data assets. | ||||||||||
| items | |||||||||||
| path | If type is unit - is a SystemD unit, such as a service, that will be saved to path and enabled via systemctl enable [filename] | ||||||||||
| location | (see data) | ||||||||||
| type | boot action framework supports assets of several types - 'unit','file', 'pkg_list' . pkg_list is a list of packages | 'file' | |||||||||
| data | The asset contents can be sourced from either the in-document data field of the asset mapping or dynamically generated by requesting them from a URL provided in location. | ||||||||||
| location_pipeline | The boot action framework supports pipelines to allow for some dynamic rendering. There are separate pipelines for the location field to build the URL that referenced assets should be sourced from and the data field (or the data sourced from resolving the location field). | template | |||||||||
| data_pipeline | The For 'template' - Treat the data element as a Jinja2 template and apply a node context to it. The defined context available to the template is below. | location | type | 'unit','file', 'pkg_list | data | location_pipeline | template | data_pipeline | base64_encode', 'template', 'base64_decode', 'utf8_encode','utf8_decode'' | ||
| permissions | If type is file. is simply saved to the filesystem at path and set with permissions.permissions | ||||||||||
| node_filter | filter for selecting to which nodes this boot action will apply. If no node filter is included, all nodes will receive the boot action. Otherwise it will be only the nodes that match the logic of the filter set. | ||||||||||
| filter_set_type | Either intersection|union | union | |||||||||
| filter_set items | |||||||||||
| filter_type | same as filter_set_type. | ||||||||||
| node_names | Names of the node. | ||||||||||
| node_namestagsnode_ | Node tags | ||||||||||
| node_labels | Node labels. | ||||||||||
| rack_names | Rack Names | ||||||||||
| rack_labels | Rack Labels |
Rack
| Parameter | Sub-Category | Description | Example Value | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| tor_switches | For one or more switches, define the following. | ||||||||||
| mgmt_ip | IP address of the management port | 1.1.1.1 | |||||||||
| sdn_api_uri | The URI for SDN based configuration | https://polo.opnfv.org/switchmgmt?switch=switch01name | |||||||||
| location | |||||||||||
| clli | Common Language Location Identifier Code - used within the North American telecommunications industry to specify the location and function of telecommunications equipment. | HSTNTXMOCG0 | |||||||||
| grid | The grid code. | EG12 | |||||||||
| local_networks* | Networks wholly contained to this rack. Nodes in a rack can only connect to local_networks of that rack | pxe_network1 | tor_switches | mgmt_ip | sdn_api_uri | location | clli | grid | local_networks* | labels |
Region
| Parameter | Sub-Category | Description | Example Value |
|---|---|---|---|
| tag_definitions* | |||
| tag | |||
| definition_type | lshw_xpath | ||
| definition | |||
| authorized_keys* | |||
| repositories | |||
| remove_unlisted | |||
| repo_type+ | |||
| url+ | |||
| distributions | |||
| subrepos | |||
| components | |||
| gpgkey | |||
| arches+ | |||
| options |
...