...
| Attribute | Qualifier | Cardinality | Content | Description |
|---|---|---|---|---|
| description | M | 1 | String | Describes the service exposed. |
| virtualLinkRequirement | M | 1 | String | Refers in an abstract way to the network or multiple networks that the ExtCpd shall be exposed on (ex: OAM, EndUser, backhaul, LI, etc). The intent is to enable a network operator to take decision on to which actual VPN to connect the extCpd to. NOTE 1. |
| interfaceOrder | M | 0..1 | Integer, greater or equal to zero | Mandatory attribute for a secondary network interface (not applicable for a primary network interface). Defines the order in which an the additional/secondary network interface declaration appears in the pod manifest. Note that an SRIOV mated vNIC pair shall be modelled by a single vduCp, and its order value set to the lower value of the two vNIC’s order numbers; the two vNICs are expected to appear in consecutive order on the compute instance, and be attached to same network(s). See NOTE 2 |
| networkInterfaceRequirementsnetworkInterfaceRealizationRequirements | M | 0..1 | datatype.NetworkInterfaceRequirementsnetworkInterfaceRealizationRequirements | Details container implementation specific requirements on the NetworkAttachmentDefinition to . See NOTE 2 & 3. |
| inputParamMappings | M | 0..1 | datatype.extCpd.ParamMappings | Information on what parameters that are required to be provided to the deployment tools for the asdExtCpd instance. |
| resourceMapping | M | 0..1 | String | Kubernetes API resource name for the resource manifest for the service, ingress or pod resource declaring the network interface. Enables, together with knowledge on namespace, the orchestrator to lookup the runtime data related to the extCpd. |
NOTE 1: Corresponds more or less to a virtual_link requirement in ETSI NFV SOL001.
NOTE 2: Applies only for ExtCpds representing secondary network interfaces in a pod.
NOTE 3: Several ExtCpd may refer to same additional network interface requirements.
...
networkInterfaceRealizationRequirements Information Element
| Attribute | Qualifier | Cardinality | Content | Description |
|---|---|---|---|---|
| trunkMode | M | 0..1 | ”false” | ”true” | If not present or set to”false”, means that this interface shall connect to single network. If set to ”true” then the network interface shall be a trunk interface (connects to multiple VLANS). |
| ipam | M | 0..1 | ”cniManaged” ”userManaged” ”inBand” | The default value (”cniManaged”) means that the CNI specifies how IPAM is done and assigns the IP address to the pod interface. Value ”user” indicates that IPAM is done via the application inside the pod. "inBand" indicates that the application expects to receive the interface configuration through protocols/procedures over the interface itself, such as DHCP, DHCPv6, SLAAC. |
| interfaceType | M | 0..1 | ”kernel” | ”userspaceDpdk” | "memif" | This attribute is applicable for passthrough and memif interfaces. Value default value is ”kernel”. |
| interfaceOption | M | 0..N | e.g. "speed=1G|10G|25G|100G" "nic-type=virtio|i710|mlx-cx5|" | Applicable to Pod network interfaces that directly connect to a physical NIC. The value is a list of verified options for physical NIC caracteristics. |
| interfaceRedundancy | M | 0..1 | "infraProvided“ | "none“ | "matedPair" | Default value is "infra-provided”, which means that the infrastructure is expected to provide network redundancy for the pod interface. Value "none" means that the application has no requirement on network redundancy. Value ”matedPair” means that the Pod asks for a mated pair of non-redundant left/right network attachments (typically SRIOV) and handles redundancy on application level. The same set of networks shall be configured on both interfaces. |
| switchPlane | M | 0..1 | “left” | “right” | Used (only) in conjunction with networkRedundancy "none" when the application requires two independent virtual links that for redundancy reasons have to reside on different switch planes (left or right). |
| redundancyMethod | M | 0..1 | ”activePassiveBond” | ”activeActiveBond” | ”activePassiveL3” | ”activeActiveL3” | Used (only) in conjunction with networkRedundancy "matedPair". "activeActiveBond“: The bonded left/right links must be part of a multi-chassis LAG in active-active mode. | "activePassiveBond": Interfaces bonded in active-passive mode in the application with move of bond MAC address. No specific requirements on DC fabric. | "activePassiveL3": Move of application IP address. | "activeActiveL3": Anycast/ECMP. |
...