NFV ISG PoC Proposal Virtual Function State Migration and Interoperability

Transcription

1 NFV ISG PC Prpsal Virtual Functin State Migratin and Interperability A.1 NFV ISG PC Prpsal Template A.1.1 PC Team Members PC Prject Name: Virtual Functin State Migratin and Interperability Netwrk Operatrs/ Service Prviders: AT&T British Telecm Manufacturer A: Bradcm Crpratin Manufacturer B: Tiet Crpratin Cntact: Steven Wright Cntact: Dn Clarke Cntact: Paul Runcy Kumaran Siva Cntact: Mieszk Mularczyk A.1.2 PC Prject Gals PC Prject Gal #1: The gal f this Prf-f-cncept (PC) is t demnstrate that a netwrk functin that has been apprpriately develped using mdern pen-surce develpment tls, perating systems, and hypervisrs can be transparently deplyed n tw different hst systems using radically different hardware. In particular, this PC will demnstrate the same applicatin surce cde running n different Instructin Set Architectures (ISA) fr the main prcessr, in this case the x86 architecture and the MIPS-64 architecture. Furthermre, the PC applicatin has been develped in such a way that the state is separate frm the applicatin and can be migrated between server systems running the same cde n different ISAs. Prtability f VNFs is identified in several f the ISG dcuments as an bjective f NFV. GS NFV 001 (NFV: Use Cases) identifies the need fr prtability f VNFs in sectin 9.2 (virtualized IMS use case) and smth migratin f virtual machines between lcatins in sectin 13.5 (virtualizatin f fixed access netwrk functins) GS NFV 002 (NFV: Architectural framewrk) in sectin describes the scpe f NFV t include the ability t guarantee an hardware independent lifecycle, perfrmance and prtability requirements f the VNF; and in Sectin 8.2 describes VNF prtability as a study tpic in the cntext f the virtualizatin layer. GS NFV 004 (NFV: Requirements) in sectin 5.2 ntes that the NFV target is t achieve VNF prtability acrss multiple vendrs, hypervisrs, and hardware. This PC activity investigates VNF migratin acrss Instructin Set Architectures t imprve the prtability f VNFs in the NFV ecsystem. Sftware can be run n different ISA as lng as the underlying perating platfrm (perating system, hypervisr, data-plane API) is aligned. This visin is achieved in the PC using standard ff-the-shelf pen-surce platfrm cmpnents. Fr the PC these included: KVM fr hypervisr, Linux fr the guest perating system, and standard data-plane interface like DPDK r Linar ODP. Currently, running applicatins n different ISA still require recmpilatin fr the specific ISA. In the future, innvatins currently in develpment with pen surce tl chains culd enable ISA independent binary frmats (in particular LLVM byte cde) that will allw binaries t run unchanged.

2 A.1.3 PC Demnstratin Venue fr the demnstratin f the PC: The PC will be demnstrated by Bradcm at Mbile Wrld Cngress 2014, in Barcelna, Spain n February A1.4 Publicatin The abstract f ur PC will be shwn at URL: TBD A.1.5 PC Prject Timeline What is the PC start date? Nvember 1, 2013 (Already underway) (First) Demnstratin target date February 24, 2014 PC Reprt target date July 31, 2014 When is the PC cnsidered cmpleted? July 31, 2014 A.2 NFV PC Technical Details A.2.1 PC Overview The Server Platfrm in this PC will have identical sftware platfrm envirnments running n bth x86 and MIPS-64 including KVM hypervisr and Linux guest OS (same distributin, but cmpiled fr x86 and MIPS-64 respectively). As shwn in Figure 1, the chsen NFV platfrm cmpnents are pen surce and available n bth x86 and MIPS-64. #1 VNF #2 VNF #3 VNF Applicatin Applicatin Applicatin Runs ut f the bx (Java, Pythn) Prtable Re-cmpliable (C, C++) Platfrm Specific (C, C++) KVM Hypervisr OpenFlw Cntrller x86-64 External NIC Device Drivers Accelerated vswitch Platfrm MIPS-64 SC platfrm data plane acceleratin Figure 1 - Server Platfrm Sftware Architecture T enable this PC, the sftware platfrm n bth hardware platfrms need t be aligned including the develpment tls (cmpilers etc.), hypervisr and perating system between the hst systems. T be efficient, Independent Sftware Vendrs need t be able t develp netwrk functins using a cmmn tl chain that will cmpile netwrk functins t different ISAs and deply n a standard envirnment. While nt strictly required, pen-surce and pen standards are a natural chice t supprt

3 Open / Standard APIs crss-isa sftware platfrms. By the fact that the surce cde is made pen, silicn and sftware vendrs have the ability t recmpile the platfrm fr the different hardware platfrms. Fr this PC, the fllw pen-surce cmpnents are utilized and crss cmpiled fr bth x86 and MIPS-64 Instructin Set Architectures: 1. Cmpiler tl chain. Currently, the best chice is the GNU C Cmpiler r GCC. In the future, Lw-Level Virtual Machine cmpiler (r LLVM) will be the available and prvides the benefit f enabling an ISA independent byte-cde. 2. Hypervisr. KVM, Kernel-based Virtual Machine, is an pen-surce prject that leverages heavily frm Linux and is ptimized t hst Linux guest perating systems. XEN is als a pssible alternative as a hypervisr. 3. Operating System. Linux perating system has gradually becme the standard perating system fr netwrking applicatins. Early n, perfrmance f system calls impaired Linux as a mainstream ptin fr netwrking applicatins. But as framewrks, such as DPDK and ODP, enable user-space data-plane applicatins t be created, the Linux perating system has becme a viable platfrm fr netwrking functins. The surce cde fr the vepc VNF will be cmpiled with identical cmpiler tl chains fr bth x86 and MIPS-64. The initial setup will have an IP based vide surce prviding a vide stream t the vepc running n the x86 system. The vide will then flw acrss the vepc back ut t a simulated BTS and finally t a device (User Equipment). Past - Prprietary (High ISA dependency) Assembly Lib Dependency Tday Linux & GCC (Lw ISA dependency) Lib Dependency Future - Linux & LLVM (Very Lw ISA dependency) NFV API Prprietary API Prprietary Cmpiler Binary (ISA ) Prprietary API GCC Cmpiler BE Part Binary (ISA) LLVM FE Cmpiler Binary (LLVM) LLVM BE Cmpiler Binary (ISA) ISA independent binary Specific cmpiler fr each ISA Fully Prprietary Operating System (e.g. Windws) Lib/ API Drivers Linux NFV LIB Drivers Linux Cmmn/ standard API Silicn specific drivers Figure 2 Tl Chain & Operating System Evlutin In the past tl chains and perating systems were very tightly assciated with the hardware platfrm and in particular the instructin set architecture. Tday, the situatin has dramatically imprved where pen-surce cmpilers like GCC are mstly ISA independent. Similarly, pen surce perating systems like Linux are largely free f ISA dependencies except at fr a small (well defined) prtin f the Kernal cde and hardware specific drivers. Lking frward, the develpment tls are evlving twards LLVM, which have a frmal separatin between frnt-end cmpilatin which create a nn-isa specific intermediate frm binary. This intermediate frm ( LLVM byte cde ) can be cmpiled int a hardware specific ISA befre the cde is executed. The Ggle Chrme brwser utilizes LLVM byte cde t enable a multi-platfrm brwser that can run the same LLVM byte cde at near native speeds n multiple architectures. Currently the Ggle implementatin, knwn as Prtable Native Client is available n ARM, x86, and MIPS. A.2.2 PC Scenaris Scenari 1 - VNF state migratin frm x86 blade server t Bradcm XLP MIPS-64 based blade server

4 x86 NFV Blade vepc State vepc Executable Surce cde cmpiled x86 Data Plane API SR-IOV Standard KVM Migrate vepc state XLP964 NFV Blade vepc State vepc Executable Surce cde cmpiled MIPS-64 Data Plane API FMN Standard KVM #1 #2 #3 PCIe - Hst #16 #1 #2 #3 #16 PCIe - Device External NIC Card Integrated Netwrk Interface Trident II+ Tmahawk Simulated BTS User Equipment Internet : Vide Surce Server Switch ver cmmand Figure 3 - VNF Migratin PC Detail 1. Shw vepc with vide traffic flwing thrugh t the simulated BTS running n x86 system. 2. VNF n the x86 will be placed in a standby state, and the state infrmatin will be frzen. 3. VNF state will be mved frm the x86 blade t the XLP MIPS-64 blade. 4. VNF will be restarted n the MIPS-64 blade with the transitined state. 5. Traffic will flw will be reruted t the vepc running n the XLP MIPS-64 A.2.3 Mapping t NFV ISG Wrk Mapping f ur wrk t dcuments f NFV ISG is shwn belw: Use Case Requirement E2E Arch Cmments Scenari 1 UC#1 - This scenari demnstrates IaaS acrss tw different administratin dmains that are ptentially using different hardware. 1) (Optinal) If this PC intends t slve r validate any challenge r nging wrk in NFV ISG wrking grups, cmplete the table belw: INF SWA MAN REL PER Cmments Scenari 1 x This scenari extends the definitin f prtability t encmpass applicatins and envirnments that are ISA independent.

5 A.2.4 PC Success Criteria The success criteria is straight frward fr this PC: VNF shuld successfully migrate frm the x86 blade server t the XLP MIPS-64 based blade server. Bearers that are setup n the x86 shuld be transferred t the XLP MIPS-64 blade server with the delay being the nly impact and will be transparent t the user equipment. This PC des nt attempt t demnstrate perfrmance f either the x86 r MIPS-64 platfrms. Only bearers that have been setup are transitined ver t the XLP platfrm. A.2.5 Expected PC Cntributin List f cntributins twards specific NFV ISG Grups expected t result frm the PC Prject: 1. PC Prject Cntributin #1: VNF Sftware Develpment Best Practices t achieve ISA Independence, t NFV Grup SWA (NFV-SWA001) This cntributin will include recmmendatins fr a fully ISA Independent Open-Surce Server Sftware Architecture including hypervisr, perating system, data-plane interface and clud management pieces. vepc will be shwn as an example f what can be accmplished using ISA independent sftware architecture. 2. PC Prject Cntributin #2: vepc active migratin use case, t NFV Grup INF (NFV-INF008)