The document summarizes a demonstration by Red Hat at the OPNFV Summit 2016 of using ManageIQ, an open source cloud management platform, to build an NFV orchestrator (NFVO) capable of orchestrating network services across multiple virtualized infrastructure managers (VIMs), sites, and technologies. The demo showed deployment of an IMS network service spanning OpenStack, AWS, and Kubernetes environments to illustrate ManageIQ's potential as a carrier-grade cloud management and NFV orchestration platform.

1. 1
OPNFV Summit 2016 Demo
NFVO based on ManageIQ,
a Cloud Management Platform (CMP)
Red Hat
6/17/2016

2. 2
During OPNFV 2016, Red Hat demonstrated how ManageIQ could be
used to build an open source carrier-class Cloud Management Platform
(CMP), including NFV Orchestrator (NFVO) capabilities, that supports
orchestration/automation of modern cloud-native applications as well as
network services that require specific telco features.
Please read blog
Join Red Hat to create a truly open source automation solution
● http://verticalindustriesblog.redhat.com/join-red-hat-to-create-a-truly-open-source-automat
ion-solution/
●

3. 3
Outline
●
Demo Overview and Scope
●
NFV MANO vs. Cloud Management Platforms
●
Demo Applications
●
Demo Management Architecture Overview
●
Demo !
●
Call to action

4. 4
Demo Overview
•
Demonstrate network service deployment in
•
multi-VIM (RHT OpenStack & AWS),
•
multi-technology (VMs & containers), and
•
multi-site (OPNFV, RHT Raleigh, AWS East) scenario
•
ManageIQ as NFVO, integrating management of:
•
OpenStack cloud, Tacker as G-VNFM
•
AWS cloud (managed through AWS APIs)
•
Kubernetes + Docker containers in VMs in AWS,
managed through OpenShift integration
•
Ansible for integrated configuration management

5. 5
Demo in ETSI NFV Architecture Context
Focus
of Demo
Included
in Demo
Not
Included
EM-NBI
(application specific)
VNF-EM (internal)

6. 6
Gartner Cloud Management Platform (CMP)
Reference Architecture
General Cloud Management Platform needs:
●
Legacy Integration, extensibility
●
Platform scalability and high availability
●
Heterogeneous clouds w/ multi-site support,
●
Multi-VIM (e.g. OpenStack, VmWare),
●
Multi-cloud (e.g. AWS, GCE, Azure, …),
●
Multi-tech (MaaS, VMs, containers),
●
Full-Stack Integration,
●
Common information model
●
Inventory management (available and allocated res.)
●
Compute Centric (needs network integration)
●
Workflow automation, policy based management
●
Performance, SLAs → service assurance
●
Service Availability; “enterprise class”
●
Security management
●
Service Agility,
●
DevOps, CI/CD flows integration
●
End User's Service ←IaaS/PaaS+VF+VF configs
The leading open source Cloud
Management Platform & community=

7. 7
NS-LCM
VNF-LCM
MANO and CMP requirements are similar
NFV / MANO requires most things that CMP requires
Key additional requirements from MANO:
●
MANO is Network Centric (but needs compute)
●
NFV specific features in descriptors etc. (e.g TOSCA for NFV / EPA extensions)
●
End User's Service ← IaaS/PaaS+pNFs+vNFs+pvNF configs (physical & virtual NF mixes)
●
Network service quality (SLA) assurance
●
Service Availability and continuity → “carrier grade”

8. 8
IMS
Demo connectivity and management overview
The
Internet
The
Internet
IMS
OPNFV Summit (Berlin) Red Hat (Raleigh, NC) AWS (US-East)
VPN tunnel associations

9. 9
IMS
Demo application - call & media flows
IMS
Red Hat (Raleigh, NC) AWS (US-East)
Signaling transaction flows
Call bearer flows (media)
VPN tunnel associations
OPNFV Summit (Berlin)
The
Internet

10. 10
NFV + Container = NFC （ Network Function Containerization ）
• Fast: e.g. IMS core network Deployed in 30s, and launched in less than 10s
• Elastic: Auto scaling of CSCF(Call Session Control Function) Pod
• High Performance: light-weight virtualization
Project Overview
• Network function deployed with Docker containers on Openshift/Kubernetes Platform
2015, China Mobile proposed NFC concept

11. 11
Call to Action
●
Check out more info on our Blog
– http://verticalindustriesblog.redhat.com/join-red-hat-to-create-a-t
ruly-open-source-automation-solution/
–
●
Provide feedback on our demo approach
– nfv@manageiq.org
●
Join ManageIQ community (NFV Orchestration)
– http://manageiq.org/
●
Join OpenShift community (Containers / DevOps)
●
www.openshift.org/

12. 12
Openshif
Node Master
Containerized IT ApplicationContainerized Network Function
Containerized ICT Integration PoC Architecture
Docker
Container
Docker
Container
Host OSHost OS
ComputeCompute StorageStorage NetworkNetwork
Docker
Container
Docker
Container
Docker
Container
Docker
Container
CSCFCSCF TASTAS HSSHSS CTFCTF hadoophadoop Text
Search
Text
Search
Text
Search
Text
Search
SchedulerScheduler
ManagementManagement
AuthenticationAuthentication
• vIMS(clearwater) and IT applications shared resources on Openshift Platform
• IMS phone calls can be made while IT application running
hadoophadoopXDMSXDMS
March 2016, China Mobile and Red Hat implemented PoC

13. 13
Containerized ICT Integration PoC Demo
• Elastic expansion and auto scaling while IMS phone call
Pod Number (vIMS vs. IT application)
CPU usage (vIMS vs. IT application)

14. 14
Demo components in NFV Architecture context
EM-NBI
(application
specific)
Application
Config Management
Tacker
G-VNFM
(VMs)
VNFs (VM):
“VNFM”
(Containers)
Container Mgmt. Integration
NSD VNFD
VNF (container):
VNF and NS descriptors based on current TOSCA
NFV Drafts, aligned with ETSI std. direction

15. 15
IMS
Key management relationships in demo
IMS
Red Hat cloud (Raleigh, NC) AWS (US-East)
Tacker
(G-VNFM)
VNF(VM)VNF(VM)VNF(VM) VNF(VM)
VNF(Containers in VMs)
HOT
HOT,APIs,SW
images
Or-Vnfm
Or-Vi
Vi-Vnfm
Nf-Vi
APIs, VNFDs
Associated ETSI NFV arch. reference point
Ref. point or technology not (yet) covered by ETSI NFV
Or-Vi
NFVI
EM-NBI
Or-Vi [containers]
VNFDs
CF, APIs, SW images
NSDs

16. 16
Demo High Level Flow
●
Deploy Network Topology & Applications (VNFs)
●
NSD, VNFDs, and SW images in associated catalogs
●
Deploy NSD scenario from ManageIQ
●
Application configuration
●
Initial config automated w/ ManageIQ & Ansible
●
Show mgmnt operations in MiQ+OpenStack+OpenShift
●
Connect clients to created network through VPN tunnels
●
Do a Zoiper call demo to show that it all works
●
Terminate network service (and remove deployed stuff)