limitations of optimization for multi site nfv network
play

Limitations of Optimization for Multi-site NFV Network Service - PowerPoint PPT Presentation

Limitations of Optimization for Multi-site NFV Network Service Delivery Use Cases and Early Analysis Andy Veitch Premise Orchestration with integrated planning algorithms for SDN/NFV is necessary to deliver optimal utilization of compute


  1. Limitations of Optimization for Multi-site NFV Network Service Delivery Use Cases and Early Analysis Andy Veitch

  2. Premise • Orchestration with integrated planning algorithms for SDN/NFV is necessary to deliver optimal utilization of compute and networking infrastructure and the successful delivery of services (over multiple locations) • To date, the definitions and development of these in SDOs and open source projects have been independent • This is a reasonable time for the IETF (IRTF) to engage in identifying requirements, architecture options, and possible implications for current (legacy) functions and protocols

  3. Motivation • SDN / NFV is expected to reduce OPEX and CAPEX • Orchestration solutions expected to – Maximize the utilization of infrastructure – compute, storage, network – Keep costs low – Deliver network services that meet SLAs – Follow policies – Minimize migrations • Tradeoffs – Utilization vs. SLAs • NFV and SDN orchestration solutions are separate and independent – Orchestration for NFV / SFC (MANO) – Orchestration for networks (SDN, PCE) – Deployment planning computations must be unified or cooperative 2016/07/22 3

  4. Activities • Review use cases • Review current SDO and open source projects and current research literature • Review (some) options for unification / cooperation – LCM (activation) – Roles – Information passing – Possible requirements • Review possible impact on IETF definitions • Develop informational drafts describing use cases and requirements

  5. Simple Network Service Service defini6on, from network service descriptor Network Service Descriptor / PNF VNF VNF VNF SFC to instan6ate Low latency and jiEer required between VNF R and VNF G. Solu6on 1 – independent planning Solu6on 2 – Unified or Collabora6ve planning NFV orchestra6on algorithm computes VNF loca6ons Solu6on considers network service condi6ons. Low based on policies, NFVI resources, costs, etc latency and jiEer requirement between VNF R and Solu6on does not account for network conges6on VNF G is met. Lower cost with VNF B in DC 1. Datacenter 1 Datacenter 2 Datacenter 1 Datacenter 2 Enterprise Enterprise Access Access PNF PNF VNFB VNFR VNF VNF VNFB VNFR VNF VNF WAN WAN Datacenter 3 Datacenter 3 VNF VNF VNFR VNFG

  6. vCDN and virtual IoT (Sensors) Gateways High Volume Rapid Deployment • Need to support a rapid rise in source and access to information – Emergency, e.g. Nice – Rock concerts – shared videos – Natural disasters – sensor data • NFV enables makes possible the dynamic, elastic, and scalable deployments – Sensor gateways – vCDNs, cache servers – Real-time data • Must consider network, compute and storage, etc. all together

  7. Service Deployment Adjustments - Migrations • Monitoring and analytics indicate it is Opportunity to consolidate to Datacenter 2 and reduce opera6ng costs of DC 3. time to re-configure the deployment of some services Datacenter Datacenter Enterpr 1 V 2 ise V V V N V • Examples PN V V Access V N N N PN F V V N N N PN F N F F F F G N N F F F F F B R G F F B R G – Consolidate services to fewer B R datacenters, reduce energy usage and WAN Datacenter costs V 3 V N V V N F N – Reduce network delays due to N F G F F G G congestion – Reduce chance of service interruptions / SLA violations – move paths from OTN Consolida6on raises usage of WAN connec6on between DC 1 and DC circuit showing increased errors 2. Even aWer path re-computa6on, the conges6on, latency and loss may be increased to an unacceptable level. A beEer overall solu6on would be possible if the op6miza6on algorithms were integrated or • Migrations are to be avoided coopera6ve. – Impact on service performance – SLA Datacenter Datacenter Enterpr – Each service deployment must consider 1 V 2 ise V V V N V PN Access V V V N N N PN F V V N N N V N PN F F F F broader optimization implications F G N N V F F F N F B R F WAN G V F F N B R F G N B R F G F G G 2016/07/22 7

  8. Openstack with OpenDaylight – Split Optimization • OpenStack OpenStack – Receives a network service request via Tacker Tacker Nova – Chooses how and where to SwiW Neutron implement with Nova, Swift – Communicates SFC connectivity graph via Neutron (networking-sfc) Loca6ons and • OpenDaylight OpenDaylight connec6vity Computes requirements Path – Processes connectivity needs and connec6vity SFC compute computes connections to meet Networking-sfc Network requirements SBI – Establishes connectivity using underlying networking technology – No feedback possible to OpenStack for smarter VNF placement VNF VNF VNF 1 2 3 Datacenters/WAN 2016/07/22 8

  9. ETSI Architecture • Introduces WIM as integration point from NFVO to WAN Controller

  10. E2E Orchestrator Controls NFV and Network • Used in a number of open source • E.g. Open O, MEF LSO, TMForum E2E Orchestra6on Topology WIM / WAN NFVO Controller WAN J WAN K Network Network Controller Controller Netw Netw VNF ork ork VNF VIM VIM Ms Contr Contr Ms ol ol Packet Network NFVI-PoP X1 NFVI-PoP X2 network Gateway network Gateway Op6cal Network VNF VNF VNF VNF VNF VNF

  11. NFVO Collaborates with WAN Controller • Used in some open source • SONATA Topology OSS NFVO WIM / WAN Controller WAN J WAN K Network Network Controller Controller Network Network VNFMs VIM VIM VNFMs Control Control NFVI-PoP X1 NFVI-PoP X2 WAN J WAN K network Gateway Gateway Gateway network VNF VNF VNF VNF VNF VNF

  12. Hierarchical and Multiple NFVOs Admin Domain X Admin Domain X OSS Topology NFVO Admin Domain Y WIM / WAN NFVO NFVO Controller Netwo rk VNFM VIM Contr s ol WAN Network Controller NFVI-PoP X2 Netw Netw VNF ork ork VNF Gateway network VIM VIM Ms Contr Contr Ms ol ol VNF VNF VNF NFVI-PoP X1 NFVI-PoP Y1 Gatew WAN network Gateway network ay VNF VNF Op6cal Network VNF VNF VNF VNF

  13. Common Agents Across Architectures • Identify Policies Integrated – Possible roles of agents Catalogue Op6miza6on / Instances Orchestra6on • Where are functions located Topology • Multiple options Resources – Knowledge representation options Network Agent NFV Agent • What is necessary to enable the rapid SDN Controller / Network Agent NFVO NFV Agent computation SDN Controller / PCE NFVO PCE • Information distillation or summarization – KPI, policies, etc – Implications on functional blocks and communications • Controllers, PCE, etc Integrated Integrated Op6miza6on / Op6miza6on / • What information is exchanged and Orchestra6on Orchestra6on when Network Network – Develop requirements Agent Network Agent Network NFV Agent NFV Agent SDN Agent SDN Agent NFVO NFV Agent NFVO NFV Agent Controller / SDN Controller / SDN NFVO NFVO Controller / PCE Controller / PCE PCE PCE

  14. Next Steps • Continue use case definitions and analysis an document • Develop requirements and document • Evolve (update) and validate, repeat – Coordinate in open source, etc.

  15. Relevant IETF Work • PCE – PCEP • TEAS – Controller based TE / Hybrid • ALTO – NFV/SDN • SFC – H-SFC • YANG modeling

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend