Changes between Initial Version and Version 1 of GeniAggregate/UCLAInstaGENIOpenFlow

07/17/14 14:45:00 (8 years ago)



  • GeniAggregate/UCLAInstaGENIOpenFlow

    v1 v1  
     1= InstaGENI Aggregate  =
     3'''UCLA InstaGENI !OpenFlow'''
     5This InstaGENI aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).
     7= InstaGENI Aggregate Overview =
     9|| Aggregate Manager URL || ||
     10|| Aggregate Manager URN || ||
     11|| Aggregate Manager Common Name || ucla-ig-of ||
     12|| Aggregate Resources || An InstaGENI aggregate includes 5 Hosts (3 VM Servers and 2 dedicated PCs) that can load experimenter specified OS images. Racks also support !OpenFlow topologies, usually including extensions onto campus !OpenFlow networks.  Rack servers are HP !ProLiant DL380p Gen8. ||
     13|| Typical Experiments || InstaGENI provides a controllable, predictable, and repeatable network environment. Experimenters can get virtual machines or dedicated PCs on which they have full "root" access, run available operating systems of their choice, and connect nodes in an arbitrary topology that can support !OpenFlow.  ||
     14|| Sample RSpecs       || Link to RSpecs used successfully for rack site confirmation tests. ||
     15|| Aggregate Status || Operational monitoring not widely available, restricted access to monitoring at [ GMOC]||
     16|| Slice Authorities Recognized ||GENI Portal (, ProtoGENI ( ||
     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 || Connects directly to the CENIC COTN network  ||
     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 took 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      || []   ||
     32|| Developer Links    || Software pages: [ InstaGENI],  [ FOAM], and [ FlowVisor];  Project page: [ InstaGENI Racks Project]; Developer mailing list: [] ||