Defining ONAP VNF Package Model
30 June 2017
Andrew J. Mayer,
Ph.D.
© 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.
What
Develop a common VNF Package Model (information model &
TOSCA representation) for ONAP which will allow Service
Providers to rapidly integrate VNFs into ONAP so that
they can rapidly introduce capabilities to their
E – Services
BSS / OSS
Big
customers
and
within their infrastructure
ONAP
Architecture
Data
ONAP Portal
Dashboard
OA&M
Operation
Administrati
on
&
Maintenance
Recipe/Engineer
ing Rules &
Policy
Distribution
Service Design & Creation
Policy Creation
Analytic Application
Design
Design Functions
External Data Movement & APIs
Active &
Available
Inventory
Service
Orchestrator
Common Services, Data Movement, Access Control & APIs
Data Collection &
Analytics
Operational Functions
ONAP
Controlle
r
Storage
Compute
Networking
VNFs / Applications
Controllers
Engineering Rules
& Inventory
Why
•
•
•
•
•
Service Providers need to provide a clear and unambiguous
abstraction of the Network Cloud so that VNFs can describe
their infrastructure requirements in a common and
consistent fashion.
Service Providers want to rapidly integrate VNFs into ONAP
so that they can rapidly introduce capabilities to their
customers and within their infrastructure.
Service Providers want to manage the entire lifecycle of
VNFs within ONAP in a common way so that they can ensure
orchestration, manageability and control of each VNF in an
easily integratable and low cost way.
VNF Providers we want to know how to package and implement
VNFs for any Network Cloud so VNF Providers can minimize
cost and maximize value.
Model Driven approach: a cohesive way to have a shared view
of information describing the VNF Package that can be used
as input into a model driven process to enable automated
on-boarding and lifecycle management of VNFs into the ONAP
VNF SDK Project
VNF Package Model Within VNF SDK Project
VNF Package Initial Scope for Release 1
Related ONAP Projects
•
•
•
•
•
•
•
•
•
VNF-SDK: VNF Package Creation
VNF-SDK: VNF Package Validation
VNF Requirements Project
VNF Validation Program (ONAP ICE)
Modeling Sub-committee
SD&C Project
Policy Project
Standards Coordination
Other projects that use VNF Package Info (APP-C,
VF-C, DC&A, etc.)
High Level Project Plan For Release 1
Focus: Technical Requirements, Resource Metadata,
Business Information, Fault and Performance
1. Analysis of current VNF Package Models and
Requirements
2. Refine High Level Mindmap
3. Define UML Information Model for VNF Package
(reuse existing models where appropriate, e.g.
core node types from OASIS)
4. Define TOSCA Representation (build from OASIS
effort)
Time Line
M1
ProjectProject
12 June Scope
29 June
M2
M3
Functional
API
ity
24 August
3 August
Related Industry Activities
•
•
•
•
•
•
•
•
•
•
ETSI VNF Packaging Information Model
OPNFV On-Boarding
TM Forum ZOOM
TM Forum Multi-Provider VF On-boarding
ONAP VNF Requirements (particularly ECOMP & HEAT)
ONAP Open-O VNF Management Requirements & TOSCA
Template
Open-O VNF Template
OASIS VNF Profiles
MEF TOSCA Guidelines
OSM (VNF Wizard, YANG)
VNF Package Mindmap (high level)
class VNF On-boarding
VMFlav orSeries
AICNodeDescription
-
HostProfile
UML Model (example)
-
cpuPinning: int
cpuRatio: int
dPDKvRouter: int
hugePages: int
hyperThreading: int
kernelvRouter: int
kvmLiveMigration: int
numaAlignment: int
srIOV: int
tenantDataTraffic: int
tenantOamTraffic: int
vCPUOvercommitRatio: int
ResourceMetadata
-
category: string
invariantUUID: string
lastUpdaterAttUid: string
lifecycleState: string
name: string
resourceType: string
subcategory: string
toscaModelURL: string
uuid: string
version: string
VMFlav or
-
VNFStorageMetadata
-
description: int
name: string
nodeAffinity: int
bootPlusEphemeralDiskPerVMSize: int
iOOperations: int
sharedVfStorageSpacePerVMBlock: int
vfStorageSpacePerVFObject: int
vfStorageSpacePerVMCinder: int
ephemeralStorageSize: int
isPublic: boolean
metadata: string
name: string
numaOverrideOptions: int
numOfvCPUs: int
ramSize: int
rootDiskSize: int
storageOptions: int
swapSpace: int
VNFOperationsMetadata
VNFMetadata
-
specializedVirtualizationFeatures: int
qaasMetadata
VNFComputeMetadata
-
additionalHypervisorDrivers: int
affinityGroups: int
aicOrSelfManagedImage: int
antiAffinityGroups: int
availabilityZones: int
cpuOversubscription: int
creationTimeTasks: string
guestOperatingSystem: int
hostAggregateZones: int
hotSpecifications: int
imageSize: int
isMultiRegionalVF: boolean
maximumNumberVMs: int
memoryPerVM: int
minimumNumberVMs: int
numberGuestVCPUsPerVM: int
preferredHypervisor: int
scalingTimeTasks: string
vfDependencies: int
-
numberOfClientVMs: int
numberOfQueues: int
quotaNeeded: int
VNFFirew allMetadata
-
VNFNetw orkMetadata
-
accessControlFiltering: int [1..*] {sequence}
hypervisorLevelNetworkAdjacency: int
intelDPDK: int
ipAddressingPlan: int
jumboFrames: int
networkingInterfacesPerVM: int
networkIpAddressingScheme: int
sR-IOV: int
application: int
dedicatedOrShared: int
destinationIP: int
destinationNode: int
destinationPort: int
direction: int
protocol: int
sourceIP: int
sourceNode: int
VNFLoadBalancingMetadata
VNFVnicMetadata
-
Name:
Author:
Version:
Created:
Updated:
12
VNF On-boarding
am803u
1.0
10/28/2016 12:00:00 AM
11/15/2016 12:10:09 PM
externalNetworkConnectivity: int
ipVersions: int
protocolsUsed: int
trafficPurpose: int
-
clientPersistence: int
healthCheck: int
healthCheckTimer: int
ipVersions: int
iRULEDevelopment: int
knowClientSourceIPAddress: int
lbAlgorithm: int
lbProfile: int
listenPort: int
poolMembers: int
poolName: int
protocol: int
virtualServerIP: int
virtualServerName: int
TOSCA (Example)
BACKUP MATERIAL
14
© 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.