ONAP E2E Flow
`
vCPE Service
vCPE Servce
vBNG
2
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
vHGW
vRouter
E2E Steps in Lifecycle Management of VNF
Onboarding
3
Design
(involves Portal and SDC)
(involves Portal and SDC)
• Vendor provided VNFs &
VNF artifacts
• Analytics processing VNF
events
• Service Agnostic Control
loop templates design
• Service Design steps
including:
1. Instantiation
2. Performance and Fault
Management (Control
Loops)
3. Change Management
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
Runtime
(most ONAP
components)
Runtime steps:
1. Instantiation
2. Performance and Fault
Management (Control
Loops)
3. Change Management
Step 1: Onboarding
Using the VNF-SDK:
- get images, Heat files, various models from vendors
Onboard
VNFs
VNF-SDK
4
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
vCPE Servce
vBNG
vHGW
vRouter
Step 2: Service Design and
Distribution
vCPE
Service
Design
vCPE Policy
Creation
Service
Design
Policy Creation
Analytic
Application Design
Design Studio
Policy Editor
Analytics SDK
Resource Onboarding
Policy Rules
Certification Studio
Conflict Identification
Catalog
Policy Storage
Resource
Templates
SO
KPIs, Alarms,
Operators, etc.
Links to Artifacts
Artifact
Xi / n
Analytic
distribution
Applications
Library
Y=
Recipe/Engineering Rules & Policy Distribution
(metadata artifacts/recipes)
SDC
Not a one time activity – happens whenever
the service is modified/enhanced
5
vHGW
vRouter
vCPE
Analytics
Design
Library
Recipes & Eng. Rules
vBNG
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
DMaaP
---- ---------Product
------- -------Process
Service
vCPE Servce
DCAE
A&AI
Controllers
Controllers
Controllers
Step 3: Customer Order
External to ONAP
6
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
vCPE Servce
vBNG
vHGW
vRouter
Step 4.1: Instantiation and
Chaining
vCPE Servce
vBNG
0
From
SDC
vCPE
BPELs
0.5
Heat
Instantiation
Request
vCPE
Resources
assignments
2
Create virtual
machines
Infrastructure
7
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
5
vCE
vCE
VMs
Create virtual
networks
6
vBNG
7
Create
Objects
Update
Objects
From
SDC
A&AI
Inventory
From
SDC
3
OpenStack
1
Homing/placement
Function
SDNC
From
SDC
vRouter
vCPE
orchestration request
SO
4
vHGW
vHGW
vRouter
Update/create
Objects
DCAE
Step 4.2: Configuration and
Activation
vCPE Servce
vBNG
vHGW
vRouter
Service is
active
17
From
SDC
Inventory
update
SO
11
From
SDC
A&AI
Inventory
12
8
vCPE is up
and running
16
13
15
Event System
Configure
resources
Inventory
read
vCPE is monitored
5
Controller
From
SDC
9
From
SDC
VNFs configuration
& control
Inventory
update
DCAE
10
14
vCE
vCE
VMs
vBNG
vHGW
vRouter
From
SDC
8
Information Security Level 2 – Sensitive
© 2017 – Proprietary & Confidential Information of Amdocs
Local telemetry
collection &
Analysis
Local
DCAE
Control Loop Flow (Design time – Fault Management)
SO
9
Onboard VNF (vBNG)
create service
1
Distribute
Service Update
Create CL template
2
8
9
A&AI
3
SDC
Advance change
toward distribution
Distribute
Service Update
9
Query template
services,
VNFs 4
5
User configures
template
11
User can control
Start/stop/update
7
Upload Blueprint
and Locations File
as artifacts
6
Create and activate
Configuration policies,
Operation policies
Policy
Engine
DCAE Inventory
DCAE
CL Runtime statistics
Reporting, etc.
Get alarm files
Distribute
CL blueprint
(Tosca)
Distribution
Client
Control Loop
Dashboard
SDC : Control Loop
Designer/cockpit
10
DCAE Service Type for CL
is pushed to Inventory
Control Loop
Runtime
A&AI trigger
Or
MSO
CL Runtime
Cockpit &
Dashboard
ONAP
Portal
Dispatcher API
Inventory API
DCAE
Orchestrator
Inventory
Orchestration
DMaaP
Controller
DCAE
Controller
Policy API
DCAE Central
APIs
Policy
Engine
DMaaP
Local
CL Flow
Execution
Event
Normalizer
Fault
Management
Microservice
Docker Server
CDAP Cluster
SNMP Trap
Collector
A&AI
Microservice
Restart VM
Docker Server
Docker Server
NTC
OpenStack
Source VF:
vBNG
10
10
DCAE Edge
FTL
App-C
Restart VM
CM Process Design
SDC (catalog)
Onboard component
capabilities
CM Building Blocks in Catalog
•
DCAE micro-services, A&AI APIs, Controller
capabilities (e.g., health check APIs),
scripts/workflows.
A&AI
DCAE
Controllers
CM Designer
•
Modular composition to stitch different building
blocks into a workflow (using a visual designer)
e.g., In-place software upgrade, Build and
Replace.
SDC (CM Designer)
SDC (CM catalog)
Change Management Scheduling & Conflict Avoidance
ONAP Portal
CM Schedule Optimizer
Create a schedule/plan for rolling out
a change such that we minimize
service disruption during the change
within the specific completion time
Dependency modeling
•
•
•
•
Conflict scoping
Service Impact scoping
Execution ordering
5
6
Tracking/
Notification
OSS
•
4
3
CM Portal
1
7
CM schedule
optimizer
3
DCAE
Orchestrator
2
3
A&AI
Policy
1 – Send workflow, VNF list and time range to schedule optimizer
2 – Request constraints for scheduling
3 – Request data for optimal schedule
4 – Identify CM schedule
5 – Provide the schedule for approval
6 – Once approved, send the schedule to Change tracking/notification OSS.
7 – Push the approved change schedule for execution
Change Execution
ONAP Portal
CM Portal
**
Orchestration Execution:
•
Execute the orchestration building blocks and
use RESTAPIs to interface controller for
software upgrade, or A&AI for updates to the
CM flag
ONAP Portal:
• Track status of CM workflow execution –
success/failure status of each building block
• Intercept CM workflow execution –
pause/resume functions, and ability to inject
new steps in the workflow
Pre / Post Analytics:
• Performance analytics – pre/post performance
comparisons, go/no-go decisions for networkwide deployment
2b
Orchestration
2
1
Policy
7
5 6
3
4
8
7b
A&AI
DCAE
Controller
1 – Start execution based on schedule
2 – Conflict check
2b – Check roll-out status
3 – (Pre) health check
4 – Update CM flag
5 – VNF upgrade
6 – (Post) health check
7 – Pre/post impact analysis
7b – Fallback (possibly)
8 – Update CM flag
** – Status tracking and pause/resume execution at any/all times