From 3dfa3e7e0f00e15bb32e68760a73d41a25187661 Mon Sep 17 00:00:00 2001 From: Kevin Scaggs Date: Wed, 27 Nov 2019 13:59:36 -0600 Subject: Minor updates to Vnf Performed minor updates to the Vnf model in the area of allotted resource. Issue-ID: MODELING-104 Change-Id: I52f068d26995a07edddbb9d330413833765e02d2 Signed-off-by: Kevin Scaggs --- ONAP Information Model/Vnf.notation | 33 ++++++++++++++++++++++++++------- ONAP Information Model/Vnf.uml | 35 +++-------------------------------- 2 files changed, 29 insertions(+), 39 deletions(-) diff --git a/ONAP Information Model/Vnf.notation b/ONAP Information Model/Vnf.notation index 10419a4..230b083 100644 --- a/ONAP Information Model/Vnf.notation +++ b/ONAP Information Model/Vnf.notation @@ -9272,6 +9272,30 @@ + + + + + + + + + + + + + + + + + + + + + + + + @@ -9838,12 +9862,7 @@ - - - - - - + @@ -10427,7 +10446,7 @@ - + diff --git a/ONAP Information Model/Vnf.uml b/ONAP Information Model/Vnf.uml index dc537dd..f8e0c06 100644 --- a/ONAP Information Model/Vnf.uml +++ b/ONAP Information Model/Vnf.uml @@ -336,18 +336,6 @@ NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the - - -

- - - - - - - - -

@@ -589,10 +577,9 @@ This will probably need to move to common The Uses relationship is covered by the service instance expressing the sharable infrasturcture capability which has a relationship to the sharable resource. The ANF instance also has a relationship to the same sharable resource. - Anfs cannot run on top of Anfs. An anf can run on a sharable Vnf or Pnf. - - - Resource Not yet 'Rooted" + - Pnfs cannot run on a Vnf or Anf + +- Pnfs cannot run on Pnfs, etc. @@ -2307,18 +2294,6 @@ This could include the number of CPU cores on this logical node, a memory config - - - An AllottedLink is a link provided (or allotted) by some service instance. The Allottedlink may be incorporated into the topology of some consuming service like other links. - - - - - - - - - Security group rule specifies the matching criteria for the ingress and/or egress traffic to/from the visited connection points. If an ingress traffic is accepted, the corresponding egress response shall be allowed, regardless of the security group rules on the egress direction. If an egress traffic is allowed, the corresponding ingress response shall be accepted, regardless of the security group rules on the ingress direction. The design of security group rule follows a permissive model where all security group rules applied to a CP are dealt with in an "OR" logic fashion, i.e. the traffic is allowed if it matches any security group rule applied to this CP. @@ -3486,8 +3461,6 @@ The attached VDUs shall connect to the same internal VLD. - - @@ -3568,7 +3541,6 @@ The attached VDUs shall connect to the same internal VLD. - @@ -3706,7 +3678,6 @@ The attached VDUs shall connect to the same internal VLD. - -- cgit 1.2.3-korg