E2E Services using Cloud Visitation Platforms

Virtual

.

Pre-Story: The First HomeBox

Marat Zhanikeev -- [email protected] E2E Services using Cloud Visitation Platforms -- http://tinyurl.com/marat140221 2/23...

2/23

.

The First HomeBox

…

Bigger ISP

Bigger ISP

ISP Network

Inside home ADSL router

• Router • QoS Broker • Meter

End user

• L2 VLAN • Shaping • Policing

ISP NOC

02 myself+0 "A Home Gateway Box with Meter, Probe and L2 QoS Policy Edge" COMPSACW (2013)


3/23

.

HomeBox: Early Usecases• e2e probing, packet capture, L2/L3 QoS Policy Edge

Home Gateway Box

switch/mirror

meter Mirror traffic

Data to ISP (1) Flow (2) Probing

Probes

Probing tasks 2 devices in 1 box

Probing methods



4/23

.

HomeBox: The Actual Box

1G Hub

Internet

Touch screen interface Home

network

Router Meter



5/23

.

HomeBox: Lessons Learned

1. too expensive! 2 boxes, twice the price

2. high maintenance cost◦ device is at home, firmware updates?

3. higher flexibility is needed


6/23

.

Briefly on Clouds


7/23

.

Cloud Platforms

• let's forget about *aaS terminology and focus on practice

• TIER 1: Data Centers and Physical Machines (PMs) they house

• TIER 2: Virtualization Platform which turns PMs into VMs◦ VM management software is required◦ large systems can work acrossmultiple data centers◦ potentially across providers in federated clouds 06

S

• TIER 3: Apps running on top of TIER 2◦ some apps are platforms like heroku 04 -- see next page◦ heroku is used as the main example throughout the slides 06

06 K.He+5 "Next stop, the cloud: understanding modern web service deployment..." IMC (2013)

04 C.Kemp+1 "Professional Heroku Programming" Wiley (2013)


8/23

.

Clouds: Multitenant Platforms

• one VM, multiple APPs• heroku is arguably one of the biggest examples 06

• the platform itself is TIER3, but creates anther tier for application running on topof the platform◦ warning: not a separate/new tier!◦ heroku simply packages and runs user apps, there is no added virtualization per

se

• multitenancy is a great idea -- one VM, many apps◦ the proposal is based on the same very idea

06 K.He+5 "Next stop, the cloud: understanding modern web service deployment..." IMC (2013)


9/23

.

Main Problems in Clouds

1. vertical integration is preferred by businesses

◦ heroku is entirely based on Amazon's cloud◦ when Amazon cloud breaks, heroku breaks◦ major prolonged failure in June 2013

2. e2e concept is effectively lost in the virtualization mesh/mess

◦ end users are not taken into consideration◦ services do not care and e2e networks between themselves and user communities

3. cloud today is an extremely centralized system -- very lowreliability◦ pushing cloud to edges might help -- cloud offload?


10/23

.

How HomeBox Can Help

• e2e performance probing 01

◦ many existing projects of similar nature 09 10◦ HomeBox can scale -- its main advantage

• social computing◦ applications from several users can visit with each other◦ visit means share the same location

• HomeBox Virtual (next) is one way to implement Internet of Things (IoT)

• offload CPU, storage, etc. to client boxes on edges -- ideally homes

01 1+myself "Active Network Measurement: Theory, Methods and Tools" ITU Association of Japan (2009)

09 "MLab: Measurement Lab" http://www.measurementlab.net/ (2009)

10 "TTM: Test Traffic Measurement Service" http://www.ripe.net.ttm (1999)


11/23

.

CVP: Cloud Visitation Platform


12/23

.

CVP: The Concept• simply, CVP needs to implement all the tiers in one device

Location 1 Location 2 …

Cloud Management Platform(s )

Cloud APPs … Tier 1 Tier 2 Tier 3

Cloud Visitation

Platforms


13/23

.

CVP: Am I the First?• apparently, Cisco also had a similar... though very foggy... idea


14/23

.

CVP: 3 Tiers, 1 Box

• TEAR1: the device needs to implement a virtualization platform◦ convert one PM into several VMs (one CPU core per VM)◦ CVP is unique by having interfaces here◦ CVP starts and ends here!

• TEAR2: VMs need to be made multitenant◦ a heroku-like container approach◦ containers are unique by having special default APIs supported by CVPs

beneath

• TEAR3: APPs can be anything supported by the container


15/23

.

CVP as HomeBox Virtual

• step 1: implement the deviceas a small cloud

• step 2: make it possible torun cloud apps on yourdevice

• that's all!

Storage Sensors Misc. Devices

…

Cloud Visitation Platform

Container

Cloud Visitation Platform APIs

App App App …

API

Container App

App App …

API

Multitenancy

Physical Device

… Interfaces …


16/23

.

CVP: Interfaces

• warning: a newpart!

• CVP apps would like to uselocal resources

• CVP implements them as

Interfaces• quotas, control, parallel access,scheduling

• special-purpose devices arepossible -- sensors, wifirouters, etc.


…


Container


App App App …

API

Container App

App App …

API

Multitenancy

Physical Device

… Interfaces …


17/23

.

CVP: Container APIs


…


Container


App App App …

API

Container App

App App …

API

Multitenancy

Physical Device

… Interfaces …

• warning: a newpart!

• heroku has API-less containers

• APIs are for hardwarefunctions

• APPs can use APIs to accesslocal hardware

• CVP provides specialcontainers and supportsAPIs


18/23

.

Example Use: E2E Probing


19/23

.

Example: E2E Probing on CVP• back to the e2eprobing scenario in thefirst box

• pull-baseddesign -- apps are pulledfrom device provider◦ note: pull-based installation

ismore feasible --higher security

• apps know which destinationsto probe to◦ schedule, start time, end time,

kinds of probes, end of life,etc.

Global Network


App App App …

Device Provider

Global Services

Requests, probes, etc.

Pull-Based Installation


20/23

.

Example: Implementation

• probing tools08 implemented as apps, then containers in CVP

• simple public containers are used 12

• current CVP is simply Zen's XCP cloud platform◦ presented CVP design is in development◦ will be announced soon

08 "e2eprobe: collection of probing tools" https://github.com/maratishe/e2eprobe (2013)

12 "Example heroku-like framework" https://github.com/progrium/dokku/ (2012)


21/23

.

Wrapup

• home devices are implemented as CVP: Cloud Visitation Platforms

• hardware functionality is abstracted via interfaces and APIs

• simple example: CVP makes e2e probing possible in a totally newway◦ low maintenance◦ high scalability◦ total openness

• major note: reliability of devices is completely different --virtualization = isolation

• into the future: anything can be CVP◦ switching equipment, wifi routers, sensors, robots, digital libraries, ....


22/23

.

That’s all, thank you ...


23/23

.

[01] 1+myself (2009)Active Network Measurement: Theory, Methods and ToolsITU Association of Japan

[02] myself+0 (2013)A Home Gateway Box with Meter, Probe and L2 QoS Policy EdgeCOMPSACW

[03] myself+1 (2012)Analytical Models for L2 versus L3 QoS ProvisioningIEICE PN研

[04] C.Kemp+1 (2013)Professional Heroku ProgrammingWiley

[05] C.Dovrolis+4 (2010)Measurement Lab: Overview and an Invitation...ACM Comp. Comm. Review


23/23

.

[06] K.He+5 (2013)Next stop, the cloud: understanding modern web service deployment...IMC

[07] IETF (2008)Management of Performance Measurement for NGNITU-T Y.2173

[08] (2013)e2eprobe: collection of probing toolshttps://github.com/maratishe/e2eprobe

[09] (2009)MLab: Measurement Labhttp://www.measurementlab.net/

[10] (1999)TTM: Test Traffic Measurement Servicehttp://www.ripe.net.ttm


23/23

.

[11] (2007)ntophttp://www.ntop.org

[12] (2012)Example heroku-like frameworkhttps://github.com/progrium/dokku/


23/23

E2E Services using Cloud Visitation Platforms

Technology

Transcript of E2E Services using Cloud Visitation Platforms