An Approach Based on Situation Management and Mashups for Overcoming Network Management Situations

Instituto de Informática – UFRGS

An Approach Based on Situation Management and Mashups for Overcoming

Network Management Situations

Oscar Mauricio Caicedo Rendón

Supervisor: Lisandro Zambenedetti Granville

Federal University of Rio Grande do Sul – UFRGS

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

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

Porto Alegre, RS – Brazil

03-10-2014 1

Outline

• Introduction

• Mashment ecosystem

• Process for addressing nmsits

• Mashment system architecture

• Evaluation

• Summary and conclusions

Oscar Mauricio Caicedo Rendón 2

Introduction

Contextualization

• Situation Management (SM)

• Mashups


Introduction

Contextualization

• SM application domains – Origin militar

– Satellite networking (Gopal, 2007)

– Disaster response (George et al., 2010)

– Smart power grid (Magoutas et al., 2011)

– Civil crisis (Hein et al., 2012)

– Aviation (Koelle and Tarter, 2012)

– Public health (Pereira et al., 2013)

– Electric power systems (Krohns-Valimaki et al., 2013)


There is few work about the use of SM in network management

5

Introduction

Contextualization • What is SM?

– Address situations happening or that might happen in dynamic systems (Jakobson et al., 2005)

– A situation is a composed entity in a particular application domain whose components are other entities, their attributes, and relationships in a time interval (Kokar et al., 2009)

– Provide solutions that enable analyzing, correlating, and coordinating interactions among people, information, technologies, and actions targeted to overcome situations (Jakobson, 2014)


6

Introduction

Contextualization

• What are mashups? – Mashups are Web applications built up by end-users through the combination of Web resources

available along the Internet (Simmen et al., 2008) (Cappiello et al., 2010)

– Mashups allow end-users, without advanced programming skills, to create their own and customized applications (Laga et al., 2012)

– Mashups encourage both cooperation and reuse among end-users (Huang et al., 2012)


7

Introduction

Mashups have not been used to face the complexity and time of tasks performed by network administrators in their daily work when coping with situations

Contextualization

• Mashups application domains – Project management (Ozkan and Abidin, 2009)

– Water floods (Tosti and Smari, 2010)

– Fire emergencies (Jchrzak and More, 2011)

– Telco services (Gebhardt et al., 2012)

– Data integration (Han et al., 2013)

– Immersive mirror worlds (Stirbu et al., 2013)

– Specific tasks for network management (Bezerra et al., 2010) (Santos et al., 2010)


8

Introduction

Problem Statement


Find the root cause of unexpected and multiple packet transmission failures in network slices formed by OpenFlow networks

Situations Options Shortcomings

Manage the abrupt performance degradation of one or more switches/routers on networks that use diverse virtualization technologies

Monitor sudden violations in service level agreements in a near real time way

Employ non-integrated solutions such as traceroute, ZenOSS, and OpenNMS

Develop low-level scripts to integrate mismatched solutions

Use research solutions based on policies (e.g. PROCERA), business processes (e.g. MEICAN), and service composition (NetOpen)

It hinders and overloads the work carried out by network administrators

Developing scripts is complex for a network administrator because, usually, he/she is not an experienced programmer

Writing policies, queries, or primitives in specific languages and/or controllers remains complexity in network management

(Chen et al., 2010) (Kim and Kim, 2011) (Santanna et al., 2012)

(Monsanto et al., 2013) (Kim and Feamster, 2013)

9

Introduction

Problem Statement

• In the network management domain, large research efforts (Chen et al., 2010) (Kim and Kim, 2011) (Santanna et al., 2012) (Monsanto et al., 2013) (Kim and Feamster, 2013) have been made to automate and facilitate the management tasks

• So far, none of these efforts has carried out network management by means of SM and mashups


How to carry out network management, in an effective way, by SM and mashups?

Introduction

General Objective

• Investigate the feasibility of using SM and mashups as an effective approach for network management

• Effective approach in terms of – The complexity perceived and the time taken (time-consuming) by network administrators

when carrying out tasks for facing situations

– The traffic and the time of response (time-response) of solutions used by network administrators for coping with situations


11

Introduction

Hypothesis

• The employment of SM and mashups provides an effective approach for network management


12

Introduction

Research questions

• What is the performance, in terms of the complexity and consuming of time, of solutions that use SM and mashups for network management?

• What is the performance, in terms of traffic and time of response, of solutions based on SM and mashups for network management?

• Which mechanisms could be employed to improve the performance of solutions that use SM and mashups for network management?


13

Introduction

Contributions

• Conceptual – The network management situation

concept and its data model

– The mashment concept and its data model

• Specific ― The mashment ecosystem

― The process for addressing network management situations

― The mashment system architecture

― The model for measuring complexity and time-consuming

― The mechanism to automatically recognize network management situations

― The mechanism to dynamic composition of mashments


Mashment Ecosystem

An Approach based on Situation

Management and Mashups for Overcoming


OSCAR MAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. A Mashup Ecosystem for Network Management Situations. The IEEE Global Communications Conference (GLOBECOM 2013), 9-13 December 2013, Atlanta, United States

14 Oscar Mauricio Caicedo Rendón

15

Mashment ecosystem

What is a nmsit?

• A network management situation (nmsit) is an unexpected, dynamic, and heterogeneous situation happening or that might happen in the network management domain – Manage the abrupt performance degradation of one or more switches/routers on networks

that use diverse virtualization technologies

– Monitor sudden violations in service level agreements in a near real time way when, for instance, links formed by virtual switches suffer abrupt and intermittent performance degradation

– Find the root cause of the unexpected traffic overload suffered by a set of routers/switches


16

Mashment ecosystem

• Mashment ― Tunable mashup

― Diverse types of resources

― Multiple providers

― SM investigative aspect

― SM control aspect

― Facilitate the work of network administrators when facing nmsits

What is a mashment?


17

Mashment ecosystem

What is a mashment ecosystem?

Interactions among

software entities,

providers, and end-users

Mashment Ecosystem

Acting as a single unit

Software entities

supporting activities

Activities performed by end-users and

providers

Mashments

End-users creating and

using mashments

Resources for network

management

Providers supplying

resources for network

management and software

entities


Mashment ecosystem

Resources

• A Situation Management Resource is an entity conceived or that can be adapted to deal with one or more nmsits

― Network Management Resources (Ganglia and NetOpen)

― Web-based Management Resources (Google Maps and RRDTool)

― Analytics Management Resource (Junos Networks Analytics Suite)

― Network Situational Resources (JESS and JBoss Drools)

― Operator Resources (Split and Merge)

― Situation Management Resource as a Service

― Mashments


Mashment ecosystem

Stakeholders

• A stakeholder affects and is affected by the activities and interactions performed by other one

― Network Management Resource Providers (Cysco and Citrix)

― Web-based Management Resource Providers (Google and Yahoo )

― Analytics Management Resource Providers (Junos Networks Analytics Suite)

― Network Situational Resource Providers (Jboss and Apache)

― Software Entity Providers


Mashment ecosystem

Stakeholders

• A stakeholder affects and is affected by the activities and interactions performed by other one

― Resource Creator (an expert programmer) is in charge of adapting the resources to be used for coping with nmsits

― Mashment Creator (a professional developer) create, publish, share, sell, and buy mashments

― Network Administrator deal wih nmsits by developing and launching mashments


Mashment ecosystem

Activities

• An activity is an action conducted by one or more of stakeholders or software entities ― Releasing Resource Creators

― Creating

― Reusing

― Publishing

― Selling

― Buying

― Sharing

― Launching Network Administrators

Network Administrators and

Mashment Creators

Mashment Maker


Mashment ecosystem

• An interaction takes place in the relationships stakeholder/stakeholder, software entity/software entity, and stakeholder/software entity

― Occur and Cope represent the emerging of nmsits and the corresponding responses offered by mashments

― Provide and Consume represent the supplying and consumption of resources --> Resource Providers, Resource Creators, Mashment Creators, and Network Administrators

― Instantiate represents the request to execute a mashment--> Maker and Executor

Interactions


Mashment ecosystem

• An interaction takes place in the relationships stakeholder/stakeholder, software entity/software entity, and stakeholder/software entity

― Announce represents the publishing of mashments to be commercialized --> Maker and Marketplace

― Commercialize represents the sharing, purchasing, and selling --> Mashment Creators and Network Administrators

Interactions


Mashment ecosystem

Software Entities

• The software entities are responsible for supporting and automating the activities and interactions happening in the Mashment Ecosystem

― Mashment Maker allows to create, reuse, launch, and publish Mashments

― Mashment Executor creates instances and control the lifecycle of Mashments

― Mashment Marketplace allows to stablish a new value chain in which revenues are shared not only by providers but by all stakeholders


Mashment ecosystem


Process for adressing nmsits




OSCAR MAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. An Approach to Overcome the Complexity of Network Management Situations by Mashments. The 28th IEEE International Conference on Advanced Information Networking and Applications (AINA 2014), 13-16 May 2014, Victoria, Canada


Process for addressing nmsits

Overall Process


28 / 16


Complexity

Complexity is the difficulty perceived by network administrators to carry out tasks targeted to overcome nmsits

These complexities are expressed by using per-task metrics defined for IT Service Management processes (Diao and Keller, 2006)


𝞯 = 𝞯𝑠𝑒𝑙

𝑖

1

+ 𝞯𝑐𝑜𝑛 + 𝞯𝑐𝑜𝑚 + 𝞯𝑙𝑎𝑢

𝑜

1

𝑘

1

𝑗

1


Complexity of Select

• M is the total number of elements used to build up a mashment • 𝑐𝑚 is the complexity of selecting the m-resource

― 0 - if fully automated ― 1 - if manual but tool-assisted ― 2 - if manual

• nAvailableResources is the number of resources available to build up a mashment • gF is the grade of guidance provided to select the resources needed to form a mashment

― 1 - if correct recommendation ― 2 - if general information ― 3 - if information is not provided

• cF represents the impact of wrong selection of resources ― 0 - if negligible impact ― 1 - if moderate impact ― 2 - if severe impact


𝞯𝑠𝑒𝑙 = 𝑐𝑚

𝑀

1

+ 𝑛𝐴𝑣𝑎𝑖𝑙𝑎𝑏𝑙𝑒𝑅𝑒𝑠𝑜𝑢𝑟𝑐𝑒𝑠 − 1 × 𝑔𝐹 × 𝑐𝐹


Complexity of Configure

• N is the total number of elements to be configured • 𝞯𝑛 is the complexity of configuring the n-resource • 𝑠𝑜𝑢𝑟𝑐𝑒𝑃𝑎𝑟𝑎𝑚𝑒𝑡𝑒𝑟(𝑝)

― 0 - if parameter from automation ― 1 - if parameter may be chosen freely ― 2 - if parameter from task documentation ― 3 - if parameter extrapolated from task documentation ― 4 - if parameter is not trivial for unexperienced network administrators ― 5 - if parameter is fixed by the environment to a specific value after additional search ― 6 - if parameter is constrained by the environment to a limited set of possible choices where Network Administrators need to infer the right choice


𝞯𝑐𝑜𝑛 = 𝐶𝑛

𝑁

1

𝐶𝑛 = 𝑠𝑜𝑢𝑟𝑐𝑒𝑃𝑎𝑟𝑎𝑚𝑒𝑡𝑒𝑟(𝑝)

𝑃

1


Complexity of Combine

• L is the total number of links created to build up a mashment • 𝑐𝑙 is the complexity of creating the l-link

― 0 - if link is automatically created ― 1 - if link is created using a tool and data must not be adapted ― 2 - if link is manually created and data must not be adapted ― 3 - if link is manually created and data must be adapted

• M is the total number of resources used to build up a mashment • goF is the grade of guidance provided to create the links needed to form a mashment

― 1 - if correct guidance ― 2 - if general information ― 3 - if information is not provided

• coF represents the impact of wrong combination of resources ― 0 - if negligible impact ― 1 - if moderate impact ― 2 - if severe impact


𝞯𝑐𝑜𝑚 = 𝑐𝑙

𝐿

1

+ 𝑀 − 1 × 𝑔𝑜𝐹 × 𝑐𝑜𝐹


Complexity of Launch

• The complexity of Launch can take one of three values depending on the automation for launching a mashment ― 0 - if entirely automated

― 1 - if manual but tool-assisted

― 2 - if manual



Time-consuming

Time-consuming is the time that network administrator takes to carry out tasks targeted to face nmsits

These times are expressed using the Keystroke-Level Model (Kieras, 2001) (Tian et al., 2011)


𝑻= 𝑻𝑠𝑒𝑙 𝑖1 + 𝑻𝑐𝑜𝑛 + 𝑻𝑐𝑜𝑚 + 𝑻𝑙𝑎𝑢

𝑜1

𝑘1

𝑗1


Time-consuming of Select

• M is the total number of elements used to build up a mashment • 𝛕𝒎 is the time required to select the m-resource

― 0 - if fully automated ― dnd - if manual but tool-assisted ― h+p+2b+nc*k - if manual

Actions of Keystroke Level Model Time (s)

Press and release a key (k) 0.2

Type a string nc * k

Point the mouse (p) 1.1

Hold or release the mouse (b) 0.1

Move the hand from mouse to keyboard (h) 0.4

Drag-and-drop a visual element (dnd) 1.3

Wire two visual elements (wire) 4.1

(Kieras, 2001) (Tiang et al., 2011)


𝑻𝑠𝑒𝑙 = 𝛕𝑚

𝑀

1


Time-consuming of Configure

• N is the total number of elements to be configured • 𝛕𝑛 is the time required to configure the n-resource

― 0 - if fully automated ― h+p+2b+nc*k - if manual


𝑻𝑐𝑜𝑛 = 𝛕𝑛

𝑁

1


Time-consuming of Combine

• L is the total number of links used to build up a mashment • 𝛕𝑙 is the time required to select the m-resource

― 0 - if fully automated ― wire - if manual but tool-assisted ― h+p+2b+nc*k - if manual


𝑻𝑐𝑜𝑚 = 𝛕𝑙

𝐿

1


Time-consuming of Launch

• The time-consuming of Launch can take one of three values depending on automation of requesting the execution of a mashment ― 0 - if entirely automated

― h+p+2b - if manual but tool-assisted

― h+p+2b+nc*k - if manual


38 / 16

Mashment system architecture




OSCAR MAURICIO CAICEDO RENDON, Carlos Raniery P. dos Santos, Arthur Selle Jacobs, Lisandro Zambenedetti Granville. Monitoring Virtual Nodes Using Mashups. Computer Networks (COMNET), v. 64, pp. 55-70, May 2014. ISSN 1389-1286 OSCAR MAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. A Mashup-based Approach for Virtual SDN Management. The 37th IEEE Annual International Computer Software & Applications Conference (COMPSAC 2013), 22-26 July 2013, Kyoto, Japan


Managed resources layer



Adaptation layer



Composition layer



43 / 16

Composition layer



44 / 16

Composition layer



Composition layer



Presentation layer



Evaluation





SDN Case Study - test environment -

challenge: it is needed the fast and ease development of a solution able to present, in an integrated, visual, and intelligible way, information about Open vSwitches, links, and flows handled by Beacon, POX, and Floodlight

nmsit: the Network Administrator needs to investigate which are the Open vSwitches that are causing sudden performance degradation in the OpenFlow-based networks of the test environment



• The Network Administrator creates, launches, and uses different and mismatched Web-based solutions (e.g., Beacon Web Tool, Floodlight Web Tool, and POX Web Tool)

• The Network Administrator creates, launches, and uses a Situational Script that integrates such mismatched solutions



• The Network Administrator develops and launches PMM by the Mashment Maker



• The Network Administrator uses PMM to retrieve information about switches, links, and flows handled by Beacon, POX, and Floodlight


52 / 16 Oscar Mauricio Caicedo Rendón


• The Network Administrator uses PMM to retrieve information about switches, links, and flows handled by Beacon, POX, and Floodlight

SDN Case Study - complexity -


The mashment-based approach decreases the complexity (approx 37%)

SDN Case Study - time-consuming -


The mashment-based approach decreases the time-consuming (approx 75%)

SDN Case Study - time-response-


The time-response of PMM is always ranked as good

Time-response (Joines et al., 2002) optimal (r < = 100) good (100 < r < = 1000) admissible (1000 < r < = 10000) deficient (r > 10000)



The time-response of PMM is always ranked as good



The time-response of PMM is always ranked as admissible

SDN Case Study - traffic-


PMM - additional traffic less than 10%



PMM - additional traffic less than 10%



The additional traffic is less than 10 %

Virtual Nodes Case Study - test environment -

challenge: it is needed a situational solution that presents, in an integrated, visual, and intelligible way, information about Xen, VirtualBox, guests, and Open vSwitches (including links, flows, ports, and traffic)

nmsit: the Network Administrator needs to investigate the Host Computer Systems and guests suffering unexpectedly overload in processor, memory, and/or network as well as the Open vSwitches that are causing sudden performance degradation in an OpenFlow-based network handled by Floodlight


Virtual Nodes Case Study - test environment - • The Network Administrator creates, launches, and uses diverse and disparate Web-based solutions

(e.g., oVirt and Floodlight Web Tool)

• The Network Administrator creates, launches, and uses a Monitoring Script that integrates such disparate solutions



• The Network Administrator develops and launches VNMM by the Mashment Maker


64 / 16


• The Network Administrator uses VNMM to retrieve information about guests, switches, and links located at a virtual node


65 / 16

Virtual Nodes Case Study - complexity -


The mashment-based approach decreases the complexity (about 20%)

Virtual Nodes Case Study - time-consuming -


The mashment-based approach decreases the time-consuming (about 75%)

Virtual Nodes Case Study - time-response-


The time-response of VNMM is always ranked as good

Virtual Nodes Case Study - time-response-


VNMM – extra time less than 10%

Virtual Nodes Case Study - traffic-


VNMM – additional traffic less than 10%

Virtual Nodes Case Study - traffic-


From 1 to 32 guests VNMM generates less traffic for Vbox than Xen

Summary and conclusions

Partial considerations

• The network management is driven towards an environment focused on situations, composite situational solutions, and network administrators

• The mashup foundations are brought up to the SM discipline to carry out its investigative and control aspects

• The mashup technology is led to a novel application domain located in the intersection of SM and the network management


• Flexibility ― Mashments provide a flexible and easy-to-use way for user-centric service

composition

― Network technologies and situational management operations are represented as mashup-able components

― Network Administrators do not require a lot of Web programming skills to create situational management capabilities

― Network Administrators can customize and improve their workspace by themselves




• Extensibility ― Network Administrators can addressing nmsits by conducting a simple

process for creating/using mashments

― Network Administrators who develop mashments are able to extend the Mashment Ecosystem and, therefore, enhance/improve their workspace

― Building up a mashment from existing applications is easier than developing a composite application from scratch




74 / 16


Answering the research questions

What is the performance, in terms of the complexity and consuming of time, of solutions that use SM and mashups for network management?

The evaluations indicate that the mashment-based approach can be less complex and consuming of time than proprietary and incompatible CLIs and GUIs used currently for coping with nmsits

What is the performance, in terms of traffic and time of response, of solutions based on SM and mashups for network management?

Which mechanisms could be employed to improve the performance of solutions that use SM and mashups for network management?

The evaluations indicate that the time of response of mashments can be ranked as optimal and/or good. Their behavior in traffic is similar to the current solutions used for coping with nmsits

Mechanisms for nmsits recognition and dynamic mashment composition are already defined but their impact on performance of the mashment-based approach needs to be evaluated yet



Next steps of investigation

• Evaluation of automatic recognition of nmsits

• Evaluation of dynamic composition of mashments

• Submission of a paper to the journal IEEE Internet Computing (IEEE Transactions on Computers)



Publications

• OSCAR MAURICIO CAICEDO RENDON, Carlos Raniery P. dos Santos, Arthur Selle Jacobs, Lisandro Zambenedetti Granville. Monitoring Virtual Nodes Using Mashups. Computer Networks (COMNET), v. 64, pp. 55-70, May 2014. ISSN 1389-1286

• OSCAR MAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. An Approach to Overcome the Complexity of Network Management Situations by Mashments. The 28th IEEE International Conference on Advanced Information Networking and Applications (AINA 2014), 13-16 May 2014, Victoria, Canada


77 / 16


Publications

• OSCAR MAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. A Mashup Ecosystem for Network Management Situations. The IEEE Global Communications Conference (GLOBECOM 2013), 9-13 December 2013, Atlanta, United States

• OSCARMAURICIO CAICEDO RENDON, Felipe Estrada-Solano, Lisandro Zambenedetti Granville. A Mashup-based Approach for Virtual SDN Management. The 37th IEEE Annual International Computer Software & Applications Conference (COMPSAC 2013), 22-26 July 2013, Kyoto, Japan



Collaboration

• Wanderson Paim de Jesus, Ricardo L. dos Santos, OSCAR MAURICIO CAICEDO RENDON, Lisandro Zambenedetti Granville. A Platform for Programmable Virtual Network Management. The 31st Brazilian Symposium on Computer Networks and Distributed Systems (SBRC 2013), 6-10 May 2013, Brasilia, Brazil


Guambianos – Colombia Volcán Puracé – Colombia

¡Gracias!





An Approach Based on Situation Management and Mashups for Overcoming Network Management Situations

Technology

Transcript of An Approach Based on Situation Management and Mashups for Overcoming Network Management Situations