Experimenter Workflow and Services WG

Global Environment for Networked Innovation

GENI Engineering Conference (GEC)

www.geni.net 1

www.geni.netClearing house for all GENI news and documents

Workflow & Services WG

• Chair: Jeff Chase• Scope:

– What do experimenter-users need from GENI? Consider planning, scheduling, running, debugging, analyzing experiments; long running experiments & how they grow; archiving data.

• Activities:– Develop sample workflows, use cases– Define experimenter-support services– Develop measurement strategies

www.geni.net 2

A moment of homage

• Jay Lepreau 1952-2008• Co-chair of this group• “A brilliant computer scientist, avid

outdoorsman, champion procrastinator and fantastic bicycle racer…up all night reinventing the internet…”

• “He got caught on his long uphill race against multiple myeloma….”

• “More than twenty years ago he saw the redrock country of Southern Utah and loved it enough to move here to work with the Southern Utah Wilderness Alliance to protect it.”

www.geni.net 3

Agenda

• Introduction of/from new WG Engineer– Vic Thomas– Overview of Use Scenarios

• Spiral 1 talks– Jeannie Albrecht: GUSH (slice control)– Edge environments: lightning talks

• Hongwei Zhang (Kansei), Max Ott (Orbit)

– John Hartman: provisioning sliver packages– Jim Griffioen: instrumentation tools– Deniz Gurkan: optical layer measurements

• Discussion and WG focus/future– Use cases document

www.geni.net 4

Experimenter Workflow & Services WG

www.geni.net 5

Measurement Plane O&M

AggregateControl

Measure-ments

Components

Aggregate A

O&MMeasure-

ments

Components

Aggregate B

Researcherwith Tools

Clearinghouse

List ofOrganizations

List ofAggregates

O&M Policy

Control Plane

Data Plane

Federation

Trust

Interface

Internet

Opt-inUser (??)

AggregateControl

ResearchOrganization

Experimenter Workflow & Services WG

www.geni.net 6

Measurement Plane O&M

AggregateControl

Measure-ments

Components

Aggregate A

O&MMeasure-

ments

Components

Aggregate B

Researcherwith Tools

Clearinghouse

List ofOrganizations

List ofAggregates

O&M Policy

Control Plane

Data Plane

Federation

Trust

Interface

Internet

Opt-inUser (??)

AggregateControl

ResearchOrganization

The Researcher-Facing WG

• Specify/design the “core services”:– Important enough and hard enough to argue about– Must be part of facilities planning– Directly motivated by usage scenarios– Deliver maximum bang for ease-of-use– User-centric, network-centric

• Enable flowering of extensions/plugins– Find/integrate technology pieces of value

• What requirements do these services place on other WGs?

Focus areas for today

• Slice control– Programmatic control/orchestration for GENI

experiments and their slices.

• “Building blocks”– Sliver programming, off-the-shelf code elements,

provisioning slices with code objects.– Composing/validating slice configurations

• Information plane– Monitoring slices and enabling, gathering, processing,

querying, filtering, archiving, processing measurement/instrumentation data.

www.geni.net 8

www.geni.net 9

RFC: GENI Usage Narratives

• We need a taxonomy of helper systems and tools, so we can “divide and conquer”.

• Key deliverable: usage narratives to “traverse” the taxonomy.– Also known as experiment lifecycle.– Driven by the project tuples of Spiral-1

• Its purpose is narrative communication rather than coverage or to “debug the design”.– What areas do we need to flesh out?

www.geni.net 10

Overview of GENI uses

Sliverable GENI Substrate(Contributing domains/Aggregates)

Wind tunnel

Experiments(Guests occupying slices)

Embedding

Petri dish

Observatory

+ “test tubes”

Candidate use cases: routing etc.

• Virtual router appliance with canned traffic loads– What’s a “sliver” on a programmable router?– Kevin Fall, Intel Research Berkeley

• Layer-3 route adaptation based on substrate-level measures– Keren Bergman, Columbia

• Congestion pricing and packet auctions for router fast lane vs. slow lane– Xiaowei Yang, Duke

• Your example here

www.geni.net 12

Fertile ground

• From an earlier GENI review panel: areas of opportunity…

• “rethinking networking from the point of view of extreme manageability”

• “rethinking how networking can assist in reducing the collateral damage caused by end host security problems”

www.geni.net 13

Usage Scenarios (P. Steenkiste)

• A group of researchers has developed architectural mechanisms to support mobile users accessing the Internet. They include a new addressing scheme, mechanisms for route adaptation based on user location, and fast proxy deployment to help the user access Internet services.

• The researchers want to test their prototypes using realistic mobile users, i.e. the dynamics of the wireless connections (e.g. variable bandwidth and delay, temporary disconnects, etc.) must be realistic, using either emulation or modeling.

• They also want realistic workloads at the level of both individual users and groups of “nearby” users.

• Straw man scenario 2: testing architectures to defend against DOS attacks.

• Straw man scenario 3: combine 1 and 2.

www.geni.net 14

Discussion Questions

• What experiment control functionality do researchers want/need on GENI?– Support for both novice and advanced users

• How much control should be exposed?• How do I specify an experiment?• What is the API between experiment controllers

and the underlying control frameworks? • What is the API between the experiment

controller and GENI Clearinghouses?

Jeannie Albrecht

Specifying an experiment

• GUSH focuses on edge compute nodes– XML with component blocks describing required

components and the “processes” to “run” on them.– Monitoring/adaptation is hard: notifications generated

by built-in process monitoring on nodes, and scripted response behaviors.

• Use a DSL based on Ruby (Orbit)• Programmatic controller using APIs to

request/reserve, with upcalls to launch, and ordering primitives (Orca/Shirako)

www.geni.net 16

Slice controller: feature creep

• Support for incremental resource allocation and notify slice when allocation changes.– Orca/Shirako guest controller, and Gush on Shirako

• Support for detecting abnormal program behavior, application-level callbacks, debugging, etc.– E.g., Monitoring agents at the components generate controller

notifications of unexpected conditions and trigger scripted response actions (Gush).

• Feed back substrate-level performance measures to drive adaptation of the slice controller or guest software– Specify invariant conditions for slices, change the set of slivers to

maintain invariants (e.g., wireless sensor: Orbit, Kansei)

Code objects and provisioning

• Experiment specification names code objects by URIs, fetched externally. (Orbit)

• Common file/storage system?– A CDN for code artifacts and/or instrumentation

artifacts?– CNRI object registry, DSpace?

• How to specify sliver prerequisites to run the code?

• How to check validity of compositions?

www.geni.net 18

Instrumentation (Edulab)

• Separate instrumentation gathering from the data plane: use the control network.

• Display measures back to user GUI.• Traffic graphs: click to browse packet traces,

e.g., with wireshark.• Snapshot all GUI display, e.g., to consult and

expert for debugging.

www.geni.net 19

Instrumentation, continued

• Must have remote access to measurement configuration (Deniz Gurkan)

• Buffer measurement data locally, provide an interface to access it during/after the experiment.

www.geni.net 20