Project Proposal NGVS Nextgen VIM Scheduler 8 March

Project Proposal “NGVS” Nextgen VIM Scheduler 8 March 2017 Wassim Haddad, Ericsson Amar Kapadia, Aarna Networks

Problem Statement • New upcoming requirements for the VIM scheduler (currently Open. Stack Nova) – – Higher performance Higher density of compute instances Higher security Greater support for distributed NFV (MEC, network edge virtualization, v. CPE) 2

Solution: Containers 1. Scaling NFV – Are containers the answer 2. Open. Stack + Kubernetes + Hypercontainer = The Container Platform for NFV 3. Container Integrated for NFV 4. NFV Deployment Models: Journey from Open. Stack to Containers Open. Stack ZUN and High Performance Container Workloads • 10 x density 5. 6. Implications of 5 G and Edge Computing • 10 x faster boot time 7. Next Generation Telco/ NFV – VNF Containers 8. Container Based VNFs – Deploy on Open. Stack • Lower security 9. Building NFV to Enable Cloud-Native Services on Open. Stack 10. Open Source Orchestration and Service Chaining of Containerized VNFs … • Others thinking similarly 11. Cloud-Native NFV: Challenges for Operators 12. Containerized & Scalable NFV’s in Open. Stack Cloud … Containerizing SBC 13. How to Enable High Performance Containerized VNFs with Open. Stack ZUN 14. End-to-End IOT Platform based on Open. Stack 15. Secure Fast Packet Processing in Containers 16. Is Open. Stack Ready for Cloud Native Telco 17. Connecting Cloud Native VNF … Kubernetes with Open. Daylight 18. Telco Cloud Evolution with Open. Stack and Container-Based VNFs Architecture – OPNFV already has container projects • • • 3 K 8 s scenarios in Danube LXD support Open. Retriver – Open. Stack Boston Summit has 18 NFV + Container Proposals 3

Solution: Unikernels • 10 x density • 100 x faster boot time – Fast enough to support serverless (event driven) scheduling • 2 x performance • Higher security • But requires VNF recompile See Unikernel presentation by Wassim & Heikki 4

Net-net • VM, containers and unikernels need to be supported all at once – on the same service chain • Static and serverless scheduling both need to be supported • Full support for distributed NFV 19 February 2015 Linux Foundation Collaboration Summit 5

Project Description • Requirements Collection • Reconfirm Nova as the best option or identify another open source scheduler (e. g. container orchestration engines) • Reconfirm KVM as the best hypervisor option or identify another open source hypervisor • Influence upstream project(s) to incorporate new requirements 19 February 2015 Linux Foundation Collaboration Summit 6

Out-of-Scope • Upstream code contribution • Integration • Testing • Documentation 19 February 2015 We are excluding these items to contain the scope of the project. We might request a scope expansion once this phase is complete. Linux Foundation Collaboration Summit 7

Dependencies • Open. Stack Core Services • Open. Stack Zun • OPNFV Retreiver 19 February 2015 Linux Foundation Collaboration Summit 8

Team • Committers: – – • Wassim Haddad (wassim. haddad@ericsson. com) Heikki Mahkonen (heikki. mahkonen@ericsson. com) Amar Kapadia (akapadia@aarnanetworks. com) Sriram Rupanagunta (srupanagunta@gmail. com) Contributors: We will reach out to everyone who submitted an Open. Stack Boston NFV + Container Proposal to see if they can join – Srinivasa Addepalli (srinivasa. r. addepalli@intel. com) 19 February 2015 Linux Foundation Collaboration Summit 9

Deliverables • Requirements document • Analysis of existing solutions • Blueprints to influence upstream projects 19 February 2015 Linux Foundation Collaboration Summit 10

Schedule • Complete project by Euphrates Release 19 February 2015 Linux Foundation Collaboration Summit 11