Changes between Version 2 and Version 3 of PlasticSlices


Ignore:
Timestamp:
04/27/11 10:08:31 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlasticSlices

    v2 v3  
    11[[PageOutline]]
    22
    3 = 1. Introduction =
     3= GENI Plastic Slices =
    44
    5 This is the first project in the Meso-Scale Campus Experiments plan, for evolving meso-scale experiments between now and GEC 12. The overarching purpose is to set shared campus goals, and to agree on a schedule and resources to support experiments. This first project, dubbed "Plastic Slices", is an effort to run ten (or more) GENI slices continuously for multiple months -- not merely for the sake of having ten slices running, but to gain experience managing and operating production-quality GENI resources.
     5The GENI Plastic Slices Project has a goal to advance meso-scale experiments to operate with production-quality GENI resources, while gaining experience in managing such an environment. The Plastic Slices project sets shared campus goals within an agreed upon schedule(by GEC12).  This project plans to run ten (or more) GENI slices continuously for multiple months.
    66
    7 Experiments are currently coming from three sources:
     7= Project Plan =
    88
    9  * Outreach tutorials and workshops sponsored by NSF and BBN
    10  * IT and research staff at the participating universities
    11  * GENI early operations trials
     9The Plastic Slices Project overall plan for running and managing simultaneous slices is captured in the [http://groups.geni.net/geni/wiki/PlasticSlices  Plastic Slices Project Plan] document. (replace with wiki:PlasticSlices/ProjectPlan)
    1210
    13 Rather than wait for all experiment requirements to be final, this document focuses on detailed requirements for running and managing multiple simultaneous slices for long-term experiments. These requirements are common for current suggested experiments from all three sources. We expect that much of what we do for this project will be reusable by other experiments, shortening the startup time for new experimenters. We also expect that campuses will actively manage their project resources, giving them more hands-on experience and a relatively low-risk way for campuses to try out production procedures for GENI experiments.
    1411
    15 Results from this project will be presented to the GENI community at GEC 11 (Jul 26 - 29, 2011). We expect to complete the next meso-scale experiment project plan in May, covering follow-on experimenter requirements for GEC 12 (Nov 15 - 17, 2011) in more detail.
     12= Requirements tracking =
    1613
    17 This document is a draft, and proposes schedules and activities not yet approved by participants. Please provide feedback and changes by April 20th, 2011.
     14The [http://groups.geni.net/geni/wiki/PlasticSlices#a2.1.Experimenterrequirements Experimenters Requirements] detailed in the project plan are tracked in the Plastic Slices effort in the [wiki:PlasticSlices/RequirementsTracking Requirements Tracking] page.
    1815
    19 = 2. Purpose and scope =
     16= Baseline Evaluation Plan =
    2017
    21 During Spiral 3, campuses have been expanding and updating their !OpenFlow deployments. All campuses have agreed to run a GENI AM API compliant aggregate manager, and to support at least four multi-site GENI experiments, by GEC 12. This lays the foundation for GENI to continuously support and manage multiple simultaneous slices that contain resources from GENI AM API compliant aggregates with multiple cross-country layer 2 data paths.  (The [wiki:GeniApi GENI API] page has more information about what it means to be a "GENI AM API compliant aggregate.") This campus infrastructure can support the transition from building GENI to using GENI continuously in the meso-scale infrastructure. Longer-term, it can also support the transition to at-scale production use in 2012, as originally proposed by each campus.
     18Details for each baseline evaluation are captured in the [wiki:PlasticSlices/BaselineEvaluation Baseline Evaluation Plan].  The Baselines Evaluations are designed to capture progress throughout the Plastic Slices project. Each baseline captures environment, evaluation details, evaluation criteria and a baseline report. 
    2219
    23 This project will investigate technical issues associated with managing multiple slices for long-term experiments, and will also try out early operations procedures for supporting those experiments.  We expect to have early results from both efforts to share at GEC 11, and to use the procedures, software, and tools from this project to support more live experiments from new GENI researchers at GEC 12.
     20= Environment =
    2421
    25 == 2.1. Experimenter requirements ==
     22Capturing the definition of the environment used to validate the baselines scenarios  is a crucial part of this activity.  A complete definition will be captured to facilitate the repeatability of the baseline scenario in the Quality Assurance step to be performed by Georgia Tech. As part of the effort, the following will be captured:
     23    * [wiki:PlasticSlices/SliceSnapshots Slice Snapshots] - A slice-centric record of the experiment environment will be captured at each baseline.
     24    * [wiki:PlasticSlices/SiteDiagrams Site Diagrams] - A site-centric capture the topology used at each site.
     25    * [wiki:PlasticSlices/SliceDiagrams Slice Diagrams] - A slice-centric capture each experiment topology.
    2626
    27 Requirements from GENI experimenters are a major input to the general technical requirements that drive the overall scope for meso-scale experiments. In this project, we intend to cover these requirements:
     27As the Plastic Slices project evolves, the GPO will generate recommendations for contributors managing campus sites for the [wiki:PlasticSlices/MonitoringRecommendations Monitoring], [wiki:PlasticSlices/MyPLCRecommendations MyPLC], and [wiki:PlasticSlices/OFRecommendations OpenFlow] areas.  The GPO will also define [wiki:PlasticSlices/ExperimenterRecommendations Experimenters recommendations] and provide examples for potential types of experiments.
    2828
    29  * Include resources from multiple interoperating aggregates in a slice.
    30  * Allow experimenters to control end-to-end data planes supporting a slice.
    31  * Allow multiple experiment team members to share resources in a slice.
    32  * Operate experiments continuously for three or more months.
    33  * Operate many experiments simultaneously.
    34  * Support non-IP protocol experiments.
    35  * Support comparison of IP and non-IP path results within an experiment.
    36  * Support video and audio applications.
     29= Project Status =
    3730
    38 We intend to address these requirements in the next meso-scale experiment plan:
     31Detailed status for major areas of the Plastic Slices project can be found in the following pages:
    3932
    40  * Support control and data connections from mobile endpoints.
    41  * Support use of cloud services with GENI slices.
    42  * Support up to 1000 hosts in an experiment.
    43  * Support BGPMux in an experiment.
    44  * Support experimenter-controlled load sharing.
    45  * Support bandwidth enforcement (QoS-like functions).
     33||[http://groups.geni.net/geni/wiki/PlasticSlices/MonitoringStatus Monitoring Status]|| Monitoring status and recommendations ||
     34|| ||
     35||[http://groups.geni.net/geni/wiki/PlasticSlices/MyplcStatus MyPLC Status]|| MyPLC configuration status and recommendations ||
     36|| ||
     37|| [http://groups.geni.net/geni/wiki/PlasticSlices/OFStatus OF Status] ||  OF configuration status and recommendations ||
    4638
    47 Some of these requirements may not be feasible to meet until after 2012.
     39Each Baseline Evaluation Status includes description of the test topology, traffic profiles, tools used, the criteria used to determine success and any assumptions made. This table provides the the "environment" (Slice Snapshots), the "plan" (Baseline Evaluation Details) and the "results" (Baseline Evaluation Status) for each baseline in the Plastic Slices project:
     40||                || '''Environment'''|| ''' Plan''' || '''Results'''||
     41|| ||
     42|| '''Baseline1'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline1 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline1 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline1 Evaluation Status] || 
     43|| ||
     44|| '''Baseline2'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline2 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline2 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline2 Evaluation Status] ||
     45|| ||
     46|| '''Baseline3'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline3 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline3 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline3 Evaluation Status] ||
     47|| ||
     48|| '''Baseline4'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline4 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline4 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline4 Evaluation Status] ||
     49|| ||
     50|| '''Baseline5'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline5 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline5 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline5 Evaluation Status] ||
     51||
     52|| '''Baseline6'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline6 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline6 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline6 Evaluation Status] ||
     53|| ||
     54|| '''Baseline7'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline7 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline7 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline7 Evaluation Status] ||
     55|| ||
     56|| '''Baseline8'''|| [wiki:PlasticSlices/SliceSnapshots#Baseline8 Slices Snapshot]|| [wiki:PlasticSlices/BaselineEvaluation#Baseline8 Evaluation Details] || [wiki:PlasticSlices/BaselineStatus#Baseline8 Evaluation Status] ||
    4857
    49 In addition to the campuses and !OpenFlow software support teams, this project will include the GMOC and NCSA, who are implementing national GENI operations procedures and tools to support campuses where needed. For example, campuses can use the GMOC Emergency Stop procedure to request an experiment shut-down on infrastructure the campus does not directly control. This approach will improve both technical and operations support for GENI in parallel.
    5058
    51 General operations requirements for the meso-scale experiments include the following requirements from campuses, operators, and experimenters:
     59[[BR]]
    5260
    53  * Ensure that GENI experiments are compatible with campus security policies.
    54  * Allow campuses to manage access to the resources they contribute to GENI.
    55  * Ensure that the level of effort required from campus IT staff to manage GENI experiments is reasonable, compared to similar research programs.
    56  * Make experiments easier to set up and take down than they were at GEC9.
    57  * Make experiments easier to change (add/delete resources, change data paths) than they were at GEC9.
    58  * Try out operations procedures and policies that can transition to production at-scale use.
     61= Reports =
    5962
    60 This project covers all of these operations requirements, but we expect that each will also need further work in the next meso-scale experiment plan, and some may not be feasible until after 2012.
     63While periodic updates are to be generated for each baseline to capture [wiki:PlasticSlices/BaselineStatus status] progress against the planned activities, there are also three interim reports planned to be posted to the egeni-trials@lists.stanford.edu mail list and to [wiki:PlasticSlices/Reports Plastic Slices Reports] page.  The interim reports to be published will be at the following dates:
    6164
    62 The rest of this document covers only plans for this project; other projects in the overall Meso-Scale Campus Experiments plan will be documented separately, beginning with the GEC12 research experiments plan in May.
     65|| '''Interim Report''' || '''Related Activities'''   ||
     66|| ||
     67||[wiki:PlasticSlices/Reports#Interimreport2011-05-09 2011-05-09 ] ||  Report before Baseline 1, when BBN finalizes the initial slice configuration (all eight campuses, running ten artificial experiments).  ||
     68||[wiki:PlasticSlices/Reports#Interimreport2011-06-06 2011-06-06 ] || At the completion of baseline 4, after BBN replaces some artificial experiments with real experiments, and revises the slice/campus/experiment configuration as needed.||
     69||[wiki:PlasticSlices/Reports#Interimreport2011-06-27 2011-06-27 ] || At the completion of baseline 8, after BBN replaces more artificial experiments with real experiments, and revises the slice/campus/experiment configuration as needed. ||
    6370
    64 == 2.2. Goals ==
     71Additionally a final report will be presented at GEC11 which will also be available in the [wiki:PlasticSlices/FinalReport Final Evaluation Report] page.
    6572
    66 This project aims to accomplish the following technical and production goals:
    6773
    68  * Verify that multiple simultaneous slices and end-to-end data paths can operate within GENI over a long period of time (compared to previous GENI activities).
    69  * Verify that these slices can support technical requirements gathered from potential GENI experimenters. (To accommodate the proposed timeline, these slices will initially run artificial experiments that are meant to be representative of expected actual experiments. The artificial experiments will be replaced by real experiments as real experiments become ready.)
    70  * Determine whether the aggregates, tools, and procedures used in this project will be able to support the number of real slices and experiments expected in GENI through the end of 2011.
    71  * Identify and correct ways in which GENI is still difficult for real experimenters to use.
    72  * Gain experience operating GENI resources while GENI is still at a relatively small size.
    73  * Verify that campuses can support experiments with little (if any) assistance from Stanford and BBN.
    74  * Verify implementations of GMOC procedures, such as Emergency Stop.
    75  * Verify that campuses can support the aggregates, tools, and procedures needed to support experiments in keeping with their campus security policies and the GENI Aggregate Provider Agreement.
    76  * Gather feedback from campuses to GMOC, NCSA, and BBN on the state of operations support for campuses.
    7774
    78 == 2.3. Resources ==
     75= Quality Assurance =
    7976
    80 This project will use the following GENI resources:
     77Any documents, procedures or guidelines that we generate as part of the hand-off to Georgia Tech for the Quality Assurance phase of this project will be captured here.
    8178
    82  * The [wiki:NetworkCore GENI network core], in Internet2 and NLR.
    83  * An !OpenFlow network at each of eight campuses, consistent with the recommended [wiki:OpenFlow/CampusTopology campus topology], connected to the GENI network core.
    84  * A GENI AM API compliant MyPLC aggregate at each of eight campuses, each with two or more hosts.
    85  * A GENI AM API compliant Expedient aggregate at each of eight campuses, managing the !OpenFlow network connecting the MyPLC hosts to the GENI network core.
    86  * Additional incidental resources to support monitoring and security.
    87 
    88 == 2.4. Participants ==
    89 
    90 Participants will include:
    91 
    92  * BBN, who will design and manage the project, gather and publish results, and provide GENI resources that slices will allocate and use.
    93  * Stanford, who will help design and manage the project, maintain the !OpenFlow-related software used by the slices, and provide GENI resources that slices will allocate and use.
    94  * Six additional campuses, who will provide GENI compute and network resources that slices will allocate and use. (Clemson, Georgia Tech, Indiana, Rutgers, Washington, and Wisconsin)
    95  * Two backbone providers, who will provide GENI network resources that slices will allocate and use. (Internet2 and NLR)
    96  * The GENI Meta Operations (GMOC) team at the Global Research Network Operations Center (GRNOC), who will implement and test nationwide operations procedures and tools to support campuses.
    97  * The National Center for Supercomputing Applications (NCSA), who will support GMOC and the campuses for security-related analyses and procedures.
    98 
    99 Additional participants may be added as interest and availability permit.
    100 
    101 = 3. Information sharing =
    102 
    103 Information about the project will be shared via the GENI wiki, various software repositories, and various mailing lists.
    104 
    105 == 3.1. The GENI wiki ==
    106 
    107 http://groups.geni.net/geni/wiki/PlasticSlices is the canonical location of this project plan. This page will contain links to additional pages relevant to this project.
    108 
    109 == 3.2. Software repositories ==
    110 
    111 The project will use the following software:
    112 
    113  * Software that provides GENI resources:
    114    * HP !OpenFlow firmware 2.02v, available by special arrangement from HP
    115    * NEC !OpenFlow firmware 11.1.C.Ae, available by special arrangement from NEC
    116    * Indigo !OpenFlow firmware 2011.04.07, available from http://www.openflowhub.org/display/Indigo/Indigo+-+Download+Page
    117    * !FlowVisor 0.7.2, source available from git://gitosis.stanford.edu/flowvisor.git, instructions for downloading binaries at http://www.openflow.org/wk/index.php/FlowVisor_run, maintained by Stanford
    118    * Expedient AM 4.0.2, instructions for downloading binaries at http://www.openflow.org/wp/deploy-expedient-oim/, maintained by Stanford
    119    * Expedient OIM 0.2.4.2, instructions for downloading binaries at http://www.openflow.org/wp/deploy-expedient-oim/, maintained by Stanford
    120    * MyPLC 0.5-rc14 on Fedora 8, RPMs available from http://build.planet-lab.org/planetlab/f8/planetlab-f8-i386-5.0-rc14/, maintained by PlanetLab
    121 
    122  * Software used to conduct experiments and gather results:
    123    * iperf 2.0.4, http://iperf.sourceforge.net/
    124    * Ganglia 3.0.7, home page at http://ganglia.sourceforge.net/
    125    * various !OpenFlow controllers
    126    * other software we run within the slices themselves
    127 
    128 We won't necessarily know the version numbers of all of the software in this latter category until we complete each baseline -- especially true for experimental tools and controllers -- but the versions of all of the software used to accomplish each baseline will be captured before the baseline is considered complete.
    129 
    130 If new versions of these packages are released, this document may be updated to use them.
    131 
    132 == 3.3. Mailing lists ==
    133 
    134 The following mailing lists will be used to share information about the project:
    135 
    136  * egeni-trials@lists.stanford.edu (!OpenFlow Campus Trials announcements)
    137  * response-team@geni.net (GENI resource providers)
    138  * gpo-infra@geni.net (BBN GPO infrastructure team)
    139  * stanford-deployment@openflowswitch.org (Stanford !OpenFlow deployment team)
    140  * clemson-deployment@openflowswitch.org (Clemson !OpenFlow deployment team)
    141  * gatech-deployment@openflowswitch.org (GT !OpenFlow deployment team)
    142  * indiana-deployment@openflowswitch.org (Indiana !OpenFlow deployment team)
    143  * rutgers-deployment@openflowswitch.org (Rutgers !OpenFlow deployment team)
    144  * washington-deployment@openflowswitch.org (Washington !OpenFlow deployment team)
    145  * wisconsin-deployment@openflowswitch.org (Wisconsin !OpenFlow deployment team)
    146  * geni-openflow@internet2.edu (Internet2 !OpenFlow deployment team)
    147  * openflow@nlr.net (NLR !OpenFlow deployment team)
    148  * gmoc@grnoc.iu.edu (GMOC team)
    149 
    150 == 3.4. Real-time chat ==
    151 
    152 At times when real-time online communications would be valuable (such as when testing Emergency Stop), we'll use a channel on the BBN Jabber server (plastic-slices@conference.j.ir.bbn.com) to chat.
    153 
    154 = 4. Description of work =
    155 
    156 This section contains a timeline of the work to be performed for the project, and more details about the various parts.
    157 
    158 == 4.1. Timelines ==
    159 
    160 These timelines describe when various project-related tasks will be completed. All dates are for the completion for the work.
    161 
    162 === 4.1.1. Campus resources ===
    163 
    164 The campus participants will prepare the resources that the slices and experiments will use. (The first two items have already been done, but are included here for completeness.)
    165 
    166 || 2011-04-05 || BBN and Stanford agree on a campus !OpenFlow topology to recommend to campus participants. ||
    167 || 2011-04-06 || BBN and Stanford communicate to campuses our desires for this topology and some resources. ||
    168 || 2011-04-25 || Three campuses are ready with the recommended topology and resources. (BBN, Stanford, and Clemson) ||
    169 || 2011-05-02 || Six campuses are ready with the recommended topology and resources. (add Rutgers, Wisconsin, and Washington) ||
    170 || 2011-05-09 || All campuses are ready with the recommended topology and resources. (add Georgia Tech and Indiana) ||
    171 || 2011-05-09 || BBN and Stanford test all campus topologies and resources. ||
    172        
    173 === 4.1.2. Backbone resources ===
    174 
    175 The backbone participants will also prepare inter-campus resources that the slices and experiments will use.
    176 
    177 || 2011-04-25 || BBN and GMOC engineer and implement all appropriate VLANs in NLR and I2, including peering between the two providers. ||
    178 || 2011-04-25 || I2 and NLR are ready to provide and support !OpenFlow resources. ||
    179 
    180 === 4.1.3. Slices ===
    181 
    182 Over the course of the project, we'll create slices in which to run the various experiments.
    183 
    184 || 2011-04-25 || BBN creates ten initial slices, including resources at three campuses, running the simple Hello GENI experiment. ||
    185 || 2011-05-02 || BBN modifies the initial ten slices to include subsets of six campuses and to run different artificial experiments. ||
    186 || 2011-05-09 || BBN finalizes the initial slice configuration (all eight campuses, running ten artificial experiments). ||
    187 || 2011-06-06 || BBN replaces some artificial experiments with real experiments (pending experimenter availability), and revise the slice/campus/experiment configuration as needed. ||
    188 || 2011-06-27 || BBN replaces more artificial experiments with real experiments (pending experimenter availability), and revise the slice/campus/experiment configuration as needed. ||
    189 
    190 === 4.1.4. Baselines ===
    191 
    192 We'll use those slices to run some experiments, and establish a series of baselines to demonstrate progress throughout the project.
    193 
    194 || 2011-05-16 || Baseline 1 - Ten slices, each moving at least 1 GB of data per day, for 24 hours. ||
    195 || 2011-05-23 || Baseline 2 - Ten slices, each moving at least 1 GB of data per day, for 72 hours. ||
    196 || 2011-05-31 || Baseline 3 - Ten slices, each moving at least 1 GB of data per day, for 144 hours. ||
    197 || 2011-06-03 || Baseline 4 - Ten slices, each moving at least 1 Mb/s continuously, for 24 hours. ||
    198 || 2011-06-07 || Baseline 5 - Ten slices, each moving at least 10 Mb/s continuously, for 24 hours. ||
    199 || 2011-06-13 || Baseline 6 - Ten slices, each moving at least 10 Mb/s continuously, for 144 hours. ||
    200 || 2011-06-20 || Baseline 7 - Perform an Emergency Stop test while running ten slices, each moving at least 10 Mb/s continuously, for 144 hours. ||
    201 || 2011-06-20 || Baseline 8 - Create one slice per second for 1000 seconds; then create and delete one slice per second for 24 hours. ||
    202 || 2011-06-27 || BBN defines additional July baselines. ||
    203 
    204 === 4.1.5 Monitoring and reporting ===
    205 
    206 Throughout the project, we'll monitor the slices and resources, and report on the results.
    207 
    208 || 2011-04-18 || GMOC and BBN complete and test the monitoring data API. ||
    209 || 2011-04-25 || GMOC is ready to receive monitoring data from campuses. ||
    210 || 2011-05-02 || BBN is automatically submitting monitoring data from MyPLC and !OpenFlow aggregates to GMOC. ||
    211 || 2011-05-02 || BBN is able to obtain monitoring data from GMOC. ||
    212 || 2011-05-02 || GMOC completes emergency contact database. ||
    213 || 2011-05-09 || All campuses are automatically submitting monitoring data from MyPLC and !OpenFlow aggregates to GMOC. ||
    214 || 2011-05-09 || NLR and I2 are automatically submitting monitoring data from !OpenFlow aggregates to GMOC. ||
    215 || 2011-05-09 || BBN publishes interim results to egeni-trials@lists.stanford.edu and the GENI wiki. ||
    216 || 2011-06-06 || BBN publishes interim results to egeni-trials@lists.stanford.edu and the GENI wiki. ||
    217 || 2011-06-27 || BBN publishes interim results to egeni-trials@lists.stanford.edu and the GENI wiki. ||
    218 || 2011-07-26 || BBN presents final results at GEC 11, and publish them to the GENI wiki. ||
    219 
    220 == 4.2. Participant roles ==
    221 
    222 These sections describe the work that each of the participants will perform, broken out by participant. Some of the work is ongoing throughout the project, and thus isn't tied to a specific point in the timeline.
    223 
    224 === 4.2.1. Campuses ===
    225 
    226 All eight campuses will provide and support some GENI resources:
    227 
    228  * Configure a local !OpenFlow network consistent with the recommended [wiki:OpenFlow/CampusTopology campus topology], connected to the [wiki:NetworkCore GENI network core].
    229  * Operate a GENI AM API compliant MyPLC aggregate with two or more hosts.
    230  * Provide a GENI AM API compliant Expedient aggregate managing the !OpenFlow network connecting the MyPLC hosts to the GENI network core.
    231  * Create a [wiki:GeniAggregate GENI aggregate information page] for each of those aggregates.
    232  * Submit monitoring data for each of those aggregates using the API the GMOC develops, as it beomes available.
    233  * For each of those aggregates, agree to the the [attachment:"wiki:ComprehensiveSecurityPgm:Aggregate Provider Agreement v3.pdf" GENI Aggregate Provider Agreement]. (Or discuss with BBN if this is problematic.)
    234  * Provide best-effort support to keep these resources up and running and available, testing operations and security procedures, and responding to outages.
    235  * Test operations and security procedures for supporting these resources and responding to outages on a best-effort basis.
    236 
    237 === 4.2.2. Internet2 and NLR ===
    238 
    239 Internet2 and NLR will provide and support some GENI resources:
    240 
    241  * Provide an Expedient aggregate managing the !OpenFlow resources in the Internet2 portion of the GENI network core.
    242  * Create an [wiki:GeniAggregate GENI aggregate information page] for it.
    243  * Submit monitoring data for it using the API the GMOC develops, as it beomes available.
    244  * Agree to the the [attachment:"wiki:ComprehensiveSecurityPgm:Aggregate Provider Agreement v3.pdf" GENI Aggregate Provider Agreement]. (Or discuss with BBN if this is problematic.)
    245  * Provide best-effort support to keep these resources up and running and available.
    246  * Test operations and security procedures for supporting these resources and responding to outages on a best-effort basis.
    247 
    248 === 4.2.3. BBN ===
    249 
    250 In addition to the items in section 4.2.1, BBN will:
    251 
    252  * Write and maintain this project plan, including communication with other participants about their requirements, tracking whether requirements are being met, etc.
    253  * Lead the design of the experiments to run in each of the slices, and ensure that they run continuously, with at least some detectable activity at least daily.
    254  * Obtain and review the monitoring data submitted by campuses to GMOC.
    255  * Support campuses in setting up and maintaining their !OpenFlow resources.
    256  * Support campuses in setting up and maintaining their MyPLC resources.
    257  * Support campuses in setting up a feed of monitoring data to the GMOC.
    258  * Support experimenters in setting up and running their experiments, once we begin to replace the initial artificial experiments with real ones.
    259  * Provide and support a GENI AM API compliant ProtoGENI aggregate with four hosts.
    260 
    261 === 4.2.4. Stanford ===
    262 
    263 In addition to the items in section 4.2.1, Stanford will:
    264 
    265  * Support campuses in setting up and maintaining their !OpenFlow resources.
    266  * Maintain the !FlowVisor and Expedient software used by the slices.
    267  * Respond to software bug reports in a timely fashion (first response within three business days, resolution within ten business days if possible).
    268 
    269 === 4.2.5. GMOC ===
    270 
    271 GMOC will:
    272 
    273  * Design, document, and implement an API which campuses can use to submit monitoring data.
    274  * Provide and maintain a host which all participating campuses can use to submit monitoring data using that API.
    275  * Provide and maintain a host and API which BBN (and other participants) can use to obtain the monitoring data that campuses have submitted.
    276  * Build and populate a GENI operational contact database that includes all project participants.
    277  * Implement and test the Emergency Stop procedure with all project participants.
    278  * Respond to monitoring outages within one business day.
    279 
    280 === 4.2.6. NCSA ===
    281 
    282 NCSA will:
    283 
    284  * Review operations security plans for the project and recommend appropriate procedures to participants as necessary.
    285  * Carry out the GENI Legal, Law Enforcement and Regulatory Representative functions for the project as necessary.
    286  * Investigate and try to resolve any issues campuses raise with the GENI Aggregate Provider Agreement.
    287 
    288 == 4.3. Baselines ==
    289 
    290 These technical baselines will demonstrate progress throughout the project. As each baseline is completed, BBN will capture system configuration and software version information, and the results of the baseline, for use in the various interim and final reports. (See the [wiki:GEC9_snapshots GEC 9 Plenary Demo Snapshots] page for examples.)
    291 
    292 If necessary, BBN will propose changes to the baselines to all participants, who should approve or reject the changes within three business days.
    293 
    294 Note that the 24-hour and 72-hour baselines may need to be repeated if early attempts have too many errors or failures. There isn't enough time in the schedule to repeat a 144-hour baseline unless it fails very early in the process.
    295 
    296 The goal is to complete each baseline with few (if any) errors or failures. If a baseline has too many errors or failures, BBN will either propose changes to the schedule to allow it to be repeated; or propose that we conclude that the baseline not be completed, and document why not.
    297 
    298 While completing Baselines 1 - 8, BBN will review the status of upcoming research experiments, and propose July baselines that help prepare the participants to support those experiments at GEC12.  We expect the July baselines will use a combination of real experiments and artificial ones.
    299 
    300 === 4.3.1. Baseline 1 ===
    301 
    302 Cause the experiment running in each slice to move at least 1 GB of data over the course of a 24-hour period. Multiple slices should be moving data simultaneously, but it can be slow, or bursty, as long as it reaches 1 GB total over the course of the day.
    303 
    304 The purpose of this baseline is to confirm basic functionality of the experiments, and stability of the aggregates.
    305 
    306 === 4.3.2. Baseline 2 ===
    307 
    308 Similar to the previous baseline, cause the experiment running in each slice to move at least 1 GB of data per day, but do so repeatedly for 72 hours.
    309 
    310 The purpose of this baseline is to confirm longer-term stability of the aggregates.
    311 
    312 === 4.3.3. Baseline 3 ===
    313 
    314 Similar to the previous baseline, cause the experiment running in each slice to move at least 1 GB of data per day, but do so repeatedly for 144 hours.
    315 
    316 The purpose of this baseline is to confirm even longer-term stability of the aggregates.
    317 
    318 === 4.3.4. Baseline 4 ===
    319 
    320 Cause the experiment running in each slice to move at least 1 MB/second continuously over the course of a 24-hour period (approximately 10 GB total).
    321 
    322 The purpose of this baseline is to confirm that an experiment can send data continuously without interruption.
    323 
    324 === 4.3.5. Baseline 5 ===
    325 
    326 Similar to the previous baseline, cause the experiment running in each slice to move at least 100 MB/second continuously over the course of a 24-hour period (approximately 1 TB total).
    327 
    328 The purpose of this baseline is to confirm that an experiment can send a higher volume of data continuously without interruption.
    329 
    330 === 4.3.6. Baseline 6 ===
    331 
    332 Similar to the previous baseline, cause the experiment running in each slice to move at least 100 MB/second continuously over the course of a 144-hour period.
    333 
    334 The purpose of this baseline is to confirm that an experiment can send a higher volume of data continuously without interruption, for several days running.
    335 
    336 === 4.3.7. Baseline 7 ===
    337 
    338 Repeat the previous baseline, but call an Emergency Stop while it's running, once per slice for each of the ten slices. Campuses will not be informed in advance about when each Emergency Stop will be called. There will be at least one instance of two simultaneous Emergency Stops, and at least one instance of a single campus being asked to respond to two simultaneous Emergency Stops. After each Emergency Stop, verify that all resources have been successfully restored to service.
    339 
    340 GMOC will define precisely how each Emergency Stop test will be conducted, and what resources will be stopped, presumably selecting a combination campus resources (e.g. disconnecting an on-campus network connection) and backbone resources (e.g. disabling a campus's connection to an inter-campus VLAN).
    341 
    342 The purpose of this baseline is to test Emergency Stop procedures.
    343 
    344 === 4.3.8. Baseline 8 ===
    345 
    346 This baseline creates new temporary slices, rather than using the existing ten slices, creating a thousand slices at the rate of one slice per second, and then continuing to delete and create a new slice every second, for 24 hours. Each slice will include resources at three campuses, selected randomly for each slice. Automated tools will confirm that the resources are available, e.g. by logging in to a host and running 'uname -a'.
    347 
    348 The purpose of this baseline is to confirm that many users can create slices and allocate resources at the same time.
    349 
    350 = 5. Reporting =
    351 
    352 BBN will produce three interim reports on the status of the project, and a final presentation at GEC 11 (a poster and/or a talk). Each report will include details of what all the resources and experiments were, and results including:
    353 
    354  * CPU usage on hosts and switches
    355  * memory usage on hosts
    356  * network usage on hosts and slivers
    357  * anything that caused anything to break or crash
    358  * any actual research results
    359 
    360 All reports will also be published to the GENI wiki.
    361 
    362 The timeline in section 4.1.5 has target dates for these reports.
    363 
    364 = 6. Quality assurance =
    365 
    366 To validate the proposition that these results are repeatable and well documented, Georgia Tech will reproduce baselines 1, 4, and 7 after GEC 11, using only documentation from the project, and provide a brief report to the participants on their experience.
    367 
    368 After BBN and other participants have reviewed Georgia Tech's report, and improved the documentation as needed, all other campuses will reproduce the same baselines and provide a similar report.
    369 
    370 Separately, BBN and GMOC will work with campuses to confirm that they can provision and release inter-campus VLANs.
    371 
    372 = 7. Risks =
    373 
    374 All participants must be available on the proposed timeline in order for the project to complete before GEC 11; this has not been verified. Availability around graduation and in the summer may be an issue for some participants.
    375 
    376 BBN and GMOC staff must complete needed tools and automation in time to monitor baselines; this has not been formally verified, although both organizations have said in the past that they expect to do this at some point.
    377 
    378 BBN and GMOC monitoring tools may be technically more difficult than anticipated; if tools are late, it may reduce the amount or nature of the information we can gather for each baseline.
    379 
    380 Stanford software developers must fix any bugs that prevent baselines from being completed promptly; availability and priority for this timeline has not been formally verified.
    381 
    382 Resource outages that are not addressed promptly could cause baselines to slip (e.g. hardware failure, site construction etc).
    383 
    384 Georgia Tech planned to use VMs for their MyPLC hosts, and we have not verified that the recommended campus !OpenFlow topology will work with VMs; if it doesn't, this could delay Georgia Tech's ability to provide resources.
    385 
    386 = 8. Revision history =
    387 
    388 Last updated on 2011-04-15 (Fri) at 14:42 EDT
    389 
    390 Click "Last Change" above for a full revision history
     79----