GENI technical risk areas

To GENI Working Groups-

At the end of the current planning process, 2-4 years from now, GENI
needs to have a mature design, budget, and buildout schedule.  Towards
that end, this fall the GPO is planning to issue the first of a series
of semi-annual solicitations for proposals to perform risk reduction
design and prototyping.  Risk reduction activities are those that make
it more likely that the GENI will perform as desired and be
constructed on-budget and on-schedule.

The coming solicitation will be targeted at areas which GPO system
engineering feels are the top concerns that need to be addressed over
the coming year.  We have compiled the following initial list:

* Architecture & requirements development. Create/improve designs for
   for areas including instrumentation, security (conceptual design for
   identity, authentication, and authorization; mappings to existing
   technologies), resource description and discovery, federation, and
   end-user opt-in. Some prototyping in these areas will be useful.

* Slicing as a basic construct, employed end-to-end across a range of
   technologies. Here near-term, working demonstrations of the relevant
   GENI subsystems and trial integrations will be particularly useful,
   as will early demonstrations of instrumentation in a sliced
   environment.

* Developing a practical approach for administrative and operational
   control that addresses the needs of cooperative facility hosts
   (e.g., universities); federated, interconnected facilities (e.g.,
   non-NSF GENI facilities); subcontracted facilities (e.g., optical
   networks or co-location facilities); and a GENI Network Operations
   Center.

There will be a session for open discussion of project risks on
October 9th at the GENI Engineering Conference [1].  We are interested
in hearing feedback on whether elements on this list should be removed
(i.e., well-understood, not risky or not timely) or replaced by other
items which are of greater concern.

Looking ahead, the GPOs risk assessment will be informed by the GENI
working groups.  At future GEC meetings, the GPO staff system
engineers supporting the working groups will be responsible for
reporting on each working group's readiness.  Areas which are not
ready are potential risk areas.  Risk areas the GPO determines to be
near-term and significant may appear in future solicitations.

We invite your participation in this discussion.

--aaron

[1] http://www.geni.net/geni-engineering-conference


---
    Aaron Falk
    Interim Engineering Architect
    GENI Project Office
    http://www.geni.net



_______________________________________________
opt-in-wg mailing list
opt-in-wg@...
http://lists.geni.net/mailman/listinfo/opt-in-wg