Network as a Service principle virtual CPE as a Service TERENA - PowerPoint PPT Presentation

Network as a Service principle virtual CPE as a Service TERENA Network Architects Workshop Victor Reijs, HEAnet victor.reijs@heanet.ie 22 November 2012 1

Agenda • Clouds and XaaS services... • OpenFlow, SDN and NaaS... • Why Network as a Service?... • Cloud resources... • A Danish cloud... • OpenNaaS architecture... • Use cases (virtual CPE)... • Questions and Answers…

Clouds and XaaS services • SaaS: Software as a Service • PaaS: Platform as a Service • IaaS: Infrastructure as a Service – NaaS: Network as a Service • MaaS: Management as a Service http://csrc.nist.gov/publications/drafts/800 ‐ 146/Draft ‐ NIST ‐ SP800 ‐ 146.pdf

Essential characteristics • On ‐ demand self ‐ service • Broad network access • Resource pooling • Rapid elasticity • Measured service

OpenFlow, SDN and NaaS • OpenFlow Management protocol for forwarding tables • SDN Supports a control plane abstraction • NaaS Integration; virtualisation; and service oriented

SDN’s design axis Centralised control Decentralised Microflow Aggregated Reactive forwarding Proactive Virtual systems Physical Fully consistent state Eventually consistent http://opennetsummit.org/talks/ONS2012/heller ‐ mon ‐ intro.pdf

Why Network as a Service? (1/2) • IP cloud • On ‐ demand self ‐ service • Broad network access • Resource pooling • Rapid elasticity • Measured service

Why Network as a Service? (2/2) • Lower layers • More flexibility in routing (NetFlow resource) • Allowing applications with more dynamic network needs, which need more than Internet ‐ service: security/VPN, capacity and energy ‐ consumption

Cloud resources • Machine and human resources (Amazon Mechanical Turk Worker) have an important function to play in generating services • They can be integrated nowadays properly: using for instance APIs, WebServices • Resources can be for working (Worker ‐ Resources: WoR) or for managing the Working ‐ Resources (Management ‐ Resources: MaR) • Management ‐ Resources becomes an User issue: making it a single domain... • Management ‐ Resources (follows FCAPS): Trouble; Configuration&Activation; Information; Quality; and Policy • Standardisation is important: OGF, DMTF, ISOF ‐ RG, TMF, eTOM

A Danish cloud http://www.2dots ‐ era.com/2012/08/lego ‐ cloud ‐ sculptures ‐ x ‐ eric ‐ maldre.html

LEGO stud specification http://en.wikipedia.org/wiki/File:Lego_dimensions.svg

Resource shopping list Worker Management Resource* Resource* Fibre/Air Ethernet IP Video * defined in MaaS: GN3 ‐ JRA1 ‐ T4

Going to the marketplace

Putting together with the LEGO studs http://www.youtube.com/watch?v=wa ‐ trX3ifR8

OpenNaaS architecture Network Intelligence • Integration with Northbound OpenStack NS 3P OpenNebula Middleware Scripting NSA (NSI) Middleware • IaaS/Cloud managers GUI . . . • Other NMS. The user • Remoting NaaS Layer Network Resource Router Resource • Network HAL abstraction to 3P Optical Switch BoD Resource infrastructure. Extensions Resource Resources manageable by the user. • • Access controlled by the Sec. . . . Manager. Resource Layer Resource Lifecycle Platform • Reusable building blocks, common to Persistence Manager Resource Protocol Session Manager Queue all extensions. CLI Security • Controls access to the infrastructure. • Integrity, Policy, etc.. . . . Platform Managed infrastructure BoD

Use cases • virtual Client Premises Equipment (vCPE) (HEAnet)... • Supporting of moving VMs within hybrid clouds (private/community/public) (GridIreland/NORDUnet) • Multiple providers acting on same hardware (DeIC/Danish Health network) • Multimedia network (University of Bristol)

virtual Client Premises Equipment Core routers Aggregated vCPE CPE Client 1 Client 2 Client 3

Virtualise the network resources Make routers virtually Configure them up Make links between them Delegate partial control to the user Nice interface

P2P provisioning system Quick, easy changes Automatic inventory Automatic monitoring Access to outside networks

OpenNaaS Provisioning system for logical routers Open source CLI + RESTful API Developing a GUI Integrated with Bandwidth on Demand

Including GÉANT BoD

Conclusions • Getting experience with XaaS • Integration of Network and other layers • Resource management still needs to be defined together with marketplace • Work in progress, but plan to provide pilot/operational vCPE services in 2013

Q&A