Changes between Initial Version and Version 1 of Gec5ClusterCAgenda


Ignore:
Timestamp:
07/14/09 17:12:00 (12 years ago)
Author:
ricci@cs.utah.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Gec5ClusterCAgenda

    v1 v1  
     1= Cluster B Meeting Agenda for GEC5 =
     2
     3The GPO has given us two timeslots to meet as a cluster at the next GEC.
     4Below are draft agendas for those meetings. Feedback and suggestions
     5welcome!
     6
     7Please note two things:
     8
     9 1) For those of you who have signed up to do demos, there's a strong chance that our cluster meeting will happen in a meeting room, not the demo room.  The meeting room is supposed to have a projector and !WiFi.  Will this be okay for everyone?
     10
     11 2) I have a slot in the agenda for the second meeting for projects to give (short) status reports, but only one group signed up so far. If anyone else would like to give a report, please let me know.
     12
     13== Cluster Meeting: Monday, July 20, 1:00 - 5:00 ==
     14
     15Because it's hard for those giving demos in the demo session to go around and
     16see others' demos, and because it's particularly important for cluster members
     17to see each others' demos, we'll be using this time as a sort of "dress
     18rehearsal": a chance to present our demos, one at a time, to each other. The
     19set of projects that have agreed to present are:
     20
     21    ProtoGENI:                   Robert Ricci (Utah)[[BR]]
     22    Digital Object Architecture: Giridhar Manepalli (CNRI)[[BR]]
     23    DTunnels and BGPMux:         Nick Feamster (Georgia Tech)[[BR]]
     24    Million-node GENI:           Justin Cappos (and others?) (Washington)[[BR]]
     25    Measurement System:          Charles Thomas (Wisconsin-Madison)[[BR]]
     26    TIED:                        Ted Faber (ISI)[[BR]]
     27
     28I will not be putting specific time limits on these demos, since I expect we
     29will not use the entire four hour slot that's been alloted to us. However, do
     30keep in mind that people will be watching several demos during this session,
     31and that there will be a demo session afterwards, so please try not to go too
     32long.
     33
     34Logistics: Depending on the number of people who choose to attend and the
     35sizes of the spaces, we may hold this session either in the "cluster meeting
     36room" or the demo room. We will have access a projector and wireless Internet
     37in the cluster room. It's unknown at this point how early all of the equipment
     38in the demo room will be set up.
     39
     40== Cluster Meeting: Tuesday, July 20, 1:00 - 5:00 ==
     41
     42This meeting will give us an opportunity to discuss some of the technical
     43challenges facing our cluster. Most topics within this meeting will be
     44group discussions, kicked off by a short presentation.
     45
     46=== A. Introductions and Status Reports ===
     47
     48This will be a chance for any projects that wish to introduce themselves to the
     49cluster or to give status reports. Any other group that would like to sign up
     50for this agenda item are welcome to; presentations may be as formal or informal
     51as you'd like.
     52
     53 *  ETRI Korea has proposed to join this cluster in Spiral 2; they will be giving a status update
     54
     55=== B. Control Framework Plans and Priorities ===
     56
     57This session will be a chance for the ProtoGENI project to present its plans
     58for Spiral 2, with particular emphasis on how this will affect the other
     59projects that rely on it as a common control framework. We hope this will stir
     60up some feedback, helping us to alter our priorities to match what's needed by
     61others in the cluster, and to help set priorities for the cluster as a whole.
     62
     63=== C. Design Discussion: Integrating Million-Node GENI ===
     64
     65The Million-Node GENI project from the University of Washington has joined
     66Cluster C, and presents a particularly interesting integration challenge. In
     67many ways, it has semantics that do not mesh with those described in many of
     68the GENI design documents and on the ProtoGENI wiki. In many cases, this seems
     69to be due to the fact that this project aims to control a very large set of
     70resources (millions of nodes) owned by many different owners (potentially tens
     71or hundreds of thousands.) The semantics that make sense for such a loose
     72collection of resources are different than those in the cluster's current
     73model, and working with the Million-Node GENI project presents an opportunity
     74to expand our control framework to encompass such resources. This discussion
     75will center on the ways in which the design of our control framework can be
     76informed by the experiences of the Million-Node GENI project.
     77   
     78=== D. Backbone Discussion ===
     79
     80In partnership with Internet2 and HP, the ProtoGENI project is in the process
     81of rolling out a nationwide backbone. Connectivity on this backbone is planned
     82for several GENI projects and campuses. This portion of the meeting will give
     83updates on the design of the backbone, status reports, and ideas for connecting
     84to projects and campuses.