Roadmap

• Milestone: TIED:Identify specific year 1 outreach communities.

  1 year late (01/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Identify specific outreach communities for the year-1 program. Identify and document initial requirements they impose on TIED federation architecture and interfaces.

• Milestone: GMOC:Integrate Security services in GMOC framework

  1 year late (04/01/09)

  100%

  Closed tickets:

  2

  Active tickets:

  0

  Work with other GENI projects providing security services to GENI. The security services will be integrated into the GMOC framework as they become available. Ongoing work in months 1-6.

• Milestone: REGOPT:Produce reference opt-in design for a Spiral 1 project

  1 year late (04/01/09)

  Produce a reference design showing how a planned Spiral 1 project(s) opt‐in can be implemented with Spiral 1 end‐to‐end connections. Demonstrate how the design meets opt‐in requirements from the initial requirements document. Submit results to Opt-in, Control Framework, and OMIS working groups.

• Milestone: TIED:Provide user access to DETER via TIED.

  10 months late (05/01/09)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  Provide user access to DETER testbed using TIED building blocks (month 7 - month 12 of year 1).

• Milestone: GENI4YR: Survey of research and education experiments

  9 months late (06/01/09)

  Provide a survey of research and education experiments of interest to 4 year colleges, and the substrate resources required to enable them.

• Milestone: ENTGENI: Demonstrate OpenFlow in GENI

  8 months late (07/01/09)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Demonstrate use of OpenFlow switches with a GENI clearinghouse in the Phase 0 deployment. Present demonstration at a GEC meeting. Can happen as late as 10/01/09, depending on schedule. Can happen at an event similar to GEC if there are GEC scheduling issues.

• Milestone: ENTGENI: Deploy Phase 0 Enterprise GENI network at Stanford

  8 months late (07/01/09)

  100%

  Closed tickets:

  2

  Active tickets:

  0

  Deploy Phase 0 of Enterprise GENI comprising an OpenFlow network of few switches and wireless APs and a couple of computers in the Gates building of Stanford campus.

• Milestone: ENTGENI: Start integrating interfaces from ENTGENI AM to Clearinghouse

  8 months late (07/01/09)

  100%

  Closed tickets:

  2

  Active tickets:

  0

  Start integrating interfaces to a GENI control framework clearinghouse in an aggregate component manager for an OpenFlow network. This work is ongoing. The milestone:"ENTGENI: Demonstrate OpenFlow in GENI" requires significant progress on the ongoing work.

• Milestone: ORBIT: 1d Provide VLAN connections to the GENI backbone

  8 months late (07/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  d) Provide VLAN connections from your testbeds to the GENI backbone network on NLR (via MAGPI East in Philadelphia). (9mo)

• Milestone: REGOPT:Experimental use of local opt-in prototype

  8 months late (07/01/09)

  Present the opt-in prototype to the local Computer Science communities to encourage them to explore its capabilities. Solicit some real networking experiments from the community to gain real field experience with these opt-in techniques. (Work is ongoing from month 9-12).

• Milestone: MeasurementSys: Prototype with basic measurement functionality.

  8 months late (07/20/09)

  Develop a prototype with basic measurement functionality, including interface to a GENI control framework. Test implementation in WAIL.

• Milestone: GENI4YR: Identify spiral-1 supported experiments

  7 months late (08/01/09)

  Focus on spiral-1 substrate technologies and identify which experiments from the survey could be supported on spiral-1

• Milestone: REGOPT:Develop local opt-in prototype

  7 months late (08/01/09)

  Since there is not significant field experience with wholesale opt-in already available, develop a local opt-in prototype that permits local researchers to interpose experimental networking equipment in the path to the public Internet. Make the scripts and configurations available to interested GENI participants via download.

• Milestone: MeasurementSys: Basic functionality prototype available.

  7 months late (08/10/09)

  Make basic functionality prototype available to GENI users in WAIL testbed.

• Milestone: INSTOOLS: Integrate and Document Instrumentation Toolset

  7 months late (08/15/09)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Begin integrating existing University of Kentucky tools in the prototype testbed. Produce a document describing the architecture/design of the instrumentation toolset along with a description of some of the proposed tools. (Ongoing in months 10-12.)

• Milestone: D Meas: Describe the network connections

  6 months late (08/31/09)

  Describe the network connections between specific external test equipment identified/recommended above and spiral-1 substrate components.

• Milestone: PlanetLab: Document architecture for v0.2

  6 months late (09/01/09)

• Milestone: PlanetLab: Establish direct connectivity between project facilities and Internet 2

  6 months late (09/01/09)

• Milestone: PlanetLab: complete integration of v0.2 sw into CF cluster aggregates

  6 months late (09/01/09)

  Deploy component and clearinghouse packages v0.2 in GENI testbed, and assist other groups and projects to *complete* integration with the following:
  

  • federation with other PlanetLab-related testbeds;
    
  • PlanetLab programmable host clusters;
    
  • VINI network;
    
  • specialized network nodes, paired with VINI PoPs?;
    
  • enterprise access networks;
    
  • other enterprise elements, including host clusters, network nodes
    
  • and wireless access nodes;
    
  • researcher helper tools;
    
  • researcher helper tools;
    
  • extended programmable host nodes;
    
  • aggregate of optical networks, including connections to Internet2;
    
  • regional optical network, with programmable optical nodes;
    
  • overlay hosting network nodes;

• Milestone: TIED:Participate in NSF TRUST Science and Technology Center's teacher education program.

  6 months late (09/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Participate in NSF TRUST Science and Technology (S&T) Center's Summer, 2009 Teacher Education program to familiarize TRUST's pool of undergraduate and underrepresented community institution faculty with educational use and potential of TIED/GENI facilities. (Exact timing depends on dates of program, but should be completed by September 1, 2009.)

• Milestone: INSTOOLS: Deploy AM and open UKY Edulab for GENI

  6 months late (09/15/09)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Deploy the Aggregate Manager in the Kentucky GENI prototype, and support limited operations to allow experimental use of the testbed through the ProtoGENI clearinghouse. (This work in ongoing in months 11 and 12.)

• Milestone: BGPMux: Make BGP mux and tunnel software available -

  5 months late (09/30/09)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  Software release. Make BGP mux and tunnel software available for download by other GENI prototype projects.

  • This will be a bare-bones release: A user at ProtoGENI will be able to specify tunnels and BGP sessions through the management interface

  • This will produce an RSpec that our scripts can read and:

  o Produce tunnels on ProtoGENI nodes

  o Produce BGP sessions between the BGP mux and protoGENI clients

  This due date of this milestone was changed from 6/1/09 to 9/30/09. See Ticket #183 for details.

• Milestone: GMOC:Complete initial GMOC Data Exchanger Implementation

  5 months late (09/30/09)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  The initial GMOC framework implementation will include a Data Exchanger. This is the software implementation and protocol used to receive and transmit operational datasets among GMOC partner projects and with the GMOC. Work ongoing in months 6-12.

• Milestone: GMOC:Complete initial GMOC Operational Dataset Translater Implementation

  5 months late (09/30/09)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  The initial GMOC framework implementation will include an Operational Dataset translator. This will be software used to convert data in existing formats from existing projects that would be of operational interest into the GMOC Native Operational Data Format. Work ongoing in months 6-12.

• Milestone: GMOC:Complete initial implementation of Emergency Stop and notifications

  5 months late (09/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  2

  Actively provide “emergency stop” functionality to participating projects to isolate or turn down disruptive experiments, and actively notify partner projects of operational issues, as they want

• Milestone: GMOC:Complete initial implementation of prototype GMOC

  5 months late (09/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  The working prototype GMOC is a documented suite of systems and processes working to share operational data among all the partner projects. Work ongoing in months 6-12.

• Milestone: GMOC:Demonstrate initial GMOC Framework Implementation at a GEC

  5 months late (09/30/09)

  67%

  Closed tickets:

  2

  Active tickets:

  1

  Exact timing of GEC demonstration depends on particulars of GEC schedules.

• Milestone: GMOC:Draft GENI Concept of Operations

  5 months late (09/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Help develop GENI Concept of Operations. Coordinate with GENI projects and the OMIS working group to develop a draft GENI Concept of Operations framework. Work ongoing in months 1-12.

• Milestone: REGOPT:Demonstrate local opt-in

  5 months late (09/30/09)

  Develop a demonstration based on the reference Spiral 1 prototype design, and present the demonstration at a GENI Engineering Conference. Make demonstration scripts and configurations available to interested GENI participants via download. (Exact timing of demonstration will depend on GEC schedules.)

• Milestone: TIED:Demonstrate extended functionalities for outreach communities.

  5 months late (09/30/09)

  Demonstrate extended clearinghouse/component functionalities key to outreach communities (e.g., extended security model access).

• Milestone: TIED:Provide direct VLAN interface to TIED resources

  5 months late (09/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Provide direct external ethernet-level (VLAN) access interface to TIED resources.

• Milestone: TIED:Support running federated experiments.

  5 months late (09/30/09)

  Demonstrate and support running federated experiments by owner(s) outside the development team by the end of year 1.

• Milestone: ENTGENI: Collaborate with O&M and Security teams

  5 months late (10/01/09)

  Collaborate with GENI O&M and Security teams on enterprise network topics. This work will be part of working group participation. Ongoing work for months 1-12.

• Milestone: ENTGENI: Integrate EntGENI with GENI virtual ethernets

  5 months late (10/01/09)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Integrate Enterprise GENI Stanford deployment with the GENI Spiral 1 switched Ethernet VLAN infrastructure assuming tunneling to Internet2.

• Milestone: ORCABEN: 1g Make a working and tested prototype of BEN and GENI available for limited external research

  5 months late (10/01/09)

  1g

  Make a working and tested prototype of BEN and GENI (substrate and control framework) available for limited external research

  Only to researchers who have access to NLR either directly or in the form of tunnels.

• Milestone: PlanetLab: make CF available for use by students

  5 months late (10/01/09)

  Make the GENI control framework available to universities for use in student projects and coursework.

• Milestone: PlanetLab: open integrated cluster testbed to users

  5 months late (10/01/09)

  Open testbed to GENI researchers, to utilize aggregates and components in combination to complete experiments, and maintain use records.

• Milestone: Quilt: S2.a Form Workshop Committee

  5 months late (10/01/09)

• Milestone: WiMAX: 1d First release v1.0 of GENI base station node software

  5 months late (10/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  d) Implement and document a first release (v1.0) of Linux-based GENI base station node (GBSN) software. (12mo)

• Milestone: WiMAX: 1f VLAN connections to the GENI backbone network

  5 months late (10/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  f) Provide VLAN connections from your base station testbed to the GENI backbone network on NLR (via MAGPI East in Philadelphia). (9-12mo)

• Milestone: GENI4YR: Deliver Use-case Scenario(s)

  5 months late (10/15/09)

  Provide use-case scenarios (at least 1) of an experiment identified for spiral-1, this will include the specifics of one of the GENI prototype control frameworks and is limited to the substrate resources in that cluster.

• Milestone: SPP: Component Manager ICD

  5 months late (10/15/09)

  Delivery of SPP component manager interface documentation to GPO

• Milestone: SPP: Limited research available

  5 months late (10/15/09)

  Make initial SPP deployment available for limited external research

• Milestone: SPP: User Web Site

  5 months late (10/15/09)

  Develop web site for user documentation and feedback.

• Milestone: BGPMux: S2.a Security review 1

  4 months late (11/01/09)

  - Provide project draft input to GENI Spiral Security Review 1.

• Milestone: DOME: S2.k POC to GENI response team

  4 months late (11/01/09)

  Provide POC to GENI Prototype Response and Escalation team. (11/1/09)

• Milestone: DSL: S2.a Messaging app on CyrusDSL available to FB community

  4 months late (11/01/09)

  Launch the DSL messaging/application to the public FB community (CyrusDSL)

• Milestone: ORBIT: S2.j POC to GENI response team

  4 months late (11/01/09)

  Provide POC to GENI Prototype Response and Escalation team. (11/1/09)

• Milestone: ORCABEN: S2.m POC to GENI response team

  4 months late (11/01/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Provide POC to GENI Prototype Response and Escalation team. (11/1/09)

• Milestone: ViSE: S2.n POC to GENI response team

  4 months late (11/01/09)

  Provide POC to GENI Prototype Response and Escalation team. (11/1/09)

• Milestone: ViSE: S2.o POC to GENI security team

  4 months late (11/01/09)

  Provide POC to Security team and provide input for security review in Spiral 2. (11/1/09-3/1/10)

• Milestone: WiMAX: S2.l POC to GENI response team

  4 months late (11/01/09)

  Provide POC to GENI Prototype Response and Escalation team. (11/1/09)

• Milestone: CRON: S2.a

  4 months late (11/06/09)

  Identify responsible person who can respond to queries from GENI Operations and take action in case of an incident.

• Milestone: BGPMux: S2.b Initial definition of reference experiment

  4 months late (11/15/09)

  Publish initial definition of reference experiment. For instance, an experiment could be one that used ProtoGENI to acquire BGP-Muxes, OpenFlow? switches, and EmuLab? nodes at Georgia Tech and Univ. Wisconsin interconnected by a GENI backbone and used the BGP-Mux to control Internet route accessibility at the two campuses.

• Milestone: SPP: S2.d demo6

  4 months late (11/15/09)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  Perform demonstrations at GEC6. 11/15/09

• Milestone: COGRADIO: S2.a Roadmap for stand-alone and infrastructure-class platforms

  4 months late (11/16/09)

  Define and maintain a roadmap for stand-alone and infrastructure-class cognitive radio platforms, utilizing input from white paper produced by "A Mobile Programmable Radio Substrate for Any-layer Measurement and Experimentation” project when it becomes available. (starting 11/16/09, GEC6)

• Milestone: OKGEMS: S2.a Plan to integrate sensor nodes

  4 months late (11/16/09)

  Complete a detailed technical plan for integrating sensor nodes, in both laboratory and field settings, into GENI using the ORCA control framework, for sharing by multiple researchers. (11/16/09, GEC6)

• Milestone: ORBIT: S2.a Cluster plan for VLANs between testbeds

  4 months late (11/16/09)

  Work with GPO and WiMAX and cognitive radio projects in cluster to complete a plan for the setup of VLANs between testbeds, to be carried by Internet 2 (or NLR) backbone network between the testbeds. (11/16/09, GEC6)

• Milestone: ORCABEN: S2.h BEN testbed access by GENI users

  4 months late (11/16/09)

  Make BEN testbed available to GENI users from other projects, and early GENI users as authorized. (11/16/09-9/30/10)

• Milestone: UMLPEN: S2.a Develop plan to deploy PEN

  4 months late (11/16/09)

  Develop plan to deploy PEN SW elements on additional select platforms in GENI prototype infrastructure to support external research. (11/16/09, GEC6)

• Milestone: WiMAX: S2.a Outdoor WiMAX available to GENI users

  4 months late (11/16/09)

  Release outdoor WiMAX/ORBIT experimental capabilities to end-users, initially with 2-3 static WiMAX Clients. (11/16/09, GEC6)

• Milestone: WiMAX: S2.b Cluster plan for VLANs between testbeds

  4 months late (11/16/09)

  Work with GPO and other projects in cluster to complete a plan for the setup of VLANs between testbeds, to be carried by Internet 2 (or NLR) backbone network between the testbeds. (11/16/09, GEC6)

• Milestone: CMU Lab:S2.a Automate VPN management

  3 months late (11/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Tasks: • Develop software to create, allocate keys into, start/stop, and deallocate OpenVPN configurations • Integrate the software into emulab (conceptually lightly similar to snmpit+cisco) • Integrate the software into ProtoGENI • Develop a working model for how layer 2 VPNs should be configured beyond what OpenVPN handles (protocol layering, avoiding collisions with existing networks on hosts) • Define Database and rspec designs to encapsulate the above • Define ways to configure bridging of these VPNs

  This offers: • Layer 2 or Layer 3 VPNs between any hosts regardless of if they can directly communicate (provided a chain of configurable systems between them that can communicate exists) • VPNs to be considered more lightweight and isolated rather than shared

• Milestone: Hive: S2.a

  3 months late (11/30/09)

  Selection of control framework for initial deployment of Hive Mind security software

• Milestone: LAMP: S2.a Requirements and design doc

  3 months late (11/30/09)

  Document describing basic ProtoGENI metrics and the mechanisms via which the core model can be extended.

• Milestone: OFNOX: S2.a Publish NOX feature list

  3 months late (11/30/09)

  Publish NOX feature list with technical descriptions for OpenFlow? 1.0 releases planned for January and June 2010.

• Milestone: PGTools: S2.a V1.0 release of experimenter tools

  3 months late (12/01/09)

  V1.0 release of ProtoGENI experimenter tools.

  Ability to create and run experiments using a web interface. Components (resources) are user-selected and come from multiple ProtoGENI aggregates. Components include nodes and network links/tunnels. Experiment swapin and swapout supported.

• Milestone: RAVEN: S2.a continuous

  3 months late (12/01/09)

  a) Support continuous operation of GENI. Raven/Stork repository must be available for use by experimenters using GENI. (Dec 1, 2009)

• Milestone: KGENI: S2.a PoC for Response and Escalation

  3 months late (12/11/09)

  Identify responsible person who can respond to queries from GENI Operations and take action in case of an incident

• Milestone: BGPMux: S2.d Release 1 integration s/w

  3 months late (12/15/09)

  BGP-Mux will support basic tunnel between BGP Mux and VINI node at Georgia Tech. Aggregate manager extension to check a resource request against available resources.

• Milestone: ProtoGENI.S2.b: Integration Release 2

  3 months late (12/15/09)

  GENI Software Integration Release 1.

• Milestone: Quilt: S2.b Convene Planning Committee

  3 months late (12/15/09)

• Milestone: CRON: S2.b

  3 months late (12/18/09)

  Establish 10Gbps connection from LONI to ProtoGENI through Internet 2.

• Milestone: KGENI: S2.b Network Selected

  2 months late (12/30/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Network (NLR or I2) selected for connection between ETRI Korea and IU

• Milestone: Attrib: S2.a

  2 months late (12/31/09)

  Outline of report including description and background of problem of attribution in GENI.

• Milestone: GpENI: S2.c tools

  2 months late (12/31/09)

  Identify user helper tools developed within other GENI projects and integrate them into GpENI. Document in a short technical note the list of tools that were integrated (and how), and the list of tools that were not (and why). 12/31/09

• Milestone: GpENI: S2.e VINI

  2 months late (12/31/09)

  Collaborate with Princeton on the programmable router feature using VINI/Quagga; document in a short technical note. 12/31/09

• Milestone: GpENI: S2.f MAX

  2 months late (12/31/09)

  Investigate options for interconnecting MAX with GpENI; document in a short technical note. 12/31/09

• Milestone: LAMP: S2.b Prospectus on integration of perfSONAR with other monitoring efforts

  2 months late (12/31/09)

  Prospectus will include proposal for a common schema for measurement data and metadata.

• Milestone: MAX: S2.b NetFPGA as a GENI Resource Plan

  2 months late (12/31/09)

  Develop a plan to enable the NetFPGA systems to be generally available as part of a GENI slice/sliver and topology provisioning. This will include a review of the work by ProtoGeni? and others on the development of NetFPGA virtualization technologies.

• Milestone: MAX: S2.c DRAGON Aggregate Manager Enhancement Design

  2 months late (12/31/09)

  Complete design for the enhancements to the DRAGON Aggregate Manager. This will include enhancement of the current Aggregate Manager to enable user specification of a topology which includes both compute and network resources. The DRAGON Aggregate Manager will be responsible for authorization and resource verification (topology computation) in advance of resource provisioning in accordance with the user specified topology descriptions. This work will extend the previous DRAGON Aggregate Manager to provide the basis for an extensible control and provisioning framework.

• Milestone: MAX: S2.d Common Control Framework Design

  2 months late (12/31/09)

  Work with GENI community to develop an approach for a common control framework and/or other mechanisms to allow interoperation between GENI facilities. Develop initial documentation of this plan in sufficient detail for the various clusters to take implementation action for their respective control frameworks.

• Milestone: MAX: S2.e User Support

  2 months late (12/31/09)

  Work with and support interested users on use of the DRAGON GENI Facility.

• Milestone: MAX: S2.f DRAGON Aggregate Manager Documentation

  2 months late (12/31/09)

  Update the design and installation documents for the DRAGON Aggregate Manager. Provide updated open source software distribution of GENI DRAGON Aggregate Manager and other related software.

• Milestone: NETKARMA: S2.b webpage

  2 months late (12/31/09)

  Set up project web page

• Milestone: NETKARMA: S2.c identify tools

  2 months late (12/31/09)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Establish connections with relevant experimental tools projects

  Identify Year 2 projects with which to integrate, in consultation with the GPO. The scope of the integration work will be on par with the level of effort integrating with RAVEN and GUSH.

• Milestone: OppWireless: S2.a

  2 months late (12/31/09)

  Detailed description of experiment to be performed on ProtoGENI/CMU wireless emulator aggregate including resources used, instrumentation, etc. Solicit comments from the GPO, ProtoGENI project, CMU wireless emulator project, and other interested parties.

• Milestone: PGTools: S2.b Initial user guide

  2 months late (12/31/09)

  Initial user guide for ProtoGENI experimenter tools

• Milestone: ProtoGENI.S2.c: Evaluate ProtoGENI design

  2 months late (12/31/09)

  Evaluate ProtoGENI design based on forthcoming control framework requirements document. (within 2 months of requirements document being released)

• Milestone: RAVEN: S2.b GUSH integration

  2 months late (12/31/09)

  b) Integration with GUSH. Integrate provisioning into the GUSH set of experimenter tools. (Dec. 31, 2009)

• Milestone: RAVEN: S2.c two cluster plan

  2 months late (12/31/09)

  c) Plan for using Raven as a provisioning service for one other cluster. (Dec. 31, 2009)

• Milestone: SPP: S2.c userdoc

  2 months late (12/31/09)

  Develop user documentation and tutorial material. 12/31/09

• Milestone: SPP: S2.m code

  2 months late (12/31/09)

  Provide sample applications using SPP fast paths and provide complete, documented source code that researchers can use as basis for their own applications. Two base applications will be completed. These will include an IPv4 forwarder and a simple virtual-circuit application. 12/31/09

• Milestone: BGPMux: S2.e BGP Mux in GaTech syllabus

  2 months late (01/01/10)

  - Release “integration of BGP Mux as a tool for learning about BGP” into the undergraduate syllabus at GaTech?. Milestone here is release of the syllabus.

• Milestone: PLFED: S2.a demo federated slice

  2 months late (01/01/10)

  Create federated slice using SFA machinery across PLC, PLE, and PLJ. Assume minimal peering policy based on sliver count. Users interact with system using SFI command-line tool. Assume pair-wise peering among these three organizations

• Milestone: MillionNodeGeni: S2.b End hosts with intermitted connectivity

  2 months late (01/04/10)

  b) Operation with end-hosts that have intermittent connectivity and/or are behind firewalls and NATs.

• Milestone: DSL: S2.b Plan for DSL/FB applications on ProtoGENI

  2 months late (01/15/10)

  Document describing design and operation of the system running on ProtoGENI. Document should include expected ProtoGENI resource usage (computing, network, storage), availability targets for the application and approach to meeting them, instrumentation plans and privacy plans.

• Milestone: IMF: S2.a Initial architecture-

  2 months late (01/20/10)

  50%

  Closed tickets:

  1

  Active tickets:

  1

  Develop and document an initial architectural view of all the components required in this project to realize cross-layer experiments using SILO, consistent with the Cluster D roadmap, identifying and defining at the data‐model level all new interfaces that will come to exist, identifying which of these will require new protocols to realize, and identifying what existing protocols (or planned to be developed in some other projects) will be leveraged, and review with other projects at GEC. (11/16/09, GEC6)

  Changed to 01/20/10, per note from Rudra Dutta on 1/6/10;

  "As you probably know, all this time our SRO has been negotiating language on the contract, so the contract never got signed. As of Dec 23rd, I understand that they have reached an agreement with BBN on how it should read. It is ready to be signed.

  There is one hitch - one of the milestones was due on Nov 16 i.e. GEC6, and it can no longer read that way in the contract. In reality, as you know, we have been working on it and one PI and one student attended GEC6, and made the presentation. But for the purpose of the language of the contract, we have to change it to something after the start date of the contract, which we need to agree on.

  Since it has very little reality, I propose we use some arbitrary date. I suggest Jan 20th, 2010."

  And approved by Henry Yeh on 1/6/10

• Milestone: PGINTEGRN: S2.c Reference Component Manager

  1 month late (01/29/10)

  Deliver initial reference component manager based on API version 2. This component manager will be designed to have a replaceable back-end, so that integration partners do not need to implement front-end RPC, authentication, etc. This will be accompanied by a document giving guidance to projects using it to implement their own CM.

• Milestone: GTools: S2.b Initial user guide

  1 month late (01/31/10)

  Initial user guide for ProtoGENI experimenter tools.

• Milestone: OFGT: S2.a1 Select vendors

  1 month late (01/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Select vendors for on-campus hardware evaluations.

• Milestone: OFNOX: S2.b Release NOX supporting OpenFlow 1.0

  1 month late (01/31/10)

  Release software that supports OpenFlow? 1.0. In GENI environments. Provide support and security contacts for the software to the GPO.

• Milestone: OFNOX: S2.c Initial rough NOX API documentation

  1 month late (01/31/10)

  Provide initial rough NOX API documentation for OF development team review.

• Milestone: OFPR: S2.a1 Select vendors

  1 month late (01/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Select vendors for on-campus hardware evaluations.

• Milestone: OnTime: S2.c: Platform setup for OnTimeMeasure-GENI

  1 month late (01/31/10)

  Platform setup for “OnTimeMeasure-GENI” Version 1.0 software development, testing and deployment.

  - Multi-federation measurement testbed will be setup involving 4-sites on OARnet backbone, and relevant ProtoGENI and GMOC measurement resources (e.g. instrumented-nodes, databases, registry entries) - Scripts and documentation will be developed/configured/deployed for accessing ProtoGENI and GMOC resources, as well as internal project task tracking, source version control management, and bug-tracking

• Milestone: COGRADIO: S2.b Phase 1 radio card for stand-alone system

  1 month late (02/01/10)

  Redesign, manufacturing, testing and integration of frequency-extended Phase 1 radio card for use in stand-alone cognitive radio system. (2/1/10)

• Milestone: DSL: S2.c Launch suite of games based on the DSL FB kernel

  1 month late (02/01/10)

  Launch suite of online social networking/Facebook games based on the DSL Facebook Kernel (CyrusDSL). Enhance existing games for usability.

• Milestone: IMF: S2.d First component architecture

  1 month late (02/01/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Develop and document a v1.0 architectural view of all the components required in this project to realize cross-layer experiments using SILO. (2/1/10)

• Milestone: ORCAAUG: S2.a Rel 2.1_2 ORCA code to projects

  1 month late (02/01/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Implement and provide release 2.1 of ORCA code to other Cluster D projects, including the following features: (2/1/10) 1) Computational substrate 1: Substrate support. Additional drivers/handlers for new types of substrate. Integration of Eucalyptus. 2) Computational substrate ontology 1: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Initial ontology for edge computational substrates. 3) Ontology integration 1: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Integration of ontology resource handling mechanisms into ORCA core. 4) Policy development 1: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Development of resource provisioning policies based on ontologies. 5) Actor registry/trust brokering 1: Resource discovery. Enable dynamic resource discovery. Single registry of actors, including brokers. Also simplifies trust setup. 6) Initial Shibboleth integration 1: Identity management. Establish use of identity management system to authenticate principals and portals. Integrate with Shibboleth to provide portal-level authentication. 7) Note: Additional release 2.1 features will be provided by ORCA/BEN project.

• Milestone: ORCABEN: S2.a Rel 2.1_1 ORCA code to projects

  1 month late (02/01/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Implement and provide release 2.1 of ORCA code to other Cluster D projects, including the following features: (2/1/10) 1) Better packaging 1: Simplified installation, config script auto-configuration, simple usability extensions, simplified certificate management. 2) Keymaster 1: Keymaster allows a slice controller to bind to its instantiated slivers securely, e.g., to load experiment code images into a sliver, and/or to configure and launch the sliver. 3) Lease feature extensions 1: Enabling simple non-reverting cancellations of leases prior to their expiration. 4) External experiment control 1: Generic XML-RPC interface for use by experiment control tools written in multiple languages. This interface supports a subset of ORCA resource reservation capabilities modeled after the ProtoGENI XML-RPC interface and enables (possibly modified) Gush to be ORCA experiment control tool. 5) Backbone integration 1a: Integration with dynamic provisioning mechanisms of major national research networks. Integration with Sherpa CGI. 6) Backbone integration 1b: Integration with dynamic provisioning mechanisms of major national research networks. Integration with Internet2 IDC (also enables Dragon) 7) Note: Additional release 2.1 features will be provided by ORCA augmentation project.

• Milestone: Hive: S2.b

  1 month late (02/05/10)

  Develop design specification for devices using security framework and means of mapping Battelle’s distributed sensor algorithms to GENI requirements. Document to be reviewed by GPO and selected control framework.

• Milestone: LAMP: S2.c Updated prospectus

  3 weeks late (02/19/10)

  Solicit comments on initial version of prospectus from GPO, other measurement projects, ProtoGENI project, and other interested parties. Update prospectus based on comments and any new information gathered since initial version of prospectus.

• Milestone: OppWireless: S2.b

  3 weeks late (02/19/10)

  Report on experiences including ease of access of testbed, usability of tools, etc. Early experiments may be based on a limited implementation of a pigeon network protocol.

• Milestone: PGINTEGRN: S2.d Experimenters guide

  2 weeks late (02/26/10)

  Release a guide for experimenters using ProtoGENI (expanded version of existing tutorial).

• Milestone: CMU Lab:S2.b Define RSpecs for wireless channels

  2 weeks late (02/28/10)

  Define RSpecs for wireless channels. These RSpecs should make it possible to get access to the interesting features of both Homenet (where channels cannot be controlled) and the Emulator (where channels can be controlled). The definition will be based on the extensible RSpec model under development at Utah.

• Milestone: DIGOBREG: S2.c Complete Clearinghouse impl. & federate w/ ProtoGENI

  2 weeks late (02/28/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Complete development of the GENI Federated Clearinghouse (GFC) and federate with ProtoGENI clearinghouse. The GFC would be made available to ProtoGENI and other clusters to search and discover the federated information.

• Milestone: DSL: S2.d Dualism support for email clients

  2 weeks late (02/28/10)

  This feature will allow DSL/FB users to utilize Facebook for their SMTP email traffic. This indicates that their regular email traffic will be routed through GENI.

• Milestone: DSL: S2.e DSL/FB application ported to ProtoGENI

  2 weeks late (02/28/10)

  The DSL/Facebook application has been ported to ProtoGENI and is being used by select users at UC Davis.

• Milestone: ProtoGENI.S2.d: GENI Spiral Security Review 2 input

  2 weeks late (02/28/10)

  Provide project draft input to GENI Spiral Security Review 2

• Milestone: BGPMux: S2.f Security review 2

  1 week late (03/01/10)

  Provide project draft input to GENI Spiral Security Review 2.

• Milestone: IMF: S2.e Initial IMF software

  1 week late (03/01/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Develop a skeleton version of the IMF software module that interfaces with the UMF to gather measurements from the optical substrate, based upon the UMF interfaces provided by the ERM project. (3/1/10)

• Milestone: ORBIT: S2.k POC to GENI security team

  1 week late (03/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (11/1/09-3/1/10)

• Milestone: ORCAAUG: S2.j First draft of the ontology schema

  1 week late (03/01/10)

  In cooperation with the ORBIT project, based upon the results of the first ontology workshop, create a v0.1 draft of the ontology schema. (3/1/10)

• Milestone: ORCABEN: S2.n POC to GENI security team

  1 week late (03/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (11/1/09-3/1/10)

• Milestone: WIMXRG: S2.a Develop Install/Ops Guidelines

  1 week late (03/01/10)

• Milestone: WiMAX: S2.m POC to GENI security team

  1 week late (03/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (11/1/09-3/1/10)

• Milestone: ERM: S2.b Demo software interface from UMF to embedded measurement subsystem

  1 week late (03/04/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Establish and demonstrate a working software interface between the UMF and at least one subsystem that is capable of embedded physical layer measurements, such as bit-error rate measurement or optical power monitoring. This experimental demonstration will use the interface specifications developed in year-1 (e.g. use the networking management protocol: SNMP). [3/4/10 (6 months).]

• Milestone: CRON: S2.c

  6 days late (03/05/10)

  Establishing a 10Gbps connection from CRON to ProtoGENI through LONI and Internet2

• Milestone: DSL: S2.f Updated plans for DSL/FB apps

  6 days late (03/05/10)

  Updates to document in Milestone S2.b. Plans must be reviewed and approved by the GPO and ProtoGENI before public launch of DSL/FB apps on ProtoGENI.

• Milestone: MillionNodeGeni: S2.c Implement example applications

  6 days late (03/05/10)

  c) Implement example applications on the VM such as Chord and a web redirection service.

• Milestone: ABAC: S2.b

  Due in 17 hours (03/12/10)

  A document or Wiki page describing the design and APIs of the ABAC prototype for ProtoGENI.

• Milestone: Attrib: S2.b

  Due in 17 hours (03/12/10)

  Report updated with several example scenarios, including possibly one involving privacy as a motivation. The scenarios will revolve around both situations arising in GENI and in the next generation Internet.

• Milestone: CRON: S2.d

  Due in 17 hours (03/12/10)

  Rspec definition based on ProtoGENI Rspecs.

• Milestone: ExptsSec: S2.b

  Due in 17 hours (03/12/10)

  Run experiment designed in Milestone 1 on ProtoGENI/Emulab. Identify potential security vulnerabilities. Develop revised experimentation plans to validate/exploit potential vulnerabilities. Interact with the ProtoGENI PI to get feedback on the potential vulnerabilities and the experiment plans. Deliver software/scripts/documentation needed to repeat experiment.

• Milestone: KGENI: S2.c ETRI-IU Connection Live

  Due in 17 hours (03/12/10)

  The two institutions are connected and GMOC-dvNOC interoperability trials begin.

• Milestone: KGENI: S2.d Playbook Version 1.0

  Due in 17 hours (03/12/10)

  Playbook for international research projects that want to connect with GENI at Layers 2 & 3

• Milestone: PGINTEGRN: S2.e Service implementer's guide

  Due in 17 hours (03/12/10)

  Release a guide for projects implementing services in ProtoGENI slices, such as monitoring services, about how best to use the ProtoGENI APIs to hook in their services.

• Milestone: PGTools: S2.c V1.1 release of experimenter tools

  Due in 17 hours (03/12/10)

  V1.1 release of ProtoGENI experimenter tools

  Release includes integration of Slice Embedding Service with resource mapper, allowing use of arbitrary topologies to be instantiated with frontend. Also includes complete client side configuration on ProtoGENI components of popular Emulab features such as tarballs, RPMs, network interface configuration, routing configuration, and user accounts for all project members.

• Milestone: SPP: S2.e demo7

  Due in 4 days (03/15/10)

  Perform demonstrations at GEC7. 3/15/10

• Milestone: SPP: S2.g tutorial7

  Due in 4 days (03/15/10)

  Conduct user tutorials at GEC7. 3/15/10

• Milestone: COGRADIO: S2.c Integrate stand-alone platform

  Due in 5 days (03/16/10)

  Integration of Phase I radio card with off-the-shelf components to develop a stand-alone cognitive radio platform; validation with basic tests; demonstration. (3/16/10, GEC7)

• Milestone: DICLOUD: S2.e Demo archiving sensor data

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demo 1: Archiving of sensor data on a storage service. We will demonstrate an early version of our handlers and our simple FCFS Clearinghouse policy, which will allow a user to lease servers from EC2 and storage volumes from EBS (as an aggregate). We will highlight the addition of storage by uploading sensor data (from CASA’s Oklahoma testbed) to EBS through an EC2 server. The functions will be exposed by extending ViSE’s web portal (3/16/10, GEC7).

• Milestone: DOME: S2.c Control VLAN connections

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstrate control of VLAN connections between UMass endpoint server and backbone network, contingent upon availability of VLAN transport service by backbone network. (3/16/10, GEC7)

• Milestone: IGENI: S2.c Integrate iGENI with ORCA

  Due in 5 days (03/16/10)

  Integrate the prototype iGENI infrastructure with the ORCA control framework, utilizing ORCA’s extended features and any necessary iGENI drivers, and demonstrate the setup of L2 (VLAN) connections between L2 transport services from two or more connected networks. (3/16/10, GEC7)

• Milestone: IMF: S2.f Integrate the IMF and UMF with BEN

  Due in 5 days (03/16/10)

  Integrate the IMF and UMF(provided by the ERM project) with devices in BEN that include performance monitoring capabilities, and demonstrate gathering measurements from these devices. (3/16/10, GEC7)

• Milestone: KANSEI: S2.d Extend researcher portal for use with Kansei and Neteye

  Due in 5 days (03/16/10)

  Extend KanseiGenie Researcher Portal to Support Use with either Kansei and NetEye? (3/16/10, GEC7) • Extensions for interaction with ORCA service manager, federated scheduling, and network stitching • OSU and WSU

• Milestone: KANSEI: S2.e Bring up NetEye testbed at WSU

  Due in 5 days (03/16/10)

  Bring up additional KanseiGenie testbed at WSU (NetEye?), utilizing v1.0 software package. (3/16/10, GEC7) • Develop new hierarchical AM/CM for KanseiGenie Site Authority to accommodate a new Fedora/laptop substrate • Port Kansei Genie user services to accommodate new substrate • Integrate with ORCA and instantiate broker within RENCI clearinghouse • WSU

• Milestone: KANSEI: S2.f Connections from Kansei and NetEye to Internet2

  Due in 5 days (03/16/10)

  Demonstrate connections from Kansei and NetEye? testbeds to Internet2 network; contingent upon availability and additional support of potential cost associated with VLAN transport service by backbone network, demonstrate VLAN connections from Kansei and NetEye? to backbone network. (3/16/10, GEC7)

• Milestone: LEARN: S2.c Establish ORCA framework

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Establish local ORCA control framework, for eventual integration with LEARN network. (3/16/10, GEC7)

• Milestone: LEARN: S2.i Implement and integrate Measurement Handler

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Collaborate with the ERM project to complete specification of the data file format for transfer of measurement data between the Measurement Handler software and the Integrated Measurements Framework; implement the Measurement Handler software to make optical measurements using Infinera Digital Transport Nodes (DTNs); integrate the Measurement Handler software with the Integrated Measurements Framework provided by the ERM project; demonstrate the Measurement Handler using DTNs, and dark fiber resources from LEARN. (3/16/10, GEC7)

  Wording changed on 12/14/09:

  demonstrate the Measurement Handler using DTNs that are part of BEN (at RENCI).

• Milestone: OKGEMS: S2.c Integrate lab sensor nodes

  Due in 5 days (03/16/10)

  Integrate a small set of sensor nodes (e.g. 20 nodes) in a laboratory setting into GENI, using a locally-deployed ORCA control framework, including an experiment control portal, and allow access by local researchers. (3/16/10, GEC7)

• Milestone: ORBIT: S2.b Extend OMF for experiments with multiple testbeds

  Due in 5 days (03/16/10)

  Extend OMF interfaces and software to support experiments which concurrently use resources from more than one testbed. Include integration with experiment control and measurement, and provide for multiple concurrent slices. Introduce a ticket-based resource authentication mechanism, compatible with evolving GENI control framework structures. (3/16/10, GEC7)

• Milestone: ORBIT: S2.c Extend OMF for experiments driven by context

  Due in 5 days (03/16/10)

  Extend OMF in mobile environments to support experimentation driven by context, particularly location information, such as passing a specific location or detecting a new neighbor. (3/16/10, GEC7)

• Milestone: ORBIT: S2.d Federate cluster testbeds

  Due in 5 days (03/16/10)

  Work with WiMAX and cognitive radio projects, to integrate their testbeds (utilizing OMF interfaces and software), into your OMF operating environment, as federated testbeds. (3/16/10, GEC7)

• Milestone: ORBIT: S2.e Demo VLAN connection to backbone

  Due in 5 days (03/16/10)

  Demonstrate control of VLAN connections from your testbed to backbone network, contingent upon availability of a managed end-to-end VLAN transport service (e.g., Internet2 DCN) by backbone network. (3/16/10, GEC7)

• Milestone: ORCAAUG: S2.e Single registry of brokers

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstrate single registry of brokers. (3/16/10, GEC7)

• Milestone: ORCAAUG: S2.g Broker authorization based on attributes from Shibboleth

  Due in 5 days (03/16/10)

  Demonstrate a trivial ticket broker authorization policy based on existing attributes from local Shibboleth provider (IdP); user authenticates to the broker’s container. (3/16/10, GEC7)

• Milestone: ORCAAUG: S2.h Eucalyptus VM provisioning

  Due in 5 days (03/16/10)

  With Eucalyptus, demonstrate VM provisioning from site-approved images. (3/16/10, GEC7)

• Milestone: ORCAAUG: S2.k Second ontology workshop

  Due in 5 days (03/16/10)

  In cooperation with the ORBIT project, hold the second ontology workshop, to review the v0.1 draft document of the ontology schema. (3/16/10, GEC7)

• Milestone: ORCABEN: S2.i BEN testbed access from remote sites

  Due in 5 days (03/16/10)

  Implement access to BEN testbed from experiment control tools and service manager(s) that are located at a site remote from your testbed, and demonstrate. (3/16/10, GEC7)

• Milestone: ORCABEN: S2.j VLANs from BEN to backbone

  Due in 5 days (03/16/10)

  Demonstrate control of VLAN connections from BEN testbed to backbone network, contingent upon availability of VLAN transport service by backbone network. (3/16/10, GEC7)

• Milestone: PrimoGENI: S2.c: Demonstration

  Due in 5 days (03/16/10)

  Demonstrate initial PrimoGENI functionality at GEC 7.

• Milestone: UMLPEN: S2.b Implement clock synchronization

  Due in 5 days (03/16/10)

  Implement clock synchronization on network processor based NICs to support high fidelity measurement. (3/16/10, GEC7)

• Milestone: UMLPEN: S2.c Enhance PEN virtual router templates and set-up scripts

  Due in 5 days (03/16/10)

  Enhance PEN virtual router templates and set-up scripts as elements of a component manager or user-help tools within a specified GENI control framework. (3/16/10, GEC7)

• Milestone: ViSE: S2.f Installation of cameras

  Due in 5 days (03/16/10)

  Installation and virtualization of camera devices on CSB and MA1 tower nodes. (3/16/10, GEC7)

• Milestone: ViSE: S2.g Integration of virtualization

  Due in 5 days (03/16/10)

  [M8] Integration of virtualization/slivering in testbed. (3/16/10, GEC7)

• Milestone: ViSE: S2.h Import extended ORCA v2.1

  Due in 5 days (03/16/10)

  [M12] Update experiment control framework (ECF), based upon updated reference software, provided by RENCI/Duke group at 2/1/10, and integrate new features as needed. (3/16/10, GEC7)

• Milestone: ViSE: S2.i Demo control of VLAN connections

  Due in 5 days (03/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstrate control of VLAN connections from ViSE testbed to backbone network, contingent upon availability of transport by backbone network. (3/16/10, GEC7)

• Milestone: WiMAX: S2.c Demo main base station functions

  Due in 5 days (03/16/10)

  Implement and demo main functionality of base station in your testbed (multiple virtual slices, programmable layers 2,3, GMC-like control interface). (3/16/10, GEC7)

• Milestone: WiMAX: S2.d Demo VLAN connection to backbone

  Due in 5 days (03/16/10)

  Demonstrate control of VLAN connections from your testbed to backbone network, contingent upon availability of a managed end-to-end VLAN transport service (e.g., Internet2 DCN) by backbone network. (3/16/10, GEC7)

• Milestone: WiMAX: S2.e Federate with other cluster testbeds

  Due in 5 days (03/16/10)

  Work with the ORBIT project, to integrate your testbed with their testbed(s) (all utilizing OMF interfaces and software) to from an environment of federated wireless testbeds, and demo main functionality of your base station in this environment. (3/16/10, GEC7)

• Milestone: GENICLOUD S2.a Demonstration at GEC7

  Due in 1 week (03/19/10)

  Demonstrate the ability to configure slices on a Eucalyptus cluster using the SFA command-line tools. The Eucalyptus Aggregate Manager will be functional, but will only support the "lite" federation model and will operate on a basic Eucalyptus RSpec resembling the PlanetLab RSpec. The Aggregate Manager will be deployed on the HP Labs Eucalyptus cluster in Palo Alto. Deliver the software used at the demo along with documentation (e.g. a wiki page).

• Milestone: LAMP: S2.d Demonstration of perfSONAR on ProtoGENI

  Due in 1 week (03/19/10)

  Demonstration of perfSONAR on ProtoGENI at GEC.

• Milestone: OnTime: S2.d: Demo at GEC

  Due in 1 week (03/19/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstration of basic OnTimeMeasure-GENI functionality on ProtoGENI.

• Milestone: PGTools: S2.d Demonstration

  Due in 1 week (03/19/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstration of v1.1 ProtoGENI experimenter tools at GEC

• Milestone: S3MONITOR: S2.c Demonstration

  Due in 1 week (03/19/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstration of measurement system at GEC.

• Milestone: OppWireless: S2.c

  Due in 2 weeks (03/22/10)

  Updated experiment design document based on comments on earlier version and based on experiences with early experiments.

• Milestone: CompSec: S2.b

  Due in 2 weeks (03/26/10)

  Catalog of GENI assets, value of assets and risks to assets. Focus on asset identification and valuation. Circulate report to stakeholders for comments.

• Milestone: SECUREUPDATES: S2.d client lib demo

  Due in 2 weeks (03/28/10)

  Demonstrate client library implementation that protects against replay and freeze attacks for Linux.

• Milestone: SECUREUPDATES: S2.e repo lib demo

  Due in 2 weeks (03/28/10)

  Demonstrate repository library implementation that protects against replay and freeze attacks.

• Milestone: CMU Lab:S2.c IRB approval for broader Homenet user access

  Due in 3 weeks (03/30/10)

  IRB approval is required to give users (both CMU users using CMUlab and non-CMU users through federation) access to Homenet nodes, since they nodes are placed in residential areas and can be used to sniff and disrupt regular user traffic. Will work with the CMU IRB to define how and under what constraints Homenet can be used by non-CMU users. Will report back and collaborate with the GENI community on solving this problem in a general sense.

• Milestone: GUSH: S2.d GUI 0.1

  Due in 3 weeks (03/30/10)

  d) Nebula (graphical user interface for Gush) v0.1 release. March 30, 2010

• Milestone: GMOC: S2.b Prototype manual emergency shutdown

  Due in 3 weeks (03/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Prototype manual emergency shutdown. Implement initial emergency shutdown process with control framework and exemplar projects. This process will be based on the emergency stop documentation from the GMOC’s spiral 1 work.

• Milestone: GMOC: S2.c Prototype slice view of operational data sharing

  Due in 3 weeks (03/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Prototype slice view of operational data sharing. Develop a per-slice operational view capability. View should include topology of a specified slice, including information about components being used, active operational status of slivers and components, and utilization data for slice traffic. This prototype will be enhanced to use data from real exemplar projects if appropriate data is available.

• Milestone: GpENI: S2.g deploy DCN in GpENI

  Due in 3 weeks (03/31/10)

  Deploy DCN within GpENI, based on GPN, GPO and Internet2 feedback to the above-mentioned report. 03/31/10

• Milestone: GpENI: S2.h 2nd Ciena switch

  Due in 3 weeks (03/31/10)

  Purchase second Ciena switch and integrate into GpENI. 03/31/10

• Milestone: GpENI: S2.i web-portal

  Due in 3 weeks (03/31/10)

  Create an integrated web-portal for MyPLC and MyVINI within GpENI. 03/31/10

• Milestone: LAMP: S2.e V1.0 of perfSONAR on ProtoGENI

  Due in 3 weeks (03/31/10)

  Prototype perfSONAR deployment on ProtoGENI infrastructure. Deliver software, documentation and user manual.

• Milestone: MAX: S2.g NetFPGA as a GENI Resource Implementation

  Due in 3 weeks (03/31/10)

  Implement the results of the plan from milestone S2.a. The expected result is for the NetFPGA systems to be available as MANFRED GENI slice/sliver resource.

• Milestone: MAX: S2.h DRAGON Aggregate Manager Enhancement Initial Implementation

  Due in 3 weeks (03/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Complete initial implementation of enhanced DRAGON Aggregate Manager. This initial implementation will focus on user interface and topology specification which combines compute and network resources into a common user request format.

• Milestone: MAX: S2.i Common Control Framework Design Update

  Due in 3 weeks (03/31/10)

  Continue work with the GENI community to develop an approach for a common control framework and/or other mechanisms to allow interoperation between GENI facilities. Update associated documentation.

• Milestone: MAX: S2.j Common Control Framework Implementation

  Due in 3 weeks (03/31/10)

  Develop an initial common framework implementation sufficient for interoperability testing. Conduct interoperability testing with other GENI Facilities to evaluate ability for multiple GENI facilities to interoperate.

• Milestone: MAX: S2.k Common Control Framework Documentation

  Due in 3 weeks (03/31/10)

  Generate a document summarizing the results of interoperability testing and general capabilities for GENI Facilities to interoperate.

• Milestone: MAX: S2.l User Tool Evaluation and Development Plan

  Due in 3 weeks (03/31/10)

  Review the available user tools across the GENI facilities and clusters and identify best candidate for integration into the DRAGON facility and control framework.

• Milestone: MAX: S2.m User Support

  Due in 3 weeks (03/31/10)

  Work with and support interested users on use of the DRAGON GENI Facility.

• Milestone: MAX: S2.n DRAGON Aggregate Manager Documentation

  Due in 3 weeks (03/31/10)

  Update the design and installation documents for the DRAGON Aggregate Manager. Provide updated open source software distribution of GENI DRAGON Aggregate Manager and other related software.

• Milestone: NETKARMA: S2.d demo

  Due in 3 weeks (03/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Demonstrate working version of netKarma ingesting from GUSH. Demo includes simple display of provenance. Delivered at GEC-7.

• Milestone: OFCLEM: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFCLEM: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFGT: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFGT: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFIU: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFIU: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFNOX: S2.d Release software that supports OpenFlow 1.0 configuration protocol, and NOX API V2

  Due in 3 weeks (03/31/10)

  Release software that supports OpenFlow? 1.0 configuration protocol. Deliver version 2 of NOX API documentation suitable for campuses. Develop testing framework and first cut at full system tests.

• Milestone: OFPR: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFPR: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFRG: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFRG: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFUWA: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFUWA: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: OFUWI: S2.a2 Purchase equipment

  Due in 3 weeks (03/31/10)

  Purchase equipment.

• Milestone: OFUWI: S2.b Campus small deployments

  Due in 3 weeks (03/31/10)

  Finish all campus small deployments.

• Milestone: ProtoGENI.S2.e: ProtoGENI backbone resources available to other clusters

  Due in 3 weeks (03/31/10)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Make ProtoGENI backbone resources available to projects in other clusters (with whom we have worked out direct connections) by making the ProtoGENI Slice Authority, Clearinghouse, and Aggregate Manager interfaces available to them.

• Milestone: RAVEN: S2.d pubsub

  Due in 3 weeks (03/31/10)

  c) Plan for using Raven as a provisioning service for one other cluster. (Dec. 31, 2009)

• Milestone: RAVEN: S2.e rel 3.0

  Due in 3 weeks (03/31/10)

  e) Raven release v3.0 including documentation. (Mar. 31, 2010)

• Milestone: S3MONITOR: S2.d V0.1 release

  Due in 3 weeks (03/31/10)

  V0.1 of measurement system.

  Supports deployment of sensor pods on multiple ProtoGENI nodes. Includes initial version of interface to conduct measurements. Deliver software and documentation.

• Milestone: SPP: S2.a geniwrapper

  Due in 3 weeks (03/31/10)

  Continue development of component interface software. Implement GENI-wrapper on SPP-PLC to allow SPP users to setup slices through the GENI management framework, and to allow the SPP aggregate to be integrated into a larger management hierarchy. 3/31/10

• Milestone: SPP: S2.j secreview

  Due in 3 weeks (03/31/10)

  Consult with SPARTA to review SPP security and develop recommendations for improvements. 3/31/10

• Milestone: SPP: S2.k opsreview

  Due in 3 weeks (03/31/10)

  Consult with GMOC on SPP operational procedures and monitoring mechanisms. 3/31/10

• Milestone: SPP: S2.n openflow

  Due in 3 weeks (03/31/10)

  We also plan to implement OpenFlow-in-a-slice by 3/31/10

• Milestone: WIMXCOLUM: S2.a Prepare site

  Due in 3 weeks (03/31/10)

• Milestone: DOME: S2.d Import extended ORCA v2.1

  Due in 3 weeks (04/01/10)

  Import an extended GENI-compliant control framework from the ORCA project provided at 2/1/10, and integrate new features as needed. (4/1/10)

• Milestone: ORBIT: S2.f Support integration of latest OMF code into cluster testbeds

  Due in 3 weeks (04/01/10)

  Support integration of latest OMF code into WiMAX and cognitive radio projects. (starting 4/1/10)

• Milestone: PLFED: S2.b demo policy engine federated slice

  Due in 3 weeks (04/01/10)

  Demonstrate new policy engine (based on sfa_tables) by introducing richer peering policies; e.g., white-lists and black-lists.

• Milestone: WiMAX: S2.f WiMAX client platforms study

  Due in 3 weeks (04/01/10)

  Study and report on WiMAX client platforms, including PCs and handsets. (4/1/10)

• Milestone: KGENI: S2.e Playbook Review Complete

  Due in 1 month (04/09/10)

  Playbook review by GPO, GENI projects related to operations and security, and other interested parties.

• Milestone: PGTools: S2.e Updated user guide

  Due in 1 month (04/09/10)

  Second version of user guide for ProtoGENI experimenter tools.

  Release user guide and support experimenters using ProtoGENI

• Milestone: Quilt: S2.c Complete Workshop Program

  Due in 1 month (04/15/10)

• Milestone: GENICLOUD S2.b Plan for GUI

  Due in 1 month (04/16/10)

  Investigate options for GUI including (1) existing PlanetLab tools such as GUSH/Nebula, (2) building a new GUI. Identify plan and document rationale for plan.

• Milestone: CompSec: S2.c

  Due in 2 months (04/30/10)

  Catalog of GENI assets, value of assets and risks to assets. Updated to include risk assessment and comments on v 0.1.

• Milestone: OFCLEM: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFGT: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFIU: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFNOX: S2.e Support campus installations of GENI software with AM API

  Due in 2 months (04/30/10)

  Campuses will be installing GENI software with AM API implementation; support the NOX-related aspects of this activity.

• Milestone: OFPR: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFRG: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFUWA: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: OFUWI: S2.c Install GENI software with AM API implementation

  Due in 2 months (04/30/10)

  Install GENI software with AM API implementation.

• Milestone: ProtoGENI.S2.f: Improved interfaces

  Due in 2 months (04/30/10)

  100%

  Closed tickets:

  1

  Active tickets:

  0

  Add improved interfaces for viewing operational state, history, and usage, and export at least a subset (including at least ProtoGENI component history and backbone link utilization) of these to other projects.

• Milestone: Quilt: S2.d Open Registration and Travel Request Form

  Due in 2 months (04/30/10)

• Milestone: WIMXCOLUM: S2.b Start software for WORKIT nodes

  Due in 2 months (04/30/10)

  Start software to enhance WORKIT nodes with WiMax? clients.

• Milestone: BGPMux: S2.g Intro slides and tutorial

  Due in 2 months (05/01/10)

  Release of BGP Mux introductory slides and tutorial code for using BGP-Mux as a route monitoring tool (based on undergraduate coursework).

• Milestone: DOME: S2.e Improve virtualization and experiment control

  Due in 2 months (05/01/10)

  Extend the software for your mobile nodes (bricks), your centralized server, and web-based experiment control software, to improve virtualization and experiment control functions. (5/1/10)

• Milestone: DSL: S2.g Launch of DSL/FB instance on ProtoGENI

  Due in 2 months (05/01/10)

  Launch of DSL/FB instance on ProtoGENI with new applications:

  DSL/FB applications publicly available. Recommendations from review of Milestone 6 document must be implemented before launch.

• Milestone: LEARN: S2.j Deliver release of Measurement Handler

  Due in 2 months (05/01/10)

  Deliver release of Measurement Handler code for Infinera DTN and documentation to GPO. (5/1/10)

• Milestone: VMI-FED: S2.c GEC8 demo

  Due in 2 months (05/01/10)

  05/01/10 - Demonstration of initial VMI library on cluster nodes at UA (Demo at GEC8)

• Milestone: WIMXRG: S2.c Upgrade base station software

  Due in 2 months (05/01/10)

• Milestone: MillionNodeGeni: S2.d Create an example assignment

  Due in 2 months (05/05/10)

  d) Create an example assignment leveraging Seattle that an educator might use for the GENI outreach plan for Spiral 2.

• Milestone: BGPMux: S2.c BGP-Mux ops transition -

  Due in 2 months (05/15/10)

  33%

  Closed tickets:

  1

  Active tickets:

  2

  BGP-Mux Operations Transition. Support for (non-developer) experimental use of BGP-Mux, contingent upon availability of adequate IP address block.

  Planned completion date moved from 11/30/09 to 5/15/10. See #275.

• Milestone: DICLOUD: S2.f Use CloudWatch to monitor usage

  Due in 2 months (05/15/10)

  Report on the feasibility of using Amazon’s new CloudWatch? service to monitor fine-grained usage costs. Amazon’s CloudWatch? was not available at the time of the proposal; in the initial proposal we planned to not give users root access on servers, and, instead, proposed a per-server root monitoring daemon. CloudWatch? may remove this need. (5/15/10).

• Milestone: CompSec: S2.d

  Due in 3 months (05/28/10)

  Updated Asset Valuation and Risk Assessment report based on comments from telephone review of report by GPO, other security projects, control frameworks, stakeholders and other interested parties.

• Milestone: SECUREUPDATES: S2.f push demo

  Due in 3 months (05/30/10)

  Demonstrate push mechanism that provides security metadata to the repository library.

• Milestone: SECUREUPDATES: S2.g client lib example

  Due in 3 months (05/30/10)

  Make available the code for example client software update system implementation using the client library.

• Milestone: WIMXUCLA: S2.a Begin deployment of dual-mode vehicular nodes (WiFi and WiMax)

  Due in 3 months (05/30/10)

• Milestone: CMU Lab:S2.d Better Support for Testing and Upgrades

  Due in 3 months (05/31/10)

  Explore and implement mechanisms by which the downtime and risks associated with systems upgrades can be mitigated.

  Implement the control migration functionality, which will allow nodes to be moved between separate boss-ops pairs. Evaluate the (large) design space (use of VLANs, DNS, VPNs, etc.) and pick the most appropriate option(s). Complement the code development with a short best practices guide on how to use the feature. Update the guide as experience is gained with the feature.

• Milestone: CMU Lab:S2.e Ehernet VLAN-based Control and Data Plane

  Due in 3 months (05/31/10)

  Use tagged VLANs to support multiplexing of control and data planes across the same physical Ethernet infrastructure (such as the private network used by CMUlab). This will eliminate the requirement that testbed nodes be multi-homed. Evaluate and document the performance difference between the VLAN and VPN based solutions, as seen from the perspective of users (running experiments).

• Milestone: DIGOBREG: S2.d Collaborate on security design for Spiral 2

  Due in 3 months (05/31/10)

  Collaborate with the Security team on security design for Spiral 2 in relation to the offered Registry and Repository services. Also, analyze the identity management system selected by GENI vis-a-vis adapting the Handle System to manage user identity credentials in a distributed fashion. For example, if Shibboleth is adopted by GENI as the common identity management system, then the analysis will identify the technical requirements for allowing distributed management of Shibboleth records using the Handle System.

• Milestone: DIGOBREG: S2.e Continuously operating GENI Federated Clearinghouse

  Due in 3 months (05/31/10)

  e) Provide infrastructure and other operations support in order to have a continuously operating GENI Federated Clearinghouse and other services, if any, available to GENI members.

• Milestone: GMOC: S2.d Revised Concept of Operations document

  Due in 3 months (05/31/10)

  Complete revised Concept of Operations document. Revise the Concept of Operations document drafted in Spiral 1 based on lessons learned from exemplar interactions, emergency shutdown, and visualization prototypes. May also include any new drafts for Common Operational Data set document and Operational data format documents. Document will be reviewed and discussed at GEC8.

• Milestone: Hive: S2.c

  Due in 3 months (05/31/10)

  For monitoring software, modify the guest operating systems (largely Linux and BSD) to capture data via the operating systems' BSM interfaces and capture information on network traffic measurements. For distributed sensors, begin sketching means of employing Battelle’s distributed sensor algorithms. Deliver software, and documentation including user manuals.

• Milestone: OFCLEM: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFGT: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFIU: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFPR: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFRG: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFUWA: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OFUWI: S2.d Begin integration testing with Stanford and BBN

  Due in 3 months (05/31/10)

  Integration testing with Stanford and BBN. (Ongoing.)

• Milestone: OnTime: S2.e: OnTimeMeasure-GENI available to early experimenters

  Due in 3 months (05/31/10)

  OnTimeMeasure-GENI V1.0 software available to early experimenters.

  - Measurements scheduler software package with documentation will be developed that will perform centralized and distributed measurement orchestration and collection using various measurement tools in OnTimeMeasure-GENI testbed; software features will include: measurement conflict-avoidance, centralized scheduling using our EDF-CE algorithm [Calyam-RTSS], distributed scheduling using our enhanced Raymond algorithm [Calyam-TC], modified scheduling algorithms catering to network status sampling frequencies adopted in GENI or specified by users (e.g. periodic, probabilistic, adaptive), any necessary web-services (e.g. SOAP, XML, HTTP) integration to support measurement request/response schemas that initiate/check /terminate measurement status and move measurement datasets between databases, instrumented-nodes and users - User manual for configuring and using OnTimeMeasure-GENI - Deliver source code, documentation and database schemas - Support early experimenters

  (Assumption: Measurement request/response schemas and related APIs are already defined and are available to use in the GENI facility for projects such as this to use and extend as required.)

• Milestone: IMF: S2.b Initial ontology for measurement

  Due in 3 months (06/01/10)

  Collaborate with the ORCA Augmentation project to develop and document an initial ontology for substrate measurement capabilities. (6/1/10)

• Milestone: ORCAAUG: S2.b Rel 2.2_2 ORCA code to projects

  Due in 3 months (06/01/10)

  Implement and provide release 2.2 of ORCA code to other Cluster D projects, including the following features: (6/1/10) 1) Computational substrate ontology 2: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Initial ontology for edge computational substrates. 2) Measurement substrate ontology 2: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Initial ontology for substrate measurement capabilities. 3) Ontology integration 2: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Integration of ontology resource handling mechanisms into ORCA core. 4) Policy development 2: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Development of resource provisioning policies based on ontologies. 5) Broker querying 2: Resource discovery. Enable dynamic resource discovery. Ability to query a broker about resources available, and total delegated. Consistency not enforced. 6) Note: Additional release 2.2 features will be provided by ORCA/BEN project.

• Milestone: ORCABEN: S2.b Rel 2.2_1 ORCA code to projects

  Due in 3 months (06/01/10)

  Implement and provide release 2.2 of ORCA code to other Cluster D projects, including the following features: (6/1/10) 1) Better packaging 2: Simplified installation, config script auto-configuration, simple usability extensions, simplified certificate management. 2) Configuration manager 2: Flexible configuration manager capable of executing arbitrary sequences of configuration actions with complex control flows on complex substrates. Configuration commands can be created using either NDL toolkit or custom mechanisms. 3) External management interface 2: An extensible SOAP-based interface allowing ORCA to interface with management entities. e.g. GMOC. Providing GMOC capabilities to look at current slices and a STOP SLICE `button’. 4) Note: Additional release 2.2 features will be provided by ORCA augmentation project.

• Milestone: SCAFFOLD: S2.d stream code

  Due in 3 months (06/01/10)

  Deliver source code and documentation for SCAFFOLD stream socket API for UNIX

• Milestone: SCAFFOLD: S2.e multi server

  Due in 3 months (06/01/10)

  Demonstrate multi-server SCAFFOLD network within L2 domain: client, multiple servers (part of same SCAFFOLD group), switch, rendezvous

• Milestone: SCAFFOLD: S2.f basic stateless server

  Due in 3 months (06/01/10)

  Deliver source and documentation for basic implementation of stateless servers: transparent migration/recovery of application TCP flows (e.g., HTTP transfers of static content) in unmodified legacy applications and unmodified clients (e.g., Web browsers and HTTP servers)

• Milestone: ERM: S2.c Demo UMF in an experimental use-case

  Due in 3 months (06/03/10)

  Demonstrate the working prototype by implementing an experimental use-case, as delivered by Milestone 5 in year-1. This may consist of a proactive protection mechanism, whereby the UMF may monitor a physical layer signal (e.g. optical power). If the power undershoots a predefined threshold, the UMF will export this information such that external protection protocols can then reroute the impaired channel to avoid packet loss and uncorrectable bit errors. This work will be performed at the Lightwave Research Laboratory test-bed at Columbia University. [6/3/10 (9 months).]

• Milestone: PGINTEGRN: S2.f API document

  Due in 3 months (06/11/10)

  Component Manager API document (Version 3).

  Collect feedback from integrations partners about CM API Version 2. Solicit comments about how well the API fits substrates' capabilities and services' needs. Update API and document based on feedback.

• Milestone: Quilt: S2.e Close Registration and Travel Requests

  Due in 3 months (06/15/10)

• Milestone: CRON: S2.e

  Due in 4 months (06/25/10)

  Installing a slice authority and a component manager; and design interfaces for viewing operational resources at the federated CRON testbed.

• Milestone: Attrib: S2.c

  Due in 4 months (06/30/10)

  Report updated with information on infrastructure support for attribution requirements of scenarios; refinement of scenarios where appropriate.

• Milestone: LAMP: S2.f V1.1 of perfSONAR on ProtoGENI

  Due in 4 months (06/30/10)

  Version to include interfaces for storage of measurement data and metadata. Define metadata extensions to capture data provenance. Deliver software, documentation and user manual. Make perfSONAR available to experimenters on GENI and support use of perfSONAR by experimenters.

• Milestone: OFNOX: S2.f Port existing applications to latest OpenFlow identifiers

  Due in 4 months (06/30/10)

  Port existing applications to latest OpenFlow? identifiers.

• Milestone: OFNOX: S2.g Add support for multiple Openflow protocols

  Due in 4 months (06/30/10)

  Add support for multiple OpenFlow? protocols (specifically 0.9 and 1.0) within the same build.

• Milestone: OFNOX: S2.h Increase portability

  Due in 4 months (06/30/10)

  Increase portability to support latest tool changes on current Linux distributions (CentOS, Debian, Ubuntu, Fedora).

• Milestone: OFNOX: S2.i Release first version of SNAC/NOX console software

  Due in 4 months (06/30/10)

  Release first version of SNAC/NOX console software with features needed to support campus deployments and GEC9 demo

• Milestone: RAVEN: S2.f better xfer

  Due in 4 months (06/30/10)

  f) Add support for better transfer mechanism (e.g. SET). (June 31, 2010)

• Milestone: S3MONITOR: S2.e V0.2 release

  Due in 4 months (06/30/10)

  V0.2 of measurement system released for use by ProtoGENI experimenters

  Software release includes backend database to store measurement data using schema based on discussions with other projects and GPO and interface for researchers to obtain measurements. Deliver software with documentation and user manual for obtaining measurements.

• Milestone: IGENI: S2.g POC to GENI response team

  Due in 4 months (07/01/10)

  Provide POC to GENI Prototype Response and Escalation team. (7/1/10)

• Milestone: IGENI: S2.h POC to GENI security team

  Due in 4 months (07/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (7/1/10)

• Milestone: IMF: S2.g Protocol between SILO and IMF

  Due in 4 months (07/01/10)

  Define and document the protocol to communicate control/management/measurement data between SILO and IMF consistent with the v1.0 architectural view, implement the protocol in both the IMF and in SILO, and integrate. (7/1/10)

• Milestone: PLFED: S2.c demo hierarchical peering

  Due in 4 months (07/01/10)

  Demonstrate hierarchical (not pair-wise) peering by including VINI, M-Lab, and G-Lab in the federation

• Milestone: WIMXNYUPT: S2.a Complete Installation

  Due in 4 months (07/01/10)

• Milestone: WIMXRG: S2.b Deliver kits to two campuses

  Due in 4 months (07/01/10)

• Milestone: MillionNodeGeni: S2.e Integrate with ProtoGENI

  Due in 4 months (07/02/10)

  Integrate with ProtoGENI so that calls to get resources & release resources work across both frameworks. This milestone is contingent on agreement with ProtoGENI of what the interface should be no later than Mar 1 2010.

• Milestone: PrimoGENI: S2.d: PrimoGENI Aggregate release

  Due in 4 months (07/02/10)

  Make PrimoGENI Aggregate 1.0 available to early experimenters. Deliver aggregate manager software. Identify point of contact (PoC) for the GENI Prototype Response and Escalation Group.

• Milestone: CompSec: S2.e

  Due in 4 months (07/09/10)

  Document outlining an initial operations security plan for GENI

• Milestone: ExptsSec: S2.c

  Due in 4 months (07/09/10)

  Run experiments designed in Milestone 2 to validate/exploit vulnerabilities in ProtoGENI/Emulab. Suggest improvements to ProtoGENI/EMULab security and experimenter support tools. Deliver software/scripts/documentation needed to repeat experiment.

• Milestone: BGPMux: S2.h Release 2 integration s/w

  Due in 4 months (07/15/10)

  GENI Integration Software Release 2. Will support extension of Spiral 1 aggregate manager for basic user authentication. Will support allocation of a ProtoGENI node with BGP Mux connectivity through the ProtoGENI interface.

• Milestone: ProtoGENI.S2.g: Integration Release 2

  Due in 4 months (07/15/10)

  GENI Software Integration Release 2. Will formally define Manifest, which will be used to report component "packing list" details, and may be modified to effect changes in the component. Include some level of support in the ProtoGENI Component Manager for producing manifests and accepting modified ones to configure resources (such as loading disk images.) Will add support for multiple aggregates to the ProtoGENI Slice Embedding Service, enabling automatic mapping of experiments across multiple aggregates.

• Milestone: SPP: S2.f demo8

  Due in 4 months (07/15/10)

  Perform demonstrations at GEC8. 7/15/10

• Milestone: SPP: S2.h tutorial8

  Due in 4 months (07/15/10)

  Conduct user tutorials at GEC8. 7/15/10

• Milestone: VMI-FED: S2.d resource doc

  Due in 4 months (07/15/10)

  07/15/10 - Finalize and post initial UA resource analysis summary document for review by GENI researchers and personnel. (Promote at GEC8)

• Milestone: WiMAX: S2.j Release v2.0 of basestation code for first WIMAX kits

  Due in 4 months (07/15/10)

  Implement and document second release (v2.0) of Linux-based GENI base station node software, to be used in first campus WiMAX kits. (7/15/10)

• Milestone: ABAC: S2.c

  Due in 4 months (07/16/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  This software and related documentation will be delivered prior to the July 2010 GEC, as well as integrated within the ProtoGENI cluster for use in a demonstration, conditional on the readiness and availability of ProtoGENI development software and staff to support the integration.

• Milestone: InfoSubstrate: S2.a V1.0 Information plane system design issues

  Due in 4 months (07/16/10)

  Deliver a document that examines system design issues important for designing the GENI information plane. Solicit comments from GPO, GENI Operations and the GENI engineering community.

• Milestone: PGTools: S2.f V1.2 release of experimenter tools

  Due in 4 months (07/16/10)

  V1.2 release of ProtoGENI experimenter tools.

  Release includes ability to display of all known ProtoGENI components on experimenter interface, watchdog and idle detector operational on ProtoGENI nodes.

• Milestone: COGRADIO: S2.d Initial integration stand-alone system and with OMF

  Due in 4 months (07/20/10)

  Initial integration of stand-alone cognitive radio platform with v0.1 software, initial integration into ORBIT Management Framework, and demonstration. (7/20/10, GEC8)

• Milestone: COGRADIO: S2.e Stand-alone system available to GENI users

  Due in 4 months (07/20/10)

  Make stand-alone cognitive radio system available for use by selected GENI researchers. (7/20/10, GEC8)

• Milestone: DICLOUD: S2.g Demo initial proxy aggregate manager

  Due in 4 months (07/20/10)

  Demo 2: Researchers use an initial version of the proxy aggregate manager to interact with EC2 control interfaces (e.g., to reboot servers or get console output). Note that these EC2 control interfaces will not include interfaces to EBS (see Demo 3 in Year 2). We will demonstrate a sample experiment using an initial version of our proxy aggregate manager, that uses meteorological detection algorithms tested on historical weather data. (7/20/10, GEC8).

• Milestone: DOME: S2.f Import extended ORCA v2.2

  Due in 4 months (07/20/10)

  If desired, import an extended GENI-compliant control framework from the ORCA project provided at 6/1/10, and integrate new features as needed. (7/20/10, GEC8)

• Milestone: DOME: S2.g Include 900MHz radios

  Due in 4 months (07/20/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Implement improved virtualization and experiment control functions, including the 900 Mhz radios. (7/20/10, GEC8)

• Milestone: DOME: S2.h Demo experiment with another testbed

  Due in 4 months (07/20/10)

  Demonstrate experiments that involve more than one testbed. (7/20/10, GEC8)

• Milestone: DOME: S2.i Plan for VLANs to endpoints

  Due in 4 months (07/20/10)

  Develop a plan for extending VLAN connectivity to DOME endpoints on busses, etc. (7/20/10, GEC8)

• Milestone: IGENI: S2.d Demo VLAN connections between GENI aggregates

  Due in 4 months (07/20/10)

  Implement and demonstrate the setup of L2 (VLAN) connections between aggregates in Clusters D and E, via coordinated setups that include several sets of GENI resources within other networks, e.g., iGENI, C-Wave, Internet 2, NLR, BEN and/or CENIC networks, and/or the aggregates themselves. (7/20/10, GEC8)

• Milestone: IGENI: S2.e Demo VLAN connections including other research communities

  Due in 4 months (07/20/10)

  Implement and demonstrate the setup of L2 (VLAN) connections between aggregates in Clusters D and E, and researchers in other research communities, via iGENI and transport resources that connect with another research networks. (7/20/10, GEC8)

• Milestone: IGENI: S2.f Control of iGENI via ORCA to GENI users

  Due in 4 months (07/20/10)

  Make control of L2 connections utilizing iGENI available via the ORCA control framework available to GENI users, e.g., by defining an access method and other enabling methods. (7/20/10, GEC8)

• Milestone: IMF: S2.c First GENI instrumentation and measurement architecture

  Due in 4 months (07/20/10)

  Collaborate with other GENI projects and GPO to develop and document a v1.0 common GENI instrumentation and measurement architecture. (7/20/10, GEC8)

• Milestone: IMF: S2.h Update the IMF software

  Due in 4 months (07/20/10)

  Update the IMF software to v0.5, and integrate with both SILO and UMF in BEN, to demonstrate a 2-way flow of control/management/measurement data between SILO and IMF, and conduct a simple cross layer experiment, e.g., where an optical layer measurement influences routing. (7/20/10, GEC8)

• Milestone: KANSEI: S2.g Import extended ORCA v2.1

  Due in 4 months (07/20/10)

  Import updated ORCA GENI-compliant control framework software provided by RENCI group at 2/1/10, and integrate new features as needed, expected to include: (7/20/10, GEC8)

  • Certificate distribution for instantiating authentication • Identity management for portals • Extended resource description mechanisms • Extended resource allocation policies • Support fine-grain intra-array resource discovery and allocation • Broker registry • Interface for external experiment control tools • OSU and WSU

• Milestone: KANSEI: S2.h Demo experiment using Kansei and NetEye

  Due in 4 months (07/20/10)

  Demonstrate on-line federated experiment involving Kansei testbed and NetEye? testbeds (7/20/10, GEC8) • OSU/WSU • Support fine-grain intra-array resource discovery and allocation

• Milestone: LEARN: S2.d Initial integration LEARN into ORCA

  Due in 4 months (07/20/10)

  Complete initial integration of the LEARN network into the ORCA control framework (GENI Cluster D), to enable GENI researchers to utilize the LEARN network for L2 (VLAN) transport between a limited number of sites, e.g., University of Houston and Rice University. (7/20/10, GEC8)

• Milestone: LEARN: S2.k List of measurement handlers for GENI

  Due in 4 months (07/20/10)

  Based upon results of Data Plane Measurements project, collaborate with GPO and other projects in Cluster D, to establish a list of measurement handlers that are needed for commercial transport and measurement equipment that will be used in GENI. (7/20/10, GEC8)

• Milestone: MPRADIO: S2.a White paper on programmable radio substrate capabilities

  Due in 4 months (07/20/10)

  White paper on recommended capabilities for a programmable radio substrate in GENI, and review of white paper with staff of “Cognitive Radios for GENI Spiral II” project. (7/20/10, GEC8)

• Milestone: OKGEMS: S2.d Integrate field sensor nodes

  Due in 4 months (07/20/10)

  Integrate a set of field-deployed sensor nodes into GENI, connected via a Stargate (equipped with a cellular modem) through cellular networks to the OKGems server, and demonstrate. (7/20/10, GEC8)

• Milestone: OKGEMS: S2.e Plan to integrate robotic nodes

  Due in 4 months (07/20/10)

  Complete a detailed technical plan for integrating robotic nodes into GENI using the ORCA control framework, , for sharing by multiple researchers, including an experiment control portal; the abstraction of components in the robots will be designed to cover microcontrollers, communication, dozens of sensors, actors, power, and attached sensor nodes. (7/20/10, GEC8)

• Milestone: ORBIT: S2.g Demo experiments with multiple testbeds

  Due in 4 months (07/20/10)

  Develop experiments that demonstrate federation and mobility functions, including experiments that utilize multiple testbeds, do end-to-end validation testing, and demo at a GEC. (7/20/10, GEC8)

• Milestone: ORBIT: S2.h Federated testbeds available to GENI users

  Due in 4 months (07/20/10)

  Provide OMF support for experimentation on federated testbeds by GENI users outside of related projects. (starting 7/20/10, GEC8)

• Milestone: ORCAAUG: S2.f Query broker for available resources

  Due in 4 months (07/20/10)

  Demonstrate ability to query a broker about resources available, and total delegated. (7/20/10, GEC8)

• Milestone: ORCABEN: S2.k Integration of GUSH

  Due in 4 months (07/20/10)

  Demonstrate integration of GUSH with Service Manager. (7/20/10, GEC8)

• Milestone: ORCABEN: S2.l Experiments BEN and other testbeds

  Due in 4 months (07/20/10)

  Implement experiments that include BEN and its associated resources, plus resources from other testbeds, and demonstrate. (7/20/10, GEC8)

• Milestone: PrimoGENI: S2.e: Demonstration

  Due in 4 months (07/20/10)

  Demonstrate ProtoGENI experiment that uses PrimoGENI resources. Deliver software, scripts and documentation necessary to repeat experiment.

• Milestone: UMLPEN: S2.d Implement packet header capture functionality

  Due in 4 months (07/20/10)

  Implement packet header capture functionality on network processor based NICs to support packet trace archiving. (7/20/10, GEC8)

• Milestone: ViSE: S2.j Import extended ORCA v2.2

  Due in 4 months (07/20/10)

  [M12] If needed, update experiment control framework (ECF), based upon updated reference software, provided by RENCI/Duke group at 6/1/10, and integrate new features as needed. (7/20/10, GEC8)

• Milestone: ViSE: S2.k Allocation policy for sensors

  Due in 4 months (07/20/10)

  [M9] Testbed allocation policy for sensors. Allocation of energy as a resource to be done on a best-effort basis. (note: power now available at all node sites). (7/20/10, GEC8)

• Milestone: ViSE: S2.l Demo experiment with another testbed

  Due in 4 months (07/20/10)

  [M10, D3 and D4] Demo testbed resources shared among multiple experiments. Demo experiments that include resources in multiple testbeds. Demo easy access and testbed use by end-users at GEC. [Experimental control framework, exporting common functionality needed to execute experiments such as, automatic file distribution, sequenced process workflow execution, log file collection, and experiment monitoring.] (7/20/10, GEC8)

• Milestone: WiMAX: S2.g Integrate latest OMF code

  Due in 4 months (07/20/10)

  Import latest OMF software from the ORBIT project at 6/1/10, and integrate. (7/20/10, GEC8)

• Milestone: WiMAX: S2.h Demo experiments with multiple testbeds

  Due in 4 months (07/20/10)

  Work with the ORBIT project, to develop experiments that test federation and mobility functions, including experiments that utilize multiple testbeds, do end-to-end validation testing, document, and demo at a GEC. (7/20/10, GEC8)

• Milestone: WiMAX: S2.i Testbed available to GENI users

  Due in 4 months (07/20/10)

  Make your (federated) testbed available to GENI users (outside of associated projects). (starting 7/20/10, GEC8)

• Milestone: GENICLOUD S2.c Demonstration at GEC8

  Due in 4 months (07/23/10)

  Demonstrate the ability to configure slices on multiple Eucalyptus clusters using a basic GUI as well as the SFA command-line tool. The Eucalyptus Aggregate Manager will support both the light and full federation models. The Eucalyptus RSpec will be extended to enable the user to specify the disk image to load on a particular sliver and the virtual networking mode to use. The Aggregate Manager will be deployed on the HP Labs and UIUC Eucalyptus clusters. Deliver the software used at the demo along with documentation (e.g. a wiki page).

• Milestone: Hive: S2.d

  Due in 4 months (07/23/10)

  Demonstration of Hive Mind security concept at GEC

• Milestone: LAMP: S2.g Demonstration of perfSONAR on ProtoGENI

  Due in 4 months (07/23/10)

  Demonstration of perfSONAR on ProtoGENI at GEC

• Milestone: PGTools: S2.g Demonstration

  Due in 4 months (07/23/10)

  Demonstration of v1.2 experimenter tools at GEC

• Milestone: S3MONITOR: S2.f Demonstration 2

  Due in 4 months (07/23/10)

  Demonstration of measurement system at GEC

• Milestone: GUSH: S2.e support two control frameworks

  Due in 5 months (07/30/10)

  e) Extend GUSH experiment description language to allow specification and control of experiments running on at least two control frameworks. July 30, 2010.

• Milestone: DIGOBREG: S2.f Evaluation report on GENI Federated Clearinghouse

  Due in 5 months (07/31/10)

  Evaluate the GENI Federated Clearinghouse (GFC) in terms of performance, administration and operations needs, scalability, and security. The evaluation will be based on the user activity at the operational GFC. Additionally, the results from a series of benchmarking tests performed on the GFC will be included in the evaluation report.

• Milestone: DIGOBREG: S2.g Collaborate with O&M team

  Due in 5 months (07/31/10)

  Collaborate with the O&M team on methods for Spiral 2 in relation to the offered Registry and Repository services.

• Milestone: NETKARMA: S2.e identify partners

  Due in 5 months (07/31/10)

  Establish connections with relevant projects in Control Plane and Measurement Plane such as the following. Produce plan for working with Control Plane and Measurement Plane projects.

• Milestone: OFCLEM: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFCLEM: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: OFGT: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFGT: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: OFIU: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFIU: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: OFNOX: S2.j Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFNOX: S2.k Support campuse upgrades to OF 1.0 and GENI API

  Due in 5 months (07/31/10)

  Campuses will be upgrading their small deployments to use OF 1.0 implementations and GENI API (software only); support the NOX-related aspects of this activity.

• Milestone: OFPR: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFPR: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OF 1.0 implementations and GENI API (software only).

• Milestone: OFRG: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFRG: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: OFUWA: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFUWA: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: OFUWI: S2.e Plan and engineer GEC 9 demo

  Due in 5 months (07/31/10)

  Plan and engineer demo for GEC 9 in November.

• Milestone: OFUWI: S2.f Upgrade small deployments to use OF 1.0

  Due in 5 months (07/31/10)

  Upgrade small deployments to use OpenFlow? 1.0 implementations and GENI API (software only).

• Milestone: DSL: S2.h Federated version of decentralized DSL kernel

  Due in 5 months (08/01/10)

  A decentralized version of DSL running, simultaneously, over both Cryus and ProtoGENI. I.e., some of the data and activities will take place on either one of the platforms.

• Milestone: IGENI: S2.j Explore dynamic L1 connections

  Due in 5 months (08/01/10)

  Explore and report on the potential for using dynamic L1 connections among aggregates, for possible emphasis in Year-2. (8/1/10)

• Milestone: UMLPEN: S2.e Provide POC to Security team

  Due in 5 months (08/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (8/1/10)

• Milestone: MillionNodeGeni: S2.f Clearinghouse API spec. for end-hosts

  Due in 5 months (08/06/10)

  Specification for Clearinghouse API for end-hosts: A description of the interface by which the clearinghouse (SeattleGENI) interacts with end-hosts. This involves describing how the node manager API is manipulated by SeattleGENI to track the state of resources.

• Milestone: CompSec: S2.f

  Due in 5 months (08/13/10)

  Telephone review of security plan document by GPO, other security projects, control frameworks and other interested parties.

• Milestone: DICLOUD: S2.h Release initial proxy aggregate manager

  Due in 5 months (08/13/10)

  Finish and release an initial version of the proxy aggregate manager to monitor fine-grained usage metrics, such as the number of I/Os and the aggregate network bandwidth. Expose Amazon’s API for EC2 to users through the proxy. (8/13/10)

• Milestone: Hive: S2.e

  Due in 5 months (08/13/10)

  Begin integrating distributed sensor algorithms. Deliver software, and documentation including user manuals.

• Milestone: PGINTEGRN: S2.g Reference Component Manager

  Due in 5 months (08/13/10)

  Updated reference Component Manager implementation.

  Deliver revised reference component manager based on API Version 3.

• Milestone: PGTools: S2.h Updated user guide

  Due in 5 months (08/13/10)

  Third version of user guide for ProtoGENI experimenter tools.

• Milestone: KGENI: S2.f Playbook Version 2.0

  Due in 5 months (08/20/10)

  Playbook updated based on completed GMOC-dvNOC interoperability trials, review of Version 1.0 of Playbook

• Milestone: OppWireless: S2.d

  Due in 5 months (08/20/10)

  Complete implementation of an experiment based on a Pigeon network algorithm on the ProtoGENI/CMU wireless emulator. Should be able to run experiment on ProtoGENI/CMU wireless emulator. Deliver software, scripts and documentation necessary to repeat experiment.

• Milestone: S3MONITOR: S2.g Evaluation report

  Due in 5 months (08/20/10)

  Report on evaluation of measurement system.

  Evaluate measurement system for ease of use, measurement overhead, etc.

• Milestone: OnTime: S2.f: Report on experiences

  Due in 6 months (08/27/10)

  Report on experiences with implementing and using OnTimeMeasure on ProtoGENI

  Document will include validation experiences and a study of integration points with PlanetLab as well as other GENI control frameworks comprising of multiple aggregates

• Milestone: CMU Lab:S2.f Expanded Homenet testbed

  Due in 6 months (08/30/10)

  Expand the Homenet testbed to about 25 nodes (after CMU IRB approval).

• Milestone: BGPMux: S2.i Test multi-site experiment

  Due in 6 months (08/31/10)

  Implement, document, and deploy test multi-site experiment.

• Milestone: CMU Lab:S2.g RSpecs as basis for CMUlab-emulator coordination

  Due in 6 months (08/31/10)

  Move to an RSpec based model for wireless channels in the emulator.

• Milestone: DIGOBREG: S2.h Contribute to GENI outreach

  Due in 6 months (08/31/10)

  CNRI personnel will prepare at least one journal article describing CNRI’s GENI work during the year. Additionally, one summer intern, at the upper class or graduate level, will be dedicated to GENI work during 2010.

• Milestone: DOME: S2.m Contribution to GENI outreach

  Due in 6 months (08/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Specific contribution to GENI outreach plan required for Spiral 2: TBD (9/1/09-8/31/10)

• Milestone: ERM: S2.d Integrate UMF with BEN

  Due in 6 months (08/31/10)

  Contribute to the Cluster D effort by integrating the UMF subsystem with the Cluster D network substrate. This will be done by physically migrating the developed hardware and software resources to the BEN infrastructure at RENCI. [8/31/10 (12 months).]

• Milestone: ERM: S2.e Design and demo XML data exchange software modules

  Due in 6 months (08/31/10)

  Design the XML data exchange software modules for the UMF to interact with the researcher or an intermediate measurement software architecture (e.g. SILO, perfSONAR, etc.) Demonstrate the inter-operability of these software modules with BEN at RENCI. [8/31/10 (12 months).]

• Milestone: ERM: S2.f Plan to integrate UMF within anpther infrastructures

  Due in 6 months (08/31/10)

  Work with other GENI clusters (outside of Cluster D) and/or other networking communities, such as Wisconsin’s Measurement System GENI project or Internet2’s perfSONAR framework, to define mechanisms to integrate the UMF within their infrastructures. [8/31/10 (12 months).]

• Milestone: GENICLOUD S2.d Eucalyptus aggregate manager available to experimenters

  Due in 6 months (08/31/10)

  Make Eucalyptus clusters available to GENI experimenters using the PlanetLab. Eucalyptus cluster(s) and aggregate managers are up and running continuously and available to experimenters (for some reasonable definition of continuous given this is not a production system yet). Provide reasonable support to GENI experimenters using Eucalyptus.

• Milestone: GUSH: S2.f spiral 2 id mgmt

  Due in 6 months (08/31/10)

  f) Modify GUSH to use PlanetLab’s Spiral 2 identity management mechanisms. August 31, 2010.

• Milestone: GUSH: S2.g 0.3 release

  Due in 6 months (08/31/10)

  g) Gush prototype v0.3 release. August 31, 2010.

• Milestone: GpENI: S2.j federate

  Due in 6 months (08/31/10)

  Federate with Public PlanetLab using SFA + GENIwrapper + MyPLC. 08/31/10

• Milestone: GpENI: S2.k XORP and VINI

  Due in 6 months (08/31/10)

  Assess practicality of incorporation of XORP in VINI; document in short technical note. 08/31/10

• Milestone: GpENI: S2.l DCN GpENI MAX

  Due in 6 months (08/31/10)

  Collaborate with MANFRED group to deploy DCN between GpENI and MAX with GPO assistance and Internet2 approval, if practical given hardware and connectivity across Internet2. 08/31/10

• Milestone: GpENI: S2.m security

  Due in 6 months (08/31/10)

  Collaborate with Security Team on security design by responding to requests for information and document reviews. 08/31/10

• Milestone: GpENI: S2.n outreach

  Due in 6 months (08/31/10)

  Contribute to GENI outreach plan, as detailed in year-1 milestone, 08/31/10

• Milestone: KANSEI: S2.l Contribution to GENI outreach

  Due in 6 months (08/31/10)

  Specific contribution to GENI outreach plan required for Spiral 2. (9/1/09-8/31/10) • Diversity efforts in undergraduate and graduate program

• Milestone: MillionNodeGeni: S2.g v0.1 of end-host clearinghouse

  Due in 6 months (08/31/10)

  Reference implementation v0.1 of end-host clearinghouse (SeattleGENI)

• Milestone: MillionNodeGeni: S2.h Sprial 2 identify management mechanisms

  Due in 6 months (08/31/10)

  Integrate Sprial 2 identify management mechanisms into SeattleGENI.

• Milestone: MillionNodeGeni: S2.i Collaborate with O&M team

  Due in 6 months (08/31/10)

  Collaborate with O&M team on methods to share O&M data with other GENI groups for Spiral 2.

• Milestone: ORBIT: S2.i GMOC access to operating data

  Due in 6 months (08/31/10)

  Collaborate with GMOC operations group on providing access to OMF operating data. (11/1/09-8/31/10)

• Milestone: ORBIT: S2.l Contribution to GENI outreach

  Due in 6 months (08/31/10)

  Specific contribution to GENI outreach plan: (9/1/09-8/31/10)

• Milestone: ProtoGENI.S2.h: Deploy 3 additional backbone network nodes

  Due in 6 months (08/31/10)

  Acquire hardware and deploy 3 additional backbone network nodes, and make these resources available under the ProtoGENI APIs.

• Milestone: RAVEN: S2.g spiral 2 id mgmt

  Due in 6 months (08/31/10)

  g) Modify Raven to use Spiral 2 identity management mechanisms. (Aug. 31, 2010)

• Milestone: UMLPEN: S2.f Specific contribution to GENI outreach plan

  Due in 6 months (08/31/10)

  Specific contribution to GENI outreach plan (9/1/09-8/31/10)

• Milestone: ViSE: S2.p Contribution to GENI outreach

  Due in 6 months (08/31/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Specific contribution to GENI outreach plan required for Spiral 2: [M13] 3-day class at the U. Puerto Rico. (9/1/09-8/31/10).

• Milestone: WIMXCOLUM: S2.c Begin teaching modules

  Due in 6 months (08/31/10)

  Begin work on teaching modules to explore wide area wireless network issues and applications.

• Milestone: WIMXUWI: S2.a Initial integration of static and mobile nodes in MadBed testbed with ORBIT

  Due in 6 months (08/31/10)

  Initial integration of static and mobile nodes in MadBed? testbed (except for their WiMax? components) with ORBIT.

• Milestone: WiMAX: S2.k GMOC access to WIMAX operating data

  Due in 6 months (08/31/10)

  Collaborate with GMOC operations group on providing access to WiMAX base station operating data. (11/1/09-8/31/10)

• Milestone: WiMAX: S2.n Contribution to GENI outreach

  Due in 6 months (08/31/10)

  Specific contribution to GENI outreach plan required for Spiral 2: (9/1/09-8/31/10)

• Milestone: SCAFFOLD: S2.g demo ingress proxy

  Due in 6 months (09/01/10)

  Demonstrate ingress proxy for unmodified clients

• Milestone: SCAFFOLD: S2.h deliver ingress proxy

  Due in 6 months (09/01/10)

  Deliver source code and documentation for ingress proxy for unmodified clients

• Milestone: SCAFFOLD: S2.i demo flow migration

  Due in 6 months (09/01/10)

  Demonstrate SCAFFOLD network within L2 domain with unmodified clients and with flow migration across servers

• Milestone: SCAFFOLD: S2.j http stateless server

  Due in 6 months (09/01/10)

  Demonstrate “stateless servers” technique on SCAFFOLD network for static HTTP content

• Milestone: VMI-FED: S2.e GENI VMI demo

  Due in 6 months (09/01/10)

  09/01/10 - Demonstration of initial VMI functionality on GENI cluster nodes (cluster TBD).

• Milestone: WIMXNYUPT: S2.b Multi-campus Demo

  Due in 6 months (09/01/10)

• Milestone: WIMXRG: S2.d Demo with at least two sites

  Due in 6 months (09/01/10)

• Milestone: PrimoGENI: S2.e: PrimoGENI Aggregate 2.0 plan

  Due in 6 months (09/06/10)

  PrimoGENI Aggregate 2.0 design and development plan.

  Provide an implementation plan for PrimoGENI aggregate 2.0, with extended virtualization capabilities supporting multiple simultaneous large-scale high-fidelity network experiments, and necessary tools for streamlining experiment workflow (including configuring, deploying, monitoring and controlling network experiments).

• Milestone: DSL: S2.i Report on experiences

  Due in 6 months (09/10/10)

  Report on experiences with DSL/FB apps on ProtoGENI.

  Report on usage statistics, resource utilization, type and amount of data collected, experiences with supporting these apps on a GENI testbed, etc.

• Milestone: DICLOUD: S2.i Extend ViSE web portal to include cloud

  Due in 6 months (09/15/10)

  Extend ViSE’s web portal to include functions for users to lease EC2, S3, and EBS resources. Augment ViSE Trac website with documentation for installing and using software artifacts in conjunction with Orca. (9/15/10).

• Milestone: CRON: S2.f

  Due in 6 months (09/17/10)

  Perform experiment over the beta version of federation among CRON, LONI, ProtoGENI sites. Report to describe experiences with tools, desired improvements/features, etc. Deliver software, scripts and documentation necessary to repeat experiment.

• Milestone: Hive: S2.f

  Due in 6 months (09/17/10)

  Report on efficacy of distributed security sensors.

• Milestone: ABAC: S2.d

  Due in 7 months (09/24/10)

  This software may also incorporate features that are forwarding looking to support other control frameworks and cross-control framework integration.

• Milestone: ABAC: S2.e

  Due in 7 months (09/24/10)

  Updated document describing the design, APIs and configuration of the ABAC software prototyped under year 1 of this effort.

• Milestone: OppWireless: S2.e

  Due in 7 months (09/24/10)

  Report on experiences including ease of access of testbed, usability of tools, ability to sufficiently instrument experiment, suggestions for improvement of testbed, etc.

• Milestone: ExptsSec: S2.d

  Due in 7 months (09/28/10)

  Design experiment to extend the scope of the security assessment of ProtoGENI. Add at least one more aggregate to scope of experiment (preferably a wireless aggregate such as the CMU wireless emulator). The experiment design will be documented and sent to the ProtoGENI and CMU Wireless projects for review.

• Milestone: Attrib: S2.d

  Due in 7 months (09/30/10)

  Updated report including suggestions for further work related to Attribution for GENI

• Milestone: COGRADIO: S2.f Release design information for stand-alone system kit

  Due in 7 months (09/30/10)

  Release a full set of design information for stand-alone cognitive radio system “kit”, including hardware and v0.1 software. (9/30/10)

• Milestone: COGRADIO: S2.g Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan for Spiral 2. (9/30/10)

• Milestone: CompSec: S2.g

  Due in 7 months (09/30/10)

  Updated operations security plan document.

• Milestone: DICLOUD: S2.j Make available initial set of resources

  Due in 7 months (09/30/10)

  Make initial set of functions available to GENI researchers through the public ViSE portal. These functions will focus on EC2 leasing and control through the proxy. S3 and EBS will follow in early Year 2 as detailed below. (9/30/10)

• Milestone: DICLOUD: S2.k POC to GENI response team

  Due in 7 months (09/30/10)

  Provide POC to GENI Prototype Response and Escalation team. (9/30/10)

• Milestone: DICLOUD: S2.l POC to GENI security team

  Due in 7 months (09/30/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (9/30/10)

• Milestone: DICLOUD: S2.m Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan for Spiral 2. (9/30/10)

• Milestone: GMOC: S2.e Prototype S2 data sharing system

  Due in 7 months (09/30/10)

  0%

  Closed tickets:

  0

  Active tickets:

  1

  Complete Spiral 2 prototype data sharing system. Complete implementation and testing and put prototype data sharing in place for all projects identified in milestone S2.a Prototyping Plan. Data collected will include either the full set of required data in the Common Operational Dataset document or a subset of critical data, depending on each project's capabilities, and the discussions in milestone S2.a.

• Milestone: GMOC: S2.f Prototype multi-cluster GENI-wide visualization

  Due in 7 months (09/30/10)

  Prototype multi-cluster GENI-wide visualization. Generate a prototype GENI map that visualizes multiple clusters at a time, in order to show integration within and between clusters, and the activity of slices across clusters.

• Milestone: IGENI: S2.i Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan required for Spiral 2. (9/30/10)

• Milestone: IMF: S2.i First release of IMF and SILO software

  Due in 7 months (09/30/10)

  Finish development and deliver a v1.0 version of the IMF and SILO software. (9/30/10)

• Milestone: IMF: S2.j Contribution to GENI outreach plan

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan for Spiral 2. (9/30/10)

• Milestone: InfoSubstrate: S2.b V2.0 Information plane system design issues

  Due in 7 months (09/30/10)

  Updated version of document that incorporates comments on previous version and new issues discovered since publication of the previous version.

• Milestone: KGENI: S2.g Playbook 2.0 Review Complete

  Due in 7 months (09/30/10)

  Playbook review by GPO, GENI projects related to operations and security, and other interested parties

• Milestone: LAMP: S2.e V2.0 of perfSONAR on ProtoGENI

  Due in 7 months (09/30/10)

  Complete LAMP framework prototype released. Deliver software, documentation and user manual.

• Milestone: LAMP: S2.h Evaluation report

  Due in 7 months (09/30/10)

  Evaluate perfSONAR on ProtoGENI (ease of use, measurement system overhead, etc).

• Milestone: LEARN: S2.e Move broker to clearinghouse

  Due in 7 months (09/30/10)

  Move broker to Cluster D clearinghouse, and make control of L2 (VLAN) connections in LEARN available via the ORCA control framework to other GENI users. (9/30/10)

• Milestone: LEARN: S2.f POC to GENI response team

  Due in 7 months (09/30/10)

  Provide POC to GENI Prototype Response and Escalation team. (9/30/10)

• Milestone: LEARN: S2.g POC to GENI security team

  Due in 7 months (09/30/10)

  Provide POC to Security team. (9/30/10)

• Milestone: LEARN: S2.l Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan for Spiral 2. (/30/10)

• Milestone: MMOGpENI: S2.a report

  Due in 7 months (09/30/10)

  A final report that includes discussion of (1) how to best expand GpENI internationally, given that it does not have international optical connectivity; (2) how to use international research networks (including JANET, GEANT2, and NORDUnet) to run GpENI infrastructure, as well as what is feasible beyond tunneling; and (3) the possibility of getting optical (or virtual optical) connectivity into selected international GpENI node clusters with the assistance of Internet2, DANTE, GEANT2, JANET, and SWITCH. The work will be done coordinating and sharing information with the other GENI projects that are studying federation.

• Milestone: NETKARMA: S2.f experience report

  Due in 7 months (09/30/10)

  Deliver document on experience in gathering information from experimental tools with any suggestions for additional information that could be collected that would enhance the provenance record.

• Milestone: NETKARMA: S2.g user doc

  Due in 7 months (09/30/10)

  Deliver netKarma User Document

• Milestone: NETKARMA: S2.h prototype

  Due in 7 months (09/30/10)

  Deliver persistent prototype of provenance service hosted at Indiana University that collects and serves experiment layer provenance. Prototype demo, which will have support for Raven and GUSH, will be held at GEC-9 with venue/process for soliciting user feedback.9/30/10

• Milestone: OFNOX: S2.l Improve system and regression test support

  Due in 7 months (09/30/10)

  Improve system and regression test support in NOX software.

• Milestone: OFNOX: S2.m Publish feature list for 2011 releases

  Due in 7 months (09/30/10)

  Publish NOX feature list with technical descriptions for software releases planned for 2011.

• Milestone: OKGEMS: S2.f Move broker to clearinghouse

  Due in 7 months (09/30/10)

  Move ORCA broker to the RENCI clearinghouse. (9/30/10)

• Milestone: OKGEMS: S2.g Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan required for Spiral 2. (9/30/10)

• Milestone: ORCAAUG: S2.c Rel 2.3_2 ORCA code to projects

  Due in 7 months (09/30/10)

  Implement and provide release 2.3 of ORCA code to other Cluster D projects, including the following features: (9/30/10) 1) Computational substrate ontology 3: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Initial ontology for edge computational substrates. 2) Measurement substrate ontology 3: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Initial ontology for substrate measurement capabilities. 3) Ontology integration 3: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Integration of ontology resource handling mechanisms into ORCA core. 4) Policy development 3: Resource description mechanisms and policies. Ontology-based resource description mechanisms integrated into ORCA core. Development of resource provisioning policies based on ontologies. 5) In-depth Shibboleth integration 3: Identity management. Establish use of identity management system to authenticate principals and portals. Integrate with Shibboleth at the level of service manager and user tools. 6) Note: Additional release 2.3 features will be provided by ORCA/BEN project.

• Milestone: ORCAAUG: S2.d Rel 2.x_1 ORCA code, docs to GPO

  Due in 7 months (09/30/10)

  Deliver release 2.x ORCA code and documentation to GPO. (9/30/10)

• Milestone: ORCABEN: S2.c Rel 2.3_1 ORCA code to projects

  Due in 7 months (09/30/10)

  Implement and provide release 2.3 of ORCA code to other Cluster D projects, including the following features: (9/30/10) 1) Better packaging 3: Simplified installation, config script auto-configuration, simple usability extensions, simplified certificate management. 2) Lease feature extensions 3: Enable fully implemented cancellations of leases prior to their expiration. 3) Note: Additional release 2.3 features will be provided by ORCA augmentation project.

• Milestone: ORCABEN: S2.d Rel 2.x_1 ORCA code, docs to GPO

  Due in 7 months (09/30/10)

  Deliver release 2.x ORCA code and documentation to GPO (9/30/10)

• Milestone: ORCABEN: S2.e Operate, extend clearinghouse

  Due in 7 months (09/30/10)

  Operate and extend as needed Cluster D (ORCA) clearinghouse at RENCI. (10/1/09-9/30/10)

• Milestone: ORCABEN: S2.f GMOC access to clearinghouse

  Due in 7 months (09/30/10)

  Collaborate with GMOC operations group on providing access to Cluster D clearinghouse operating data. (10/1/09-9/30/10)

• Milestone: ORCABEN: S2.o Contribution to GENI outreach

  Due in 7 months (09/30/10)

  Specific contribution to GENI outreach plan required for Spiral 2: (10/1/09-9/30/10)

• Milestone: OnTime: S2.g: Validation and refinements to OnTimeMeasure-GENI service

  Due in 7 months (09/30/10)

  System and documentation updates.

  - Software updates, consulting and support for ProtoGENI early experimentation users and GMOC operations; updates include bug fixes, refinements such as improved log generation for debugging, and exception cases handling

• Milestone: PLFED: S2.d demo gui

  Due in 7 months (09/30/10)

  Demonstrate GUI-based interface as alternative to SFI command-line interface.

• Milestone: PrimoGENI: S2.g: Aggregate 2.0 plan review

  Due in 7 months (09/30/10)

  Complete review of PrimoGENI 2.0 design document by ProtoGENI, GPO and any other interested parties.

• Milestone: S3MONITOR: S2.h V0.3 release

  Due in 7 months (09/30/10)

  V0.3 of measurement system released for use by ProtoGENI experimenters.

  Software update to include bug fixes, performance and usability improvements, etc.. Updated documentation and user manual.

• Milestone: S3MONITOR: S2.i V1.0 Spec

  Due in 7 months (09/30/10)

  Specification for measurement system V1.0.

  Includes specification of policy-based measurement scheduling and rspec extensions for measurement data.

• Milestone: SECUREUPDATES: S2.h client lib trust design

  Due in 7 months (09/30/10)

  Deliver a design document for client library selective trust delegation and key management.

• Milestone: SECUREUPDATES: S2.i repo lib trust design

  Due in 7 months (09/30/10)

  Deliver a design document for repository library selective trust delegation and key management.

• Milestone: SPP: S2.b rspec

  Due in 7 months (09/30/10)

  Develop RSpec for SPPs, enabling users to reserve fast paths and SPP interface bandwidth across nodes in an integrated way. 9/30/10

• Milestone: SPP: S2.i ops support

  Due in 7 months (09/30/10)

  Provide operational support for deployed systems throughout year. 9/30/10

• Milestone: SPP: S2.l transition plan

  Due in 7 months (09/30/10)

  Develop plans for transitioning operational support to GMOC. 9/30/10

• Milestone: SPP: S2.o interfacedoc

  Due in 7 months (09/30/10)

  Deliver interface documentation for version 1 of SPP component manager software. 9/30/10

• Milestone: VMI-FED: S2.f scale up demo

  Due in 7 months (09/30/10)

  9/30/10 - Delivery of initial VMI functionality on cluster nodes at cluster scale. (Demo at GEC9)

• Milestone: VMI-FED: S2.g analysis doc

  Due in 7 months (09/30/10)

  9/30/10 - Finalize and post initial Federation Framework Analysis document for feedback from GENI researchers, personnel and selected potential federation partners. (Promote at GEC9)

• Milestone: WIMXBBN: S2.a WiMax base station installed and operational

  Due in 7 months (09/30/10)

  WiMax? base station installed and operational using ORBIT Management Framework (OMF), dependent on timely receipt of WiMAX base station and software from Rutgers. (9/30/10)

• Milestone: WIMXCOLUM: S2.a Redesign remote management/power system

  Due in 7 months (09/30/10)

  Redesign remote management/power system at Boulder to support WiMax? equipment. (9/30/10)

• Milestone: WIMXCOLUM: S2.a WiMax base station installed and operational

  Due in 7 months (09/30/10)

  WiMax? base station installed and operational using ORBIT Management Framework (OMF), dependent on timely receipt of WiMAX base station and software from Rutgers. (9/30/10)

• Milestone: WIMXCOLUM: S2.b Install the WiMax base station kit and antennas

  Due in 7 months (09/30/10)

  Install the WiMax? base station kit and antennas, if available. (9/30/10)

• Milestone: WIMXUWI: S2.b Implementation and deployment of user trial nodes enhanced with Mobile Access Router (MAR)

  Due in 7 months (09/30/10)

  Implementation and deployment of user trial nodes enhanced with Mobile Access Router (MAR).

• Milestone: SPPI2: S2.a Support SPP I2 nodes

  Due in 7 months (10/01/10)

  Provide space and power for, and help support, the nodes recently installed in Salt Lake City, Kansas City, and Washington DC.

• Milestone: DOME: S2.l POC to GENI security team

  Due in 8 months (11/01/10)

  Provide POC to Security team and provide input for security review in Spiral 2. (11/1/09-3/1/10)