Changes between Initial Version and Version 1 of TemplateAggregatePage

01/26/11 12:45:59 (11 years ago)
Vic Thomas



  • TemplateAggregatePage

    v1 v1  
     1= Aggregate Name  =
     3Name of the aggregate.  [[Image(Federation-logo.png, 80)]] [GeniApprovedMeaning What does this mean?]
     5= Aggregate Overview =
     6|| Aggregate Resources || Brief description of the types and numbers of resources provided by the aggregate ||
     7|| Typical Experiments || Kinds of experiments aggregate might be suited for (wireless, security, etc) ||
     8|| Aggregate Web Page || Link to web page with information about the aggregate ||
     9|| Aggregate Status || Link to web page with current status (operational status, resources available, etc) ||
     10|| Layer 2 Connectivity || Which GENI backbones, if any, does this aggregate connect to ||
     12= Experimenter Support =
     13|| Guides and Documents || Links to docs/web pages describing how experimenters can request, program/configure and control aggregate resources. If at all possible help docs must include example experiments that use the aggregate resources. ||
     14|| Support || Link to experimenter support mailing list.  If available, information on mailing lists, newsgroups, blogs, call centers, etc. set up to support experimenters using aggregate resources. ||
     15|| Compatible tools || Experiment control tools, instrumentation tools and programming tools that are compatible with this aggregate. ||
     17= Using this Aggregate =
     18|| Clearinghouses Recognized || Links to web pages for clearinghouses recognized by this aggregate ||
     19|| Usage Policies || Aggregate specific policies on who can use resources, how many resources can be held for how long, etc. ||
     21= Aggregate Management =
     22|| Aggregate Operator || Name of organization that operates the aggregate manager. Link to URL of organization. ||
     23|| Resource Owner || Name(s) of the organization(s) that owns the aggregate resources, if different from the operator of the aggregate manager. If this information cannot be provided (such as with aggregates consisting of contributed resources), provide a statement about who provides the resources. ||
     24|| Operation POC || Contact information for person or team that operates this aggregate ||
     25|| Technical POC || Contact information for the PI or research team that develops/maintains the aggregate ||
     26|| Developer Links || Links to aggregate code base, design docs, developer mailing lists, etc. ||