Recursive Virtualization and Programming for Network and Cloud - - PowerPoint PPT Presentation

Status Changes Summary

Recursive Virtualization and Programming for Network and Cloud Resources

draft-irtf-nfvrg-unify-recursive-programming-00 Robert Szabo† Zu Qiang† Mario Kind‡

†Ericsson and ‡Deutsche Telekom AG

NFVRG, IETF 95 4/7/2017

1 / 6

Status Changes Summary

History and Updates

RG adoption call in 2015: Changes: new: policy considerations; new: report on experimentations (details in draft-unify-sfc-control-plane-exp-00); updated: Yang data model (based on the needs of the experiments);

2 / 6

Status Changes Summary

New: Policy Considerations

T1 T2...Tn | | | +-----|--|---|------+ |NVFO | | | | Tenant | +--+--+---+----+ | <- Policies | |NFVO: | | Operational | |Service | | Policies-> | |Lifecycle | | | |Management | | | +------+-------+ | | | | | +------+-------+ | | |NFVO: | | Operational | |Resource | | Policies-> | |Orchestration | | ^ | +--+---+----+--+ | |Import to +-----|---|---------+ |Policies

• ther NFVO

/ \ \ +-------+ \ \ / \ to NFVO ^ +------\------|-----+ \ / |Export |VIM \ | | \ / |Policies | +-----+----+---+ | +--------|----|-----+ | |VIM: | | |VIM | | | Tenant | |Orchestration | | | +-----+----+---+ | <- Policies | |& | | | |VIM: | | | |Optimization | | . | |Orchestration | | | +------+-------+ | . | |& | | <- Operational | | | | |Optimization | | Policies | +------+-------+ | | +------+-------+ | | |VIM: | | | | | | |Virtualized 2 | | | +------+-------+ | | |Pys mapping | | | |VIM: | | <- Operational | +--------------+ | | |Virtualized 2 | | Policies +-------------------+ | |Pys mapping | | | +--------------+ | +-------------------+

Hierarchical resource management architecture, with Tenant policies Operational policies Import and export policies

3 / 6

Status Changes Summary

New: SFC Control Plane Experiments

To show that the proposed abstraction and control API for network and cloud resources enables programing of end-to-end SFCs across domains: SF instantiation (VNF) and SFP creation For further details see draft-unify-sfc-control-plane-exp-00

Tenant : +---------+ |SFC&NFV | |Ctrller G| |Global | +---------+ ......’ : : ’..................... U . : ’...........U :U +---------+ : +---------+ +---------+ |SFC&NFV | : |SFC&NFV | |SFC&NFV | |Ctrller M| : |Ctrller D| |Ctrller O| |Mininet | : |Docker | |OpenStack| +---------+ : +---------+ +---------+ : : : : : : : +---------+ : : : |OpenStack| +---------+ +---------+ : |based | |Mininet | |Transport|-#----------------|Cloud | |SDN |-#-|SDN | +----:----+ +---------+ |Click EE | |Domain |-#--|Docker | +---------+ +---------+ |Host | | | # ENNI reference points +---------+ SFC: H1--->--------------------->----------------------+WebSrv ’-HDC--HC---------------<-------Sniffer------DPI-’ Host2<------------’ 4 / 6

Status Changes Summary

Updates: Yang data model changes

Easier IP layer configuration was needed to help bootstrap different planes, especially the management plane: The same control API is used for

data plane, control plane management plane

service function chain definitions. EM – VNF IP connectivity is configured then an EM may easily handle the rest of the configurations.

API o __ | \ Software Ctrler \ API O-------------+ \ \ | \ \ Compute Ctrler \ | | \ | | +---------------------+ | | | | | Joint Software & | | {vCPU | | Network Ctrl API | | memory | |

• | |

storage} | | | | | | | +---------------------+ | | | | | {{vCPU | | |Compute Node | \ [1 memory 3] | | | ==> | storage} | | +----------x----------+ / [2 {port rate 4] \ | | | switching delay}} | +----------x----------+ | +---------------------+ | | | Big Switch & [1 {port rate 3] | Big Software (BiS-BiS) | switching delay} | | with joint [2 4] / Software & Network Ctrler | Network Element | / +---------------------+ / __/ 5 / 6

Status Changes Summary

Summary

The draft shows one approach to combine Network Function Virtualization (NFV) orchestration and Service Function Chain (SFC) control in a recurring (hierarchical) way. We added policy considerations and pointers to an experimentation report based on a proof of concept prototype. Next step: We would like to bring our proof of concept demonstration to IETF.

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. 619609). 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 6 / 6