...
IM Table Format
attribute table
| attribute name | cardinality | data type | constraint | description | provider | consumer | note |
|---|---|---|---|---|---|---|---|
| name of the attribute | allowed range of occurrence, format: an exact number, or min...max | data type of the attribute | usage constraint | description of the attribute | who provides the value of the attribute | who consumes the value of the attribute | note, reference, comment, etc... |
| (example) | |||||||
| vnfdInvariantId | 1 | invariant identifier of the VNF model | vendor | SDC, AAI? | SDC: invariantUUID | ||
| vnfName | 0..1 | name of the VNF | vendor | SDC, AAI? | SDC: nf_naming, ETSI IFA011v231: vnfProductName | ||
| vnfdVersion | 1 | version of the VNF model | vendor | SDC, AAI? | SDC: version, ETSI IFA011v231: vnfdVersion |
relationship table
| class name | relationship | source/target | cardinality |
|---|---|---|---|
| name of the class | category of the relationship, e.g., association, generalization | whether the described class is source or target of this relationship | allowed range of occurrence, format: an exact number, or min...max |
| (example) | |||
| VnfcDesc | association | target | 1..N |
| VnfVlDesc | association | target | 1..N |
NFC/VNFC Run Time Model
| AAI (aai_schema_v11 vnfc) | ECOMP IM (VNFC Instance) | ETSI IFA008 (VnfcInfo) | Comment | Description |
|---|---|---|---|---|
| orchestration-status | vnfcState | Xu Yang: Is it the same as vnfcState (i.e., start or stop)? Xu Yang: vnfcState describes the state of a VNFC instance, possible values are: STARTED, STOPPED. STARTED means the VNFC instance is up and running, and STOPPED means the VNFC instance has been shut down (but not terminated/deleted). Similar to the VM power on/off concept. | Orchestration status of this VNF, mastered by APP-C | |
| group-notation | Xu Yang: need further clarification on how this attribute is used | Group notation of VNFC | ||
| model-version-id | the SDC model version for this resource model | |||
| relationship-list | association (VM, Docker, LXC) | AAI: relationship with vserver, vf-module and generic-vnf |
...
| AAI (generic_vnf) | ECOMP IM (VNF instance) | ETSI IFA007 (VnfInfo) | Comment | Description |
|---|---|---|---|---|
| orchestration-status | Xu Yang: only used by SO? Xu Yang: could you elaborate more on the valid values and their meaning? | Orchestration status of this VNF, used by SO. | ||
| management-option | Xu Yang: Need clarification on how this attribute is used. | identifier of managed by service provider or customer | ||
| ipv4-loopback0-address | Xu Yang: same as above | v4 Loopback address | ||
| nm-lan-v6-address | Xu Yang: same as above | v6 Loopback address | ||
| vcpu | Xu Yang: only used by uCPE? | number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE | ||
| vcpu-units | Xu Yang: only used by uCPE? | units associated with vcpu, used for VNFs with no vservers/flavors, to be used only by uCPE | ||
| vmemory | Xu Yang: only used by uCPE? | number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE | ||
| vmemory-units | Xu Yang: only used by uCPE? | units associated with vmemory, used for VNFs with no vservers/flavors, to be used only by uCPE | ||
| vdisk | Xu Yang: only used by uCPE? | number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only uCPE | ||
| vdisk-units | Xu Yang: only used by uCPE? | units associated with vdisk, used for VNFs with no vservers/flavors, to be used only by uCPE | ||
| resource-version | Xu Yang: Is it used internally in AAI? can be omitted in the general model. | Used for optimistic concurrency. Must be empty on create, valid on update and delete. | ||
| model-customization-id | captures the id of all the configuration used to customize the resource for the service | |||
| as-number | Xu Yang: Please clarify the usage of this attribute. | as-number of the VNF | ||
| regional-resource-subzone | Regional way of organizing pservers, source of truth should define values | |||
| nf-type | Xu Yang: What's the difference between vnf-type and nf-type? | Generic description of the type of NF | ||
| nf-role | NetworkRole | role in the network that this model will be providing | ||
| selflink | Xu Yang: what controller? | Path to the controller object | ||
| vlan-id-outer | Xu Yang: only used by VCE? | Temporary location for S-TAG to get to VCE | ||
| nm-profile-name | Network Management profile of this VNF | |||
| relationship-list | Xu Yang: Is the description correct? | relationship with l-interface, availability-zone, lag-interface, l3-network, pserver, vserver, service-instance, vf-module, volume-group, vnfc and logical-link | ||
| l-interfaces | logical interfaces | |||
| lag-interfaces | Collection of link aggregate interfaces | |||
| vf-modules | a deployment unit of VNFCs | |||
| licenses | license information | |||
| entitlements | entitlement information | |||
| HomingPolicy | Reference to VNF-level homing policy that ECOMP will use when VNF deployment target node is auto-selected | |||
| TargetNodePrompt | "Y" indicates operator-supplied VNF instance target deployment node required. Present prompt to operator: "Enter target node for deployment of this VNF instance" "N" indicates that the target deployment node for this VNF instance will be auto-selected by ECOMP | |||
| VLAN Range Plan | Identifies the VNF-level VLAN Range Plan that must be used by ECOMP to assign VLAN tags to an instance of this VNF type | |||
| VNF Name Prompt | "Y" indicates operator-supplied VNF name required. Present prompt to operator: "Enter the name for this VNF instance" "N" indicates that the name for the VNF instance will be auto-generated by ECOMP | |||
| VNF Naming Policy | Reference to VNF-level naming policy that ECOMP will use when VNF-level name is auto-generated | |||
| VNF Network Tag | Must correlate to the set of defined “network-role” identifiers from the associated HEAT templates | |||
| metadata | Additional VNF-specific metadata describing the VNF instance. | |||
| extension | VNF-specific attributes that affect the lifecycle management of this VNF instance by the VNFM, or the lifecycle management scripts. |
VNF Design Time Model
...
ONAP VNFD IM - based on IFA011 v231.docx
ONAP VNFD IM draft based on IFA011 v231 format and models: for discussion
...
Xu Yang: need clarfication on how this attribute is used.
...
Describes specific DF(s) of a VNF with specific requirements for capacity and
performance.
...
Describes the modifiable attributes of the VNF.
...
ExternalVirtualLink Design Time Mode
...