wiki:ClusterD

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

--

Cluster D Integration

Projects

ORCA/BEN and ORCA Augmentation
DOME
ViSE
KanseiSensorNet (KANSEI)
Embedded Real-Time Measurements (ERM)
Data Intensive Cloud Control (DICLOUD)
OKGems: Cyber-Physical System (OKGEMS)
Integrated Measurement Framework (IMF)
iGENI Distributed Network Research Infrastructure (IGENI)
LEARN Network (LEARN)
BBN ORCA Node

Meetings and Demos

ORCA-fest May 28, 2009, web site
Cluster D Conference Call on June 11, 2009
Cluster D Review Meeting July 2, 2009
"ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009
"ORCA/BEN Integration Demo July 7, 2009, web site
Cluster D Meetings at GEC5 July 20 and 21, 2009

References and Documents

GENI - ORCA web site, including ORCA code and ticket system
Subscribe to Cluster D mailing list (cluster-d@renci.org), for PIs and senior personnel, to discuss administrative cluster-wide issues
Subscribe to CLuster D mailing list (geni-orca-users@renci.org), primarily for developers, to discuss technical issues about the implementation, etc.
Prototype DOME controller and handler modules for ORCA, 2009
Spiral 1 Plan Document, on 7/02/09
Spiral 2 Roadmap slides, with task ratings, on 7/21/09
Cluster D Roadmap Document, on 10/15/09
Cluster D Roadmap Drawings, on 10/15/09

Roadmap for Spiral 2

Goals

The following goals have been established by the GPO for Spiral 2.

Goal 1: Live experiments, the central goal of Spiral 2. Support significant numbers of research experiments in the end-to-end prototype systems. The GPO expects live experimentation to begin near the end of Spiral 1, which will intensify through Spiral 2 as we begin continuous operation of the prototype systems. This will begin to give us all substantial (early) operational experience, as these experiments will help us all understand the prototypes' strengths and weakness, which will drive our Spiral 3 goals.

Goal 2: Identity management

Goal 3: Improved integration of data & control planes, within clusters

Goal 4: Instrumentation

Goal 5: Interoperability, permitting clusters to access the widest number of aggregate

Key Dates

Begin 9/1/09 or 10/1/09, depending on the project
ORCA Rel 1.3 10/1/2009
GEC6 11/16/09
ORCA Rel 2.1 2/1/10
GEC7 3/16/10
ORCA Rel 2.2 6/1/10
GEC8 7/20/10
End 8/31/10 or 9/30/10, depending on the project
ORCA Rel 2.3 10/1/10

ORCA Software Releases

The following roadmap describes features and capabilities of ORCA software releases.

These releases are currently scheduled for every 4 mo. , and include work done by both Solicitation 1 (1582) and Solicitation 2 (1700) ORCA projects.

For latest status, go to GENI - ORCA, web site maintained by RENCI, including ORCA code and ticketing system or contact Ilia Baldine Ilia Baldine at RENCI

ORCA Rel 1.3 10/1/2009
ORCA Rel 2.1 2/1/10
ORCA Rel 2.2 6/1/10
ORCA Rel 2.3 10/1/10

Current issues:

Revoking / Canceling Leases

With ORCA, is there a method for leases to be canceled, or for outstanding requests to be revoked? This is required, or at least very highly desired, for DOME. Some scenarios:

  • An experiment is started on the buses and the researcher begins getting erroneous results, or the experiment starts generating too much data (this happens). We'd like to be able to prematurely terminate a lease to stop the experiment, even if the allocated resources are not returned to the pool.
  • An experiment is scheduled for the future, but then the researcher discovers he or she wants to change the experiment or alter the time.

Obviously, there are many other scenarios that make the functionality desirable.



Cluster D Operating Capabilities and Clearinghouse

The following roadmap describes features and capabilities of the Cluster D operating environment, including a production-level Cluster D clearinghouse.



fig 1-1

fig 1-2

fig 1-3

fig 1-4

Connectivity

BEN Connectivity
DOME Connectivity
ViSE
Kansei Connectivity

Instrumentation and Mesurements

Experiments

Cluster D Clearinghouse at RENCI ; get login from Ilia Baldine
DOME and Federated Scheduling, i.e., towards an experiment that utilizes resources from multiple testbeds

Interoperability

Attachments (23)