Summit 16: Open-O Mini-Summit - Architecture & Technology
2 likes801 views
The document discusses the Open-O architecture focused on orchestrating services across various networks, emphasizing the need for unified service orchestration that accommodates both legacy and modern SDN/NFV environments. It outlines the roles of different orchestration components including GS-O, NFV-O, and SDN-O while highlighting the importance of model-driven frameworks and analytics for effective service management. Current status indicates an agreement on preliminary architecture with plans for integration and the approval of multiple projects in the development pipeline.
Summit 16: Open-O Mini-Summit - Architecture & Technology
- 1. OPEN-O Architecture Any service on any network Chris Donley Christopher.donley@huawei.com TSC Chair
- 2. Why Open Orchestration? SDN & NFV Adoption 2 Source: Coleman Parkes Research. 2015 for HPE
- 3. VIM SDN CtrlVNFM BSS: Product Layer OSS: Service Layer Network: Resource Layer App/BSS /OSS Portal (GUI) VIM Customer Facing Service Spec Resource Facing Service Spec Network Service Spec PNFs VNFs Product Spec Resource Spec SDN CtrlG-VNFM GS-O Global Service O SDN-ONFV-O Promotional/Bundled/Simple Offerings Product SpecProduct Resource Facing Service SpecResource Facing Service Network Service SpecNetwork Service Resource SpecNetwork Resource Customer Facing Service TMF Customer Device ETSINFV From OSS to OSS: Where OPEN-O fits in a Carrier Network TOSCA YANG
- 4. OPEN-O Architecture 4 TOSCA Yang Portals Operator GUI OSS Infrastructure Legacy Networks SDN Networks NFVI Tools Common Services Orchestration Services SDN-O NFV-O GS-O BSS End-User Portals
- 5. GS-O Global Service Orchestrator • Targets:E-2-E network service orchestration • Goal: Unified service orchestration of Legacy & SDN/NFV network resources • Typical Scenarios: Service LC mgmt. for users/tenants • Operation- Service design/deployment/activation/provisioning • Maintenance- Close-loop Automation NFV- Orchestrator • Targets：Virtualized applications, network functions • Goal：NS On boarding, NS LC Mgmt/Resource Mgmt • Typical Scenarios： •VNF Deployment/On-boarding/Scaling/Fault- recovery SDN-Orchestrator • Targets：Network Connectivity Services • Goal: Provide CONNECTIVITY across access & WAN networks • Typical Scenarios： •Network connectivity mgmt. • Traffic Engineering A Closer Look at OPEN-O
- 6. Orchestration Common: Model Driven Framework Why model-driven? • Unified service creation and provisioning process needs a normalized data model, • Model driven configuration & management makes system extensible, • Model driven framework provides basis for openness of network capability. Highlights: •Model conflict detection •both static & dynamic •Model Dry Run allow validation before service provisioning
- 7. Orchestration Common: Analytics and Policy • OPEN-O with analytics module and policy module becomes more intelligent. • Machine learning methods (e.g. ANN, SVM, logistic regression, etc.) -> Analytics model • The analytics module can predict the future situation and interact with the policy module to control / manage the system. Double Closed Loop • Short term (quick response) Data -> Analytics -> Policy -> NFVO Component -> Data • Long term (slow response) Data -> Analytics -> Policy -> Orchestrator -> NFVO Component -> Data Data GS-O NFV-O/SDN-O Analytics Policy short term long term predictions actions collections Policy Validation SPP SAP Policy Designer Policy Engine Layered Policy Model Global policy Local policy
- 8. Use Case: vCPE VLAN VXLAN IPSec WAN ThinCPE PE1 TOR OS AP P OS AP P TOR OS AP P OS BRAS CP VXLAN VLAN VIM2 (OS2) DC Controller (Neutron Plugin) WAN Controller Super/D Controller Access Controller OPEN-O GW overlay underlay VLAN MPLS BGP L3VPN OS vCPE OS vFW Enterprise Site Tenant Cloud for Enterprise POP/TIC Edge G-VNFM1 (Juju/vFW, …) VIM1 (OS1) S-VNFM1 (vCPE) G-VNFM2 (SFC/vVA S) Neutron interface SDN-O NFV-OLegend: PE2 SPTN pCPEResidential BRAS DP TIC Core MPLSTP L2VPN PE1 S-VNFM1 (BRAS CP) SPTN VLAN SPTN MPLSTP L3VPN
- 9. Catalogue Modeling for virtual CPE/CE Internet Access Service 500M, with Firewall and NATOverlay NS Internet Access Service 500M with Firewall and Policy Cntl Overlay NS (Enterprise) DC Service Chain with vCPE and vNAT Overlay NS (DC) Underlay Connectivity (complex, multiple CoSs, hierarchical) Underlay NS
- 10. Global-Service-O (GS-O) NFV-O (DC)NFV-O (Enterprise) Overlay NS Overlay NS Topology/Graph DC Transport vCPE vNAT SDN-O Underlay NS Underlay NS Topology/Graph TransportController 1: Connectivity 1 EMS1: pCE Controller 2: Connectivity n EMS2: TTGW Overlay NS (DC) Underlay NS DC Topology/Graph Design Time Catalog Virtual CPE/CE Use Case Overlay NS (Enterprise) Enterprise Transport Firewall Policy Control Underlay NS DC Topology/Graph Enterprise VIM Enterprise SDN Controller EMSs SDN Controllers DC VIM DC SDN Controller
- 11. Current Status • Architecture Committee – Agreement on preliminary architecture – Integration plan incorporating 7 codebases • TSC Kickoff – June 7-9 • Planning first release – 4 projects approved (so far) • NFV-O, GS-O, SDN-O, Common Services – 2+ projects under review • VNF Onboarding, Common TOSCA
- 12. 12 OPEN-O Release 1 Planning Common (TOSCA) Workflow Parser Catalog Model Designer GS-O Service Decomposer Service Lifecycle Mgr. Service Formation Abstract NBI GUI Portal SDN Driver ACCESS/WAN SDN Controller Drivers SDN-O SDN Res. Mgr. Abstract NBI Abstract SBI VPN SDN Lifecycle Mgr. Traffic Optimize SDN Monitor EMS/NMS Driver VIM Drivers GUI Portal VNFM Drivers VIM Drivers NFV SDN Controller Drivers NFV-O NFV Res. Mgr. NFV Monitor NS Lifecycle Mgr. Abstract NBI Abstract SBI NFV Driver GUI Portal Common Service HA Log Driver Mgr. Micro- Service Bus Protocol Stack Auth. VNF Onboarding
- 13. Q&A
- 14. Thank You