Configuring the PNF descriptor

Specify the settings of the physical network function in a PNF descriptor in YAML or XML format, then add the PNF descriptor to the root directory of the PNF package. A PNF descriptor has the following structure:

Section/setting	Description
`name`	Name of the physical network function.
`description`	Brief description of the physical network function.
`description_file`	Name of the PDF file with the technical documentation or specification of the physical network function. This file must be placed in the root directory of the PNF package. Users can view and download the file in the orchestrator web interface. Optional parameter.
`provider`	Provider of the physical network function.
`version`	Version of the physical network function.
`external_connections`	External connection points of the physical network function.
`internal_connections`	Internal connection points of VDUs that are part of the physical network function. This section is optional.
`configurations`	Scripts for performing actions at various stages of the physical network function lifecycle, for example, during deployment of the physical network function.
`flavours`	Flavours of the physical network function. You can select one of the specified flavours of the physical network function in the orchestrator web interface.
`scaling`	Physical network function scaling parameters. This section is optional.
`user_configurations`	Orchestrator web interface inputs that are added to the settings area of the physical network function. This section is optional.
`backups`	Physical network function backup tasks. This section is optional.

PNF descriptor example

external_connections

The external_connections section has the following structure:

Section/setting		Description

`- name`		Name of the external connection point.
	`description`	Brief description of the external connection point.
	`ip`	IP address of the external connection point. Enter a value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126`
	`mask`	Subnet mask of the external connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `255.255.255.0` The subnet mask is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the subnet mask cannot be changed. `AUTO` — The subnet mask is assigned automatically using an external DHCP server or a script from the `configurations` section.
	`gw`	IP address of the gateway of the external connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126` The IP address is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the IP address cannot be changed. `AUTO` — The IP address is assigned automatically using an external DHCP server or a script from the `configurations` section. Optional parameter.
	`dns`	IP address of the DNS server of the external connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126` The IP address is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the IP address cannot be changed. `AUTO` — The IP address is assigned automatically using an external DHCP server or a script from the `configurations` section. Optional parameter.
	`group`	The group to which the external connection point belongs. This setting is required if multiple VDUs within the physical network function use the same external connection point.

Example of this section

internal_connections

The internal_connections section has the following structure:

Section/setting		Description

`- name`		Name of the internal connection point.
	`description`	Brief description of the internal connection point.
	`ip`	IP address of the internal connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126` The IP address is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the IP address cannot be changed. `AUTO` — The IP address is assigned automatically using an external DHCP server or a script from the `configurations` section.
	`mask`	Subnet mask of the internal connection point. Possible values: Value in the XXX.XXX.XXX.XXX format, for example: `255.255.255.0` The subnet mask is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the subnet mask cannot be changed. AUTO — The subnet mask is assigned automatically using an external DHCP server or a script from the `configurations` section.
	`gw`	IP address of the gateway of the internal connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126` The IP address is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the IP address cannot be changed. `AUTO` — The IP address is assigned automatically using an external DHCP server or a script from the `configurations` section. Optional parameter.
	`dns`	IP address of the DNS server of the internal connection point. Possible values: Value in the `XXX.XXX.XXX.XXX` format, for example: `192.168.110.126` The IP address is assigned using DHCP via MAC-based reservation of an OpenStack port. In this case, the IP address cannot be changed. `AUTO` — The IP address is assigned automatically using an external DHCP server or a script from the `configurations` section. Optional parameter.
	`group`	The group to which the internal connection point belongs. This setting is required if multiple VDUs within the physical network function use the same internal connection point.

Example of this section

configurations

The configurations section has the following structure:


Section/setting		Description
`- name`		Name of the script.
	`filename`	File name of the script or Ansible playbook. You must place the script in the /scripts directory of the PNF package.
	`stage`	The stage of operation of the physical network function at which the script runs. Possible values: `initialization` to run the script on deployment of the physical network function. `termination` to run the script on deletion of the physical network function. `none` to run the script when a value changes in the `user_configurations` section in the settings area of the physical network function in the orchestrator web interface.
	`executor`	Script interpreter. Possible values: `ansible` `expect` `/bin/sh` `bin/bash` `<path to the custom script interpreter>`, for example `/usr/bin/php`.
	`authentication`	Method for authenticating the VNFM in the physical network function for running scripts. Possible values: `key` means the VNFM is authenticated in the physical network function using a key that is generated when that physical network function is deployed. You need to use a script to get the key, so we recommend not to specify this value for the first script. `password` means the VNFM is authenticated in the physical network function with a user name and password from the `flavours` → `vdus` section.
	`files_path`	Path to files for running scripts using SSH. You need to create a directory in the /scripts directory of the PNF package and place the files in that directory. The files are copied to the VDU. Optional parameter.
	`timeout`	The time to wait for the script to finish, in seconds. If the script does not finish within the specified time, execution is terminated. The timeout starts at the moment the script is run. You can specify this parameter if you have specified a path to a custom script executor for the `executor` parameter.

Example of this section

flavours

The flavours section has the following structure:

Section/setting		Description

`- name`		Name of the deployment option.
	`description`	Brief description of the flavour.
	`position`	Sequential number of the flavour. The flavour with the lowest position has the lowest performance.
	`management`	Parameters of VDU administration consoles.
	`vdus`	VDU settings.

The management section has the following structure:

Section/setting			Description

`ssh`			Settings for managing VDUs using the SSH console.
	`- vdu_name`		Name of the VDU.
		`def_user`	User name for establishing the SSH session.
		`authentication`	Method for authenticating the VNFM in the physical network function for running scripts. Possible values: `key` means the VNFM is authenticated in the physical network function using a key that is generated when that physical network function is deployed. You need to get the key using a script from the `configurations` section. `password` means the VNFM is authenticated in the physical network function with a user name and password from the `vdus` section.
`web`			Settings for managing VDUs using the web console.
	`- vdu_name`		Name of the VDU.
		`protocol`	Protocol for connecting to the web console. Possible values: `http` `https`
		`port`	Port for connecting to the web console. Enter a value in the range of 1 to 65,536. By default, port 80 is used.
		`path`	Path to the web console.
		`def_user`	User name for authenticating in the web console.
		`def_password`	Password for authenticating in the web console.

The vdus section has the following structure:

Section/setting				Description

`- name`				Name of the VDU.
	`password_rules`			VDU password requirements. This section is optional.
		`length`		Minimum length of the password.
		`use_upper_case`		Users must use uppercase characters in the password. Possible values: `true` `false`
		`use_lower_case`		Users must use lowercase characters in the password. Possible values: `true` `false`
		`use_digits`		Users must use numerals in the password. Possible values: `true` `false`
		`specific_symbols`		Whether users must use special characters in the password, such as: `@"!`
		`specific_symbols_min_usage`		Minimum number of special characters that must be present in the password.
	`check_connection_mode`			Type of VDU availability test performed during deployment. By default, an SSH test is performed. Possible values: `ssh` `none` Optional parameter.
	`zabbix_template`			Name of the Zabbix template for the VDU.
	`monitoring_type`			Monitoring type of the physical network function. Possible values: `agent` means monitoring using a Zabbix agent. `snmp` means monitoring using the SNMP protocol.
	`ssh_port`			Port number for establishing an SSH session. Optional parameter.
	`ssh_host_key_algorithm`			The host key algorithm used. Possible values: `ssh-rsa`. `ssh-ed25519`. We recommend using this host key algorithm because it is cryptographically strong. If you do not specify this setting, the ssh-rsa algorithm is used by default.
	`configurations`			Names of scripts from the `configurations` section to be run on the VDU. Specify a list of values, for example: `vdu_name:` `- config_1` `- config_2`
	`backups`			Names of backup tasks from the `backups` to be used on the VDU. Specify a list of values, for example: `vdu_name:` `- backup_1` `- backup_2` This section is optional.
	`def_user`			User name for authenticating the VNFM in the physical network function. Optional parameter.
	`def_password`			Password for authenticating the VNFM in the physical network function. Optional parameter.
	`password_authentication`			Password authentication of the VNFM in the physical network function. Possible values: `yes` `no` Optional parameter.
	`network_interfaces`			Network interface settings
		`- name`		Name of the network interface.
			`type`	Type of the network interface. Possible values: `data` is a network interface for data transfer. `management` is a management network interface that is mapped to a network port.
			`description`	Brief description of the network interface.
			`connection_point_ref`	Name of the external connection point from the `external_configurations` section for the management network interface.
	`auto_healing`			VDU auto-healing parameters.
		`triggers_set`		External triggers that initiate VDU auto-healing. Possible values: `any` to have any external trigger initiate VDU auto-healing. `all` to initiate VDU auto-healing if all specified external triggers are triggered. `<trigger name>` to initiate VDU auto-healing when the specified external trigger is triggered.
		`triggers`		External triggers.
			`- name`	Name of the external trigger. Possible values: `unreachable` `scale_up` `scale_down`
		`action_set`		Action to perform when an external trigger is triggered.
			`- type`	Type of action. Possible values: `reboot` to restart the VDU. `script` to run the specified script.
			`configuration_name_ref`	Name of the script from the `configuration` section that is run when an external trigger is triggered. This parameter must be specified if as the `- type`, you selected `script`.

Example of this section

scaling

The scaling section has the following structure:

Parameter	Description
`scale_up_status`	Vertical scaling to a scaling option with a lower sequential number. Possible values: `permit` `deny`
`scale_down_status`	Vertical scaling to a scaling option with a higher sequential number. Possible values: `permit` `deny`

Parameter

Description

scale_up_status

Vertical scaling to a scaling option with a lower sequential number. Possible values:

permit
deny

scale_down_status

Vertical scaling to a scaling option with a higher sequential number. Possible values:

permit
deny

Example of this section

user_configurations

The user_configurations section has the following structure:

Section/setting				Description

`tab`				Tabs that are added to the settings area of the physical network function.
`- name`				Name of the tab.
	`variables`			Orchestrator web interface inputs that are displayed on the tab.
	`- name`			Name of the orchestrator web interface input.
		`description`		Brief description of the orchestrator web interface input.
		`input_type`		Type of the orchestrator web interface input. Possible values: `input` to add a field. `dropdown` to add a drop-down list.
		`default_value`		Default value of the field. You can specify this parameter if as the `input_type`, you specified `input`.
		`values`		The options that are displayed in the drop-down list. This setting can be specified if as the `input_type`, you specified `dropdown`.
		`- value`		The name of the value.
			`is_default`	Default value. Possible values: `true` `false` Optional parameter.
		`required`		Required orchestrator web interface input. Possible values: `true` `false` Optional parameter.
		`type`		The type of value that can be specified in the orchestrator web interface input. Optional parameter.
		`example`		A tooltip that is displayed when the value of the orchestrator web interface input changes. Optional parameter.
		`update_configuration_name`		Names of scripts from the `configurations` section that are run when the value of the orchestrator web interface input changes. Specify a list of values, for example: `update_configuration_name:` `- config_1` `- config_2`

Example of this section

backups

The backups section has the following structure:

Section/setting			Description

`- name`			Name of the backup task.
	`description`		Brief description of the backup task.
	`backup`		Backup parameters.
		`path`	Path to the physical network function directory where the files that you want to backup are located.
		`interval`	Time interval in seconds for backup.
		`store_config`	Number of backup copies to keep.
		`backup_type`	Type of backup.
		`authentication`	Method for authenticating the VNFM in the physical network function for running scripts. Possible values: `key` means the VNFM is authenticated in the physical network function using a key that is generated when that physical network function is deployed. You need to get the key using a script from the `configurations` section. `password` means the VNFM is authenticated in the physical network function with a user name and password from the `flavours` → `vdus` section.
		`configuration_name_ref`	Name of the script from the `configurations` section to run before the backup.
	`restore`		Backup restoration parameters.
		`path`	Path to the physical network function directory where the restored files are placed.
		`backup_type`	Type of backup.
		`authentication`	Method for authenticating the VNFM in the physical network function for running scripts. Possible values: `key` means the VNFM is authenticated in the physical network function using a key that is generated when that physical network function is deployed. You need to get the key using a script from the `configurations` section. `password` means the VNFM is authenticated in the physical network function with a user name and password from the `flavours` → `vdus` section.
		`configuration_name_ref`	Name of the script from the `configurations` section to run after the restoration from backup begins.

Example of this section

Page top