1        Introduction

Proposal for cloud infrastructure model for the Edge Automation Use Case.

See:  Edge Cloud Infrastructure Enablement in ONAP

The model displayed here tries to highlight both the differences and similarities of an Owner Operated (private) Cloud from the Public Cloud, from the perspective of an Information Model.   When the similarities and differences are well-understood, the attempt may be made to consolidate the classes into a single data model where a class may represent both the public and private cloud information elements.

2        Diagrams

2.1       Overview

Qualified Name: Infrastructure::Diagrams

Description:

The information elements for a public cloud.

A&AI: pserver

1.1.1       Diagrams

Open

Open

Open

1        ObjectClasses

1.1       Overview

Qualified Name: Infrastructure::ObjectClasses

1.1.1       Classes

1.1.1.1       APIEndPoint class

Qualified Name: Infrastructure::ObjectClasses::APIEndPoint

Applied Stereotypes:

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

1.1.1.2       CapacityMeasure class

Qualified Name: Infrastructure::ObjectClasses::CapacityMeasure

Description:

Total, used and available vCPUs, memory, local storage;

SR-IOV VFs?  E.g., in OpenStack, this is visible in the Compute API to users with the administrative role, and similarly may be visible in other owner-operated cloud implementations.   The compute node capacity measure can be rolled up to availability zone, or other levels of aggregation.

Applied Stereotypes:

• ·        Experimental

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

1.1.1.3       ComputeNode class

Qualified Name: Infrastructure::ObjectClasses::ComputeNode

Description:

This is the physical compute server, or in OpenStack parlance, a host.  These are visible in the OpenStack Compute API to users with the administrative role.   They may be similarly be visible in other implementations of an Owner-Operated Cloud.

Applied Stereotypes:

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

Table 4?1 Attributes for Class ComputeNode

1.1.1.4       LocalAvailabilityZone class

Qualified Name: Infrastructure::ObjectClasses::LocalAvailabilityZone

Description:

The physical data center may be partitioned into local availability zones, one or more per local control plane.

Applied Stereotypes:

• ·        Experimental

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

1.1.1.5       LocalControlPlane class

Qualified Name: Infrastructure::ObjectClasses::LocalControlPlane

Description:

The control plane for the data center may be local rather than remote.  The data center itself may be divided up among more than one local control plane.

Applied Stereotypes:

• ·        Experimental

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

Table 4?2 Attributes for Class LocalControlPlane

1.1.1.6       NetworkZone class

Qualified Name: Infrastructure::ObjectClasses::NetworkZone

Description:

Network Zone reflects the organization of the network fabric and the WAN edges of the data center.  Network Zone information goes beyond what e..g, OpenStack APIs expose to users with the administrative role; in fact, this information is not in OpenStack.  One can think of implementations where this information is made available from the cloud to ONAP for the purpose of very precise placement.

Applied Stereotypes:

• ·        Experimental

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

1.1.1.7       OwnerOperatedFederatedCloud class

Qualified Name: Infrastructure::ObjectClasses::OwnerOperatedFederatedCloud

Description:

The cloud provider (owner) may provide a federated view of the cloud data centers, e.g., provide global API endpoints.   To facilitate operation in the cloud, identity, authentication and authorization should be federated.

Applied Stereotypes:

• ·        OnapModelLifecycle

-        LifecycleState: INPUT

• ·        OpenModelClass

-        support:  MANDATORY

Table 4?3 Attributes for Class OwnerOperatedFederatedCloud