Changes between Initial Version and Version 1 of Gec9ControlFrameworkAgenda


Ignore:
Timestamp:
10/27/10 17:02:04 (10 years ago)
Author:
Aaron Falk
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Gec9ControlFrameworkAgenda

    v1 v1  
     1= Control Framework Working Group =
     2
     3Chairs: Jeff Chase, Duke University; Rob Ricci, University of Utah[[br]]
     4System Engineer: Aaron Falk, GENI Project Office
     5
     6'''Agenda'''
     7
     8TOPIC 1: GENI APIs  (60 minutes)
     9
     10  The first part of the Control Framework Working Group meeting at GEC9 will consist of a discussion of the GENI APIs that are under development:
     11
     12      http://groups.geni.net/geni/wiki/GeniApi
     13
     14  This discussion will kick off with a talk by Tom Mitchell of BBN, who has been leading the design and a few different implementations of these APIs.
     15
     16  We would like to follow this up with short (5 minute max) talks by members of the working group, recommending changes (small and large) to the API, or discussing the need (or lack thereof) for a common API. Talks proposing changes should include a) the deficiency or opportunity motivating the change, b) the specifics of the change relative to the current API, and c) the benefits of the proposal.
     17
     18  If you're interested in giving one of these talks, please email the WG chairs (myself and Jeff Chase) and our SE, Aaron Falk. We want to leave time for discussion of these ideas, and time is limited, so we may need to limit the number of talks that we accept.
     19
     20TOPIC 2: Talks/discussion about next directions for GENI API or architecture in general. (45 minutes)
     21
     22  * Naming & Trust, Steve Schwab, ''Cobham''
     23  * Stitching, Tom Lehman, ''USC ISI''
     24  * Expedient: OpenFlow Client-GUI/Clearinghouse, Jad Naous, ''Stanford''
     25
     26TOPIC 3: Invited talk (15 min)
     27
     28  Speaker: Mathieu Lacage of INRIA's Planete team
     29
     30  ''In this talk, we will present NEPI, an experiment-plane tool which attempts to provide a unified abstraction on top of existing testbeds to describe the network-level and application-level aspects of a network experiment and automate resource reservation, application deployment, experiment monitoring, and trace collection. [http://ralyx.inrialpes.fr/2009/Raweb/planete/uid22.html NEPI project page]''