New Requirements -

R-62300 If a VNF has two or more ports that require a Virtual IP Address (VIP),
a VNF's Heat Orchestration Template's Resource 'OS::Neutron::Port' property
'allowed_address_pairs' map property 'ip_address' parameter *MUST* be used.

R-91810 If a VNF requires ONAP to assign a Virtual IP (VIP) Address to
ports connected an external network, the port
*MUST NOT* have more than one IPv4 VIP address.

R-41956 If a VNF requires ONAP to assign a Virtual IP (VIP) Address to
ports connected an external network, the port
*MUST NOT* have more than one IPv6 VIP address.

R-10754 If a VNF has two or more ports that
attach to an external network that require a Virtual IP Address (VIP),
and the VNF requires ONAP automation to assign the IP address,
all the Virtual Machines using the VIP address *MUST*
be instantiated in the same Base Module Heat Orchestration Template
or in the same Incremental Module Heat Orchestration Template.

R-98748 The VNF's Heat Orchestration Template's Resource
'OS::Neutron::Port' property 'allowed_address_pairs'
map property 'ip_address' parameter
*MUST* be declared as type 'string'.

R-41492 When the VNF's Heat Orchestration Template's Resource
'OS::Neutron::Port' is attaching to an external network,
and an IPv4 Virtual IP (VIP)
address is assigned via ONAP automation
using the property 'allowed_address_pairs'
map property 'ip_address' and
the parameter name *MUST* follow the
naming convention

• '{vm-type}_{network-role}_floating_ip'

where

• '{vm-type}' is the {vm-type} associated with the OS::Nova::Server
• '{network-role}' is the {network-role} of the external network

And the parameter *MUST* be declared as type 'string'.

R-83412 The VNF's Heat Orchestration Template's Resource
'OS::Neutron::Port' property 'allowed_address_pairs'
map property 'ip_address' parameter
'{vm-type}_{network-role}_floating_ip'
*MUST NOT* be enumerated in the
VNF's Heat Orchestration Template's Environment File.

R-35735 When the VNF's Heat Orchestration Template's Resource
'OS::Neutron::Port' is attaching to an external network,
and an IPv6 Virtual IP (VIP)
address is assigned via ONAP automation
using the property 'allowed_address_pairs'
map property 'ip_address',
the parameter name *MUST* follow the
naming convention

• '{vm-type}_{network-role}_v6_floating_ip'

where

• '{vm-type}' is the {vm-type} associated with the OS::Nova::Server
• '{network-role}' is the {network-role} of the external network

And the parameter *MUST* be declared as type 'string'.

 

R-83418 The VNF's Heat Orchestration Template's Resource
'OS::Neutron::Port' property 'allowed_address_pairs'
map property 'ip_address' parameter
'{vm-type}_{network-role}_floating_v6_ip'
*MUST NOT* be enumerated in the
VNF's Heat Orchestration Template's Environment File.

R-05257 A VNF's Heat Orchestration Template's *MUST NOT*
contain the Resource 'OS::Neutron::FloatingIP'.

R-76449 A VNF's Heat Orchestration Template's *MUST NOT*
contain the Resource 'OS::Neutron::FloatingIPAssociation'.

R-99812 A value for VNF's Heat Orchestration Template's property 'name'
for a non 'OS::Nova::Server' resource *MUST NOT* be declared
in the VNF's Heat Orchestration Template's Environment File.

R-32408 If a VNF's Heat Orchestration Template property 'name'
for a non 'OS::Nova::Server' resource uses the intrinsic function
'str_replace' in conjunction with the ECOMP
supplied metadata parameter 'vnf_name' and does not create
a unique value, additional data *MUST* be used in the
'str_replace' to create a unique value, such as 'OS::stack_name'
and/or the 'OS::Heat::ResourceGroup' 'index'.

• R-84517 The Contrail GUI has a limitation displaying special characters.
  The issue is documented in
  https://bugs.launchpad.net/juniperopenstack/+bug/1590710.
  It is recommended that special *SHOULD* characters be avoided.
  However, if special characters must be used, note that for
  the following resources:

• Virtual Machine
• Virtual Network
• Port
• Security Group
• Policies
• IPAM Creation

the only special characters supported
are - \" ! $\ \ ' ( ) = ~ ^ | @ ` { } [ ] > , . _"

R-97726 A VNF's Heat Orchestration Template's Base Module Output
Parameter names *MUST* contain {vm-type} and/or {network-role}
when appropriate.

R-88524 A VNF's Heat Orchestration Template's Volume Template
Output Parameter names *MUST* contain {vm-type} when appropriate.

R-47874 A VNF *MAY* have

• Only an IPv4 OAM Management IP Address
• Only an IPv6 OAM Management IP Address
• Both a IPv4 and IPv6 OAM Management IP Addresses

R-18683 If a VNF has one IPv4 OAM Management IP Address and the
IP Address needs to be inventoried in ECOMP's A&AI
database, an output parameter *MUST* be declared in only one of the
VNF's Heat Orchestration Templates and the parameter *MUST* be named
'oam_management_v4_address'.

R-94669 If a VNF has one IPv6 OAM Management IP Address and the
IP Address needs to be inventoried in ECOMP's A&AI
database, an output parameter *MUST* be declared in only one of the
VNF's Heat Orchestration Templates and the parameter *MUST* be named
'oam_management_v6_address'.

R-56287 If the VNF's OAM Management IP Address is assigned by ECOMP SDN-C and
assigned in the VNF's Heat Orchestration Template's via a heat resource
'OS::Neutron::Port' property 'fixed_ips' map property
'ip_adress' parameter (e.g., '{vm-type}{network-role}_ip{index}',
'{vm-type}{network-role}_v6_ip{index}')
and the OAM IP Address is required to be inventoried in ECOMP A&AI,
then the parameter *MUST* be echoed in an output statement.

R-48987 If the VNF's OAM Management IP Address is Cloud assigned and
and the OAM IP Address is required to be inventoried in ONAP AAI,
then the parameter *MUST* be obtained by the resource 'OS::Neutron::Port'
attribute 'ip_address'.

R-87004 A VNF's Heat Orchestration Template's Resource
OS::Cinder::Volume Resource ID *SHOULD use the naming convention

• {vm-type}volume{index}
  where
• {vm-type} is the vm-type
• {index} starts at zero and increments by one

R-86497 A VNF's Heat Orchestration Template's Resource
OS::Cinder::VolumeAttachment Resource ID *SHOULD* use the naming convention

• {vm-type}volume_attachment{index}
  where
• {vm-type} is the vm-type
• {index} starts at zero and increments by one

R-04747 A VNF's Heat Orchestration Template's Resource
'OS::Heat::CloudConfig' Resource ID *MUST* contain the '{vm-type}'.

R-20319 A VNF's Heat Orchestration Template's Resource 'OS::Heat::CloudConfig'
Resource ID *MAY* use the naming convention

• {vm-type}_RCC
  where
• {vm-type} is the vm-type
• 'RCC' signifies that it is the Resource Cloud Config

R-30804 A VNF's Heat Orchestration Template's Resource
'OS::Heat::MultipartMime' Resource ID *MUST* contain the '{vm-type}'.

R-18202 A VNF's Heat Orchestration Template's Resource
'OS::Heat::MultipartMime' Resource ID *MAY* use the naming convention

• {vm-type}_RMM
  where
• {vm-type} is the vm-type
• 'RMM' signifies that it is the Resource Multipart Mime

R-64197 A VNF's Heat Orchestration Template's Resource
OS::Heat::ResourceGroup Resource ID that creates sub-interfaces *MUST*
use the naming convention

• {vm-type}{vm-type_index}_subint{network-role}port{port-index}_subinterfaces
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the networks
  that the sub-interfaces attach to
• {port-index} is the instance of the the port on the vm-type
  attached to the network of {network-role}

R-08975 A VNF's Heat Orchestration Template's Resource
'OS::Heat::SoftwareConfig' Resource ID *MUST* contain the '{vm-type}'.

R-03656 A VNF's Heat Orchestration Template's Resource
'OS::Heat::SoftwareConfig' Resource ID *MAY* use the naming convention

• {vm-type}_RSC
  where
• {vm-type} is the vm-type
• 'RSC' signifies that it is the Resource Software Config

R-25720 A VNF's Heat Orchestration Template's Resource
OS::Neutron::Net Resource ID *MUST* use the naming convention

• int_{network-role}_network

R-20453 A VNF's Heat Orchestration Template's Resource
OS::Neutron::Port that is attaching to an external network Resource ID
*MUST* use the naming convention

• {vm-type}{vm-type_index}{network-role}port{port-index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {port-index} is the instance of the the port on the vm-type
  attached to the network of {network-role}

R-26351 A VNF's Heat Orchestration Template's Resource
OS::Neutron::Port that is attaching to an internal network Resource ID
*MUST* use the naming convention

• {vm-type}{vm-type_index}_int{network-role}port{port-index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {port-index} is the instance of the the port on the vm-type
  attached to the network of {network-role}

R-27469 A VNF's Heat Orchestration Template's Resource
OS::Neutron::Port that is creating a Reserve Port with an IPv4 address
Resource ID *MUST* use the naming convention

• reserve_port_{vm-type}{network-role}_floating_ip{index}
  where
• {vm-type} is the vm-type
• {network-role} is the network-role of the network
  that the port is attached to
• {index} is the instance of the IPv4 Reserve Port
  for the vm-type attached to the network of {network-role}

R-68520 A VNF's Heat Orchestration Template's Resource OS::Neutron::Port
that is creating a Reserve Port with an IPv6 address Resource ID
*MUST* use the naming convention

• reserve_port_{vm-type}{network-role}_floating_v6_ip{index}
  where
• {vm-type} is the vm-type
• {network-role} is the network-role of the network
  that the port is attached to
• {index} is the instance of the IPv6 Reserve Port
  for the vm-type attached to the network of {network-role}

R-08775 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to one {vm-type} and
more than one network (internal and/or external) Resource ID
*SHOULD* use the naming convention

• {vm-type}_security_group
  where
• {vm-type} is the vm-type

R-03595 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to more than
one {vm-type} and one external network Resource ID *SHOULD*
use the naming convention

• {network-role}_security_group
  where
• {network-role} is the network-role

R-73213 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to more than
one {vm-type} and one internal network Resource ID *SHOULD*
use the naming convention

• int_{network-role}_security_group
  where
• {network-role} is the network-role

R-17334 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to one {vm-type}
and one external network Resource ID *SHOULD* use the naming convention

• {vm-type}_{network-role}_security_group
  where
• {vm-type} is the vm-type
• {network-role} is the network-role

R-14198 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to one {vm-type}
and one internal network Resource ID *SHOULD* use the naming convention

• {vm-type}int{network-role}_security_group
  where
• {vm-type} is the vm-type
• {network-role} is the network-role

R-30005 A VNF's Heat Orchestration Template's Resource
OS::Neutron::SecurityGroup that is applicable to more than one

{vm-type}

and more than one network (internal and/or external)
Resource ID *MAY* use the naming convention

• shared_security_group
  or
• {vnf-type}_security_group
  where
• {vnf-type} describes the VNF

R-59434 A VNF's Heat Orchestration Template's Resource
OS::Neutron::Subnet Resource ID *SHOULD* use the naming convention

• int_{network-role}subnet{index}
  where
• {network-role} is the network-role
• {index} is the {index} of the subnet of the network

R-24997 A VNF's Heat Orchestration Template's Resource
OS::Nova::Keypair applies to one {vm-type} Resource ID *SHOULD*
use the naming convention

• {vm-type}keypair{index}
  where
• {network-role} is the network-role
• {index} is the {index} of the keypair

R-65516 A VNF's Heat Orchestration Template's Resource OS::Nova::Keypair
applies to all Virtual Machines in the the VNF, the Resource ID *SHOULD*
use the naming convention

• {vnf-type}_keypair
  where
• {vnf-type} describes the VNF

R-29751 A VNF's Heat Orchestration Template's Resource OS::Nova::Server
Resource ID *MUST* use the naming convention

• {vm-type}server{index}
  where
• {vm-type} is the vm-type
• {index} is the index

R-15189 A VNF's Heat Orchestration Template's Resource OS::Nova::ServerGroup
Resource ID *MAY* use the naming convention

• {vm-type}_RSG
  or
• {vm-type}_Server_Grp
  or
• {vm-type}_ServerGroup
  or
• {vm-type}_servergroup

R-53310 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv4 Address
on a port attached to an
external network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}{network-role}vmi{vmi_index}IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'IP' signifies that an IPv4 address is being configured
• {index} is the index of the IPv4 address

R-46128 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv6 Address
on a port attached to an
external network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}{network-role}vmi{vmi_index}v6_IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'v6_IP' signifies that an IPv6 address is being configured
• {index} is the index of the IPv6 address

R-62187 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv4 Address
on a port attached to an
internal network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}_int{network-role}vmi{vmi_index}IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'IP' signifies that an IPv4 address is being configured
• {index} is the index of the IPv4 address

R-87563 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv6 Address
on a port attached to an
internal network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}_int{network-role}vmi{vmi_index}v6_IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'v6_IP' signifies that an IPv6 address is being configured
• {index} is the index of the IPv6 address

R-20947 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv4 Address
on a sub-interface port attached to a
sub-interface network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}_subint{network-role}vmi{vmi_index}IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'IP' signifies that an IPv4 address is being configured
• {index} is the index of the IPv4 address

R-88540 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InstanceIp'
that is configuring an
IPv6 Address
on a sub-interface port attached to a
sub-interface network
Resource ID *MUST*
use the naming convention

• {vm-type}{vm-type_index}_subint{network-role}vmi{vmi_index}v6_IP{index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port is attached to
• {vmi_index} is the instance of the the virtual machine interface
  (e.g., port) on the vm-type
  attached to the network of {network-role}
• 'v6_IP' signifies that an IPv6 address is being configured
• {index} is the index of the IPv6 address

R-81214 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InterfaceRouteTable'
Resource ID
*MUST*
contain the '{network-role}'.

R-28189 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::InterfaceRouteTable'
Resource ID
*MAY*
use the naming convention

• {network-role}_RIRT
  where
• {network-role} is the network-role
• 'RIRT' signifies that it is the Resource Interface Route Table

R-30753 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::NetworkIpam'
Resource ID
*MUST*
contain the '{network-role}'.

R-81979 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::NetworkIpam'
Resource ID
*MAY*
use the naming convention

• {network-role}_RNI
  where
• {network-role} is the network-role
• 'RNI' signifies that it is the Resource Network IPAM

R-20065 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::PortTuple'
Resource ID
*MUST*
contain the '{vm-type}'.

R-84457 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::PortTuple'
Resource ID
*MAY*
use the naming convention

• {vm-type}_RPT
  where
• {vm-type} is the vm-type
• 'RPT' signifies that it is the Resource Port Tuple

R-76014 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::ServiceHealthCheck'
Resource ID
*MUST*
contain the '{vm-type}'.

R-65618 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::ServiceHealthCheck'
Resource ID
*MAY*
use the naming convention

• {vm-type}RSHC{LEFT|RIGHT}
  where
• {vm-type} is the vm-type
• 'RSHC' signifies that it is the Resource Service Health Check
• 'LEFT' is used if the Service Health Check is on the left interface
• 'RIGHT' is used if the Service Health Check is on the right interface

R-16437 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::ServiceTemplate'
Resource ID
*MUST*
contain the '{vm-type}'.

R-14447 A VNF's Heat Orchestration Template's Resource
'OS::ContrailV2::ServiceTemplate'
Resource ID
*MAY*
use the naming convention

• {vm-type}RST{index}
  where
• {vm-type} is the vm-type
• 'RST' signifies that it is the Resource Service Template
• '{index}' is is the index

R-96253 A VNF's Heat Orchestration Template's Resource
OS::ContrailV2::VirtualMachineInterface
that is attaching to an external network
Resource ID
*MUST*
use the naming convention

• {vm-type}{vm-type_index}{network-role}vmi{vmi_index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port (i.e. virtual machine interface) is attached to
• {vmi_index} is the instance of the the vmi on the vm-type
  attached to the network of {network-role}

R-50468 A VNF's Heat Orchestration Template's Resource
OS::ContrailV2::VirtualMachineInterface
that is attaching to an internal network
Resource ID
*MUST*
use the naming convention

• {vm-type}{vm-type_index}_int{network-role}vmi{vmi_index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port (i.e. virtual machine interface) is attached to
• {vmi_index} is the instance of the the vmi on the vm-type
  attached to the network of {network-role}

R-54458 A VNF's Heat Orchestration Template's Resource
OS::ContrailV2::VirtualMachineInterface
that is attaching to a sub-interface network
Resource ID
*MUST*
use the naming convention

• {vm-type}{vm-type_index}_subint{network-role}vmi{vmi_index}
  where
• {vm-type} is the vm-type
• {vm-type_index} is the instance of the {vm-type}
• {network-role} is the network-role of the network
  that the port (i.e. virtual machine interface) is attached to
• {vmi_index} is the instance of the the vmi on the vm-type
  attached to the network of {network-role}

R-99110 A VNF's Heat Orchestration Template's Resource
OS::ContrailV2::VirtualNetwork
Resource ID
*MUST*
use the naming convention

• 'int_{network-role}_network'
  or
• 'int_{network-role}_RVN' where RVN represents Resource Virtual Network

R-93272 A VNF *MAY* have one or more ports connected to a unique
external network. All VNF ports connected
to the unique external network *MUST* have Cloud Assigned IP Addresses
or *MUST* have ECOMP SDN-C assigned IP addresses.

R-13841 A VNF *MAY* have one or more ports connected to a unique
internal network. All VNF ports connected
to the unique internal network *MUST* have Cloud Assigned IP Addresses
or *MUST* have statically assigned IP addresses.

R-07577 If the VNF's ports connected to a unique network (internal or external)
and the port's IP addresses are Cloud Assigned IP Addresses,
all the IPv4 Addresses *MUST* be from
the same subnet and all the IPv6 Addresses *MUST* be from the
same subnet.

R-45602 If a VNF's Port is attached to a network (internal or external)
and the port's IP addresses are Cloud Assigned by OpenStack's DHCP
Service, the 'OS::Neutron::Port' Resource's

• property 'fixed_ips' map property 'ip_address' *MUST NOT* be used
• property 'fixed_ips' map property 'subnet'/'subnet_id' *MAY* be used

R-63956 If the VNF's ports connected to a unique external network
and the port's IP addresses are ECOMP SDN-C assigned IP Addresses,
the IPv4 Addresses *MAY* be from
different subnets and the IPv6 Addresses *MAY* be from different
subnets.

R-48880 If a VNF's Port is attached to an external network and the port's
IP addresses are assigned by ECOMP's SDN-Controller,
the 'OS::Neutron::Port' Resource's

• property 'fixed_ips' map property 'ip_address' *MUST* be used
• property 'fixed_ips' map property 'subnet'/'subnet_id' *MUST NOT* be used

R-18001 If the VNF's ports connected to a unique internal network
and the port's IP addresses are statically assigned IP Addresses,
the IPv4 Addresses *MAY* be from
different subnets and the IPv6 Addresses *MAY* be from different
subnets.

R-70964 If a VNF's Port is attached to an internal network and the port's
IP addresses are statically assigned by the VNF's Heat Orchestration\
Template (i.e., enumerated in the Heat Orchestration Template's
environment file), the 'OS::Neutron::Port' Resource's

• property 'fixed_ips' map property 'ip_address' *MUST* be used
• property 'fixed_ips' map property 'subnet'/'subnet_id'
  *MUST NOT* be used

R-02164 When a VNF's Heat Orchestration Template's Contrail resource
has a property that
references an external network that requires the network's
Fully Qualified Domain Name (FQDN), the property parameter

• *MUST* follow the format '{network-role}_net_fqdn'
• *MUST* be declared as type 'string'
• *MUST NOT* be enumerated in the NF's Heat Orchestration Template's
  Environment File

R-73228 A VNF's Heat Orchestration Template's parameter
'{network-role}_net_fqdn'
*MUST* be declared as type 'string'.

R-92193 A VNF's Heat Orchestration Template's parameter
'{network-role}_net_fqdn'
*MUST NOT* be enumerated in the VNF's Heat Orchestration Template's
Environment File.

R-28222 If a VNF's Heat Orchestration Template
'OS::ContrailV2::InterfaceRouteTable' resource
'interface_route_table_routes' property
'interface_route_table_routes_route' map property parameter name
*MUST* follow the format

• {vm-type}_{network-role}_route_prefixes

R-19756 If a VNF's Heat Orchestration Template
'OS::ContrailV2::InterfaceRouteTable' resource
'interface_route_table_routes' property
'interface_route_table_routes_route' map property parameter
'{vm-type}_{network-role}_route_prefixes'
*MUST* be defined as type 'json'.

R-76682 If a VNF's Heat Orchestration Template
'OS::ContrailV2::InterfaceRouteTable' resource
'interface_route_table_routes' property
'interface_route_table_routes_route' map property parameter
'{vm-type}_{network-role}_route_prefixes'
*MUST NOT* be enumerated in the VNF's Heat Orchestration Template's
Environment File.

R-99646 A VNF's YAML files (i.e, Heat Orchestration Template files and
Nested files) *MUST* have a unique name in the scope of the VNF.

R-99794 An external network *MUST* have one subnet. An external network
*MAY* have more than one subnet.

 

Deleted Requirements -

• R-61282 The VNF Heat Orchestration Template *MUST*
  adhere to the following naming convention for the property
  allowed_address_pairs and Map Property ip_address parameter,
  when the parameter is referencing an “external” network:

• {vm-type}_{network-role}_floating_ip for an IPv4 address

• {vm-type}_{network-role}_floating_v6_ip for an IPv6 address

• R-16805 The VNF Heat Orchestration Template *MUST* adhere to the
  following naming convention for the property allowed_address_pairs
  and Map Property ip_address parameter when the parameter is
  referencing an “internal” network.