wiki:Gec9ClusterDAgenda

Version 14 (modified by hmussman@bbn.com, 9 years ago) (diff)

--

Cluster-D Meetings at GEC9, Agenda and Notes

Tuesday, Nov 2, 12noon - 4:30pm
TENTATIVE

Introductions (12 noon)

Spiral 3 Goals (12:10pm, Mussman)

The following high-level goals have been established by the GPO for Spiral 3:

Experiments:

Use by outside researchers
Use involving multiple aggregates
Use for research experiments

Some expected experiments using Cluster D during Spiral 3:

Programmable Packet Networks over Dynamic Circuit Substrate (Jeff Chase, Xiaowei Yang)
Optical-layer experiments (BEN network, ERM sensors)
Mobile wireless experiments (DOME)
Sensor experiments, e.g., Nowcasting experiments, using weather data from ViSE radar, processed in local cluster and/or cloud (ViSE and DICLOUD)
Sensor network experiments (Kansei)

Interoperability:

Researchers can obtain and stitch resources from multiple aggregates
Researchers from other CFs (e.g., protoGENI) can obtain resources from Cluster D via GENI AM API
Researchers in Cluster D can obtain resources from other CFs (e.g., protoGENI)via GENI AM API

Proposed Spiral 3 Roadmap for Discussion (12:20pm, Mussman and Baldine)

Cluster D clearinghouse from Spiral 2:

Operational readiness
Connectivity by aggregates
Features

Cluster D connectivity from Spiral 2:

Control framework message flows
Component programming via SSH
VLAN connectivity to Internet 2 or NLR Many VLANs
Bridge between backbone networks
Ability to control setup of VLANs as part of experiment
Ability to control setup of VLANs as part of experiment involving multiple aggregates

Task list for Spiral 3:

Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping)
Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project)

Allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain, using their SM.
Plan to authenticate users in SM via InCommon/Shibboleth

With other CFs, a plan for consistent names and interfaces
With other CFs, a plan for resource descriptions at interoperability interfaces
Plan to interop with other CFs, particularly from and to protoGENI (Cluster C)

Allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0 (using RSpec resource description)

Allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API, same as GENI AM API v2.0? )

Plan to get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description)

Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites

Plan for operations portal into Cluster D site, including status and logs, with connections to GMOC

Demos for GEC10:

Demo experiment where Cluster D researchers obtain and stitch resources from multiple Cluster D sites (and backbone domains) using their SM.
Demo experiment where protoGENI researchers obtain resources via GENI AM API v1.0, using RSpec resource description.
Demo operations portal into Cluster D site, for status and logs, with connections to GMOC

Demos for GEC11:

Demo experiment where Cluster D researchers get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description)
Demo experiment where Cluster D researchers stitch L2 connectivity across Cluster C (protoGENI), and Cluster D sites
Demo experiment where Cluster D researchers include tools (e.g., GUSH) to help authorize, reserve and assign resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API?) (same as GENI AM API v2.0? )

Views:

Figure 1-1) and 1-2): CLuster D Config at end of Spiral 3

Figure 2): ORCA Site Config

Figure 3): Multiple ORCA Sites

Figure 4): ORCA Interop with protGENI

Figure 5): ORCA Experiment Flow

ORCA Features Spiral 2 report and Spiral 3 roadmap (12:20pm, Baldine)

  • Upcoming Bella 2.2 status
  • Bella 2.2 Features in detail
  • Bella 3.x upcoming Spiral 3 features
    • New substrate support
    • Experiment support
    • Authentication and authorization
  • ProtoGENI interoperability
    • Connectivity planning
    • Naming and format conversions
    • Handlers and policies
    • Tools integration
  • Clearinghouse and intra-cluster connectivity
    • Status
    • Actor registry
    • Future

Cluster D Project Plans for Spiral 3 (From 1:00pm through 2:40pm)

Each project should prepare NO MORE THAN THREE slides for presentation, and upload to the wiki below:

1) Functions and features planned for Spiral 3:

2) Connectivity planned for Spiral 3:

Component programming via SSH?
VLAN connectivity to Internet 2? NLR? How many VLANs?
Ability to control setup of VLANs as part of experiment?

3) Experiments planned for Spiral 3:

Use by outside researchers?
Use involving multiple aggregates?
Use for research experiments?

ORCA/BEN (1:00pm)

Ilia Baldine

DOME (1:10pm)

Brian Lynn

ViSE (1:20pm)

David Irwin

DICloud (1:30pm)

Michael Zink

KANSEI (1:40pm)

Anish Aurora

OKGems (1:50pm)

Andy Li

ERM: Embedded real-time substrate measurements for real-time cross-layer experiments (2:00pm)

Keren Bergman, Caroline Lai, Michael Wang

IMF (2:20pm)

Rudra Dutta

LEARN Measurement Handler and Network Integration (2:10pm)

Deniz Gurkan

iGENI (2:30pm)

Joe Mambretti, Jim Chen

Break (From 2:40pm through 3:00pm)

Plan for GEC10 and GEC11 demos/experiments (3:00pm - 3:15pm)

Experiments:

Use by outside researchers
Use involving multiple aggregates
Use for research experiments

Some expected experiments using Cluster D during Spiral 3:

Programmable Packet Networks over Dynamic Circuit Substrate (Jeff Chase, Xiaowei Yang)
Optical-layer experiments (BEN network, ERM sensors)
Mobile wireless experiments (DOME)
Sensor experiments, e.g., Nowcasting experiments, using weather data from ViSE radar, processed in local cluster and/or cloud (ViSE and DICLOUD)
Sensor network experiments (Kansei)

Spiral 3 Roadmap Discussion (3:15pm - 4:00pm)

Cluster D clearinghouse from Spiral 3:

Operational readiness
Connectivity by aggregates
Features

Cluster D connectivity from Spiral 2:

Control framework message flows
Component programming via SSH
VLAN connectivity to Internet 2 or NLR Many VLANs
Bridge between backbone networks
Ability to control setup of VLANs as part of experiment
Ability to control setup of VLANs as part of experiment involving multiple aggregates

Task list for Spiral 3:

Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping)
Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project)

Allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain, using their SM.
Plan to authenticate users in SM via InCommon/Shibboleth

With other CFs, a plan for consistent names and interfaces
With other CFs, a plan for resource descriptions at interoperability interfaces
Plan to interop with other CFs, particularly from and to protoGENI (Cluster C)

Allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0 (using RSpec resource description)

Allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API, same as GENI AM API v2.0? )

Plan to get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description)

Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites

Plan for operations portal into Cluster D site, including status and logs, with connections to GMOC

Demos for GEC10:

Demo experiment where Cluster D researchers obtain and stitch resources from multiple Cluster D sites (and backbone domains) using their SM.
Demo experiment where protoGENI researchers obtain resources via GENI AM API v1.0, using RSpec resource description.
Demo operations portal into Cluster D site, for status and logs, with connections to GMOC

Demos for GEC11:

Demo experiment where Cluster D researchers get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description)
Demo experiment where Cluster D researchers stitch L2 connectivity across Cluster C (protoGENI), and Cluster D sites
Demo experiment where Cluster D researchers include tools (e.g., GUSH) to help authorize, reserve and assign resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API?) (same as GENI AM API v2.0? )

Views:

Figure 1-1) and 1-2): Cluster D Config at end of Spiral 3



Figure 2): ORCA Site Config


Figure 3): Multiple ORCA Sites


Figure 4): ORCA Interop with protGENI


Figure 5): ORCA Experiment Flow


Adjourn (4:30pm)

References

Attachments (16)