Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page is used for the ONAP R2+ Resource IM drafting and discussion.

...

Content:

...

UML Comparison

This section illustrates the core IM design related to VNF resource from different sources.  

...

Run Time Model (VNF Instance)

...

References:

  • AAI: 

...

  • Design Time Model

    1) ONAP Resource Model UML
    Image Removed
    Image Removed

Image Removed

...

(omit several types for simplicity)

...

Attribute Comparison

This section compares the different IM design from different sources.

Sources:

...

  • VNFC Run Time Model

    AAI (aai_schema_v11 vnfc)ECOMP IM (VNFC Instance)ETSI IFA008 (VnfcInfo)CommentDescriptionvnfc-namevnfcInstanceIdidentifier of the vnfc instancenfc-naming-code

    Xu: Need specification/reference for the value of this attribute? Xu: Should the attribute name aligned to "vnfc"?

    James Forsyth: No, in a network function we should not care if it's physical or virtual

    short code of the vnfc instancenfc-function

    Xu: Should the attribute name aligned to "vnfc"?
    Jimmy Forsyth: No, in a network function we should not care if it's physical or virtual

    description of the vnfc instanceprov-status

    Xu: need further clarification on how this attribute is used
    James Forsyth: Service assurance systems use this status in their logic to determine the provisioning status.  Values such as: PROVISIONED, PREPROVISIONED, CAPPED might be stored in this attribute

    Trigger for operational monitoring of this resource by Service Assurance systemsorchestration-statusvnfcState

    Xu: Is it the same as vnfcState (i.e., start or stop)?
    James Forsyth: Used for lifecycle management.  We don't know what vnfcState is.

    Orchestration status of this VNF, mastered by APP-Cipaddress-v4-oam-vip

    Xu: Is this attribute mandatory? and applicable for all kinds of VNFCs?
    James Forsyth: Not mandatory and this field should be deprecated in ONAP

    Oam V4 vip address of this vnfcin-maintwhether in maintenance modeis-closed-loop-disabled

    Xu: used by DCAE?
    James Forsyth: There are closed loop actions that DCAE might have policies for, and operations can turn off those actions with this flag

    used to indicate whether closed loop function is enabled on this nodegroup-notation

    Xu: need further clarification on how this attribute is used
    James Forsyth: In some applications, a two or more VMs or VNFCs is referred to by a name, and group-notation represents the name.  Might want to use instance-group to replace this over time.

    Group notation of VNFCmodel-invariant-idvduIdthe SDC model id for this resource modelmodel-version-idthe SDC model version for this resource modelresource-version

    Xu: Is it used internally in AAI? can be omitted in the general model.
    James Forsyth: It's used internally in AAI to enforce concurrency control, other systems use it to pass to AAI on updates and delete operations.  It can be omitted from the general model

    Used for optimistic concurrency.  Must be empty on create, valid on update and deletel3-interface-ipv4-address-listl3 interface addresses, ipv4l3-interface-ipv6-address-listl3 interface addresses, ipv6relationship-listassociation (VM, Docker, LXC)AAI: relationship with vserver, vf-module and generic-vnf

...

VNFC Design Time Model

...

Describes network connectivity between a VNFC instance (based on this Vdu) and an internal Virtual Link (VL).

...

Describes CPU, Memory and acceleration requirements of the Virtualisation Container realising this Vdu.

...

Describes storage requirements for a VirtualStorage instance attached to the virtualisation container created from virtualComputeDesc defined for this Vdu.

...

The key indicates the boot index (lowest index defines highest boot priority). The Value references a descriptor from which a valid boot device is created e.g. VirtualStorageDesc from which a VirtualStorage instance is created.

...

Describes constraints on the NFVI for the VNFC instance(s) created from this Vdu.

...

Defines the virtualised resources monitoring parameters on VDU level.

...

Describes the configurable properties of all VNFC instances based on this VDU.

...

Specifies affinity or anti-affinity rules applicable between the virtualisation containers (e.g. virtual machines) to be created based on this VDU.

...

Identifier(s) of the affinity or anti-affinity group(s) the VDU belongs to.

...

VNF Run Time Model

...

Xu: use case for alternative name?
James Forsyth: Customer want aliases, so this is an alias for a VNF

...

Xu: Is there any reference/specification for the value of this attribute?
James Forsyth: This attribute should be deprecated, it was used prior to SDC modelling

...

Xu: deprecated?
James Forsyth
This attribute should be deprecated, it was used prior to SDC modelling

...

Xu: Need clarification, similar to vnfc instance model.
James Forsyth: Service assurance systems use this status in their logic to determine the provisioning status.  Values such as: PROVISIONED, PREPROVISIONED, CAPPED might be stored in this attribute

...

Xu: Need clarification on how this attribute is used.
James Forsyth: Used for lifecycle management. 

...

Xu: deprecated?
James Forsyth Yes

...

Xu: Please clarify the usage of this attribute.
James Forsyth: Deprecated

...

Xu: only used by SO?
James Forsyth: Used by anyone who wants to check it, set by SO

...

Xu: only used by SO?
James Forsyth: Not being used anymore, deprecated.

...

Xu: only used by VCE?
James Forsyth: Predates SDC modelling, deprecated

...

Xu: Need clarification on how this attribute is used.
James Forsyth: indicates who manages a specific resource, whether it's the service provider or a customer

...

Xu: Is this attribute mandatory? and applicable for all kinds of VNFs? (same question as VNFC instance model)
James Forsyth: Not mandatory, and it can be applicable for all kinds of VNFs, depending on the requirements of the VNF

...

Xu: same as above
James Forsyth: Not mandatory, and it can be applicable for all kinds of VNFs, depending on the requirements of the VNF

...

Xu: same as above
James Forsyth: Not mandatory, and it can be applicable for all kinds of VNFs, depending on the requirements of the VNF

...

Xu: same as above
James Forsyth: Not mandatory, and it can be applicable for all kinds of VNFs, depending on the requirements of the VNF

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: only used by uCPE?
James Forsyth: Yes

...

Xu: Is it used internally in AAI? can be omitted in the general model.
James Forsyth It's used internally in AAI to enforce concurrency control, other systems use it to pass to AAI on updates and delete operations

...

Xu: deprecated?
James Forsyth: Yes

...

Content:

Children Display

...

Xu: deprecated?
James Forsyth Yes

...

Xu: deprecated?
James Forsyth Yes

...

Xu: deprecated?
James Forsyth Yes

...

Xu: deprecated?
James Forsyth Yes

...

Xu: It seems to be used internally in AAI, need clarification on the usage of this attribute.
James Forsyth Deprecated, use model-version-id

...

Xu: Is it used internally in AAI? Can be omitted in general model
James Forsyth It's never been populated, yes can be omitted

...

Xu: Is it used internally in AAI? Can be omitted in general model
James Forsyth It's never been populated, yes can be omitted

...

Xu: Please clarify the usage of this attribute.
James Forsyth Has to do with routing, not applicable for all VNFs

...

Xu: What's the difference between vnf-type and nf-type?
James Forsyth - we are getting rid of vnf-type and replacing with nf-type, nf-function, and nf-role

...

Xu: what controller?
James Forsyth: Not sure if it's being populated

...

Xu: Is this attribute mandatory? and applicable for all kinds of VNFs?
James Forsyth There should be an edge to a network that has a gateway assigned to it, so this attribute should be deprecated

...

Xu: same as above
James Forsyth There should be an edge to a network that has a gateway assigned to it, so this attribute should be deprecated

...

Xu: only used by VCE?
James Forsyth Not sure

...

Xu: Is the description correct?
James Forsyth - The edge rules has the exhaustive list of possible relationships for generic-vnf

...

relationship with l-interface, availability-zone, lag-interface, l3-network, pserver, vserver, service-instance, vf-module, volume-group, vnfc and logical-link

...

"Y" indicates operator-supplied VNF instance target deployment node required. Present prompt to operator: "Enter target node for deployment of this VNF instance"

...

"Y" indicates operator-supplied VNF name required. Present prompt to operator: "Enter the name for this VNF instance"

...

Software version of the VNF. This is changed when there is any change to the software that is included in the VNF
Package.

...

Name to identify the VNF Product. Invariant for the VNF Product lifetime.

...

Identifier of the specific VNF Package on which the VNF is based.

...

Possible values: NOT_INSTANTIATED (VNF instance is terminated or not instantiated, and the identifier of the VNF instance exists), INSTANTIATED (VNF instance is instantiated).

...

Information specific to an instantiated VNF instance. Shall be present if the VNF is in INSTANTIATED instantiation state.

...

Additional VNF-specific metadata describing the VNF instance.

...

VNF-specific attributes that affect the lifecycle management of this VNF instance by the VNFM, or the lifecycle management scripts.

...

VNF Design Time Model

...

Human readable name for the VNF Product. Can change during the VNF Product lifetime.

...

Software version of the VNF. This is changed when there is any change to the
software that is included in the VNF Package.

...

Identifies VNFM(s) compatible with the VNF described in this version of the
VNFD.

...

Information about localization languages of the VNF (includes e.g. strings in the
VNFD).

...

Defines descriptors of virtual compute resources to be used by the VNF.

...

Defines descriptors of virtual storage resources to be used by the VNF.

...

Represents the type of network connectivity mandated by the VNF provider between two or more CPs which includes at least one internal CP.

...

Describes external interface(s) exposed by this VNF enabling connection with a VL.

...

Describes specific DF(s) of a VNF with specific requirements for capacity and
performance.

...

Describes the configurable properties of the VNF (e.g. related to auto scaling and
auto healing).

...

Describes the modifiable attributes of the VNF.

...

Includes a list of events and corresponding management scripts performed for the VNF.

...

Describes the associated elements (i.e. VDUs and/or VLs) of a VNFD for a certain purpose during VNF lifecycle management.

...

Declares the VNF indicators that are supported by this VNF.

...

Rule that determines when a scaling action needs to be triggered on a VNF
instance e.g. based on certain VNF indicator values or VNF indicator value
changes or a combination of VNF indicator value(s) and monitoring parameter(s).

...

PNF Run Time Model

...

PNF Design Time Model

...

Network Run Time Model

...