Unifying Carrier and Cloud Networks: Problem Statement and - - PowerPoint PPT Presentation

unifying carrier and cloud networks problem statement and
SMART_READER_LITE
LIVE PREVIEW

Unifying Carrier and Cloud Networks: Problem Statement and - - PowerPoint PPT Presentation

Unifying Carrier and Cloud Networks: Problem Statement and Challenges draft-unify-nfvrg-challenges-02 Diego Daino (Telecom Italia) A. Csaszar (Ericsson) R. Szabo (Ericsson) K. Pentikousis (EICT) Z. Qiang (Ericsson) M. Kind (Deutsche Telekom


slide-1
SLIDE 1

UNIFY is co-funded by the European Commission DG CONNECT in FP7

Unifying Carrier and Cloud Networks: Problem Statement and Challenges draft-unify-nfvrg-challenges-02

  • A. Csaszar (Ericsson)
  • K. Pentikousis (EICT)
  • M. Kind (Deutsche Telekom AG)
  • R. Szabo (Ericsson)
  • Z. Qiang (Ericsson)
  • H. Woesner (BISDN)

Diego Daino (Telecom Italia)

slide-2
SLIDE 2

Reference Scenario and Motivation

Reference Scenario

  • Integration between Network Infrastructure and DC Infrastructure
  • Implementation of NFV (for Compute, Storage and Network resources)
  • Implementation of SDN
  • Implementation of Flexible Service Chaining solutions (supported by SDN and

NFV technologies)

  • Multi-vendor, multi-technology and multi-provider environments

Motivation

  • Compute and storage virtualization and network virtualization are tightly connected

at multiple levels:

  • in a DC there are not only compute resources but also network resources,

supposed to be virtualized to be shared

  • virtualized network resources in a SDN domain, if offered to clients, imply

virtualization of compute resources if supposed to be shared

  • Argument for: joint software and network recursive programmatic interface

22/07/2015 draft-unify-nfvrg-challenges-02 2

slide-3
SLIDE 3

New in -02

  • Introduction of concept of Universal Node (UN)
  • Introduction of Unified Interface (U) and Unified Recurrent Control (URC):
  • RO Control Plane with U and URC
  • zoom into PoP DC Network with U and URC
  • New text for Problem Statement section

22/07/2015 draft-unify-nfvrg-challenges-02 3

slide-4
SLIDE 4

Universal Node

22/07/2015 draft-unify-nfvrg-challenges-02 4

Legend: Switch (SW) Compute Node (CN) Universal Node (UN)

  • An innovative element that integrates and manages in a unified

platform both compute and networking components and can present also an inner local layer of orchestration, capable to interact with an external one

+----------+ | +----+ | UN | | CN | |

  • -+--+----+--+-o

| | SW | | | +----+ | +----------+

slide-5
SLIDE 5

Unified Interface and Unified Recurrent Control

  • Unified Interface (U): a joint recursive programmatic interface to

use for both compute and network resources

  • Unified Recurrent Control (URC): an element that performs both

compute and network control and that can be used in a hierarchy structure

22/07/2015 draft-unify-nfvrg-challenges-02 5

slide-6
SLIDE 6

RO Control Plane with U and URC

22/07/2015 draft-unify-nfvrg-challenges-02 6

+---------+ |Orchestr.| | SP0 | _____+---------+_____ / | \ / V Ic2 \ | +---------+ | Ic1 V |SDN Ctrl | V Ic3 +---------+ | SP2 | +---------+ |Comp Ctrl| +---------+ |Comp Ctrl| | SP1 | / | \ | SP3 | +---------+ +--- V ----+ +---------+ | | +----+ | | | | |SW3 | | | V | +----+ | V +----+ V / \ V +----+ 1 |PoP | +----+ +----+ |PoP | 8

  • --|DC1 |----|SW2 |------|SW4 |----|DC2 |--o

+----+ +----+ +----+ +----+ +---------+ |Service | |Orchestr.| +---------+ | | V U +-------------------+ | Unified Recurrent | | Control (URC) | +-------------------+ / | \ / V U \ | +---------+ | U V | URC | V U +---------+ | | +---------+ | URC | +---------+ | URC | | | / | \ | | +---------+ +--- V ----+ +---------+ | | +----+ | | | | |SW3 | | | V | +----+ | V +----+ V / \ V +----+ 1 |PoP | +----+ +----+ |PoP | 8

  • --|DC1 |----|SW2 |------|SW4 |----|DC2 |--o

+----+ +----+ +----+ +----+

  • Existing separated compute and network

programming interfaces cannot easily provide recursions and cannot always satisfy key requirements for multi-vendor, multi-technology and multi-provider interoperability

slide-7
SLIDE 7

PoP DC Network with U and URC

22/07/2015 draft-unify-nfvrg-challenges-02 7

NBI | +---------+ |Comp Ctrl| +---------+ +----+ | IcA V | IcB:to CNs +---------+ V |SDN Ctrl | | | ext port +---------+ +---+ +---+ to|SW |SW | |SW | +-> ,+--++.._ _+-+-+ V ,-" _|,,`.""-..+ _,,,--"" | `. |""-.._ +---+ +--++ `+-+-+ ""+---+ |SW | |SW | |SW | |SW | +---+ ,'+---+ ,'+---+ ,'+---+ | | ,-" | | ,-" | | ,-" | | +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ |CN| |CN| |CN| |CN| |CN| |CN| |CN| |CN| +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ NBI | +---------+ | URC | +---------+ +----+ | U V | U:to CNs +---------+ V | URC | | | ext port +---------+ +---+ +---+ to|SW |SW | |SW | +-> ,+--++.._ _+-+-+ V ,-" _|,,`.""-..+ _,,,--"" | `. |""-.._ +---+ +--++ `+-+-+ ""+---+ |SW | |SW | |SW | |SW | +---+ ,'+---+ ,'+---+ ,'+---+ | | ,-" | | ,-" | | ,-" | | +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+ |CN| |CN| |CN| |CN| |CN| |CN| |CN| |CN| +--+ +--+ +--+ +--+ +--+ +--+ +--+ +--+

  • Joint compute, storage and network

programmatic U Interface and URC allow multi-level recursion and facilitate

  • rchestration of resources
slide-8
SLIDE 8

Problem Statement

  • This section has been revisited for better and clearer

understanding with reference to the idea of tight connection between compute virtualization and network virtualization

22/07/2015 draft-unify-nfvrg-challenges-02 8

slide-9
SLIDE 9

Summary

  • Introduction of new concepts like Universal Node (UN), Unified

Interface (U) and Unified Recurrent Control (URC)

  • New figures added for:
  • RO Control Plane with U and URC
  • zoom into PoP DC Network with U and URC
  • Editorial changes and improvements made with reference to

Problem Statement section References

  • draft-unify-nfvrg-challenges-02
  • www.fp7-unify.eu

22/07/2015 draft-unify-nfvrg-challenges-02 9

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.