Rationale:
There are some updates of the AAI schema regarding the VNF instance model, and it's identified that VFC also has an internal inventory which stores information of the VNF instance.
Propose to have an analysis from the updated AAI schema and VFC inputs (and potential ETSI spec updates) to update the R3 VNF instance model in R4.
In addition, there's some leftover issues regarding the R3 VNF instance model needs to be resolved in R4 and there're some suggestions need to be taken from the service instance model discussion.
Source:
R3 model: R3 Resource Clean Draft (Papyrus Based) - 1.2.19 VNF
VFC: https://gerrit.onap.org/r/gitweb?p=vfc/gvnfm/vnflcm.git;a=blob;f=lcm/lcm/pub/database/models.py;h=3ac4a83274a16497877cde6fb3625318bd8540bb;hb=refs/heads/master - NfInstModel
Model Analysis:
| R3 Model | AAI Schema v15 | VFC | Description | Note | Belongs in | Action | Comment |
|---|---|---|---|---|---|---|---|
| vnfInstanceId | identifier of the VNF instance | ||||||
| vnfInstanceName | name of the VNF instance. Multiple names are possible. | ||||||
| vnfProductName | name to identify the VNF Product, invariant for the VNF Product lifetime | ||||||
| description | description of the VNF instance | ||||||
| vnfProvider | provider of the VNF model | ||||||
| vnfdId | identifier of the VNF model | ||||||
| vnfdVersion | version of the VNF model | ||||||
| vnfSoftwareVersion | Software version of the VNF. This is changed when there is any change to the software that is included in the VNF package | ||||||
onboardedVnfPkgInfoId | identifier of the specific VNF package on which the VNF instance is based | ||||||
| availabilityZone | availability zone information of the VNF instance | ||||||
| operationalStatus | indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. | ||||||
| orchestrationStatus | whether the VNF instance is instantiated | ||||||
| oamlpv4Address | oam ip address, ipv4 | ||||||
| oamlpv6Address | oam ip address, ipv6 | ||||||
| instantiatedVnfInfo | information specific to an instantiated VNF instance, e.g., vm information | ||||||
| inMaint | whether the VNF instance is in maintenance mode, if yes, DCAE will not observe alarms/traps, etc. | ||||||
| isClosedLoopDisabled | whether closed loop function is enabled | ||||||
| encryptedAccessFlag | whether this VNF is accessed using SSH | ||||||
| vnfConfigurableProperty | indicator for whether autoHeal and autoScale is enabled | ||||||
| nfNamingCode | String assigned to this model used for naming purpose. | ||||||
| vnfNamingPolicyId | Identifier of the policy which has the naming logic for this VNF instance | ||||||
| vnfHomingPolicyId | Identifier of the policy which provides homing conditions. | ||||||
| nfType | Generic description of the type of network function | ||||||
| nfFunction | English description of network function that the specific VNF deployment is providing. | ||||||
| nfRole | Role in the network this model will be providing | ||||||
| closedLoopStatus | Whether closed loop capabilities are enabled for this or not. | ||||||
| _nfc (vnfcinstance) | Relatonship to the NF components that are part of this VNF. | relationship | |||||
| _vnfd | Relationship to the VNF descriptor | relationship | |||||
| _vnfvirtuallink | Relationship to VnfVirtualLink | relationship | |||||