Version 9 (modified by, 11 years ago) (diff)


Control Framework Topics

Wed, 1030-1200

Organizer: Tom Mitchell, GPO

Dial In: 866-453-5550 ; Participant pin: 6513886#

This meeting will update the GENI software development community on three key efforts: InCommon membership, !RSpec standardization and Cross-aggregate stitching. Following the brief updates we will convene a panel discussion on the Clearinghouse design. Members of the software development community will discuss what services must be included in the GENI Clearinghouse, how those services interact with experimenters and aggregates, and the implications on GENI policies and federation agreements.


  • InCommon update - Tom Mitchell, GPO slides
  • RSpec update - Tom Mitchell, GPO slides
  • Stitching update - Tom Lehman, ISI slides
  • Panel: Clearinghouse Design - Adam Slagell, Illinois, Moderator slides
    • Ilia Baldine, RENCI
    • Andy Bavier, Princeton
    • Ted Faber, ISI

Meeting Summary

Marshall Brinn was introduced. Marshall is new at the GPO and will be the technical director / software architect. Marshall wants to update the GENI wiki to reflect reality, rather than past visions or hopes. He would also like to turn "should" into "is". He thinks GENI needs to narrow the focus and work to put the vision into practice.

Tom Mitchell gave an update on Identity and InCommon integration. Both U. of Utah and Duke University are releasing attributes to the prototype identity portal. More universities are welcome, but remember, this is a prototype. The portal speaks both GENI credentials and ABAC. We anticipate updating the portal to incorporate some of the new federation concepts and the proposed ABAC vocabulary. Tom's slides are available on the session wiki page.

Tom Mitchell gave an update on RSpecs. There is a new GENI v3 RSpec schema available at This schema is identical to ProtoGENI v2 RSpecs with the exception of being housed at a new location. There is a new OpenFlow extension to describe flowspace resources. All major players (OpenFlow, ORCA, PlanetLab and ProtoGENI) are supporting the standard RSpec schema. Tom's slides are available on the session wiki page.

Tom Lehman gave an update on stitching. The stitching architecture has all the components, the schema has been published, and there is client support for tree mode in omni. Key focus areas going forward are AM API changes to support stitching (specifically negotiating link properties), Internet2 support, and getting more aggregates involved. Tom's slides are available on the session wiki page.

Adam Slagell moderated a panel discussion on Clearinghouse Design. The panel included Ilia Baldine, Andy Bavier, Ted Faber and Jeff Chase. Adam has written detailed minutes of the meeting. The panel was convened as a follow-up to Aaron Falk's GEC 11 Federation Talk to discuss in more detail the Clearinghouse itself. The panel discussed a vocabulary for talking about the Clearinghouse, its services, and entities that interact with it. The panel also discussed the Project Leader concept introduced by Aaron Falk at GEC 11. Finally, the panel discussed a set of services that the Clearinghouse must and might provide.

Panel conclusions:

  • GENI needs to include the concept of Project Leader. This is the responsible person with respect to a set of slices and a set of experimenters. The project leader decides who is included in a project as well as who can create or modify slices.
  • The set of required services for the Clearinghouse include, but are not limited to:
    • trust anchor
    • endorser of agreements
    • registrar of projects and project leaders
    • endorser of GENI actors (identity providers, slice authorities, aggregates)
  • The set of optional services for the Clearinghouse include, but are not limited to:
    • identity portal (non-exclusive)
    • slice authority (non-exclusive)
    • resource discovery (non-exclusive)

The panel duration was too short to discuss everything, so there remain a number of topics and open questions. These include, but are not limited to:

  • Who can bind slices to projects?
  • How should credential revocation be handled?
  • Is a global slice tracking mechanism required to track GENI-wide allocation limits?
  • What information should be collected at project registration?
  • What is the composition of the GENI Oversight Group?

Panel links:

Attachments (3)