Shadow: GENI_Shadownet.txt

File GENI_Shadownet.txt, 3.2 KB (added by, 14 years ago)

Q2 2010 Quarterly report in txt format

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