opt-in working group system engineering report october 29, 2008 harry mussman

18
GEC3 – October 28-30, 2008 www.geni.net 1 Opt-in Working Group System Engineering Report October 29, 2008 Harry Mussman Opt-in WG System Engineer [email protected] groups.geni.net GENI working group wiki

Upload: fay-cantrell

Post on 30-Dec-2015

22 views

Category:

Documents


1 download

DESCRIPTION

Opt-in Working Group System Engineering Report October 29, 2008 Harry Mussman Opt-in WG System Engineer [email protected]. groups.geni.net GENI working group wiki. What is GENI end-user opt-in?. - PowerPoint PPT Presentation

TRANSCRIPT

GEC3 – October 28-30, 2008 www.geni.net 1

Opt-in Working GroupSystem Engineering Report

October 29, 2008

Harry MussmanOpt-in WG System Engineer

[email protected]

groups.geni.netGENI working group wiki

What is GENI end-user opt-in?

October 29, 2008 www.geni.net 2

GENIEnd User

GENI Srvc S3

Visualization Service

GENI Srvc S2GENI Srvc S1

DOE Agg Z(federated aggregate)

Aggr Z

GENI Operations & Management

GENI Aggr A

■ Operator■ Admin

Help Desk & Tools

■ Admin & Account Tools

Host A1

Host Ax

GENI Comp B

Comp B

Measure & Store

Software Storage

● ■Aggr Mgr with Ops Portal

Admin Oper

GENI Clearinghouse

ComponentRegistry

Principal Registry

●■Ticket: Store Query

●■Principal: Register Authen Query

Slice Registry

TicketLog

SoftwareReposit

●■Slice: Register Cred Issue or Tkt Broker Query

●■Soft Mod: Store Get Query

●■Component: Register Query

Research Org A

● Researcher

● ExperimentSupport Tools

Research Org B

● Slice Admin

● PI

LocalPrincipal Registry

EndUser

via Internetor GENI

■ Ops & Mgmt Tools

● ExperimentSupport Tools● Experiment

Control Tools

Experiment Plane

Measurement Plane

● Control Plane

■ Ops and Mgmt Plane

● ■Comp Mgr with Ops Portal

Admin Oper

● ■Aggr Mgr with Ops Portal

Admin Oper

It is defined by scenarios where end users (not researchers) become involved with GENI experiments, and by the services and capabilities necessary to support them.

It is defined by scenarios where end users (not researchers) become involved with GENI experiments, and by the services and capabilities necessary to support them.

Agenda

• Goals• Introduction to WG SE and roles• Overview of Opt-in scenarios and capabilities• Relevant Spiral 1 projects• Current Opt-in issues and tasks• Planned Opt-in documents

October 29, 2008 www.geni.net 3

Goals (for this meeting)

• Understand WG SE roles• Get overview of opt-in WG activities• Discuss work plan for coming year, and make

suggestions• Recommend collaborators and authors

October 29, 2008 www.geni.net 4

Who am I?

• Harry Mussman– Current: Senior Systems Engineer in the GPO at BBN– Last: Voice-over-IP architect at BridgePort Networks

(a startup) and GTE Internetworking/Genuity– BSEE Univ Michigan, MSEE Northwestern Univ, PhD

Stanford Univ– [email protected]

• GENI roles:– Opt-in WG SE– Control Framework WG SE– GPO coordinator for six Spiral 1 projects

October 29, 2008 www.geni.net 5

Role of Opt-in WG SE

• Frame technical issues from top-down – Collect issues from WG, compile and revise– Use to identify and structure WG documents

• Synthesize input from bottom-up– Collect input from WG, and distribute– Look for and summarize consensus (or lack of it)

• Draft WG documents…– Manage process to completion

• Assist WG communications– Take and distribute notes– Maintain wiki

October 29, 2008 www.geni.net 6

How WG Creates Document

• SE drafts document• GPO does internal review• SE posts first draft

– On wiki (to start); repository up RSN

• WG discusses document on WG list– Possible one-on-one follow-ups

• SE assembles changes, and revises• SE posts revision• (Repeat, until document completed)

October 29, 2008 www.geni.net 7

Overview of GENI Opt-in Scenarios and Capabilities

• “GENI end-user opt-in is defined by scenarios where end users (not researchers) become involved with GENI experiments, and by the capabilities necessary to support them.”

• Each opt-in scenario involves:– One or more use cases.– A set of players, with differing motivations.– Unique issues.

• Each opt-in scenario requires:– A set of policies and best practices.– One or more underlying GENI capabilities to make it

work.October 29, 2008 www.geni.net 8

Opt-in Scenarios

• Have currently identified four distinct scenarios (which can overlap).

• Scenario 1: An experiment on GENI that provides a service to users and/or others

• Scenario 2: An experiment on GENI that can affect and disrupt users and/or others

• Scenario 3: When users (or others) contribute (or associate) resources to (with) experiments on GENI

• Scenario 4: When experiment data involving users is gathered on GENI, and made available to researchers, and possibly others

• Other scenarios?

October 29, 2008 www.geni.net 9

Opt-in Capabilities

• Have currently identified three basic capabilities that will be required.

• Capability 1: Gateway from GENI to another network, e.g., the Internet

• Capability 2: Contribution (or association) of a user’s node to an experiment on GENI

• Capability 3: Gathering logs and experiment data on GENI, and managing their distribution

• Other capabilities?

October 29, 2008 www.geni.net 10

www.geni.net

GENI Spiral 1 Integration: Five Control Framework Clusters

1578 Overlay Hosting Nodes1578 Overlay

Hosting Nodes

1579 ProtoGENI

1579 ProtoGENI

1595 Great Plains Environment for Ntwk Innovation

1595 Great Plains Environment for Ntwk Innovation

1646 CMU Testbeds

1646 CMU Testbeds

1609 DETERTrial Integ

1609 DETERTrial Integ

1642 Instrumentation

Tools

1642 Instrumentation

Tools

1613 Enterprise

GENI

1613 Enterprise

GENI

1600 PlanetLab

1600 PlanetLab

1658 Mid-Atlantic Crossroads

1658 Mid-Atlantic Crossroads

1602 Sensor/Actuat

or Network

1602 Sensor/Actuat

or Network

1582 ORCA/BEN

1582 ORCA/BEN

1599 Vehicular Mobile

Network

1599 Vehicular Mobile

Network

1660 ORBIT Framework

1660 ORBIT Framework

1601 Virtual Tunnels

1601 Virtual Tunnels

1657WIMAX

1657WIMAX

1633 Kansei Sensor Network

1633 Kansei Sensor Network

1628 Measurement

System

1628 Measurement

System

1621 GUSH Tools

1621 GUSH Tools

1622 Provisioning

Service

1622 Provisioning

Service

Cluster A Cluster ECluster D Cluster CCluster B

Key:

Projects with active Spiral 1clearinghouse interfaces

Column labels showcommon control framework

Highlighted Spiral 1 projects are relevant to Opt-in WG

Highlighted Spiral 1 projects are relevant to Opt-in WG

11

1663 Digital Object

Registry

1663 Digital Object

Registry

1604 GENI Meta

Operations

1604 GENI Meta

Operations

1643 Programmable

Edge Node

1643 Programmable

Edge Node

1650 Regional

Opt-In

1650 Regional

Opt-In

1632 Security Architecture

1632 Security Architecture

1645 Million- Node GENI1645 Million- Node GENI

1610 GENI at 4-

Year Colleges

1610 GENI at 4-

Year Colleges

STUDY ALL PICK ONE

1619 Optical Access

Networks

1619 Optical Access

Networks

1653 Data Plane

Measurements

1653 Data Plane

Measurements

1631 Embedded Real-time

Measurements

1631 Embedded Real-time

Measurements

Spiral 1 Projects

• Current Spiral 1 projects are focused primarily on providing a capability.

• Capability 1: Gateway from GENI to another network, e.g., the Internet– 1601 Virtual Tunnels– 1650 Regional Opt-In

• Capability 2: Contribution (or association) of a user’s node to an experiment on GENI– 1645 Million Node GENI

October 29, 2008 www.geni.net 12

continued (2)

• Work towards defining and understanding scenarios is underway.

• Scenario 1: An experiment on GENI that provides a service to users– See Opt-in Workshop report by Craig Partridge.

• Scenario 2: An experiment on GENI that can affect and disrupt users and/or others– Consider experience from PlanetLab, by Larry Peterson.

• Scenario 3: When users contribute (or associate) resources to (with) experiments on GENI– Studied as part of Spiral 1 project, 1645 Million Node GENI.

October 29, 2008 www.geni.net 13

Current Opt-in Issues and Tasks

• Scenario list:– Review, and affirm or change.

• For each scenario:– Formulate in more detail, and sub-divide as needed.– Understand the players, their relationships and their

motivations.– Formulate proposed policies and best practices.– Clearly identify and define key issues.– Determine required capabilities.– Reference current implementations, research and

projects. • Who in WG wants to contribute?

October 29, 2008 www.geni.net 14

continued (2)

• Capability list:– Review, and affirm or change.

• For each capability:– Formulate in more detail, and sub-divide as needed.– Formulate requirements.– Suggest design approaches.– Reference current implementations, research and

projects.• Who in WG wants to contribute?

October 29, 2008 www.geni.net 15

Planned Opt-in Documents

• Architecture:– Opt-in Architecture, v1 DRAFT due 3/1/09

• Scenarios?• Capabilities?• References?• Who in WG wants to be an author? Editor? • Who in WG wants to be an editor?• Who in WG wants to be a reviewer?

October 29, 2008 www.geni.net 16

Opt-in Action Items

• 1)

• 2)

• 3)

• 4)

• 5)

October 29, 2008 www.geni.net 17

Follow-up

• Notes, slides, actions, etc will be sent to the working group mail list and posted on the wiki page: http://groups.geni.net/geni/wiki/GeniOptIn

October 29, 2008 www.geni.net 18