ONAP is a platform which helps to Orchestrate the VNFs and providing the service assurance functionality to the deployed VNFs. On the other hand, most of the telcos prefer to position their VNFs on their Openstack powered data centers rather than public clouds. This brings to an interesting place where ONAP has to depend on most of the functionalities related to deployment on the Openstack. In this session, we will unfold the interesting features of using Openstack projects to deploy VNFs and provide closed loop functionality in ONAP. As part of this we will show: Usage of Openstack Tacker project as a VNF manager to ONAP. This brings loads to interesting features to the table, for example, SFC, auto scaleout, HPA support. It is a perfect example for GVNFM. Usage of Zun project to orchestrate CNFs. Here we will show how we can add zun plugin to multicloud project to achieve this functionality. Usage of Openstack based monitoring tools to be a part of Closed Loop functionality.

1. Bring the benefits of OpenStack
Landscape to ONAP
Bharath Thiruveedula – Verizon India, Tacker , VF-C (ONAP) Core
Trinath Somanchi - F5 Networks India, PTL OVN4NFV, OPNFV
Dharmendra Kushwaha – NEC India, PTL Tacker, Openstack
01.05.2019

2. Overview
What is ONAP ? and its Architecture
ONAP 101
Introduce to ONAP subsystems
Integration with Tacker as VNFM
Benefits of integrating Tacker with ONAP
Closed loop Functionality
CLF with OpenStack
OpenStack landscape for ONAP
OpenStack projects that support ONAP to realize its usecases.
OpenInfra with ONAP
StarlingX
Agenda

3. What is ONAP?
ONAP provides a comprehensive platform for real-time, policy-
driven orchestration and automation of physical and virtual
network functions that will enable software, network, IT and cloud
providers and developers to rapidly automate new services and
support complete lifecycle management
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

4. ONAP 101
Understanding ONAP

5. All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

6. Design Time
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

7. Run Time
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

8. Main Subsystems of ONAP
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

9. Service Orchestrator (SO)
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

10. VNFM in ONAP
• Virtual Functional Controller(VF-C) supports
both Specific and Generic VNF managers.
• Generic VNF Manager talks to Openstack via
multicloud project
• As of Casablanca release, VF-C supports Nokia,
Huawei and ZTE Specific VNF Managers
Network Service
Life Cycle Management
Nokia Specific-VNFM Plugin
Huawei Specific VNFM Plugin
ZTE Specific VNFM Plugin
Generic VNFM Plugin
Generic VNFM
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

11. Service Assurance Subsystem
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

12. Can I add Tacker to ONAP ?
• SOL 003 support in ONAP
• From Casablanca release, ONAP support SOL 003 interfaces to talk to external
VNF Managers.
• In the Dublin, SO project also supports SOL 003 adapter.
• Tacker can be integrated with ONAP using VFC Tacker Plugin to convert SOL
003 calls to tacker APIs
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

13. What is the benefit of integrating
with Tacker?
Except for the inventory we don't have to rely on the huge service assurance systems of ONAP.
Tacker understands TOSCA based policies and provide the closed loop functionality out of the box from the openstack using
gnochhi and aodh.
Don't have to send the telemetry data of the VNFs to the centralised servers like DCAE VES collector.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

14. Service Assurance
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

15. Can I get Service function chaining
from Tacker?
• SOL 005 support in ONAP
• The answer is no, as VNFM world is limited its own Network functions.
• In that case, we have to use Tacker as NFVO.
• In Dublin release, ONAP supports SOL 005 interface and registration of
external NFVO.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

16. OpenStack landscape for ONAP
Bringing the benefits

17. OpenStack Landscape - Overview
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

18. OpenStack benefits for ONAP
• OpenStack is a common Virtual Infrastructure Manager in any of the OpenSource
communities solving public/Private/Hybrid/Multi/Telco cloud challenges.
• With very vast scope of participating projects and differentiating solutions, OpenStack
is a default VIM solution.
• Kubernetes with OpenStack best complement the scenarios and usecase designs.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

19. Neutron - Stitching the cloud fabric
Number of ONAP usecases depend on different network requirements.
Programmable Edge to Cloud networking fabric
SDN Controller integrations, Overlay networks and SR-IOV networking is a requirement to move in speed in multi cloud deployments.
Neutron – Software Defined Fabric for different ONAP usecases. Ex: vCPE, Service Function Chaining, Container Networking (kuryr)
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

20. An overview of ONAP Usecases
Amsterdam
Residential vCPE
vVOLTE
vFirewall
Beijing
Hardware Platform awareness
enablement.
Network Function Change
Management.
VNF & Network services
manual scaling.
Casablanca
Cross Domain and Cross Layer
VPN.
Laying the foundation of 5G
support (PNFs – TOSCA,
Relatime monitoring).
Platform enhancements (Auto
Scaling support, Centralized
Representation and
Identification of Cloud regions.
Future
Releases
Use case enhancements (NFV
Edge management, Use case
improvements)
Foundations for 5G Support
(Network Slicing, NETCONF
support).
Containerized workloads in
multiple cloud regions.
.. Many more..
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

21. vCPE Usecase – An Example

22. Neutron for ONAP – 5G Network
Slicing use cases
The following features in Neutron enable it for ONAP usecase – 5G Network Slicing.
• Networking-(SFC, BGPVPN, OVN etc..) - Steer the traffic.
• QoS - Policies built with rules - Applied to Port of Network.
• GBP - “Network service chaining is a key capability of Group-Based Policy (GBP) that
describes the requirements for ordered chains of services by separating out network-
specific policies from service-specific details”.
• Octavia - Operator-grade scalable Loadbalancer.
• RBAC - Share ‘objects’ → a network between tenants.
• Common Classification Framework - Centralize common classifications of traffic, for
example networking-sfc, fwaas, others classify traffic
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.
https://www.f5.com/pdf/solution-center/f5-solutions-for-the-emerging-5g-landscape.pdf
https://www.f5.com/content/dam/f5/corp/global/pdf/solution-center/network-functions-virtualization-nfv-solution-overview.pdf

23. Senlin – A bridge between Orchestrator with OpenStack
• Instantiation, Start, Stop, Reboot, Realize,
live-migrate..
• Upgrade/Downgrade (support green/blue
model)
• Scale in/out
• Health check/recover
• Plugin framework for different backends
• Support VDU.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

24. Senlin – Cluster management service
• Senlin is a cluster management
service in openstack
• Supports heat resources. So
that Service Orchestrator can
create Senlin resources while
deploying VF Modules
• Using monitoring solutions, we
can expand(Scale in) or
Shrink(Scale out) the cluster
resources(VNF) and provide the
closed loop functionality
profile:
type: OS::Senlin::Profile
properties:
type: os.nova.server-1.0
properties:
flavor: {get_param: flavor}
image: {get_param: image}
key_name: {get_param: key_name}
networks:
- network: {get_param: network}
security_groups:
- {get_resource: security_group}
cluster:
type: OS::Senlin::Cluster
properties:
desired_capacity: 2
min_size: 2
profile: {get_resource: profile}
Example Heat Template with Senlin
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

25. Aodh – Data Collection Services
• We can make use of Ceilometer for the collection of metrics from the VNF similar to the role of VES collector.
• Gnocchi helps to store the metrics in time series fashion
• Like policy, Aodh can trigger the actions to when the alarm was raised.
Now we enforce Closed Loop Functionality
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

26. Zun – Container management
Zun manages container
as a kind of openstack
resource, and integrates
other services of
openstack, to provide
users with a unified and
simplified API.
Users can create and
manage containers
through the API, and do
not need to consider the
differences among
different container
technologies.
Zun has been integrated
with multiple openstack
services. Keystone,
neutron and kuryr-
libnetwork are necessary
services for running zun.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

27. Advantages of using Zun in ONAP
Users can extend the functions of container with the help of
OpenStack’s existing functions.
IP address assigned by Neutron and can use the authentication service provided
by Keystone. Working with Neutron - isolated network environment where the
Nova instance is located and Neutron functions (security group, QoS).
Persistent volume for the container - Zun integrates with OpenStack Cinder.
For orchestration, Zun uses an external orchestration
system for this purpose, such as Heat and Kubernetes.
With Heat, users can also define resources consisting of container resources and
OpenStack resources, such as Neutron load balancer, floating IP, Nova instance,
and more.
Kubernetes as the orchestration layer, and Kubernetes will use OpenStack Zun to
provide the “Serverless” container.
Container and Capsule kind of implementation.
Container is responsible for integrating Docker or other container engine
technologies. The concept of Capsule is a bit like Kubernetes Pod, which
represents a group of containers.
Capsule is used to group multiple containers that need to work closely with each
other to achieve service goals.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

28. OpenInfra and ONAP - StarlingX
ONAP is a Huge deployment ( ~ 200 containers).
ONAP Edge usecases can use StarlingX.
OOM with StarlingX.
• STX based K8S deployment
• ONAP in K8S cluster deployed by OpenStack using STX.
Why StarlingX for ONAP ?
• A fully featured cloud for distributed Edge.
• Builds on existing services in the open source ecosystem by taking
components of cutting edge projects such as Ceph, OpenStack and
Kubernetes and complementing them with new services like
configuration and fault management with focus on key requirements as
high availability (HA), quality of service (QoS), performance and low
latency.
• The Code is already pushed to multi VIM project.
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.

29. References
• Openstack “Stein” Release.
• Virtual Solutions for Your NFV Environment - F5 Networks
• F5 solutions for the emerging 5G landscape - F5 Networks
• SO Component - Developer Wiki - Confluence - ONAP Wiki
• VF-C User Guide - Developer Wiki - Confluence - ONAP Wiki
• OpenStack Docs: Welcome to Aodh's documentation!
• 5G NETWORK SLICING AND OPENSTACK
• ONAP Close Loop Control for Edge Cloud with Distributed MultiCloud

30. @OpenStack
THANKS.
Questions?
openstack openstack OpenStackFoundation
All product names, logos, and brands are property of their respective owners in the United States and/or other countries. All company, product and service names used on this presentation are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.
Trinath Somanchi
F5 Networks, INDIA.
https://www.linkedin.com/in/trinaths/
Bharath Thiruveedula,
Verizon, INDIA.
https://www.linkedin.com/in/bharaththiruveedula/
Dharmendra Kushwaha,
NEC, INDIA.
https://www.linkedin.com/in/dharmendra-kushwaha-034a2817/