Versions Compared

Old Version 10

changes.mady.by.user Anatoly Katzman

Saved on

compared with

New Version 11

changes.mady.by.user Anatoly Katzman

Saved on

Key

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

In the Info Model, the VDU element combines 2 aspects: application logic and expectations of the underlying infrastructure.

The Data Model implements the IM VDU element as a pair of related resources:

  1. VFC - an ONAP resource that represents a piece of application-level logic and includes:
    1. a requirement for hosting by a container
    2. a software image to launch the application logic on the container
    3. a free set of application-level requirements and capabilities
  2. Container - an ONAP resource that represents a unit of infrastructure allocation. It expresses the following ideas:
    1. a "hardware shopping list" - in the terms of TOSCA requirements, which are based on specially designed TOSCA capability types
    2. a software image that the Orchestrator uses to launch such a unit - by means of a TOSCA artifact 
    3. an ability to host application logic - modeled as a TOSCA capability of a special capability type
Note
titleNew name for "VDU"

ETSI & ONAP Info Models: VDU is a deployment unit; includes a piece of application logic (VFC) and requirements for infrastructure resources

Data Model: a narrower definition of VDU; it is very infrastructure-oriented, all that application has been shifted to the VFC resource. So maybe we find another name for this infrastructure-level resource in the Data Model. What would it be: Container? Hosting? anything else?

After the renaming, IM VDU --> ONAP VFC+"Container"

VDU is a special resource that represents an infrastructure-level unit of execution environment, carrying the following functions:

...


Code Block
titleONAP Data Model Normatives
linenumberstrue
collapsetrue
node_types:
  # the very base of the hierarchy of VDU types
  onap.nodes.VDU:
    derived_from: onap.nodes.Resource
    artifacts:
      vdu_image:
        type: tosca.artifacts.Deployment
        description: an image used to launch the VDU
    interfaces:
      Standard:
        start: 
          implementation: vdu_image
    capabilities:
      host:
        type: tosca.capabilities.Container  # the TOSCA Specs type is good enough
        occurrences: [0..UNBOUNDED]
    requirements:
      - cpu:
          capability: onap.capabilities.infrastructure.CPU:
          occurrences: [0..1]
      - memory:
          capability: onap.capabilities.infrastructure.Memory:
          occurrences: [0..UNBOUNDED]
      - storage:
          capability: onap.capabilities.infrastructure.Storage:
          occurrences: [0..UNBOUNDED]
      - io:
          capability: onap.capabilities.infrastructure.IO:
          occurrences: [0..UNBOUNDED]
      - nic:
          capability: onap.capabilities.infrastructure.NIC:
          occurrences: [0..UNBOUNDED]

...