Transcription
Limitations of Optimization forMulti-site NFV NetworkService DeliveryUse Cases and Early AnalysisAndy Veitch
Premise Orchestration with integrated planning algorithms forSDN/NFV is necessary to deliver optimal utilization ofcompute and networking infrastructure and the successfuldelivery of services (over multiple locations) To date, the definitions and development of these inSDOs and open source projects have been independent This is a reasonable time for the IETF (IRTF) to engage inidentifying requirements, architecture options, andpossible implications for current (legacy) functions andprotocols
Motivation SDN / NFV is expected to reduce OPEX and CAPEX Orchestration solutions expected to–––––Maximize the utilization of infrastructure – compute, storage, networkKeep costs lowDeliver network services that meet SLAsFollow policiesMinimize migrations Tradeoffs – Utilization vs. SLAs NFV and SDN orchestration solutions are separate andindependent– Orchestration for NFV / SFC (MANO)– Orchestration for networks (SDN, PCE)– Deployment planning computations must be unified orcooperative2016/07/223
Activities Review use cases Review current SDO and open source projects andcurrent research literature Review (some) options for unification / cooperation––––LCM (activation)RolesInformation passingPossible requirements Review possible impact on IETF definitions Develop informational drafts describing use cases andrequirements
Simple Network ServiceNetwork Service Descriptor /SFC to instan6atePNFVNFVNFService defini6on, from network service descriptorLow latency and jiEer required between VNF R and VNF G.VNFSolu6on 1 – independent planningSolu6on 2 – Unified or Collabora6ve planningNFV orchestra6on algorithm computes VNF loca6onsbased on policies, NFVI resources, costs, etcSolu6on does not account for network conges6onSolu6on considers network service condi6ons. Lowlatency and jiEer requirement between VNF R andVNF G is met. Lower cost with VNF B in DC 1.Datacenter 1EnterprisePNFAccessVNFBDatacenter 2VNFRVNFVNFWANDatacenter 1EnterprisePNFAccessVNFBDatacenter 2VNFRVNFVNFWANDatacenter 3VNFVNFDatacenter 3VNFRVNFG
vCDN and virtual IoT (Sensors) GatewaysHigh Volume Rapid Deployment Need to support a rapid rise insource and access to information– Emergency, e.g. Nice– Rock concerts – shared videos– Natural disasters – sensor data NFV enables makes possible thedynamic, elastic, and scalabledeployments– Sensor gateways– vCDNs, cache servers– Real-time data Must consider network, computeand storage, etc. all together
Service Deployment Adjustments - Migrations Monitoring and analytics indicate it istime to re-configure the deployment ofsome servicesExamples––– Consolidate services to fewerdatacenters, reduce energy usage andcostsReduce network delays due tocongestionReduce chance of service interruptions /SLA violations – move paths from OTNcircuit showing increased errorsMigrations are to be avoided––Impact on service performance – SLAEach service deployment must considerbroader optimization implications2016/07/22Opportunity to consolidate to Datacenter 2 and reduce opera6ngcosts of DC 3.EnterprisePNPNPNFFFAccessDatacenterV1 VNVVNVNFNFBFBBDatacenterVVN 2VVNFNFGFGGVNFNFRFRRWANNFDatacenterVVN 3VVNFNFGFGGNFConsolida6on raises usage of WAN connec6on between DC 1 and DC2. Even aWer path re-computa6on, the conges6on, latency and lossmay be increased to an unacceptable level. A beEer overall solu6onwould be possible if the op6miza6on algorithms were integrated N 2VVNDatacenterV1 VNVVNVNFNFBFBBVNFNFRFRRWANVN F FV NF GGVN FGNF GFGGNF7
Openstack with OpenDaylight – Split Optimization OpenStackTackerNovaSwiWNeutronLoca6ons andconnec6vityrequirements– Receives a network service requestvia Tacker– Chooses how and where toimplement with Nova, Swift– Communicates SFC connectivitygraph via Neutron tackPathcompute ght– Processes connectivity needs andcomputes connections to meetrequirements– Establishes connectivity usingunderlying networking technology– No feedback possible to OpenStackfor smarter VNF placementDatacenters/WAN2016/07/228
ETSI Architecture Introduces WIM as integration point from NFVO to WAN Controller
E2E Orchestrator Controls NFV and Network Used in a number of open source E.g. Open O, MEF LSO, TMForumE2E Orchestra6onWIM / WANControllerVNFMsNetworkControlVIMVNFVNFNFVOWAN JNetworkControllerWAN KNetworkControllerNetworkControlPacket NetworkNFVI-PoP X1networkTopologyGatewayNFVI-PoP X2GatewaynetworkOp6cal NetworkVNFVNFMsVIMVNFVNFVNF
NFVO Collaborates with WAN Controller Used in some open source SONATATopologyOSSNFVOWIM / WANControllerVNFMsNetworkControlVIMWAN JNetworkControllerWAN KNetworkControllerNetworkControlNFVI-PoP X1networkVNFVNFNFVI-PoP X2GatewayVNFVNFMsVIMWAN JGatewayWAN KGatewaynetworkVNFVNFVNF
Hierarchical and Multiple NFVOsAdminDomainAdminDomainX XOSSTopologyNFVOAdmin Domain YWIM / WANControllerNFVOVNFMsNetworkControlVIMWAN NetworkControllerNFVI-PoP ONetworkControlNFVI-PoP X1VNFVNFNFVI-PoP Y1GatewaynetworkVNFVNFMsVIMWANOp6cal NetworknetworkGatewayVNFVNFVNF
Common Agents Across ArchitecturesPoliciesIntegratedOp6miza6on /Orchestra6on Instances Where are functions located Multiple optionsTopologyResources– Knowledge representation optionsNetwork AgentSDNNetworkControllerAgent/SDNPCEController /PCENFV AgentNFVONFV AgentNFVOIdentify– Possible roles of agentsCatalogue What is necessary to enable the rapidcomputation Information distillation or summarization– KPI, policies, etc– Implications on functional blocksand communicationsIntegratedOp6miza6on /Orchestra6onNFV AgentNFVONFV AgentNFVOIntegratedOp6miza6on SDN/PCEController/PCENFV AgentNFVONFV PCEController/PCE Controllers, PCE, etc What information is exchanged andwhen– Develop requirements
Next Steps Continue use case definitions and analysis an document Develop requirements and document Evolve (update) and validate, repeat– Coordinate in open source, etc.
Relevant IETF Work PCE– PCEP TEAS– Controller based TE / Hybrid ALTO– NFV/SDN SFC– H-SFC YANG modeling
WIM / WAN Controller Topology E2E Orchestraon NFVI-PoP X1 network VNF VIM NFVI-PoP X2 VNF Ms network VNF VNF Netw ork Contr ol Gateway Gateway VNF VNF VNF VIM VNF Ms Netw ol WAN J Network Controller WAN K Op6cal Network Packet Network Used in a number of open source E.g. Open O, MEF LSO, TMForum
