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 | | | +------+-------+ | Hierarchical resource management | | | | +------+-------+ | | |NFVO: | | architecture, with Operational | |Resource | | Policies-> | |Orchestration | | ^ | +--+---+----+--+ | |Import to +-----|---|---------+ |Policies Tenant policies other NFVO / \ \ +-------+ \ \ / \ to NFVO ^ Operational policies +------\------|-----+ \ / |Export |VIM \ | | \ / |Policies | +-----+----+---+ | +--------|----|-----+ Import and export policies | |VIM: | | |VIM | | | Tenant | |Orchestration | | | +-----+----+---+ | <- Policies | |& | | | |VIM: | | | |Optimization | | . | |Orchestration | | | +------+-------+ | . | |& | | <- Operational | | | | |Optimization | | Policies | +------+-------+ | | +------+-------+ | | |VIM: | | | | | | |Virtualized 2 | | | +------+-------+ | | |Pys mapping | | | |VIM: | | <- Operational | +--------------+ | | |Virtualized 2 | | Policies +-------------------+ | |Pys mapping | | | +--------------+ | +-------------------+ 3 / 6
Status Changes Summary New: SFC Control Plane Experiments Tenant : +---------+ |SFC&NFV | |Ctrller G| To show that the proposed abstraction and |Global | +---------+ control API for network and cloud ......’ : : ’..................... U . : ’...........U :U resources enables programing of end-to-end +---------+ : +---------+ +---------+ |SFC&NFV | : |SFC&NFV | |SFC&NFV | SFCs across domains: |Ctrller M| : |Ctrller D| |Ctrller O| |Mininet | : |Docker | |OpenStack| +---------+ : +---------+ +---------+ SF instantiation (VNF) and : : : : : : : +---------+ SFP creation : : : |OpenStack| +---------+ +---------+ : |based | |Mininet | |Transport|-#----------------|Cloud | For further details see |SDN |-#-|SDN | +----:----+ +---------+ |Click EE | |Domain |-#--|Docker | draft-unify-sfc-control-plane-exp-00 +---------+ +---------+ |Host | | | # ENNI reference points +---------+ SFC: H1--->--------------------->----------------------+WebSrv ’-HDC--HC---------------<-------Sniffer------DPI-’ 4 / 6 Host2<------------’
Status Changes Summary Updates: Yang data model changes API o __ Easier IP layer configuration was needed to | \ Software Ctrler \ help bootstrap different planes, especially API O-------------+ \ \ | \ \ the management plane: Compute Ctrler \ | | \ | | +---------------------+ | The same control API is used for | | | | Joint Software & | | {vCPU | | Network Ctrl API data plane, | | memory | | o | | storage} | | | control plane | | | | +---------------------+ management plane | | | | | {{vCPU | | |Compute Node | \ [1 memory 3] | | | ==> | storage} | service function chain definitions. | +----------x----------+ / [2 {port rate 4] \ | | | switching delay}} | EM – VNF IP connectivity is +----------x----------+ | +---------------------+ | | | Big Switch & configured then an EM may easily [1 {port rate 3] | Big Software (BiS-BiS) | switching delay} | | with joint handle the rest of the configurations. [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
Recommend
More recommend
