-
Task
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Summary
- consolidated external/internal network sections for each OS::Neutron::Port - Parameters
- refactored existing requirements into newer requirements
New Requirements
- R-18008 The VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
property ‘network’ parameter MUST be declared as type: ‘string’.
- R-62983 When the VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
is attaching to an external network, the ‘network’ parameter name *MUST*
- follow the naming convention ‘{network-role}_net_id’ if the Neutron
network UUID value is used to reference the network - follow the naming convention ‘{network-role}_net_name’ if the OpenStack
network name is used to reference the network.
where ‘{network-role}’ is the network-role of the external network and
a ‘get_param’ *MUST* be used as the intrinsic function.
- R-86182 When the VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
is attaching to an internal network, and the internal network is created in a different
Heat Orchestration Template than the ‘OS::Neutron::Port’, the ‘network’
parameter name *MUST*
- follow the naming convention ‘int_{network-role}_net_id’ if the Neutron
network UUID value is used to reference the network - follow the naming convention ‘int_{network-role}_net_name’ if the
OpenStack network name in is used to reference the network.
where ‘{network-role}’ is the network-role of the internal network and a ‘get_param’ *MUST* be used as the intrinsic function.
- R-93177 When the VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
is attaching to an internal network, and the internal network is created in the same Heat
Orchestration Template than the ‘OS::Neutron::Port’, the ‘network’
parameter name *MUST* obtain the UUID of the internal network by using
the intrinsic function ‘get_resource’ or ‘get_attr’ and referencing the
Resource ID of the internal network.
- R-29872 The VNF’s Heat Orchestration Template’s Resource ‘OS::Nova::Server’
property ‘network’ parameter *MUST NOT* be enumerated in the Heat
Orchestration Template’s Environment File.
- R-34037 The VNF’s Heat Orchestration Template’s resource ‘OS::Neutron::Port’
property ‘fixed_ips’ map property ‘ip_address’ parameter *MUST* be declared as
either type ‘string’ or type ‘comma_delimited_list’.
- R-40971 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an external network, and an IPv4 address is
assigned using the property
‘fixed_ips’ map property ‘ip_address’ and the parameter type is defined
as a string, the parameter name *MUST* follow the naming
convention ‘{vm-type}{network-role}_ip{index}’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the external network
- the value for {index} must start at zero (0) and increment by one
- R-39841 The VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
property ‘fixed_ips’ map property ‘ip_address’ parameter
‘{vm-type}{network-role}_ip{index}’ *MUST NOT* be enumerated in the
VNF’s Heat Orchestration Template’s Environment File.
- R-04697 When the VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’
is attaching to an external network, and an IPv4 address is assigned using
the property ‘fixed_ips’ map property ‘ip_address’ and the parameter type
is defined as a comma_delimited_list, the parameter name *MUST* follow the
naming convention ‘{vm-type}_{network-role}_ips’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the external network
- R-98905 The VNF’s Heat Orchestration Template’s Resource ‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’ parameter ‘{vm-type}_{network-role}_ips’ *MUST NOT* be enumerated in the VNF’s Heat Orchestration Template’s Environment File.
- R-71577 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an external network, and an IPv6 address
is assigned using the property ‘fixed_ips’ map property ‘ip_address’ and
the parameter type is defined as a string, the parameter name *MUST* follow
the naming convention ‘{vm-type}{network-role}_v6_ip{index}’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the external network
- the value for {index} must start at zero (0) and increment by one
- R-87123 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}{network-role}_v6_ip{index}’ *MUST NOT* be enumerated
in the VNF’s Heat Orchestration Template’s Environment File.
- R-23503 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an external network, and an IPv6
address is assigned using the property ‘fixed_ips’ map property ‘ip_address’
and the parameter type is defined as a comma_delimited_list, the parameter
name *MUST* follow the naming convention ‘{vm-type}_{network-role}_v6_ips’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the external network
- R-93030 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}_{network-role}_v6_ips’ *MUST NOT* be enumerated in the
VNF’s Heat Orchestration Template’s Environment File.
R-78380 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an internal network, and an IPv4 address
is assigned using the property ‘fixed_ips’ map property ‘ip_address’ and
the parameter type is defined as a string, the parameter name *MUST* follow
the naming convention ‘{vm-type}int{network-role}ip{index}’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the internal network
- the value for {index} must start at zero (0) and increment by one
R-28795 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}int{network-role}ip{index}’ *MUST* be enumerated
in the VNF’s Heat Orchestration Template’s Environment File.
- R-85235 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an internal network, and an IPv4
address is assigned using the property ‘fixed_ips’ map property ‘ip_address’
and the parameter type is defined as a comma_delimited_list, the parameter
name *MUST* follow the naming convention ‘{vm-type}int{network-role}_ips’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the internal network
- R-90206 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}int{network-role}_int_ips’ *MUST* be enumerated in
the VNF’s Heat Orchestration Template’s Environment File.
- R-27818 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an internal network, and an IPv6 address
is assigned using the property ‘fixed_ips’ map property ‘ip_address’ and
the parameter type is defined as a string, the parameter name *MUST* follow
the naming convention ‘{vm-type}int{network-role}v6_ip{index}’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the internal network
- the value for {index} must start at zero (0) and increment by one
- R-97201 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}int{network-role}v6_ip{index}’ *MUST* be enumerated
in the VNF’s Heat Orchestration Template’s Environment File.
- R-93496 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter associated with an internal network, i.e.,
- {vm-type}int{network-role}ip{index}
- {vm-type}int{network-role}ip_v6{index}
- {vm-type}int{network-role}_ips
- {vm-type}int{network-role}_v6_ips
*MUST* be enumerated in the Heat Orchestration Template’s Environment
File and IP addresses *MUST* be assigned.
- R-62590 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter associated with an external network, i.e.,
- {vm-type}{network-role}_ip{index}
- {vm-type}{network-role}_ip_v6{index}
- {vm-type}_{network-role}_ips
- {vm-type}_{network-role}_v6_ips
*MUST NOT* be enumerated in the Heat Orchestration Template’s Environment File.
ONAP provides the IP address assignments at orchestration time.
- R-98569 The VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ property ‘fixed_ips’ map property ‘ip_address’
parameter ‘{vm-type}int{network-role}_v6_ips’ *MUST* be enumerated in
the VNF’s Heat Orchestration Template’s Environment File.
- R-29765 When the VNF’s Heat Orchestration Template’s Resource
‘OS::Neutron::Port’ is attaching to an internal network, and an IPv6
address is assigned using the property ‘fixed_ips’ map property ‘ip_address’
and the parameter type is defined as a comma_delimited_list, the parameter
name *MUST* follow the naming convention ‘{vm-type}int{network-role}_v6_ips’, where
- ‘{vm-type}’ is the {vm-type} associated with the OS::Nova::Server
- ‘{network-role}’ is the {network-role} of the internal network
Deleted Requirements
- R-72050 The VNF Heat Orchestration Template *MUST* contain {network-role} in the parameter name
- R-57576 The VNF Heat Orchestration Template *MUST* contain int_{network-role}
- R-41177 The VNF Heat Orchestration Template *MUST* include {vm-type} and {network-role}
in the parameter name, when a SDN-C IP assignment is made to a
port connected to an external network.
- R-84898 The VNF Heat Orchestration Template *MUST* adhere to the following naming convention,
when the parameter for property fixed_ips and Map Property ip_address
is declared type: comma_delimited_list:
- {vm-type}_{network-role}_ips for IPv4 address
- {vm-type}_{network-role}_v6_ips for IPv6 address
- R-34960 The VNF Heat Orchestration Template *MUST* adhere to the following
naming convention,
when the parameter for property fixed_ips and Map Property ip_address
is declared type: string:
- {vm-type}{network-role}_ip{index} for an IPv4 address
- {vm-type}{network-role}_v6_ip{index} for an IPv6 address
- R-62584 The VNF Heat Orchestration Template *MUST* adhere to
the following naming convention,
when the parameter for property fixed_ips and Map Property ip_address
is declared type: comma_delimited_list:
- {vm-type}int{network-role}_ips for IPv4 address
- {vm-type}int{network-role}_v6_ips for IPv6 address
- R-29256 The VNF Heat Orchestration Template *MUST* must adhere to the following
naming convention,
when the parameter for property fixed_ips and Map Property ip_address
is declared type: string:
- {vm-type}int{network-role}ip{index} for an IPv4 address
- {vm-type}int{network-role}v6_ip{index} for an IPv6 address
- R-20106 The VNF Heat Orchestration Template *MUST* adhere to the following naming convention for
the property fixed_ips and Map Property subnet_id parameter,
when the parameter is referencing the subnet of an “internal” network:
- int_{network-role}_subnet_id if the subnet is an IPv4 subnet
- int_{network-role}_v6_subnet_id if the subnet is an IPv6 subnet
- R-47716 The VNF Heat Orchestration Template *MUST* adhere to the following parameter naming
convention for the property fixed_ips and Map Property subnet_id
parameter, when the parameter is referencing a subnet of an
“external” network.
- {network-role}_subnet_id if the subnet is an IPv4 subnet
- {network-role}_v6_subnet_id if the subnet is an IPv6 subnet