Experiment Workflow using Sface and Raven

13
Experiment Workflow using Sface and Raven Andy Bavier, PlanetWorks Scott Baker, SB-Software July 27, 2011

description

Experiment Workflow using Sface and Raven. Andy Bavier, PlanetWorks Scott Baker, SB-Software July 27, 2011. What is Sface ?. A new tool available to GENI researchers for managing experiments Standalone desktop application, r uns on Linux and Mac OS X - PowerPoint PPT Presentation

Transcript of Experiment Workflow using Sface and Raven

Page 1: Experiment Workflow using  Sface and  Raven

Experiment Workflow using Sface and Raven

Andy Bavier, PlanetWorksScott Baker, SB-Software

July 27, 2011

Page 2: Experiment Workflow using  Sface and  Raven

A new tool available to GENI researchers for managing experiments◦ Standalone desktop application, runs on Linux

and Mac OS X Works with any aggregate that supports the

GENI AM API and uses GENI RSpecs “Plugin” architecture makes it easy to add

new management and monitoring services◦ Example: Raven package management service

What is Sface?

Page 3: Experiment Workflow using  Sface and  Raven

Use Sface to:◦ Discover available resources◦ Add and remove resources from a slice

Use Raven to:◦ Package an experiment◦ Deploy it into a slice◦ Monitor the experiment

Goals of this Tutorial

Page 4: Experiment Workflow using  Sface and  Raven

Slice◦ A network of communication and computing

resources capable of running an experiment or a wide-area network service

Component◦ On PlanetLab, an edge computer (a “node”)

Sliver◦ A virtual machine running on a component

Aggregate◦ A group of components (e.g., a testbed)

http://groups.geni.net/geni/wiki/GeniGlossary

Terminology

Page 5: Experiment Workflow using  Sface and  Raven

Guest1-30 accounts on PlanetLab◦ Password: geni

Login to the account assigned to you Run “sface”

Getting Started

Page 6: Experiment Workflow using  Sface and  Raven

Installing Sface (we’ve done this for you)◦ Download packages, dependencies◦ Put private key in ~/.sfi/

On Configuration screen◦ User HRN: plc.gec11.guestXX◦ Slice HRN: plc.gec11.sliceXX◦ User’s authority HRN: plc.gec11◦ Click “Apply & Save”

Configuration

Page 7: Experiment Workflow using  Sface and  Raven

Go to Main Window◦ Click “Update Slice Data”◦ Wait ~1 minute

See a list of aggregates with summaries Expand to list all of the aggregate’s nodes

◦ Some nodes may not be working… At this point, the slice should not have

slivers running on any nodes

Discover Resources

Page 8: Experiment Workflow using  Sface and  Raven

Generate and submit request for resources Double-click on a node to add it to the slice

◦ Requests a sliver on that node Type a string in the search box to only show

nodes containing that string◦ E.g., “princeton”

Pick a few nodes from PLC, PLE, and/or VINI and click “Submit”

Add Slice Resources

Page 9: Experiment Workflow using  Sface and  Raven

Double-click on a blue node to remove it from the slice

Now, remove all nodes from your slice Click “Submit” Should see empty summaries

Remove Slice Resources

Page 10: Experiment Workflow using  Sface and  Raven

Add PlanetLab-specific tags to slivers◦ Right-click on “Default tags for XYZ” to add

attribute to all slivers on aggregate XYZ◦ Right-click on a node to add attribute to the

corresponding sliver◦ Choose attribute from pull-down, type value

Add “initscript” attribute with value “stork” to all PLC nodes◦ Downloads and runs the “stork” script when the

VM starts

Slice Tags

Page 11: Experiment Workflow using  Sface and  Raven

Default tag on PLC: initscript/stork Add ~20 PLC nodes to your slice Click “Submit” Verify that nodes, tag were added to slice

Now… wait 15 minutes for slivers to be created

Set up for Raven Tutorial

Page 12: Experiment Workflow using  Sface and  Raven

Wiki page (with download links):◦ http://svn.planet-lab.org/wiki/SfaceGuide

Google Group:◦ http://groups.google.com/group/sface-users/

Sface Info

Page 13: Experiment Workflow using  Sface and  Raven

Goal: each slice has 20-30 working nodes for the Gush tutorial next…

At end of tutorial