Changes between Version 60 and Version 61 of GENIRacksHome

10/03/13 13:04:11 (9 years ago)



  • GENIRacksHome

    v60 v61  
    33= Current GENI Rack Projects =
    5 GENI racks are being implemented to meet the goals specified by the GPO [wiki:GeniRacks GENI Rack Requirements].  The first class of racks were "GENI Starter Racks." The GPO has discontinued the deployment of these racks. However, documentation for this project exists for the edification for prospective rack builders and can be found [wiki:GENIRacksHome#PastGENIRackProject here]. Current rack projects can be characterized as follows:
     5GENI racks are being implemented to meet the goals specified by the GPO [wiki:GeniRacks GENI Rack Requirements]. Current rack projects can be characterized as follows:
    159159   * InstaGENI PI contact: []
    162 ------
    164 = Past GENI Rack Project =
    166 No longer deployed by the GPO, this project delivered an early low-end solution for GENI Racks.
    168 = Starter Racks =
    170 The Starter Racks project was an effort to get [ US Ignite] cities connected to the GENI Network to facilitate experimental network and compute research, and city application development. The Starter Racks jump started the delivery of fully integrated network and compute resources to selected sites. During this period, the Starter racks did not deliver GENI software features such as an Aggregate Manager. In any case, it was possible to use a Starter Rack as a Meso-scale !OpenFlow Site, but required GPO Infrastructure support for implementation. Furthermore, details were provided in the [#GetYourOwnGENIRack section] below to build your own Starter Rack.
    172 == Starter Racks Components ==
    174 A Starter Rack delivered software and hardware components that enabled a site to be a GENI site. Each GENI Starter Rack delivered the following types of systems:
    176  * Router - Cisco IOS router sets up standard routed IP to the local network provider.
    177  * !OpenFlow switch - HP Procurve 6600 switch carries experimental traffic via layer2 to GENI backbone (I2, NLR) and to carry Eucalyptus communication between local VMs.
    178  * Eucalyptus Head Host - Host running Eucalyptus service manages Eucalyptus hosts and provides public interface to access Site VMs via NAT.
    179  * Eucalyptus Worker Hosts - Two Eucalyptus Worker hosts provide VMs. The number of VMs allowed is based on address space available at each site.
    180  * Application Host (aka Bare-metal node) - A High performance host provides experimenters a real network interfaces to be provisioned manually.
    181  * Monitoring Host - Monitors both compute and network resources for the GENI site.
    183 The Rack resource above were connected as follows:
    185 [[Image(GENI-StarterRacks-components.jpg)]]
    187 ''Note: The data plane connection from the Euca Head host to the Cisco router is used to provide public access Euca Worker VMs via NAT.''
    189 == Starter Racks Specifications ==
    191 ''__Compute Resources__''
    192   * 5 Dell™ !PowerEdge™ R510 -  1 for Eucalyptus Head, 2 for Worker hosts, 1 for Monitoring, and 1 for bare-metal node.
    194 ''__Network Components__''
    195  * 1 Cisco 2901 Integrated Services Router - Access to commodity internet.     
    196  * 1 HP !ProCurve 6600-48G-4Xg  - Access to GENI backbone.
    198 ''__Misc. Components__'' General purpose hardware included in the Starter Racks:
    199   * 1 APC Swiched Rack PDU - Load monitoring, remote power cycle.
    200   * 1 APC Smart-UPS - Network power protection
    201   * IOGEAR 8-port KVM switch - Console access
    202   * Lantronix !SecureLinx Spider Compact Remote - One port for KVM over IP access
    204 == Starter Racks Implementation ==
    206 Each GENI Starter Rack systems required a specific setup, which was captured for each of the rack components: Router, !OpenFlow Switch, IPKVM, Eucalyptus Head Host, Eucalyptus Worker Hosts, and Monitor Node. See the '''[wiki:GENIRacks/StarterCompSetup Starter Component Setup]''' for details about the required configuration. Some examples are available to get insight into '''[wiki:GENIRacksAdministration#StarterracksAdmin  Starter Racks Administration]''' tasks.
    208 == Starter Racks  Monitoring ==
    209 Starter Racks met the following [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements]. Monitoring data for the 3 deployed Starter Racks, GPO, Chattanooga and Cleveland was available at the [ GPOLab Monitor] portal, where the user selected a location and received monitoring detail for ''System load'', ''CPU load'', ''Memory usage'', and ''Network usage''. In addition, ''Services Health'' was monitored on each of the GENI Starter Racks and alert notifications were available upon request. Access to the ''Service Health'' details was provided via the [ Service Status Details] page for all Starter Rack sites.
    211 == Starter Rack Site Requirements ==
    212 Starter Racks contained the following site requirements:
    213  * Network Setup - Define how the rack will connect to the Internet and to the GENI backbones. Ex Regional connections, connection speed, VLANs to be used, etc.
    214  * Site Security Requirements- Determine changes required for rack connectivity, such as FV rules, IP filters, etc.
    215  * Address assignment for rack components - Define which address, subnet mask, routing is to be configured for the rack components.
    216  * Power requirements - based on site requirements
    217  * Administrative accounts - Setup of site administrator account that will be created on the management/head node.
    218  * Delivery logistics - Details for ''where'' the rack is to be delivered, ''who'' will accept the delivers, and ''when'' the delivery will take place.  Also covers any physical restrictions for the rack delivery.
    220 == Get Your Own GENI Rack ==
    221 Below were some of the guidelines provided by the GPO to build your own GENI Starter Rack:
    223     * Develop specification for GENI racks, defining storage, compute, network resources, etc.
    224     * Evaluate, integrate and manage new software and configurations for rack solution.
    225     * Test and integrate early rack hardware and software.
    226     * Define acceptance criteria to demonstrate successful rack deployment.