| | 1 | = Cluster B Meeting Agenda for GEC5 = |
| | 2 | |
| | 3 | The GPO has given us two timeslots to meet as a cluster at the next GEC. |
| | 4 | Below are draft agendas for those meetings. Feedback and suggestions |
| | 5 | welcome! |
| | 6 | |
| | 7 | Please 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 | |
| | 15 | Because it's hard for those giving demos in the demo session to go around and |
| | 16 | see others' demos, and because it's particularly important for cluster members |
| | 17 | to see each others' demos, we'll be using this time as a sort of "dress |
| | 18 | rehearsal": a chance to present our demos, one at a time, to each other. The |
| | 19 | set 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 | |
| | 28 | I will not be putting specific time limits on these demos, since I expect we |
| | 29 | will not use the entire four hour slot that's been alloted to us. However, do |
| | 30 | keep in mind that people will be watching several demos during this session, |
| | 31 | and that there will be a demo session afterwards, so please try not to go too |
| | 32 | long. |
| | 33 | |
| | 34 | Logistics: Depending on the number of people who choose to attend and the |
| | 35 | sizes of the spaces, we may hold this session either in the "cluster meeting |
| | 36 | room" or the demo room. We will have access a projector and wireless Internet |
| | 37 | in the cluster room. It's unknown at this point how early all of the equipment |
| | 38 | in the demo room will be set up. |
| | 39 | |
| | 40 | == Cluster Meeting: Tuesday, July 20, 1:00 - 5:00 == |
| | 41 | |
| | 42 | This meeting will give us an opportunity to discuss some of the technical |
| | 43 | challenges facing our cluster. Most topics within this meeting will be |
| | 44 | group discussions, kicked off by a short presentation. |
| | 45 | |
| | 46 | === A. Introductions and Status Reports === |
| | 47 | |
| | 48 | This will be a chance for any projects that wish to introduce themselves to the |
| | 49 | cluster or to give status reports. Any other group that would like to sign up |
| | 50 | for this agenda item are welcome to; presentations may be as formal or informal |
| | 51 | as 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 | |
| | 57 | This session will be a chance for the ProtoGENI project to present its plans |
| | 58 | for Spiral 2, with particular emphasis on how this will affect the other |
| | 59 | projects that rely on it as a common control framework. We hope this will stir |
| | 60 | up some feedback, helping us to alter our priorities to match what's needed by |
| | 61 | others in the cluster, and to help set priorities for the cluster as a whole. |
| | 62 | |
| | 63 | === C. Design Discussion: Integrating Million-Node GENI === |
| | 64 | |
| | 65 | The Million-Node GENI project from the University of Washington has joined |
| | 66 | Cluster C, and presents a particularly interesting integration challenge. In |
| | 67 | many ways, it has semantics that do not mesh with those described in many of |
| | 68 | the GENI design documents and on the ProtoGENI wiki. In many cases, this seems |
| | 69 | to be due to the fact that this project aims to control a very large set of |
| | 70 | resources (millions of nodes) owned by many different owners (potentially tens |
| | 71 | or hundreds of thousands.) The semantics that make sense for such a loose |
| | 72 | collection of resources are different than those in the cluster's current |
| | 73 | model, and working with the Million-Node GENI project presents an opportunity |
| | 74 | to expand our control framework to encompass such resources. This discussion |
| | 75 | will center on the ways in which the design of our control framework can be |
| | 76 | informed by the experiences of the Million-Node GENI project. |
| | 77 | |
| | 78 | === D. Backbone Discussion === |
| | 79 | |
| | 80 | In partnership with Internet2 and HP, the ProtoGENI project is in the process |
| | 81 | of rolling out a nationwide backbone. Connectivity on this backbone is planned |
| | 82 | for several GENI projects and campuses. This portion of the meeting will give |
| | 83 | updates on the design of the backbone, status reports, and ideas for connecting |
| | 84 | to projects and campuses. |
