Changes between Initial Version and Version 1 of OpenGENITemplateAggregate

05/27/14 10:43:44 (8 years ago)



  • OpenGENITemplateAggregate

    v1 v1  
     1= GRAM Aggregate  =
     3'''Enter aggregate name'''
     5This GENI Rack Aggregate Manager (GRAM) supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).
     7= GRAM Aggregate Overview =
     9|| Aggregate Manager URL || Enter Compute Aggregate: or FOAM: ||
     10|| Aggregate Manager URN || Enter Compute URN: or FOAM URN ||
     11|| Aggregate Manager Common Name || Enter site common name ||
     12|| Aggregate Resources || Compute nodes are Dell R620 server hosts, one of which is a control node and the rest are compute nodes from which VM's are served. Networking supported by a Dell Force10 S4810P !OpenFlow switch for L2 !OpenFlow-controlled data plan, plus Dell !PowerConnect 7048 for L3 control plane . ||
     13|| Typical Experiments || Provisions virtual machines into standalone (aggregate-internal) and stitched OF-controlled topologies including connections to both GENI and campus-internal resources.    ||
     14|| Sample RSpecs       || Enter link to sample RSpecs ||
     15|| Aggregate Status ||Enter list of supported monitoring for GRAM ||
     16|| Slice Authorities Recognized ||GENI Portal (,||
     17|| Usage Policies || A  [ GENI Recommended Use Policy] is available. Site should also add links here to their own usage policies.  ||
     18|| Layer 2 Connectivity || Enter list GENI core networks, if any, or other layer 2 networks that connect to this aggregate. ||
     20For Compute Aggregate or FOAM, <<Insert Site Diagram Here>> Make sure to note firewalls, if any, on both control (layer 3) and data paths.
     22For FOAM Aggregate only, insert <<Insert !OpenFlow Port List Here>>.  Otherwise remove this port list item for compute resource aggregate.
     27= Aggregate Management =
     29|| Aggregate Operator || Enter Site POC information, enter URL of organization.  This can be a person or (preferably) a mailing list that reaches all operators at a site. ||
     30|| Resource Owner     || Enter person that is responsible for site rack overall. This entry may also be same as POC. This is typically the person who would take responsibility for operating and maintaining the rack on behalf of their site, and who would make the final decision on policy that affects the rack such as usage policies.||
     31|| Technical POC      || Enter available mail lists for technical support.   ||
     32|| Developer Links    || Add links to Software pages,and developer mailing list ||