1 | [[PageOutline]] |
---|
2 | |
---|
3 | = GENI Shadownet Project Status Report = |
---|
4 | |
---|
5 | Period: Q2 2010 - (4/1/10-6/30/10) |
---|
6 | |
---|
7 | == I. Major accomplishments == |
---|
8 | |
---|
9 | |
---|
10 | === A. Milestones achieved === |
---|
11 | |
---|
12 | The project is still in the early phases and no milestone are due at |
---|
13 | this point. |
---|
14 | |
---|
15 | === B. Deliverables made === |
---|
16 | |
---|
17 | None yet. |
---|
18 | |
---|
19 | == II. Description of work performed during last quarter == |
---|
20 | |
---|
21 | The following provides a description of the progress made this last quarter. |
---|
22 | |
---|
23 | === A. Activities and findings === |
---|
24 | |
---|
25 | Our primary focus this quarter has been on laying the groundwork needed for |
---|
26 | the Juniper router deployment. Specifically, we were able to get the funding |
---|
27 | in place for Internet2 to be able to proceed with purchasing and installing |
---|
28 | the Juniper routers. We also initiated conversations with Juniper to |
---|
29 | involve them in the design and specification of the project and to ensure the |
---|
30 | equipment we purchase will meet the requirements of the project. We also, |
---|
31 | together with the GPO, held initial discussions regarding ways to make the |
---|
32 | Juniper SDK available to GENI users. We have arrived at a hardware |
---|
33 | configuration that we believe meets our requirements and are in the process |
---|
34 | of ordering the equipment and defining an installation schedule. |
---|
35 | |
---|
36 | In addition to defining the hardware specification, we have had various |
---|
37 | conference calls among the project participants (Kentucky, AT&T, Internet2, |
---|
38 | and Utah) to begin designing the GENI Shadownet aggeregate manager components |
---|
39 | of the system. In particular, we have tried to understand what functionality |
---|
40 | is needed in the GENI Shadownet aggregate manager and what parts will be |
---|
41 | handled by the clearinghouse and other ProtoGENI aggregate managers. We plan |
---|
42 | to leverage much of the experience Utah has already gained from incorporating |
---|
43 | SPP nodes into the ProtoGENI/Internet2 backbone, and our design will use |
---|
44 | similar ways of assigning IP address space and creating VLANs. AT&T has |
---|
45 | begun to identify changes that will need to be made to their existing code in |
---|
46 | order to make it interoperate with the ProtoGENI framework. We plan to |
---|
47 | continue this parallel development so that we will be well situated to begin |
---|
48 | testing the new software once the hardware is installed and tested. |
---|
49 | |
---|
50 | === B. Project participants === |
---|
51 | |
---|
52 | The following individuals are involved with the project in one way or another: |
---|
53 | * Jim Griffioen - Project PI (Kentucky) |
---|
54 | * Zongming Fei - Project Co-PI (Kentucky) |
---|
55 | * Kobus van der Merwe - Project Co-PI (AT\&T) |
---|
56 | * Eric Boyd - Subcontract Lead (Internet2) |
---|
57 | * Brian Cashman - Deployment Manager (Internet2) |
---|
58 | * Lowell Pike - Network administrator (Kentucky) |
---|
59 | * Hussamuddin Nasir - Technician/Programmer (Kentucky) |
---|
60 | * Emmanouil Mavrogiorgis - Research Staff (AT\&T) |
---|
61 | |
---|
62 | === C. Publications (individual and organizational) === |
---|
63 | |
---|
64 | None yet. |
---|
65 | |
---|
66 | === D. Outreach activities === |
---|
67 | |
---|
68 | Jim Griffioen attended the 2nd GENI Instrumentation and Measurement Workshop |
---|
69 | June 8-9, 2010 to participate in the design of the instrumentation and |
---|
70 | measurement plane which will be valuable later when we instrument GENI |
---|
71 | Shadownet. |
---|
72 | |
---|
73 | === E. Collaborations === |
---|
74 | |
---|
75 | Most of our collaborations have been with the Shadownet team from Kentucky, |
---|
76 | AT&T, and Internet2, but we have also had conversations with our |
---|
77 | colleagues at Utah and Delaware, and have had conversation with Juniper and |
---|
78 | the GPO. |
---|
79 | |
---|
80 | === F. Other Contributions === |
---|
81 | |
---|
82 | None yet. |
---|