From 934f9a6acd1060fc22347a2421e6faa141ed2e57 Mon Sep 17 00:00:00 2001 From: Kevin Scaggs Date: Tue, 7 Aug 2018 16:26:12 -0500 Subject: Updates to vnf and common vnf most updates are per comments from Xu. Also have some draft material on Allotted Resource. Common updates are mostly related to VES modeling. Issue-ID: MODELING-104 Change-Id: Ie99aa1579972eec6e2ed04911139f53aa2389800 Signed-off-by: Kevin Scaggs --- papyrus/ONAP Information Model/Vnf.uml | 308 +++++++++++++++++---------------- 1 file changed, 161 insertions(+), 147 deletions(-) (limited to 'papyrus/ONAP Information Model/Vnf.uml') diff --git a/papyrus/ONAP Information Model/Vnf.uml b/papyrus/ONAP Information Model/Vnf.uml index 64781d3..51dc443 100644 --- a/papyrus/ONAP Information Model/Vnf.uml +++ b/papyrus/ONAP Information Model/Vnf.uml @@ -177,15 +177,6 @@ NOTE: More software images can be attached to the virtualisation container using - - -

- - - - - -

@@ -406,14 +397,34 @@ NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the + + +

+ + + + + + + + + + + + +

+ + + + + + + Describes the associated elements of a VNFD for a certain purpose during VNF lifecycle management. - - Missing in clean, but in Sparx and ifa011 - A few quick observations 1. Using integer for number. Jessie: Created a primitive called Number which is a superset of integer and real. @@ -437,29 +448,36 @@ NOTE 2: virtualLinkProfile needs to be provided for all VLs that the CPs of the gold indicates an add or a change - discuss cpBandwidth Question + . -can protocol be enumerated? +can protocol be enumerated? - yes. Values? + +Change addrestype to enumeration . Change L2addressData and l3addressData to 0..1 given "only present...." definition - - - - discuss vlBandwidth -. -connectivity type type? -. -vlanidouter/inner type? - instanceState type? + orchestration Status - Pending, Created, Active... - Christina will query. . -onboardedVnfPkgInfoId - need class for VnfPkg? +onboardedVnfPkgInfoId - need class for VnfPkg? Yes - probably need more discussion - tied to vnf model and internal model. Vnf Instance related to vnf descriptor or onboarding pkg descriptor + + + do we need both superclass and subclass or just one??? + + + Will not try to push this out into R3 - save for R4 - - instantiationState type? + + Move from Vnf submodel to Service Submodel + + + Type of address + + + + @@ -576,6 +594,7 @@ References: tosca-nfv-YAML-v1.0-wd05-rev02 (tosca.nodes.nfv.vnfd, but node details are not defined) ETSI GS NFV-IFA 011 V2.1.3 (VNFD) + Provider of the VNF and of the VNFD. @@ -851,7 +870,7 @@ Identifies the operating system used in the software image. This attribute may a The VduProfile describes additional instantiation data for a given VDU used in a DF. - + Uniquely identifies a VDU. @@ -877,6 +896,8 @@ Identifies the operating system used in the software image. This attribute may a Specifies affinity or anti-affinity rules applicable between the virtualisation containers (e.g. virtual machines) to be created based on this VDU. + + @@ -1009,7 +1030,9 @@ NOTE: Each identifier references an affinity or anti-affinity group which expres - + + + Specifies test access facilities expected on the VL (e.g. none, passive monitoring, or active (intrusive) loopbacks at endpoints). @@ -1185,14 +1208,6 @@ BaseConfigGroup may establish internal networks such as OAM (VNF Mgmt) or MNS (M - - - Reference to the internal VDU CPD which is used to instantiate internal CPs. These internal CPs are, in turn, exposed as external CPs defined by this external CPD. - - - - - Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD. @@ -1203,17 +1218,6 @@ NOTE: In case of referencing an intCpd via its identifier, the virtualNetworkInt - - - Reference to the internal Virtual Link -Descriptor (VLD) to which CPs instantiated -from this external CP Descriptor (CPD) -connect. Either intVirtualLinkDesc or -intCpd shall be present. - - - - @@ -1515,15 +1519,9 @@ All the VDUs referenced in the level shall be part of the corresponding DF and t - - - Specifies bitrate requirements applicable to virtual links created from particular virtual link descriptors for this level. - -NOTE: If not present, it is assumed that the bitrate requirements can be derived from those specified in the VduCpd instances applicable to the internal VL. If present in both the InstantiationLevel and the VduCpd instances applicable to the internal VL, the highest value takes precedence. - - - - + + + @@ -1572,13 +1570,13 @@ NOTE: If not present, it is assumed that the bitrate requirements can be derived - Every VNF contains a BaseConfigGroup. + Every Vnf contains a BaseConfigGroup. BaseConfigGroup may set Access Control Lists (ACL's) and establish security groups and server groups. BaseConfigGroup reates/establishs storage for the VM's (OpenStack Cinder). BaseConfigGroup may establish internal networks such as OAM (VNF Mgmt) or MNS (Maintenance & Surveillance) established. -A very simple VNF may only have a BaseConfig VNFElementGroup. +A very simple VNF may only have a BaseConfig VnfElementGroup. @@ -1670,17 +1668,11 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - name of the VNF instance - - - - - - alternative name of the VNF instance + name of the VNF instance. Multiple names are possible. - - + + @@ -1731,14 +1723,6 @@ Diversity - Resources are geo-diverse ( cannot be co-located). availability zone information of the VNF instance - - - provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems - valid value example: PROVISIONED, PREPROVISIONED, CAPPED - - - - indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. @@ -1746,7 +1730,7 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - + whether the VNF instance is instantiated @@ -1927,14 +1911,6 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - - - provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems - valid value example: PROVISIONED, PREPROVISIONED, CAPPED - - - - whether the NFC instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. @@ -1953,9 +1929,11 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - An intelligent or human readable name of the vnfc instance + An intelligent or human readable name of the vnfc instance. Multiple names are possible. + + @@ -1970,13 +1948,6 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - - - Additional intelligent or human readable name of the vnfc instance - - - - English description of network function component that the specific VNFC deployment is providing. @@ -1988,7 +1959,7 @@ Diversity - Resources are geo-diverse ( cannot be co-located). indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. - + whether the VNFC instance is instantiated @@ -2011,6 +1982,26 @@ Diversity - Resources are geo-diverse ( cannot be co-located). + + + A Service instance can generate virtual Network Function instances, acting as a "Network Function Provider" of sorts. These Network Functions are different from the Network Functions that comprise the "Provider Service" itself. (E.g., a virtual PE Service comprised of a "vPERouter" and a "vPEForwarder" VNF can collectively provide a "VRF" Network Function, which includes both routing and forwarding functionality.) We distinguish the Network Functions that are provided by a Service instance from the Network Functions that comprise a Service Instance by using the term "Allotted Resource" for the former. + + + An allotted resource is a slice of some resource. + + + + + + + + + + + + + + @@ -2316,22 +2307,6 @@ Per VNF, the affinity/anti-affinity rules defined using this information element - - - - Identifies the protocol this VL gives access to (Ethernet, MPLS, ODU2, IPV4, IPV6, Pseudo-Wire). - - - - - - Identifies the flow pattern of the connectivity (Line, Tree, Mesh). - - - - - - The LinkBitrateRequirements information element describes the requirements in terms of bitrate for a VL. @@ -2472,7 +2447,7 @@ NOTE: The scriptInput values are passed to the scripts in addition to the parame - + An attribute that describes the recommended periodicity at which to collect the performance information. @@ -2573,6 +2548,24 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on Describes VNF lifecycle event(s) or an external stimulus detected on a VNFM reference point. + + + + + + + + + + + + + + + + + + @@ -2592,18 +2585,18 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - - + + + The VirtualLinkBitRateLevel information element specifies bitrate requirements applicable to a virtual link instantiated from a particular VnfVirtualLinkDesc. - - - + + + @@ -2617,8 +2610,14 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. - - + + + + + + + + @@ -2663,8 +2662,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - @@ -2788,7 +2785,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -2830,7 +2826,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -2887,8 +2882,12 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - + + + + + + @@ -2913,7 +2912,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -2922,7 +2920,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -2947,7 +2944,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -2957,7 +2953,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3007,7 +3002,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3139,9 +3133,7 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - @@ -3185,7 +3177,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3210,7 +3201,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3219,7 +3209,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3247,13 +3236,11 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - @@ -3292,8 +3279,12 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - + + + + + + @@ -3386,7 +3377,6 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - @@ -3451,16 +3441,13 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - - @@ -3473,9 +3460,7 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - @@ -3497,9 +3482,15 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - - - + + + + + + + + + @@ -3591,4 +3582,27 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on + + + + + + + + + + + + + + + + + + + + + + + -- cgit 1.2.3-korg