open management interfaces for nfv
TRANSCRIPT
Anees ShaikhGoogle Network Operationson behalf of the OpenConfig working group
www.openconfig.netgithub.com/openconfig/public
Open Management Interfaces for NFV
OPNFV SummitNovember 2015
Challenges of managing a Web-scale network
● very large number of OIDs collected
● many CLI commands issued and scraped at high frequency
● many tools, and multiple generations of software
VNF management adds additional challenges: more device variants, multi-layer monitoring, application-level coordination, diverse usage patterns, ...
2
● 20+ network device roles
● more than half dozen vendors, multiple platforms
● 4M lines of configuration files
● up to ~30K configuration changes per month
State of management isn’t helping ...● many proprietary integrations
○ CLIs, scripts, templates, modules, cookbooks, minions, ...
● lack of available abstractions and common APIs
● configuration scraping from devices
● SNMP monitoring -- poor scaling, lack of extensibility, proprietary MIBs
● complexity and cost have been pushed to operators○ long qualification processes, specialized skills, ...
3
Evolving toward a vendor-neutral approach
4
Per-vendor EMS
EMS A
platform-specific tools, processes, skills
EMS B
EMS C
VNF A VNF B VNF C
Common OSS
EMS A
proprietary integrations, common interfaces upstream
EMS C
VNF A VNF B VNF C
operator / 3rd party OSS
Common VNF mgmt APIs
common mgmnt API
proprietary integrations, common interfaces upstream
VNF A VNF B VNF C
operator OSS
Model-driven management plane
5
interoperable network-wide view
multiple vendor devices
API
common API for configuration and monitoring monitoring / collectors
transport and RPC protocols that are open, streaming, secure
Configuration TopologyTelemetryModels provide:
○ durable APIs○ vendor-independent abstractions○ forward compatibility
Model-driven streaming telemetry
6
● stream data continuously -- with incremental updates based on subscriptions
● observe network state through a time-series data stream
● device data follows a common model
● efficient, secure transport protocols (gRPC)
time-series data stream
async eventreporting
requests for ad-hoc data
gRPC endpoint
telemetrycollectors
upstream monitoring systems
OpenConfig overview
● industry collaboration among network operators
● primary output: data models for configuration and operational state, written in YANG
● operational model: informal, structured like an open source project
● development priorities driven by operator requirements
● individual and collective engagements with major equipment vendors to drive native implementations
● also now contributing tools for consuming YANG models
OpenConfig participants
8
OpenConfig progressData models (configuration and operational state)
● BGP and routing policy (adopted by IETF )● MPLS / TE● optical transport● interfaces, VLANs● more …
Native implementations -- BGP+policy models○ Cisco IOS-XR○ Juniper JUNOS○ Arista EOS○ additional vendors with implementations underway
9
OpenConfig beyond data modelsTools and APIs (examples)
● pyangbind -- generates Python classes from YANG models● goyang -- Go language YANG compiler● protocol-independent specs for config and telemetry RPCs
Design patterns and usability improvements● design patterns for operational state and model composition● model catalog and registry
10
OpenConfig and NFV
● problems are very similar○ lack of common APIs for monitoring and configuring VNFs
○ proprietary integration with VNFs and vendor EMSes
● apply OpenConfig approach to VNF management○ operator-driven with vendor partnership
○ focus on the common use cases and functions
○ make model and API support a requirement for deployment
11
OPNFV opportunities
12
OPNFV model development
● develop vendor-neutral data models for common VNFs● leverage high operator participation to define the models
model implementations
● OPNFV as an open forum for vendor feedback on models● prototype implementation, testing, and certification
integrations ● exploit ODL integration to include support for YANG models● ODL / OpenStack can provide basis for VNF managers
Summary
● network infrastructure and VNF management needs a model-driven approach
● OpenConfig is a new kind of industry collaboration○ network operators directly contributing open data models, tools,
and design patterns
● as native implementations become available, potential to significantly transform network monitoring and configuration
● approach and experience from OpenConfig can be applied directly to NFV
13
Thank you!
14