NFVO & OpenStack
Kanagaraj Manickam
21st Oct 2016
Agenda
• What Telco Faces and what they need?
•Network Virtualization
•NFV
•NFVO-MANO
•OpenStack
What Telco faces ?
•Bulky
•Costly
•Fragile
•Heavy Opex
What Telco operator needs
•Reduce equipment cost (Capex)
•Save operational costs (Opex)
•Effective power consumption & spaces
•Agile - Time-to-market for new services and functionality.
Network Virtualization
NFV
With NFV, standard IT virtualization technology is adopted to consolidate
many network equipment types onto industry standard high volume
servers, switches and storage. This involves implementing network functions
in software which can run on a range of industry-standard server hardware.
This software can then be moved to, or introduced in, various locations in the
network as required. This will simplify the roll-out of network services,
reduce deployment and operational costs and encourage innovation.
ETSI NFVO - MANO
Cloud Data-center
OpenStack is an distributed cloud operating system
provides an platform for setting up public or private cloud
on top of heterogeneous data-center.
For operator, It provides set of configurable device-
drivers/plug-ins to consume the required hardware-devices
and software-defined-devices from cloud data-center
regions.
And for consumers, it provides required Restful API, CLI to
provision and manage their cloud resources such as
instances, storage volumes, networks, etc. programmatically.
VIM - OpenStack
NFVO & OpenStack
OpenStack
Tacker + Heat
Tacker
Juju, HW CSM
Open-O, OSM
NFVO Leaders & Open-Source
Cisco: Very Strong
Ericsson: Strong
HPE: Very Strong
Huawei: Strong
Nokia: Very Strong
Oracle: Strong
ZTE: Competitive
RIFT.io
OpenSource MANO (OSM)
Open-O
OpenStack Tacker
Thank You.
My Current Open-Source Roles
• Core-reviewer @ Heat, an OpenStack Orchestrator
• Core-reviewer @ Tacker, an OpenStack NFVO Orchestrator
• Committer @ NFVO, in Open-O.
• Contributor @ SDNO OpenStack driver & VPC service, in Open-O.
• Establishing namos – OpenStack Manager

OpenStack and nfvo

  • 1.
    NFVO & OpenStack KanagarajManickam 21st Oct 2016
  • 2.
    Agenda • What TelcoFaces and what they need? •Network Virtualization •NFV •NFVO-MANO •OpenStack
  • 3.
    What Telco faces? •Bulky •Costly •Fragile •Heavy Opex
  • 4.
    What Telco operatorneeds •Reduce equipment cost (Capex) •Save operational costs (Opex) •Effective power consumption & spaces •Agile - Time-to-market for new services and functionality.
  • 5.
  • 6.
    NFV With NFV, standardIT virtualization technology is adopted to consolidate many network equipment types onto industry standard high volume servers, switches and storage. This involves implementing network functions in software which can run on a range of industry-standard server hardware. This software can then be moved to, or introduced in, various locations in the network as required. This will simplify the roll-out of network services, reduce deployment and operational costs and encourage innovation.
  • 7.
  • 8.
    Cloud Data-center OpenStack isan distributed cloud operating system provides an platform for setting up public or private cloud on top of heterogeneous data-center. For operator, It provides set of configurable device- drivers/plug-ins to consume the required hardware-devices and software-defined-devices from cloud data-center regions. And for consumers, it provides required Restful API, CLI to provision and manage their cloud resources such as instances, storage volumes, networks, etc. programmatically. VIM - OpenStack
  • 9.
    NFVO & OpenStack OpenStack Tacker+ Heat Tacker Juju, HW CSM Open-O, OSM
  • 10.
    NFVO Leaders &Open-Source Cisco: Very Strong Ericsson: Strong HPE: Very Strong Huawei: Strong Nokia: Very Strong Oracle: Strong ZTE: Competitive RIFT.io OpenSource MANO (OSM) Open-O OpenStack Tacker
  • 11.
    Thank You. My CurrentOpen-Source Roles • Core-reviewer @ Heat, an OpenStack Orchestrator • Core-reviewer @ Tacker, an OpenStack NFVO Orchestrator • Committer @ NFVO, in Open-O. • Contributor @ SDNO OpenStack driver & VPC service, in Open-O. • Establishing namos – OpenStack Manager

Editor's Notes

  • #4 Modern telecoms networks contain an ever increasing variety of proprietary hardware. The launch of new services or network reconfiguration demands the installation of yet more equipment that in turn requires additional floor space, power and trained maintenance staff. As the innovation cycles continue to accelerate, hardware-based appliances rapidly reach end of life. Simply having a hard-wired network with boxes dedicated to single functions is not the optimal way to achieve dynamic service offerings.