5.2.5.2. {network-role}
Requirement: R-69014
|
When a VNF’s port connects to an ONAP internal network or ONAP
external network,
a network role, referred to
as the |
Requirement: R-05201
|
When a VNF connects to two or more unique networks, each
network MUST be assigned a unique |
Requirement: R-21330
|
A VNF’s Heat Orchestration Template’s Resource property parameter that is
associated with an ONAP
external network MUST include the |
Requirement: R-11168
|
A VNF’s Heat Orchestration Template’s Resource ID that is associated with
an ONAP external network MUST include the |
Requirement: R-84322
|
A VNF’s Heat Orchestration Template’s Resource property parameter that
is associated with an ONAP internal network (per the ONAP definition, see
Requirements R-52425 and R-46461 and R-35666)
MUST include
|
Requirement: R-96983
|
A VNF’s Heat Orchestration Template’s Resource ID that is associated
with an ONAP internal network (per the ONAP definition, see Requirements
R-52425 and R-46461 and R-35666)
MUST include |
Requirement: R-26506
|
A VNF’s Heat Orchestration Template’s
|
Requirement: R-00977
|
A VNF’s Heat Orchestration Template’s |
For example, if a VNF has a ‘{vm-type}’ of ‘oam’ and a ‘{network-role}’ of ‘oam_protected’ would be a violation of the requirement.
Requirement: R-58424
|
A VNF’s Heat Orchestration Template’s use of |
Requirement: R-21511
|
A VNF’s Heat Orchestration Template’s use of |
Requirement: R-86588
|
A VNF’s Heat Orchestration Template’s |
Note that this document refers to {network-role}
which in reality
is the {network-role-tag}
. The value of the
{network-role}
/ {network-role-tag}
is determined by the designer of the VNF’s Heat Orchestration Template and
there is no requirement for {network-role}
/ {network-role-tag}
uniqueness across Heat Orchestration Templates for
different VNFs.
When an external network is created by ONAP, the network is also assigned a
{network-role}
. The {network-role}
of the network is not required to
match the {network-role}
of the VNF Heat Orchestration Template.
For example, the VNF Heat Orchestration Template can assign a
{network-role}
of oam
to a network which attaches to an external network with a
{network-role}
of oam_protected
.
- When the Heat Orchestration Template is on-boarded into ONAP
each
{network-role}
value in the Heat Orchestration Template is mapped to the{network-role-tag}
in the ONAP data structure.each
OS::Neutron::Port
is associated with the external network it is connecting to, thus creating the VNF Heat Orchestration Template{network-role}
/{network-role-tag}
to external network{network-role}
mapping.