Changes between Version 2 and Version 3 of GENIRacksHome
- Timestamp:
- 02/27/12 21:09:43 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome
v2 v3 3 3 = GENI Racks = 4 4 5 GENI racks are being implemented to meet the goals specified by the GPO [ http://groups.geni.net/geni/wiki/GeniRacks GENI Rack Requirements]. Current rack projects can be characterized as follows:5 GENI 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: 6 6 7 7 * '''[#GENIStarterRacks Starter Racks]''': Deployed by the GPO, a project to deliver an early low-end solution for GENI Racks. … … 15 15 ''Note: InstaGENI Racks additionally allow Layer 3 connections on the Data Plane connections'' 16 16 17 '''[wiki:GENI -Infrastructure-Portal/GENIRacksAdministration GENI Racks Administration]''' tasks are highlighted for each of these rack solutions to provide some insight into the effort required by a participant.17 '''[wiki:GENIRacksAdministration GENI Racks Administration]''' tasks are highlighted for each of these rack solutions to provide some insight into the effort required by a participant. 18 18 19 19 = GENI Starter Racks = 20 20 21 The Starter Racks project is an effort to get [http://www.nsf.gov/cise/usignite/ US Ignite] cities connected to the GENI Network to facilitate experimental network and compute research, and city application development. The Starter racks jump start the delivery of fully integrated network and compute resources to selected sites. At this time, the Starter racks do not deliver GENI software features such as an Aggregate Manager. Starter Racks can be used as Meso-scale !OpenFlow Site, but requires GPO Infrastructure support to implement, if you are interested in running !OpenFlow on a deployed Starter rack contact [mailto:help.geni.net]. If you would like to make your own GENI Starter rack, see the [ wiki:GENI-Infrastructure-Portal/GENIRacks#GetYourOwnGENIRack section] below.21 The Starter Racks project is an effort to get [http://www.nsf.gov/cise/usignite/ US Ignite] cities connected to the GENI Network to facilitate experimental network and compute research, and city application development. The Starter racks jump start the delivery of fully integrated network and compute resources to selected sites. At this time, the Starter racks do not deliver GENI software features such as an Aggregate Manager. Starter Racks can be used as Meso-scale !OpenFlow Site, but requires GPO Infrastructure support to implement, if you are interested in running !OpenFlow on a deployed Starter rack contact [mailto:help.geni.net]. If you would like to make your own GENI Starter rack, see the [#GetYourOwnGENIRack section] below. 22 22 23 23 == Starter Racks Components == … … 55 55 == Starter Racks Implementation == 56 56 57 Each GENI Starter Rack systems requires a specific setup, which is captured for each of the rack components: Router, !OpenFlow Switch, IPKVM, Eucalyptus Head Host, Eucalyptus Worker Hosts, and Monitor Node. See the '''[http://groups.geni.net/syseng/wiki/GENI-Infrastructure-Portal/GENIRacks/StarterCompSetup Starter Component Setup]''' for details about the required configuration. For specific details about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENI -Infrastructure-Portal/GENIRacksAdministration#StarterracksAdmin Starter Racks Administration]''' tasks.57 Each GENI Starter Rack systems requires a specific setup, which is captured for each of the rack components: Router, !OpenFlow Switch, IPKVM, Eucalyptus Head Host, Eucalyptus Worker Hosts, and Monitor Node. See the '''[http://groups.geni.net/syseng/wiki/GENI-Infrastructure-Portal/GENIRacks/StarterCompSetup Starter Component Setup]''' for details about the required configuration. For specific details about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENIRacksAdministration#StarterracksAdmin Starter Racks Administration]''' tasks. 58 58 59 59 == Starter Racks Monitoring == 60 Starter Racks meet the following [ http://groups.geni.net/geni/wiki/GeniRacks#D.MonitoringRequirements monitoring requirements]. Monitoring data for the 3 deployed Starter Racks, GPO, Chattanooga and Cleveland is available at the [http://monitor.gpolab.bbn.com/ganglia/ GPOLab Monitor] portal, where the user can select a location and get monitoring detail for ''System load'', ''CPU load'', ''Memory usage'', and ''Network usage''. In addition, ''Services Health'' is monitored on each of the GENI Starter Racks and alert notifications are available upon request, contact [mailto:help.geni.net] to become a notification recipient. To access the ''Service Health'' detail on demand, go to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi Service Status Details] page for all Starter rack sites.60 Starter Racks meet the following [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements]. Monitoring data for the 3 deployed Starter Racks, GPO, Chattanooga and Cleveland is available at the [http://monitor.gpolab.bbn.com/ganglia/ GPOLab Monitor] portal, where the user can select a location and get monitoring detail for ''System load'', ''CPU load'', ''Memory usage'', and ''Network usage''. In addition, ''Services Health'' is monitored on each of the GENI Starter Racks and alert notifications are available upon request, contact [mailto:help.geni.net] to become a notification recipient. To access the ''Service Health'' detail on demand, go to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi Service Status Details] page for all Starter rack sites. 61 61 62 62 == Starter rack Site Requirements == … … 113 113 Any configuration or run-time requirements for any of the InstaGENI rack systems will be documented here, when available. 114 114 115 Each InstaGENI Rack systems requires a specific setup, which is to captured for each of the rack components: !OpenFlow Switch, control node, experiment nodes, bare-metal nodes, etc.. See the '''[ http://groups.geni.net/syseng/wiki/GENI-Infrastructure-Portal/GENIRacks/InstaGENICompSetup InstaGENI Component Setup]''' for details about the required configuration. For help about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENI-Infrastructure-Portal/GENIRacksAdministration#InstaGENIAdministrationInstaGENIRacks Administration]''' tasks.115 Each InstaGENI Rack systems requires a specific setup, which is to captured for each of the rack components: !OpenFlow Switch, control node, experiment nodes, bare-metal nodes, etc.. See the '''[wiki:GENIRacks/InstaGENICompSetup InstaGENI Component Setup]''' for details about the required configuration. For help about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENIRacksAdministration#InstaGENIAdministration InstaGENIRacks Administration]''' tasks. 116 116 117 117 == InstaGENI Monitoring == 118 InstaGENI Racks meet the following [ http://groups.geni.net/geni/wiki/GeniRacks#D.MonitoringRequirements monitoring requirements]. InstaGENI Monitoring data is currently being defined and will be available at the [https://gmoc-db.grnoc.iu.edu/api-demo GMOC SNAPP home].118 InstaGENI Racks meet the following [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements]. InstaGENI Monitoring data is currently being defined and will be available at the [https://gmoc-db.grnoc.iu.edu/api-demo GMOC SNAPP home]. 119 119 120 120 == InstaGENI Site Requirements == … … 170 170 Any configuration or run-time requirements for the ExoGENI rack systems will be documented here, when available. 171 171 172 Each ExoGENI Rack systems requires a specific setup, which is to captured for each of the rack components: !OpenFlow Switch, Management node, Worker Nodes, etc.. See the '''[ http://groups.geni.net/syseng/wiki/GENI-Infrastructure-Portal/GENIRacks/ExoGENICompSetup ExoGENI Component Setup]''' for details about the required configuration. For help about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENI-Infrastructure-Portal/GENIRacksAdministration#ExoGENIAdministration ExoGENIRacks Administration]''' tasks.172 Each ExoGENI Rack systems requires a specific setup, which is to captured for each of the rack components: !OpenFlow Switch, Management node, Worker Nodes, etc.. See the '''[wiki:GENIRacks/ExoGENICompSetup ExoGENI Component Setup]''' for details about the required configuration. For help about the configuration settings, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENIRacksAdministration#ExoGENIAdministration ExoGENI Racks Administration]''' tasks. 173 173 174 174 == ExoGENI Monitoring == 175 Monitoring data for the ExoGENI rack is collected on the management node by a Nagios aggregator and then forwarded to the GMOC. The type of data that will be available is currently being defined. ExoGENI Racks meet the GENI [ http://groups.geni.net/geni/wiki/GeniRacks#D.MonitoringRequirements monitoring requirements]. ExoGENI Monitoring data will be available at the [https://gmoc-db.grnoc.iu.edu/api-demo GMOC SNAPP Home].175 Monitoring data for the ExoGENI rack is collected on the management node by a Nagios aggregator and then forwarded to the GMOC. The type of data that will be available is currently being defined. ExoGENI Racks meet the GENI [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements]. ExoGENI Monitoring data will be available at the [https://gmoc-db.grnoc.iu.edu/api-demo GMOC SNAPP Home]. 176 176 177 177 == ExoGENI Site Requirements ==