From 0f4c87536194750306ac852059ae382f8ccfc126 Mon Sep 17 00:00:00 2001 From: jjewitt58 Date: Wed, 13 Mar 2019 11:42:13 -0700 Subject: Fix LogicalNodeRequirements in Vnf Issue-ID: MODELING-104 Change-Id: Ic7c23181866627c3e52e1cac264ef4123ba000d7 Signed-off-by: jjewitt58 --- ONAP Information Model/Vnf.notation | 47 ------------------------------------- ONAP Information Model/Vnf.uml | 26 +++----------------- 2 files changed, 3 insertions(+), 70 deletions(-) diff --git a/ONAP Information Model/Vnf.notation b/ONAP Information Model/Vnf.notation index e58f0b0..de5df3c 100644 --- a/ONAP Information Model/Vnf.notation +++ b/ONAP Information Model/Vnf.notation @@ -6555,35 +6555,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -7531,14 +7502,6 @@ - - - - - - - - @@ -8065,16 +8028,6 @@ - - - - - - - - - - diff --git a/ONAP Information Model/Vnf.uml b/ONAP Information Model/Vnf.uml index 9950748..6b037c8 100644 --- a/ONAP Information Model/Vnf.uml +++ b/ONAP Information Model/Vnf.uml @@ -1530,7 +1530,7 @@ When the VnfExtCpd is mapped to a VduCpd, the values for the attributes type, su - + This references (couples) the CPD with any logical node I/O requirements (for network devices) that may have been created. Linking these attributes is necessary so that so that I/O requirements that need to be articulated at the logical node level can be associated with the network interface requirements associated with the CPD. @@ -2327,7 +2327,8 @@ This could include the number of CPU cores on this logical node, a memory config - Indicates the protocol carried over the IP layer. Permitted values: any protocol defined in the IANA protocol registry, e.g. TCP, UDP, ICMP, etc. + Indicates the protocol carried over the IP layer. Permitted values: any protocol defined in the IANA protocol registry, e.g. TCP, UDP, ICMP, etc. +See https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml Note: IFA011 defines this as an enum, but as the list is not complete, made this a string. @@ -2355,22 +2356,6 @@ Note: IFA011 defines this as an enum, but as the list is not complete, made this - - - This information element describes compute, memory and I/O requirements that are to be associated with the logical node of infrastructure. The logical node requirements are a sub-component of the VDU level requirements. As an example for illustration purposes, a logical node correlates to the concept of a NUMA cell in libvirt terminology. - - - - The logical node-level compute, memory and I/O requirements. An array of key-value pairs that articulate the deployment requirements. - -This could include the number of CPU cores on this logical node, a memory configuration specific to a logical node (e.g. such as available in the Linux kernel via the libnuma library) or a requirement related to the association of an I/O device with the logical node. - - - - - - - This information element describes requested additional capability for a particular VDU. Such a capability may be for acceleration or specific tasks. @@ -3177,7 +3162,6 @@ The attached VDUs shall connect to the same internal VLD. - @@ -3380,8 +3364,6 @@ The attached VDUs shall connect to the same internal VLD. - - @@ -3675,7 +3657,6 @@ The attached VDUs shall connect to the same internal VLD. - @@ -3744,7 +3725,6 @@ The attached VDUs shall connect to the same internal VLD. - -- cgit 1.2.3-korg