emulab and protogeni
Post on 20-Oct-2014
1.312 views
DESCRIPTION
TRANSCRIPT
FIBRE-BR Camp, 28-29 April 2012
Ouro Preto (MG), Brazil
USP Team
2
USP Team members
• General coordinator
– Tereza C. M. B. Carvalho – [email protected]
• Team members
– Marco A. Torrez Rojas – [email protected]
– Marcos F. Schwarz – [email protected]
– Fernando F. Redígolo – [email protected]
– Cristina K. Dominicini – [email protected]
– Charles C. Miers – [email protected]
– Paulo H. Fertonani – [email protected]
– Raphael Penteado – [email protected]
3
Agenda
• Part I - Emulab
• Emulab LARC/USP
• How does Emulab Works ?
• Part II – ProtoGENI
• What is ProtoGENI
• ProtoGENI Control Monitoring Framework
• ProtoGENI Backbone
• ProtoGENI Federation
• Considerations
• Part III – Demo
4
Agenda
• Part I - Emulab
• Emulab LARC/USP
• How does Emulab Works ?
• Part II – ProtoGENI
• What is ProtoGENI
• ProtoGENI Control Monitoring Framework
• ProtoGENI Backbone
• ProtoGENI Federation
• Considerations
• Part III – Demo
5
Emulab
• Experimental Facility
– Developed for perform experimental network and distributed systems
research that provides: network emulators, simulators and live
networks.
• Design Principals
– Transparency
– Virtualization
– Automation
– Efficiency
• Provided Resources
– Local nodes (PCs)
• Edge nodes, wireless nodes, software-defined radio (GNU Radio)
– Virtual Network Links
• Arbitrary topologies, local-area links and wide-area links
6
Emulab
• Main Emulab Testbed
– University of Utah
• Around 500 PC nodes;
• Design to support research and education (students and
professors)
7
Emulab LARC/USP
• Emulab LARC:
– Sponsors: Fapesp / Kyatera & Ericsson
– 24 nodes for experiments
• 17 Intel Pentium 4 (3GHz), 3GB RAM (DDR2), 80GB HD
• 7 Xeon Quad-Core 2.4Ghz, 4GB RAM, 500 GB HD
• All with 3 x Gb Ethernet interfaces for experiments
– 3 servers
• Storage of user data / OS images / Clearinghouse
– 5 Gigabit switches (Cisco and Juniper)
8
Emulab LARC/USP
Author(s):
Marcio / Fernando
Revisor(s):
26/10/11 V.2.0 1 de 3
Network Connections
x 3
x 3
(48+24+24 Stack) 96 port
Gigabit Ethernet
192.168.189.4/24
pc1.emulab.larc.usp.br
200.144.187.130/26
pc22.emulab.larc.usp.br
200.144.187.151/26
Datacenter’s
Network
Internet
200.144.187.61/30
boss.emulab.larc.usp.br
200.144.186.226/29
192.168.189.5/24console.emulab.larc.usp.br
192.168.189.6/24
es00
es01
ops.emulab.larc.usp.br
200.144.186.242/29
Control Network Switch Stack with
48 x Gigabit Ethernet ports
cs00 – Cisco 3750G-24TS – L3
200.144.187.62/30
200.144.186.225/29
200.144.187.241/29
200.144.187.129/2
192.168.189.2/24
cs01 – Juniper EX3200 24 – L2
192.168.189.3/24
pc23.emulab.larc.usp.br
200.144.187.152/26
pc24.emulab.larc.usp.br
200.144.187.153/26 x 5
x 5
es02
Rede LARC
192.168.189.x/24
Caption :
Control hardware (vlan44) Control net (vlan45) Experimental net
Private net (vlan46)External net (vlan42) Public net (vlan43)
kvm.emulab.larc.usp.br
192.168.189.7/24
clrhouse.emulab.larc.usp.br
200.144.187.226/29
VM
9
How does it work ?
User define the desired topology in a ns-2 file (directly or
through a Java apple) and submit it to Emulab control system
1
1
10
How does it work ?
Swap-in: control system allocates the physical nodes for the
experiment • Virtual topology is mapped to the physical resources, according to
what is available in any given moment
• These nodes are loaded with the desired OS and some basic
config is done
• VLAN creation for the links
• Experiment customization
• Default images / Custom images
• Software instalation / Script execution
• Static routes definition / Dynamic routing enabling
2
2a
11
Experiment Creation Process
Node
A
Node
B
Latency
50 ms
Node
A
pc 7
Node
B
pc15
Traffic
Shapper
50ms
pc 12
Node
A
pc 7
Node
B
pc15
Traffic
Shapper
50ms
pc 12
Virtual Real Hardware
Eth
ern
et S
witc
he
sP
atc
h P
an
ne
l Pro
gra
má
ve
l (sn
mp
)
VL
AN
1V
LA
N 2
Emulab Web
Ns File
Experiment
12
How does it work ?
System sends an e-mail to the user notifying that the experiment
is ready for usage
2
2b
13
Resource Allocation Process
14
How does it work ?
Resources remotelly accesible
Tipically through ssh and/or serial console
3
3
SSH nodes
addresses
15
How does it work ?
Swap-out: resources are freeded for other experiments • Process of freeing allocated resources
• 2 main limits for an automatic swap-out
• Idle-Swap: number of hours that the resources haven´t been
used (e.g.: 2hs)
• Max-duration: number of hours that the resources have been
allocated (e.g.: 16hs)
• Usually defined at experiment creation time
• Manual swap-out: researcher frees resources
4
4
16
Agenda
• Part I - Emulab
• Emulab LARC/USP
• How does Emulab Works ?
• Part II – ProtoGENI
• What is ProtoGENI
• ProtoGENI Control Monitoring Framework
• ProtoGENI Backbone
• ProtoGENI Federation
• Considerations
• Part III – Demo
17
ProtoGENI was created to provide the integration of Emulab testbeds
in order to build a GENI facility.
The integration consists of three key components:
• CMF: Control and Monitoring Framework software from the University of Utah, based on an enhanced version of the Emulab testbed management software
• Backbone: A USA nationwide, high-speed dedicated backbone on Internet2’s wave infrastructure
• Federation: A set of federated testbeds, including a variety of wireless networks (CMULab), residential broadband (CMULab), and programmable edge clusters (Emulab) that are connected to the backbone
What is ProtoGENI
18
• Enhanced version of the Emulab Control Framework:
• SFA Architecture: Aggregate Manager (AM), Clearing
House (CH), Slice Authority (SA), RSpec;
• XMLRPC Interface: to AM, CM, SA;
• I&M Tools: INSTOOLS and LAMP (based on perfSONAR);
• Flack GUI: a Flash-based interface that allows allows
visualization and manipulation of federated resources.
ProtoGENI CMF
19
The Clearing House behaves as a central registry coordinating
the federation.
Each Aggregate Manager (Component Manager) is
responsible for the allocation, operation and control of one or
more resources.
Slice Authorities are responsible for coordination, accounting
and mediation of resources provided by many aggregate
managers.
The RSpec is a data interchange format describing resources
properties. It is used in four major contexts: advertisements,
requests, tickets, and manifests.
SFA Architecture
20
Flack is a Flash-based Google Map client that allows
visualization and manipulation of federated
resources.
Flack
21
• Composed of 8 nodes connected by
1Gbps waves on the Internet2
infrastructure;
• The backbone runs Ethernet on these
waves, and is sliced with VLANs;
• Each node contains a set of sliceable,
user-programmable components:
• PCs with NetFPGA cards
• Ethernet Switches (HP Procurve)
with OpenFlow-capability under
implementation.
ProtoGENI Backbone
Backbone node Example
22
Integration of Tesbeds
ProtoGENI Federation
23
GENI Federation
Other GENI Facilities
(eg. PlanetLab)
24
ProtoGENI CMF is installed over Emulab
infrastructure and is highly dependent on Emulab
source code.
ProtoGENI @ USP: Integrate Emulab resources
under FIBRE federation
Clearing House documentation and
code/dependecies are not properly updated.
Considerations
25
Agenda
• Part I - Emulab
• Emulab LARC/USP
• How does Emulab Works ?
• Part II – ProtoGENI
• What is ProtoGENI
• ProtoGENI Control Monitoring Framework
• ProtoGENI Backbone
• ProtoGENI Federation
• Considerations
• Part III – Demo
26
Pre-requisites
An account setup on one of the Emulab aggregates.
The account can be requested at www.emulab.net, clicking
on the "Request Account" button.
Note that account creation require approval and may take a
while.
Demo
27
First logging in to Flack on http://protogeni.net/flack.
Flack uses the credentials from your issuing authority.
Select your authority and download the credentials.
Log on to Flack
28
Create a Slice
29
Nodes can be added to the slice by dragging from the aggregate where
you want to create the node.
Experiment Definition
30
Nodes can be added to the slice by dragging from the aggregate where
you want to create the node.
Experiment Definition
Common node types:
• PC (exclusive physical machine);
• VM (virtual machine shared with others).
31
Links between nodes are created by dragging a line from
one node to another.
Experiment
Definitiion
32
Optionally load a RSpec description of the experiment.
Experiment Definition
33
When the topology is ready the slice can be created.
Nodes access is done by ssh (as in Emulab)
Slice Creation
34
Questions