• End-user Opt-in

• Experiment Workflow and Services

• Facility Control Framework

• Operations, Management, Integration, & Security

• Substrate

GENI Facility Control Framework Working Group

<control-wg>

---

Chairs:

Larry Peterson <llp@princeton.edu>
John Wroclawski <jtw@isi.edu>

SE:

Aaron Falk <falk@geni.net>

Discussion Mail List Information:

subscribe
mailman archive
nabble archive

Wiki: http://groups.geni.net/geni/wiki/GeniControl

Scope:

What is universal across GENI components? How will evolution be accommodated with or without a full transition of all GENI nodes at once?

Initial Deliverables:

• A 20pp description of what can/should be implemented by Oct 2008 (including dependencies); system diagram with major entities and system interfaces; worked example showing how an experiment is instantiated and runs end-to-end across a system where GENI has federated with other facilities (i.e., interconnected with autonomously-administered facilities).

Later Deliverables:

• Implementation Plan: schedule of functional milestones (with initial emphasis on 2008); analysis of gaps in current technology and previous design work; strategy for evolving functionality
• Definition of Architectural Components: policy-agnostic resource framework; resource specification, discovery, & protection; addressing architecture; federation mechanisms; naming; authentication, & authorization; universal operations interface
• API Definitions: specify resource allocation & control interfaces
• Architectural Risks: if the choices are wrong, how might the system be limited?
• Other contributions required for GENI Project Deliverables.