-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Requirement is to create VFC Instance Group per networkrole
- Create new capability type as below and include in group type
- capabilities_types:
org.openecomp.capabilities.VLANAssignment:
derived_from: tosca.capabilities.Root
description: ability to expose routing information of the internal network
properties:
vfc_instance_group_reference:
type:string
description: ability to recognize capability per vfc instance group on vnf instance
required: true
- Create new global group types as below
group_types:
type: org.openecomp.groups.VfcInstanceGroup
derived_from: tosca.groups.Root
description: groups VFCs with same parent port role
properties:
vfc_instance_group_function_role:
type: string
required: true
description: role of this VFC group
vfc_parent_port_role
type: string
required: true
description: common role of parent ports of VFCs in this group
network_collection_function_role:
type: string
required: true
description: network collection role assigned to this group
subinterface_role:
type: string
required: true
description: common role of subinterfaces of VFCs in this group, criteria the group is created
capabilities:
vlan_assignment:
type: org.openecomp.capabilities.VLANAssignment
properties:
vfc_instance_group_reference:
type:string
- Create VFC Instance group based per Sub-interface network role
Network role is based on Port ID as defined in the HEAT Guidelines:
OS::Neutron::Port | {vm_type}{index}{network_role}_{index}_port |
{vm_type}{index}_int{network_role}_{index}_port | |
OS::ContrailV2::VirtualMachineInterface | int_{network_role}_RVMI |
Comment: if either the parent port or the sub-interface port do not following naming convention - do not create the group, while logging to the log
- Group should be created on the level where the VFCs are defined
- In patterns 1-4 - on main TOSCA
- On Complex VFC - in the inner TOSCA where the VFC is defined
- Members: all VFCs with a sub-interface of the same network role
- VFC Instance Group should be derived from the new group type as defined above
- Assign value to:
-
- subinterface_role from subinterface network role property.
-
- vfc_parent_port_role - the parent port role (we assume it will be the same for all members, so just pick first one)
- For the other two parameters - expose as new input parameter named: <subinterface_network_role>_<Group parameter name>
In case of Compl;ex VFC, on the main TOSCA we will have input per <subinterface_network_role>_<Group parameter name> so in case two nested have groups of the same role, same input will be used by both