Towards recursive virtualization and programming for network and cloud resources

Transcription

1 Towards recursive virtualization and programming for network and cloud resources (draft-unify-nfvrg-recursive-programming-02) Robert Szabo Zu Qiang Mario Kind Ericsson and Deutsche Telekom AG NFVRG, IETF 94 11/4/ / 13

2 Outline 1 Updates 2 Relation to ETSI NFV 3 Extended Examples 4 Summary 2 / 13

3 Chairs feedbacks Ramki and Diego: Below are our thoughts on the Unifying Carrier and Cloud Networks: Problem Statement and Challenges draft. Link to draft: This draft lacks detailed implementation example(s) Our suggestion is to merge this draft with which delves deeper into implementation examples. 3 / 13

4 Updates in 02 New Sec 5: Relation to ETSI NFV Revised Sec 6: Examples 4 / 13

5 Outline 1 Updates 2 Relation to ETSI NFV 3 Extended Examples 4 Summary 5 / 13

6 NFVO s and VIM s Functional Splits NVFO Service Lifecycle Management Resrouce Orchestration / \ / / \ \ / \ VIM VIM VIM VIM: VIM: VIM: Orchestration Orchestration Orchestration & & & Optimization Optimization Optimization VIM: VIM: VIM: Virtualized 2 Virtualized 2 Virtualized 2 Pys mapping Pys mapping Pys mapping NFVO VIM Network service lifecycle management. Orchestration of NFVI resources across multiple VIMs, fulfilling the Resource Orchestration functions; Orchestrating the of NFVI resources (including the optimization of such resources usage), and managing the association of the virtualised resources to the physical compute, storage, networking resources. 6 / 13

7 The Recurring Abstraction / API NVFO Service Lifecycle Management Resrouce Orchestration / \ / / \ \ / \ VIM VIM VIM VIM: VIM: VIM: Orchestration Orchestration Orchestration & & & Optimization Optimization Optimization VIM: VIM: VIM: Virtualized 2 Virtualized 2 Virtualized 2 Pys mapping Pys mapping Pys mapping NVFO Service Lifecycle Management <-- Joint API Resrouce Orchestration / / / <-- Joint API / VIM VIM VIM: VIM: Orchestration Orchestration & & Optimization Optimization <-- Joint API VIM: VIM: Virtualized 2 Virtualized 2 Pys mapping Pys mapping / 13

8 Orchestration Layouts Enabled by the Recurring Abstraction / API NVFO Service Lifecycle Management <-- Joint API Resrouce Orchestration / / / <-- Joint API / VIM VIM VIM: VIM: Orchestration Orchestration & & Optimization Optimization <-- Joint API VIM: VIM: Virtualized 2 Virtualized 2 Pys mapping Pys mapping Domain 4 Orchestration ********************** ****************** * * NFVO: * Service * Lifecycle * Management * / * / <-- Joint API * * * Orchestration ******************** * * * Domain 3 NFVO: * ******** *** ************************* Service * / Lifecycle / / Management / * * * <-- Joint API * * Orchestration * * * * * ********* ********** <-- Joint API * * * VIM: * * VIM: * Virtualized 2 * * Virtualized 2 * Pys mapping * * Pys mapping * * * * Domain 1 * * Domain 2 * ************************* * * 8 / 13

9 How and What The draft contains: motivational examples; definition of a joint software and networking abstraction; Yang data model of the Joint API (for virtualization and control); 9 / 13

10 Outline 1 Updates 2 Relation to ETSI NFV 3 Extended Examples 4 Summary 10 / 13

11 Extended Examples Added virtualization view figures to all the examples Infrastructure reports Simple VNF Forwarding Graph deployment requests VNF Benchmarking as a Service (VBaaS) draft-rorosz-nfvrg-vbaas-00 contains an example based on the proposal of this draft. 11 / 13

12 Outline 1 Updates 2 Relation to ETSI NFV 3 Extended Examples 4 Summary 12 / 13

13 Summary Status: Proof of Concept prototypes demonstrated at SIGCOMM 2015, EWSDN 2015, Globecom 2015 screen-cast coming Next steps: Merge some of the remaining Unifying Carrier and Cloud Networks: Problem Statement and Challenges into this draft RG adoption? Acknowledgements This work is supported by FP7 UNIFY, a research project partially funded by the European Community under the Seventh Framework Program (grant agreement no ). The views expressed here are those of the authors only. The European Commission is not liable for any use that may be made of the information in this document 13 / 13