mashups for network management

Instituto de Informática – UFRGS

Mashups for Network Management - A Case Study on SDN -

Oscar Mauricio Caicedo Rendón Master on Telematics

Phd Student on Computer Science

University Federal do Rio Grande do Sul – UFRGS

Computer Networks – http://networks.inf.ufrgs.br/

Institute of Informatics - http://inf.ufrgs.br/en/

Porto Alegre, Brazil

08-11-2013

ERRC 2013 - 11a Escola Regional de Redes de Computadores

Outline

• Introduction

• Mashups

• Software Defined Networking

• Mashups & SDN

• SDN Mashup System

• Slice Monitoring Mashup

• Conclusions

Oscar Mauricio Caicedo Rendón Outline

3 / 16 Oscar Mauricio Caicedo Rendón

Network Evolution

A specialized network per service A particular management per service Difficulty in introducing new services

Services

Transport

& Access

Introduction


Access

Transport

Services IP

Network Evolution

Network convergence Network continously evolving New services constantly emerging Network management becomes more complex everyday

(Gutiérrez,1998)

Introduction


What is Network Management?

Network management is to: • Monitoring and controlling networks • Planning network extensions and amendments • Incorporate new elements without interfering ongoing operations

(Leinwand and Fang, 1995)

Introduction

6 / 16

Network Management & Internet Technologies

WBEM (Web Based Enterprise Management)

XML (eXtensible Markup Language) / Web Services

WS-BPEL (Web Services – Bussines Process Execution Language)


Mashups Web 2.0

Introduction

7 / 16

XML / Web Services


Web Services Distributed Management (OASIS, 2005)

Web Services for Management (DMTF, 2006)

NETCONF (RFC 4741, 2006) (6241, 2011)

Introduction

Generic Architecture

Network Management Service 1

Network ManagementService 2

Network Management Service K

Service Registry

Service Broker

Bind Service Provider

Publish

Manager 1

Manager 2

Manager M

Service Consumer

Service Requester

Find

Agent 1

Agent 2

Agent N

Service Provider

8 / 16

NETCONF / SOAP

(Iijima et al., 2008)

8 / 16 8 / 16 Oscar Mauricio Caicedo Rendón

Introduction

Architecture

9 / 16

XML / Web Services


Introduction

Specific Architecture

Context and Origin

Mashups emerged in 2005 Mashup technology is a fundamental part of Web 2.0 Mashups are focused on end-users

(Maximilien et al., 2007)


Mashups

What is a Mashup?

A Mashup is a composite Web Application built by end-users through combining resources available along the Internet

(Sheth et al., 2007) (Simmen et al., 2008)


(Fonte: Atmail Corporation, 2011)

Calendar + GoogleMap

Mashups

Benefits

(Seyfi and Patel, 2010)

Composition model that allows combine resources (applications/data/GUI) to add value

Reuse resources and even mashups for developing novel applications and decreasing development costs

Sharing open resources and mashups Abstraction model that allows end-users without advance programming skills

to develop composite applications


Mashups

Taxonomy – Resource Type

User Interfaces: e.g. photos and maps integration Data Sources: e.g. feeds integration Services: e.g. Application logic Integration


(Fonte: Google Corporation, 2011)

Mashups

(Fonte: Motorola Corporation, 2011)

(Hoyer et al, 2008) (Xie et al., 2010)

Taxonomy – User Type

Consumer Mashups point out to Web end-users

Maps RSS Feeds Photos Weather


Enterprise Mashups targeted to company employees

Mashups

Enterprise tasks Business intelligence Record data

(Hoyer et al, 2008) (Xie et al., 2010)

Application

Initial Areas • Weather • Photos • Maps • News • Leisure activities

(Chu et al., 2010)

Web 2.0 consolidation Tools and security evolution

AJAX engine on devices such as smartphones, tablets, and so on

New Areas • IT Management • Project Management • Critical situations


Mashups

16 / 16

Benefits for Network Management?

Web Services interact with applications

Mashups interact with end-users


Network Administrators would support their daily activities by themselves

Network Administrators would develop their own content

Network Administrators would create, enhance, and customize their workspaces

Mashups


Software Defined Networking

Context

The Internet has continuously and rapidly evolved in the Network Access Layer and the Application Layer

The Internet has suffered a standstill in the evolution of both the Transport Layer and the Internet Layer --> Internet ossification

New proposals to deal with the Internet ossification: Software Defined Networks and Network Virtualization

(Chowdhury and Boutaba, 2009) (Gude et al., 2008) (Khan et al., 2012)


Architecture

SDN deployment proposals • OpenFlow • FORCES (Forwarding and Control Element Separation)

Network Application

Network Application

Network Operating System (NOS)

Network Application

Open API

Open Protocol

Packet Forwarding

Application

Plane

Control

Plane

Data

Plane


(McKeown et al., 2008) (Lantz, Heller, and McKeown, 2010) (Doria et al., 2010)


An OpenFlow Deployment

Network Application

Network Application

Beacon Controller

Network Application

Java-based Beacon API

OpenFlow Protocol

Open vSwitch, HP E6600

Application

Plane

Control

Plane

Data

Plane

Network Application

Network Application

Floodlight

Network Application

OpenFlow Protocol

Datacom 4100, NEC IP 8800

Floodlight REST API




Virtual SDN

Virtual SDN = SDN aided by virtualization technologies

A Virtual SDN is a subset of the underlying physical network and, usually, can be formed by several SDN-enabled virtual resources

Goal: Sharing a network physical infrastructure among several virtual networks

Network Application

Network Application

NOS

Open API

Open Protocol

Physical Packet Forwarding

Virtual Packet Forwarding

Virtualization Layer



Management Problem

How to manage virtual, heterogeneous, and SDN-based networks in an integrated way and regardless of NOS by focusing in the Network Administrator?

Network Application A

Network Application B

NOS_1

Open API_1

Open Protocol_1



Virtualization Layer X

Network Application C

Network Application D

NOS_n

Open API_n

Open Protocol_n



Virtualization Layer Y

Different NOS

implementations

Diverse

virtualization

technologies

Several specific NOS

management tools


Mashups & SDN

Mashups for SDN Management?

A novel mashup-based approach lets to deal with the heterogeneity of Virtual SDN and allows Network Administrators to build up SDN Management composite solutions

Approach formed by • The SDN Mashup concept • The SDN Mashup System

Mashups are Web applications created through the integration of different resources (e.g., data, application logic, and user interfaces) available on the Internet

Mashups allow end-users, without advanced programming skills to create their own and customized applications

Mashups encourage both cooperation and reuse among end-users

(Simmen et al., 2008)(Cappiello et al., 2010)(Yu, 2008)


Mashups & SDN

Stakeholders

Virtual Network Provider (VNP) operates Virtual SDN Resources and provides them to Virtual Network Operators (VNO)

A VNO provides Virtual SDN Slices to customers and/or applications

SDN Administrator (Network Administrator)

(Chowdhury and Boutaba, 2009) (Khan et al., 2012)


Mashups & SDN

Concepts

A Virtual SDN Slice is formed by one or more Virtual SDN containing several Virtual SDN Resources.

Virtual SDN Resources

• Virtual Network Elements (VNE) - e.g., Vyatta Router and Open vSwitch running on a hypervisor

• NOS – e.g., NOX, POX, Beacon, and Floodlight

• Network Applications (NAP) - e.g., a network service to multicast path selection running on NOS


Mashups & SDN

What is a SDN Mashup?

• A SDN Mashup is a composite Web application, centered in the Network Administrator, and aimed to manage any SDN that has been deployed using Network Virtualization


Mashups & SDN

SDN Mashup Characteristics

It hides the heterogeneity and complexity of SDN Resources (NAP, NOS, and VNE)

It allows to combine information retrieved from SDN Resources

It lets to blend local and external visualization APIs to generate integrated and advanced GUIs

It provides access to multiple Network Administrators to enable communication and collaboration among them by sharing and reusing SDN Mashups


Mashups & SDN

An Usage Scenario

Virtual Network Operator

Customers

Increased demand

Virtual Network Provider B

Virtual Network Provider A

Virtual SDN: POX,

Open vSwitch

Virtual SDN:

Floodlight, Open

vSwitch

GUI and CLI for POX GUI and CLI for Floodlight Programming Network

Managment Scripts

Create SDN Mashups on a Mashup Development Environment

Use/reuse SDN Mashups

SDN Administrator


Mashups & SDN

SDN Mashup

Concept


SDN Mashup System

SDN Mashup System

Architecture


Slice Monitoring Mashup

Test Environment

Challenge The monitoring of a

heterogeneous Virtual SDN Slice



Internal Operation



Run Time


Conclusions

Mashup technology empowers the SDN Administrator with the important ability to build, extend, and customize SDN management solutions

SDN Mashups have little compromise on usability, particularly during the SDN Mashup composition process

SDN Mashups leads the Mashup technology towards a new application domain (SDN Management) and the Network Management towards an environment centric in the Network Administrator

Questions?

Mashups for Network Management - A case study on SDN -

Guambianos – Colombia Volcán Puracé – Colombia

¡Muchas Gracias!

Oscar Mauricio Caicedo Rendón

37 / 16

References

N. Chowdhury and R. Boutaba, “Network Virtualization: State of the Art and Research Challenges,” Communications Magazine, IEEE, vol. 47, no. 7, pp. 20–26, july 2009. N. Gude, T. Koponen, J. Pettit, B. Pfaff, M. Casado, N. McKeown, and S. Shenker, “NOX: Towards an Operating System for Networks,” ACM SIGCOMM Comput. Commun. Rev., vol. 38, no. 3, pp. 105–110, 2008. A. Khan, A. Zugenmaier, D. Jurca, and W. Kellerer, “Network virtualization: a Hypervisor for the Internet?” Communications Magazine, IEEE, vol. 50, no. 1, pp. 136–143, january 2012. N. McKeown, T. Anderson, H. Balakrishnan, G. Parulkar, L. Peterson, J. Rexford, S. Shenker, and J. Turner, “OpenFlow: Enabling Innovation in Campus Networks,” ACM SIGCOMM Comput. Commun. Rev., vol. 38, no. 2, pp. 69–74, march 2008. A. Doria, J. Hadi Salim, R. Haas, H. Khosravi, W. Wang, L. Dong, R. Gopal, and J. Halpern, “Forwarding and Control Element Separation (ForCES) Protocol Specification,” RFC 5810, march 2010. B. Lantz, B. Heller, and N. McKeown, “A Network in a Laptop: Rapid Prototyping for Software-definedNetworks,” in Proceedings of the 9th ACM SIGCOMM Workshop on Hot Topics in Networks. New York, NY, USA: ACM, 2010, pp. 19:1–19:6. A. Tootoonchian and Y. Ganjali, “HyperFlow: a Distributed Control Plane for OpenFlow,” in Proceedings of the 2010 internet network management conference on Research on enterprise networking, ser. INM/WREN’10. Berkeley, CA, USA: USENIX Association, 2010, pp. 3–3. D. E. Simmen, M. Altinel, V. Markl, S. Padmanabhan, and A. Singh, “Damia: Data Mashups for Intranet Applications,” in Proceedings of the 2008 ACM SIGMOD international conference on Management of data. New York, NY, USA: ACM, 2008, pp. 1171–1182. C. Cappiello, F. Daniel, M. Matera, and C. Pautasso, “Information Quality in Mashups,” Internet Computing, IEEE, vol. 14, no. 4, pp. 14–22, july-august 2010. J. Yu, B. Benatallah, F. Casati, and F. Daniel, “Understanding Mashup Development,” Internet Computing, IEEE, vol. 12, no. 5, pp. 44–52, september-october 2008.


38 / 16

J. J. Jung, “Collaborative browsing system based on semantic mashup with open apis,” Expert Syst. Appl., vol. 39, no. 8, pp. 6897–6902, 2012. A. Majchrzak and P. H. B. More, “Emergency! Web 2.0 to the Rescue!” Commun. ACM, vol. 54, pp. 125–132, April 2011. H. Gebhardt, M. Gaedke, F. Daniel, S. Soi, F. Casati, C. Iglesias, and S. Wilson, “From Mashups to Telco Mashups: A Survey,” Internet Computing, IEEE, vol. 16, no. 3, pp. 70–76, may-june 2012. A. P. Sheth, K. Gomadam, and J. Lathem, “SA-REST: Semantically Interoperable and Easier-to-Use Services and Mashups,” IEEE Internet Computing, vol. 11, pp. 91–94, 2007. P. Community. (2012) POX Home. [Accessed july 20, 2012]. [Online]. Available: https://github.com/noxrepo/pox. D. Erickson. (2012) Beacon Home. [Accessed july 20, 2012]. [Online]. Available: https://openflow.stanford.edu/display/Beacon/Home. F. Community. (2011) Floodlight Home. [Accessed july 20, 2012]. [Online]. Available: http://floodlight.openflowhub.org/. K.-K. Yap, M. Kobayashi, D. Underhill, S. Seetharaman, P. Kazemian, and N. McKeown, “The Stanford OpenRoads Deployment,” in Proceedings of the 4th ACM international workshop on Experimental evaluation and characterization. New York, NY, USA: ACM, 2009, pp. 59–66. D. Mattos, N. Fernandes, V. da Costa, L. Cardoso, M. Campista, L. Costa, and O. Duarte, “OMNI: OpenFlow MaNagement Infrastructure,” in Network of the Future (NOF), 2011 International Conference on the, november 2011, pp. 52 –56. N. Kim and J. Kim, “Building NetOpen Networking Services over OpenFlow-based Programmable Networks,” in Information Networking (ICOIN), International Conference on, jannuary 2011, pp. 525 –529. R. T. Fielding and R. N. Taylor, “Principled Design of the Modern Web Architecture,” ACM Transactions on Internet Technology, vol. 2, no. 2, pp. 115–150, may 2002. S. Joines, R. Willenborg, and K. Hygh, Performance Analysis for Java Websites. Boston, MA, USA: Addison-Wesley Longman Publishing Co., Inc., 2002.

References


mashups for network management

Technology

emerging network management

specialized network

network extensions

applications mashups

mashups context

management oasis

particular management

management dmtf