...
| Parameter | Sub-Category-1 | sub-category-2 | Description | Example Value |
|---|---|---|---|---|
| signaling | 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. | 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. | |||
| 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_tags | Node tags | |||
| node_labels | Node labels. | |||
| rack_names | Rack Names | |||
| rack_labels | Rack Labels |
...
| 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 |
Region
| Parameter | Sub-Category | Description | Example Value |
|---|---|---|---|
| tag_definitions* | |||
| tag | |||
| definition_type | lshw_xpath | ||
| definition | |||
| authorized_keys* | |||
| repositories | list of SSH keys which MaaS will register for the built-in "ubuntu" account during the PXE process. This list is populated by substitution, so the same SSH keys do not need to be repeated in multiple manifests. | ||
| remove_unlisted | Whether to remove the unlisted packages? | true | |
| repo_type+ | |||
| url+ | |||
| distributions | |||
| subrepos | |||
| components | |||
| gpgkey | |||
| arches+ | |||
| options |
...