ClusterB: 2-13-09-cluster-b-invite.txt

File 2-13-09-cluster-b-invite.txt, 3.5 KB (added by Aaron Falk, 10 years ago)
Line 
1Message-ID: <4963C7A6.1030401@bbn.com>
2Date: Tue, 06 Jan 2009 16:05:42 -0500
3From: Aaron Falk <falk@bbn.com>
4User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
5MIME-Version: 1.0
6To: Larry Peterson <llp@cs.princeton.edu>,
7 Nick McKeown <nickm@stanford.edu>,
8 Guido Appenzeller <appenz@cs.stanford.edu>,
9 Guru Parulkar <parulkar@stanford.edu>,
10 Rob Ricci <ricci@cs.utah.edu>, Jon Turner <jon.turner@wustl.edu>,
11 Peter O'Neil <poneil@maxgigapop.net>,
12 James Sterbenz <jpgs@ittc.ku.edu>
13CC: Chip Elliott <celliott@bbn.com>, gpo-tech@bbn.com
14Subject: Invite to Cluster B Networking meeting - Feb 13, 2009
15Content-Type: text/plain; charset=ISO-8859-1; format=flowed
16Content-Transfer-Encoding: 7bit
17
18Folks,
19
20You are invited to a review of how the Spiral 1 control plane for Cluster B will interface with network aggregates and components. The Enterprise GENI project has examined the PlanetLab code and expressed concerns to us about the difficulty integrating OpenFlow equipment in Spiral 1 given the current state of the code and interfaces.
21
22We feel this raises a broader concern about a critical technical issue.  Spiral 1 of the GENI control plane *must* demonstrate support for network aggregates and components, as this is an item of very high technical risk.
23
24The plan has been to encourage aggregates to integrate using the PlanetLab-provided Aggregate Manager (AM). In other words, rather than implement an AM on their own to meet an interface spec, each project would adapt the aggregate-facing side of the PlanetLab reference AM.  The Enterprise GENI project has raised two specific concerns: First, if an aggregate is substantially different from a PlanetLab node, how hard is it to adapt PLC? Second, how hard will it be to evolve the over-the-wire interface once the initial cluster is integrated? We feel it is worth examining these two issues and develop consensus on integration strategy early on.
25
26Again, demonstrating control plane functionality is one of the two central goals for Spiral 1. This meeting is a chance to have a small, focused f2f discussion about the specifics of the interface and its rationale. The objective of the meeting is to come to agreement on how to demonstrate in Spiral 1 that networking components and aggregates will be supported by the GENI control plane.  Key technical contributors for the PlanetLab and Enterprise GENI projects are invited along with representatives from other networking projects in Cluster B.  The ProtoGENI project is also invited since it shares the problem of supporting networking and interoperates with PlanetLab.
27
28In preparation for the meeting, I'd like to ask each of network projects in Cluster B to review the current PlanetLab code and be prepared to talk about how you plan to integrate your aggregate.  If you like, you can prepare a few slides.
29
30Strawman Agenda
31
32  1. Review of PlanetLab code architecture
33  2. Discussion of how to integrate PLC and network aggregates
34  3. Develop a plan for demonstrating networking support in Spiral 1
35
36Invited:
37
38  PlanetLab: Larry Peterson & staff
39  Enterprise GENI: Nick McKeown, Guru Parulkar, Guido Appenzeller
40  ProtoGENI: Rob Ricci
41  GpENI: James Sterbenz
42  Mid-Atlantic Crossroads: Peter O'Neil
43  Internet Scale Hosting: Jon Turner
44  GPO staff
45
46Logistics
47
48  Time:     8:30am - 3:00pm
49  Date:     February 13th, 2009
50            plan to arrive the night before
51  Location: Denver Airport Marriott at Gateway Park
52            http://www.marriott.com/hotels/travel/dengp
53  Expenses: paid by GPO
54  Rooms:    RSVP to ekeohane@bbn.com
55            GPO will reserve a room; you pay, we will reimburse
56
57
58
59
60
61
62
63