Changes between Initial Version and Version 1 of GENIRacksHome

Timestamp:

02/27/12 20:53:42 (12 years ago)

Author:

hdempsey@bbn.com

Comment:

--

GENIRacksHome

@@ +1 @@
+[[PageOutline]]
+
+= GENI Racks =
+
+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:
+
+ * '''[wiki:GENI-Infrastructure-Portal/GENIRacks#GENIStarterRacks Starter Racks]''': Deployed by the GPO, a project to deliver an early low-end solution for GENI Racks.
+ * '''[wiki:GENI-Infrastructure-Portal/GENIRacks#InstaGENIRacks InstaGENI]''' - A mid-range cost, expandable GENI Racks solution that can will be deployed at a large number of campuses, delivering Internet cloud applications support, along with Openflow and VLAN networking. These racks are normally deployed outside a site firewall.
+ * '''[wiki:GENI-Infrastructure-Portal/GENIRacks#ExoGENIRacks ExoGENI]'''  A higher cost, flexible virtual networking topologies solution including OpenFlow, that also delivers a powerful platform for multi-site cloud applications. These racks are typically deployed as an integrated part of a campus network.
+
+All GENI Racks have layer 3 connections to the internet and layer 2 connections to the GENI core networks (curently NLR and Internet2). The racks use commodity Internet for control access to rack resources, and shared VLANS for the application and experiment data connections.  The racks may also use layer 3 Internet connections for some experiments, particularly IP cloud experiments.  This diagram illustrates logical connections for all the GENI Rack types:
+
+[[Image(GENI-Racks-connection.jpg)]]
+
+''Note: InstaGENI Racks additionally allow Layer 3 connections on the Data Plane connections''
+
+'''[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.
+
+= GENI Starter Racks =
+
+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. 
+
+== Starter Racks Components ==
+
+A Starter rack delivers software and hardware components that enable a site to be a GENI site. Each GENI Starter Rack delivers the following types of systems:
+
+ * Router - Cisco IOS router is delivered to set up standard routed IP to the local network provider.
+ * !OpenFlow switch - HP Procurve 6600 switch to carry experimental traffic via layer2 to GENI backbone (I2, NRL) and to carry Eucalyptus communication between local VMs.
+ * Eucalyptus Head Host - Host running Eucalyptus service to manage Eucalyptus hosts and provides public interface to access Site VMs via NAT.
+ * Eucalyptus Worker Hosts - Two Eacalyptus Worker hosts to provide VMs. The number of VMs allowed is based on address space available at each site.
+ * Application Host (aka Bare-metal node) - A High performance host to provide experimenters a real network interfaces to be provisioned manually.
+ * Monitoring Host - Monitors both compute and network resources for the GENI site.
+
+The Rack resource above are connected as follows:
+
+[[Image(GENI-StarterRacks-components.jpg)]]
+
+''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.''
+
+== Starter Racks Specifications ==
+
+''__Compute Resources__''
+  * 5 Dell™ !PowerEdge™ R510 -  1 for Eucalyptus Head, 2 for Worker hosts, 1 for Monitoring, and 1 for bare-metal node.
+
+''__Network Components__''
+ * 1 Cisco 2901 Integrated Services Router - Access to commodity internet.      
+ * 1 HP !ProCurve 6600-48G-4Xg  - Access to GENI backbone.
+
+''__Misc. Components__'' General purpose hardware included in the Starter Racks:
+  * 1 APC Swiched Rack PDU - Load monitoring, remote power cycle.
+  * 1 APC Smart-UPS - Network power protection 
+  * IOGEAR 8-port KVM switch - Console access
+  * Lantronix !SecureLinx Spider Compact Remote - One port for KVM over IP access
+ 
+== Starter Racks Implementation ==
+
+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.
+
+== Starter Racks  Monitoring ==
+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. 
+
+== Starter rack Site Requirements ==
+Starter racks have the following site requirements:
+ * 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.
+ * Site Security Requirements- Determine changes required for rack connectivity, such as FV rules, IP filters, etc.
+ * Address assignment for rack components - Define which address, subnet mask, routing is to be configured for the rack components.
+ * Power requirements - based on site requirements
+ * Administrative accounts - Setup of site administrator account that will be created on the management/head node.
+ * 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. 
+
+If you are interested in building your own starter help and would like help from the GPO, please contact us at [mailto:help@geni.net].
+
+------
+
+= InstaGENI Racks =
+The InstaGENI project is an effort to deploy low-end, expandable GENI Racks at large number of campuses and is typically found outside the site firewall, more details are to be added as defined. An overview of the project is available from the [http://groups.geni.net/geni/attachment/wiki/GEC12GENIUpdatePlenary/McGeer%20InstaGENI.pdf?format=raw  GEC12 InstaGENI Racks] presentation. An [http://groups.geni.net/syseng/attachment/wiki/GENI-Infrastructure-Portal/GENIRacks/InstaGENI%20Design%20Document%20Rick%202-15%282%29.doc?format=raw InstaGENI Design] document is available.
+
+== InstaGENI Components ==
+
+Each InstaGENI racks delivers a small ProtoGENI cluster with OpenFlow networking based on FOAM. This rack includes the following types of systems:
+   * Control Node -  Xen Server that runs 3 VMS to provide: 
+            * PG boss node, web server and GENI API Server
+            * Local File Server node
+            * FOAM Controller
+   * Experiment Nodes - Five nodes managed by ProtoGENI software stack, which provides boot services, account creation, experimental management, etc.
+   * Monitoring Node - Should? run on the control node...TBD 
+   * !OpenFlow Switch - Provides internal routing and data plane connectivity to the GENI backbone (layer 2 and layer 3)
+   * Management Switch - Provides control plane connectivity to the Internet (layer 3)
+
+Following are the network connections for an InstaGENI rack:
+
+[[Image(GENI-InstaGENI-components.jpg)]]
+
+== InstaGENI Specifications ==
+The current hardware components specification for the InstaGENI Racks includes:
+
+''__Compute Resource Specifications__'' 5 HP !ProLiant DL360 G7 Server series hosts to provide the VM Server, Monitoring, Storage(??), and Application functions:
+  * Control Node - 1 HP !ProLiant DL360 G7 Server, quad-core, single-socket, 12 GB Ram, 4 TB Disk (RAID), and dual NIC
+  * Experiment Nodes - 5 HP !ProLiant DL360 G7 Server, six-core, dual-socket,48GB Ram, 1TB Disk, and dual NIC
+  * Bare Metal Node??
+  * Monitoring Node??
+
+''__Network Components__'' X network components to provide access to GENI Backbone and Commodity Internet:
+ * HP !ProCurve 2610 switch, 24 10/100 Mb/s ports, 2 1 Gb/s ports
+ * HP !ProCurve 6600 switch 48 1 Gb/s ports, 4 10 Gb/s ports
+
+''__Misc. Components_'' General purpose hardware also included:
+  * 1 or more HP Intelignt Mod PDU  
+  * HP Dedicated iLO Management Port Option 
+  * HP TFT7600 KVM Console US Kit
+
+== InstaGENI Implementation ==
+Any configuration or run-time requirements for any of the InstaGENI rack systems will be documented here, when available.
+
+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#InstaGENIAdministration  InstaGENIRacks Administration]''' tasks.
+
+== InstaGENI Monitoring ==
+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].
+
+== InstaGENI Site Requirements ==
+InstaGENI racks have the following site requirements:
+ * 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.
+ * Address assignment for rack components - Define which address, subnet mask, routing is to be configured for the rack components.
+ * Power requirements - based on site requirements
+ * Administrative accounts - Setup of site administrator account that will be created on the management/head node.
+ * 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. 
+
+If you are interested in becoming an InstaGENI deployment site, please contact us at [mailto:rick.mcgeer@hp.com].
+
+--------------------
+
+= ExoGENI Racks =
+The [http://www.exogeni.net ExoGENI]project is an effort to implement high-performance GENI Racks via a partnership between RENaissance Computing Institute (RENCI), Duke and IBM.  ExoGENI racks are assembled and tested by IBM and shipped directly to sites, where they are managed by the RENCI team.  ExoGENI racks deliver support for multi-domain cloud structure with flexible virtual networking topologies that allow combining ExoGENI, Meso-scale Open-Flow and WiMAX resource.  An overview of this project was presented at the [http://groups.geni.net/geni/attachment/wiki/GEC12GENIUpdatePlenary/GEC12-ExoGENI-Racks.pptx?format=raw GEC12 ExoGENI Presentation]. Also available are a [https://code.renci.org/gf/download/docmanfileversion/13/691/ExoGENIDesignv1.02.pdf ExoGENI Design] document and a [http://www.cs.duke.edu/~chase/exogeni.pdf ExoGENI white paper].
+
+== ExoGENI Components ==
+
+An ExoGENI Rack delivers the following types of systems:
+ * Management Switch - An IBM G8052R switched is delivered to allow access to/from the local network provider.
+ * VPN appliance - A Juniper SSG5 provides backup access to manage nodes.
+ * !OpenFlow-enabled switch - An IBM G8264R switch to carry experimental traffic via layer2 to GENI backbone (I2, NRL) and to local OF campus.
+ * Management Node - An IBM x3650 host running Elastic Compute Cloud(EC2) with !OpenStack to provision VMs and running xCat to provision bare-metal nodes. Also runs monitoring functions.
+ * Worker Nodes - Ten IBM 3650 M3 Worker nodes provide both !OpenStack virtualized instances and Bare-metal Xcat nodes 
+ * Monitoring Host - None, Monitoring is through Nagios from GMOC.
+
+The ExoGENI resources have the following connections:
+
+[[Image(GENI-ExoGENI-components.jpg)]]
+
+== ExoGENI Specifications ==
+
+An initial inventory of the ExoGENI Rack hardware components is found [https://docs.google.com/document/d/1hzleT6TNmiDb0YkkgqjXxPFJ37P4O6qApLmXgKJHBZQ/edit?hl=en_US here], which is superseded by the following:
+
+''__Compute Resource__'' A total of 12 hosts are in the rack to provide the Resources, Monitoring, Storage and Application functions:
+  * Management node: 1 IBM x3650 M3, 2x146GB 10K SAS hard drives, 12G RAM, dual-socket 4-core Intel X5650 2.66Ghz CPU, Quad-port 1Gbps adapter 
+  * Worker/Bare-Metal nodes: 10 IBM x3650 M3, 1x146GB 10K SAS hard drive +1x500+GB secondary drive, 48G RAM, dual-socket 6-core Intel X5650 2.66Ghz CPU, dual 1Gbps adapter, 10G dual-port Chelseo adapter
+  * Sliverable Storage: 1 IBM DS3512 storage NAS 6x1TB 7200RPM drives
+
+''__Network Components__'' 
+ * Management Switch: IBM BNT G8052R 1G client/10G uplink ports - Access to commodity internet.
+ * !OpenFlow Switch: IBM BNT G8264R 10G client/40G uplink ports - Access to GENI backbone.
+ * VPN Appliance: Juniper SSG5 - Backup management access. 
+
+''__Misc. Components__'' General purpose hardware included:
+  * IBM PDU based on site power requirements, (GPO=IBM 5897 PDU; RENCI=DPI 5900 PDU) 
+  * No UPS included
+  * IBM Local 2x16 Console Manager (LCM16)
+  * IBM 1U 17-inch Flat Panel Console Kit (PN 172317X)
+
+== ExoGENI Implementation ==
+Any configuration or run-time requirements for the ExoGENI rack systems will be documented here, when available.
+
+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.
+
+== ExoGENI Monitoring ==
+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].
+
+== ExoGENI Site Requirements ==
+ExoGENI racks have the following site requirements:
+ * 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.
+ * Site Security Requirements- Determine changes required for rack connectivity, such as FV rules, IP filters, etc.
+ * Address assignment for rack components - Define which address, subnet mask, routing is to be configured for the rack components.
+ * Power requirements - based on site requirements
+ * Administrative accounts - Setup of site administrator account that will be created on the management/head node.
+ * 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. 
+
+If you are interested in becoming an ExoGENI deployment site, please contact us at [mailto:ibaldin@renci.org].
+-----
+
+= Get Your Own GENI Rack =
+If you are interested in making your own GENI Starter Rack, the GPO can help with the following:
+
+    * Develop specification for GENI racks, defining storage, compute, network resources, etc.
+    * Evaluate, integrate and manage new software and configurations for rack solution.
+    * Test and integrate early rack hardware and software.
+    * Define acceptance criteria to demonstrate successful rack deployment.
+To get started, please contact [mailto:help@geni.net] for getting started.
+
+If you would like to make your own InstaGENI or ExoGENI rack, or to be considered as a potential site for the next phase of funded deployments, contact the project PI:  
+   * InstaGENI PI contact: [mailto:ibaldin@renci.org]
+   * ExoGENI PI contact: [mailto:rick.mcgeer@hp.com]
+
+----
+{{{
+#!html
+Email <a href="mailto:help@geni.net"> help@geni.net </a> for GENI support or email <a href="mailto:luisa.nevers@bbn.com">me</a> with feedback on this page!
+}}}