Lean NFV Ops. Related session: Communication Networks Reloaded. Jose de Francisco, Cloud Innovation Center.

Transcription

2 Agenda 1. NFV deployment strategies 2. Present Mode of Operations 3. Network softwarization 4. The journey 5. Virtualization of mobile core and IMS (ETSI NFV use case #5) 6. Service function chaining 7. Reliability, availability and serviceability 8. DevOps: Development and operations 9. Standards 10. Early challenges 11. Future Mode of Operations 12. Closing comments If you can t explain it simply, you don t understand it Albert Einstein OPEN template well enough. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. This slide must be kept when distributed externally. 2 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

3 The evolution of useful things The Evolution of Useful Things Published in 1992 Vintage Books, Random House, New York ISBN The form of made things is always subject to change in response to their real or perceived shortcomings, their failures to function properly ( ) there can be no such thing as perfected artifact There is an ongoing evolution of new needs created by the developers of new designs ( ) that require new tools for assembly and disassembly, and these new tools in turn enable still further new designs Henry Petroski is an engineer specializing in failure analysis and professor both of civil engineering and history at Duke University. Ill served by an advisor who looks too narrowly at technical indicators to prognosticate performance in the marketplace Focusing too closely on the immediate design problem ( ) frequently results in solutions that themselves give rise to more difficult design problems Every technological change has the potential for being both cursed and praised 3 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

5 Present Mode of Operations (PMO) challenges High lead times for new system and/or service introduction estimated in months and years where technology silos prevail Complex overall Method of Procedure given hardware specifics and planning processes challenging end-to-end operations Low server to administrator ratio in environments comprised of largely physical elements, tightly integrated software and hardware under multiple management systems High human latency due to number of manual deployment, maintenance and upgrade process, communications, forms, also impacted by network and IT disconnects LT: Lead Time MOP: Method of Procedure S/A: Server to Administrator Ratio HL: Human Latency 5 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

6 Present Mode of Operations (PMO) challenges Cause Effect correlation High lead times for new system and/or service introduction estimated in months and years where technology silos prevail Compromised time to market, lengthy ordering to activation process, difficult to measure end users QoE Complex overall Method of Procedure given hardware specifics and planning processes. Challenging end-to-end operations Low server to administrator ratio in environments comprised of largely physical elements, tightly integrated software and hardware under multiple management systems Overlong capacity planning does not favor agile reconfiguration of services and components to meet demand curves Costly environment which cannot dynamically apply big data subjected to real-time changes; underutilized assets and budgets consumed by maintenance High human latency due to number of manual deployment, maintenance and upgrade process, communications, forms, also impacted by network and IT disconnects Leading Lagging indicators Taxing end-to-end management under separate fulfilment and assurance for core, access, IMs, with service upgrades often susceptible to failures LT: Lead Time MOP: Method of Procedure S/A: Server to Administrator Ratio HL: Human Latency Feedback loop CoD: Capacity on Demand TTM: Time to Market QoE: Quality of Experience 6 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

7 Is Network softwarization the answer? Translating IT virtualization concept to Telecom Network Functions Virtualization (NFV): I do not paint a portrait to look like the subject rather does the person grow to look like his portrait. - software (SW) is decoupled from hardware (HW) - telecom systems (IMS, EPC, RAN) become software instances - virtual network functions (VNF) run on virtual machines (VM) - VNFs are decomposed and modularized suited for N+K redundancy - shared infrastructure based on general purpose, high volume COTS HW - enables application multi-tenancy and distributed architectures - automation optimizes lifecycle management and resource orchestration Salvador Dalí Software Defined Networking (SDN): - control (traffic decisions) decoupled from data plane (traffic forwarding) - programmable and automated networking - centralized global network view and intelligence - controller sends packet handling rules to the switch 7 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

8 ETSI NFV reference architecture NFV management and orchestration NFV Orchestrator (NFVO) - Multi-VIM management - VNF placement - VNF policy enforcement VNF Manager (VNFM) - VNF deployment - VM level monitoring (CPU/storage) Virtual Infrastructure Manager (VIM) - Virtual resource management at hypervisor level COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

9 The journey: Early virtualization PMO Purpose built HW/ASICs Tight coupling between HW and SW Monolithic apps with specific HW configurations Scales by adding more HW Rigid service creation 1-to-1 app to purpose built HW ratio Apps run on VMs Multiple applications run on generic hardware Apps in the component form consuming one or more VMs Apps can scale by adding more VMs Various component level scaling is possible 9 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

10 The journey: FMO Single pane of glass Lifecycle management Resource orchestration Analytics IaaS Infrastructure as a Service PaaS Platform as a Service Service level orchestration Common infrastructure management Solution templates Fulfilment and assurance Resource orchestration Key performance indicators Predictive analytics Application multi-tenancy Selective lifecycle automation End-to-end automation Distributed architectures Autonomics, self-organizing 10 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

11 ETSI NFV use case #5: vepc and vims Mobile networks are populated with a large variety of proprietary hardware appliances [ ] leverage standard IT virtualization technologies to consolidate different types of network equipment located in NFVI-PoPs. Virtualization target: Mobile core network functions: EPC core and adjunct network functions, e.g. MME, S/P-GW, PCRF, etc. 3G/EPC interworking network functions, e.g. SGSN, GGSN, etc. All IMS network functions, e.g. P/S/I=CSCF, MGCF, AS. Flexible allocation of Network Functions on such hardware resource pool could highly improve network usage efficiently in day-to-day network operation. Higher service availability and resiliency provided to end users/customers by dynamic network reconfiguration. Elasticity: capacity dedicated to each Network Function can be dynamically modified according to actual load on the network, thus increasing scalability. Topology reconfiguration: Network topology can be dynamically reconfigured to optimize performances. Creation of a competitive environment where innovative implementations of third-party network applications can be supplied by unlocking the proprietary boundaries of current Mobile Core and IMS implementations. Designing newer resiliency schemes becomes possible by utilizing the portability of the VNF instances in the form of, but not limited to VM relocation, replication, etc [ ] the relocation of the managed sessions and/or connections needs to be handled appropriately to achieve operator desired service continuity and service availability. Coexistence of virtualized and non-virtualized network functions. 11 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

12 Use Case #5: Lean NFV ops demo Dynamic lifecycle use cases: Agile service selection and deployment SFC: Service Function Chaining Capacity: Growth/degrowth with analytics RAS: Reliability, Availability, Serviceability Service continuity in HA: High Availability RCA: Root Cause Analysis Smart placement (Bell Labs simulation) Demo environment: End-to-end 100% virtualized VoLTE Solutions: VNFs: VRAN, VEPC, VIMs OSS: Motive dynamic operations SDN: Nuage Networks MANO: CloudBand management system VIM: OpenStack NFVI: CloudBand cloud nodes Ecosystem: Intel, WebRTC, RealSense/Personify 12 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

13 Service Function Chaining (SFC) demo SFC leverages NFV and SDN Service function is decoupled from network topology, physical network is not required to be modified Users contract different services comprised of several applications Application sets are dynamically stitched in real time Operational flexibility: Application-driven provisioning Intelligent traffic steering, capacity adjusted based on utilization Common deployment of service functions Usage across multiple domains SSO: Self-service operations Lean NFV Ops demo screenshot Enables sharing information between service functions Simplify access to virtualized apps Upsell/cross-sell services 13 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

14 Reliability, Availability, Serviceability (RAS) demo Service assurance encompasses cloud, network, application analytics and compliance Advanced correlation relies on predictive analytics and unified event management Automation involves root cause analysis and resolution Addressing RAS: Dynamic CoD (Capacity on Demand) Automated recovery and service continuity Sustaining HA (High Availability) environment Distributed system, N+K redundancy, active standby failover Smart placement for VM relocation, replication Delivering fine grained and correlated analytics Lean NFV Ops demo screenshot Autonomation provides controls and override, involves operations team and enables immediate attention A recommendations engine presents alternative solutions starting with the most optimal 14 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

15 Continuous integration (DevOps) PMO FMO Software + hardware delivery Focus on software delivery Dedicated hardware (appliance model) Long lead times Fixed release schedule Virtualized and cloud infrastructure Short, iterative cycles Flexible, frequent delivery Version control Code review Waterfall development model Agile software development Manual processes Single source repository Highly automated build Self-testing Automation Automation Automated version control Undetected issues can snowball Early issue detection Back-end loaded process Compartmental handover Risk averse Iterative process Cross-functional process and workstyle Collaborative delivery Entrepreneurial Build Install Continuous integration Hooks and triggers Integration test Deliver/publish Issue tracking Venn Diagram COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

16 Standardization Interfaces between physical and virtual resources in the context of wireless applications and the mobile core Zero Touch Orchestration, Operations and Management for NFV-O and SDN; defines interfaces between OSS and orchestration, interest in VNF descriptor alignment In November 2012 seven of the world s leading telecoms network operators selected ETSI to be the home of the Industry Specification Group for NFV Involves network service orchestration and service function chaining OpenStack (VIM), Mistral (workflow), HOT (orchestration template) and Tacker, which uses Oasis TOSCA NFV does not intent to build standards on its own, but to provide input and requirements to standard bodies NFVI layer (cloud nodes) Research agenda 16 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

17 Ecosystem and technology readiness Readiness level provides understanding on maturity The journey can plot different paths based on readiness, adoption levels and matchmaking choices launch, live ops, LCM validation in relevant environment agile development use case - proof of concept projects basic technology research 17 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

18 Early industry challenges 1. Shifting from PoC focus to successfully crossing the ops chasm 2. Separating hype and vaporware from what actually works today 3. Assessing maturity and technology readiness levels (the journey) 4. Sprawling virtualization silos and conflicting management systems 5. Bloated architectures shortchanging operations, scalability or performance 6. Working with physical and virtual elements in hybrid environments 7. Industry standards and fragmentation 8. Diverging from cloud fundamentals that we fell in love with Toto, I ve a feeling we re not in Kansas anymore The Wizard of Oz 9. Legacy technologies last gasp 10. End-to-end (eco)systems engineering and open source 11. Business transformation and organizational dynamics 18 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

19 Lean NFV ops effective and highly efficient service delivery at any scale effective high availability Service Level Agreement efficient Lean NFV ops workload Lowest cost per bit high utilization levels 19 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

20 Future Mode of Operations (FMO) 1. Shorter LT: agile delivery throughout service lifecycle: - streamlining: end-to-end value stream mapping of the service - service lifecycle orchestration (automation) - user friendly self-service and customization from ordering to activation - continuous integration (DevOps) - leveraging ecosystem and open source (e.g. OpenStack) 2. Streamlined Ops: deconstructing and modularizing: - decoupling software from dedicated hardware - working with virtual machines - lifecycle orchestration templates, policies - asset pooling and on-demand (JIT) resource allocation - application modeling (information, data models) - smart load placement - addressing service continuity and RAS by operating in HA - furthering service decomposition and N+K, active standby failover - analytics: monitoring, alarm correlation, data driven ops, root cause analysis - predictive analytics, autonomics (machine learning, full scale automation) leading to self-organizing systems LT: Lead Time MOP: Method of Procedure S/A: Server to Administrator Ratio HL: Human Latency DevOps: Development and Operations HA: High Availability JIT: Just in Time N+K: Redundancy model Ops: Operations RAS: Reliability, Availability, Serviceability RCA: Root Cause Analysis 20 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

21 Future Mode of Operations (FMO) 3. Higher S/A ratio: Harmonizing management systems - COTS-based hardware consolidation - centralized management of virtual and distributed environments - end-to-end visibility: Abstractions, single pane of glass - autonomation (automation with controls) 4. Lower HL: - cross-functional behaviors: Organizational culture, workstyle - agile project management, continuous improvement - clear roles and responsibilities - context enabled adaptive processes - training and professional development LT: MOP: S/A: Lead Time Method of Procedure Server to Administrator Ratio HL: COTS: E2E: Human Latency Commercial off the Shelf End-to-end 21 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

22 Deconstructing Lean x NFV x Ops Lean column adapted from Kim B. Clark and Takahiro Fujimoto, Product Development Performance p. 172 and Mary and Tom Poppndieck, Implementing Lean Software Development p COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

23 Closing thoughts and Q&A Present Mode of Operations (PMO): Future Mode of Operations (FMO): Widespread industry concerns about the risks and cost of ever growing complexity Overly lengthy lead times compound the problem in today s changing environment Hybrid physical and virtual environments are expected to co-exist in the short and mid terms Making network softwarization and dynamic services happen dominates work on next-generation systems Service level orchestration becomes an operational objective NFV and SDN involve emerging technologies and IT practices that are set to disrupt the telecommunications industry Cloud presents new challenges for network operators, some already addressed by fast evolving cloud solutions Technical prowess alone is not enough as organizational and business models are morphing Starting and staying lean at any scale throughout NFV s journey is of the essence 23 COPYRIGHT 2015 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

77

78

79

80

82

83

84

85