Using the DETER Testbed

Transcription

1 Using the DETER Testbed Ted Faber 24 Jan 2011

2 Outline What is DETER? Accessing DETER infrastructure Accounts & Projects Experimenting on DETER (Hands-On) Controlling Experiments With GUI Tools Using Low Level Experiment Interfaces Graduating to Advanced Features Federation and Risky Experiments

3 DETER Testbed Facility for repeatable, controlled experiments Clean room Controlled outside interaction/observation Resources allocated on demand Encourages early experimentation Scheduled experiments can be supported Education resource Built on top of Emulab Software

4 DETER Testbed Workflow DETER Testbed Network Description Network

5 Experiment Environment Clean Room Secure Environment users.isi.deterlab.net Tools File systems Clean room access Home base

6 Terminology User You all: researchers using DETER Project Group of related researchers One user can be in multiple projects (Analog to Unix group) Experiment Set of resources Controlled by a user, shared by project (Analog to Unix process)

7 Interacting with DETER Account management Experiment management Documentation Tools portal

8 Interacting With DETER: GUI SEER experiment control system Real-time measurement Event driven experiment manipulation Extensible interfaces

9 Interacting with DETER: Low Level users.isi.deterlab.net System accounts Shared experiment info Tools Unix environment (FreeBSD) SSH access to experiment network Putty Windows

10 Hands-On Manipulating DETER by example Demonstrations Follow along (multiple users are fine): Accounts detertab detertbn (password is acct name) Cleared after tutorial Slides with screenshots DETER Documentation

11 Web Site Hands-On (Logging in)

12 My DeterLab Available Resources Context Menus Testbed News Your experiments Info Tabs

13 Creating an Experiment Experiment description Derived from ns2 Inherited from Emulab Creating Experiment Description Graphical Editor Hand coding Coming soon: more graphical tools

14 Creating An Experiment

15 Graphical Experiment Editor Drag and Drop Elements Configure Elements Layout Area

16 Doing the Creation

17 Experiment States Swapped Internal representation exists No resources allocated Active Resources allocated, configured, in use Changing State Swapping in/swapping out

18 Swapping In

19 Experiment Settings Auto swap Remove experiment after idle time Duration Remove experiment after time Batch Experiment swaps opportunistically We prefer you leave idle swap on Debugging Any good reason you have...

20 Automating Experiments Loading software tb-set-node os $node OSID tb-set-node-tarfiles $node /dir /tarfile Starting commands automatically tb-set-node-startcmd $node command Batch Commands above have GUI access

21 Experiment Page Operations Topology Visualization Resource Mapping General Data

22 Visualization Tab

23 Ns File Tab

24 Using SEER to Experiment Graphical Interface to DETER experiment Experiment description must request SEER Off by default to be conservative Realtime Data Gathering Actuate Experiment Events Extensible for Specific Domains

25 Starting SEER Webstart link Starts SEER locally

26 Attaching to an Experiment popups

27 SEER Attached

28 SEER: pinging nodes Configure 4

29 SEER: Observing the Change (Qualitative) Network usage from to

30 SEER: Qualitative Observations Right Click

31 Low Level Experiment Access Experiment Layout Details Experiment Access Mechanisms Node Access Node Control Network information

32 Experiment Structure USERS Control Network User Access System Access Experimental Network Things to study Control Network Experiment Network

33 Users: Access to Experiments Experiment nodes are firewalled All access through users.isi.deterlab.net Secure Shell access and forwarding File systems are imported to experiments Nodes have local disk to avoid overhead

34 Finding a Node from Users Experiment page Local DNS names node.experiment.project node0.faber expr.deter Resource Mapping

35 Finding a Node Inside the Experiment Node reaches experimental node Entries in /etc/hosts Entries for multihoming Node.experiment.project reaches control interface(!) This can interfere with other operations Not the experiment you intended

36 Names in the Structure USERS Control Network node0.experiment.project node0 node1.experiment.project node1 Experiment Network node2.experiment.project node2

37 Experiment Services users.isi.deterlab.net:a staging area Log into users then to nodes On the nodes Access for the associated project users Different for classes Shared files for project User home directories /proj/project directories

38 The Project Filesystems Under /proj/project Custom disk images Software (rpms, tar files) Per-experiment data Under /proj/project/exp/experiment Log files (loghole) Shared experiment data

39 Forwarding Services Example: remote desktop access Ssh process on users to forward connection ssh -N -L 24242:localhost:3389 pc110 Process on users contacts the node rdesktop localhost:24242 (This one need not be forwarded)

40 Node Control Console access console pcxxx Attaches to serial line: access w/o network Reboot or reload a node node_reboot pcxxx os_load pcxxx All experiment commands...

41 On The Nodes Complete control sudo/admin privs Servers are protected Wedged nodes can be restored node_reboot/os_load will power cycle Control network/server access Can impact other's performance How do I? Can be tricky to answer

42 Getting Outside Talking to the Internet Risky Experiment Services Controlled permeability of the DETER isolation Requires Administrative coordination Talking to other testbeds DETER federation system Incorporate other testbed nodes From ProtoGENI, Emulab,

43 Getting Help

44 When Things Go Wrong... We want to hear about problems How do I? Something's broken... Support: Business Hours (+ by appt) Reporting Trouble: IRC: we poll roughly hourly Open a trac ticket: or use link

45 Real Accounts DETER Project: DEFT-COLLAB Request Account & Join Existing Account

46 Join Project Join Project Name DEFT-COLLAB

47 Things To Try Download and install software tb-set-tarfiles Network Topologies LAN vs link Delay and loss Emulab Tutorial From Documentation menu/proxy for Emulab

48 Unsolicited Advice Probably better to start small and grow Better fits the lightweight experiment model Easy to catch problems small Ask when you get stuck But check the FAQs, too.

49 More Information These slides