[[PageOutline]] = Current GENI Rack Projects = 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: * '''[#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.[[BR]] * '''[#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. * '''[#OpenGENIRacks OpenGENI]''' - Also a mid-range, expandable GENI Racks solution delivering Internet cloud applications support, along with !OpenFlow and VLAN networking. These racks are deployed on Dell hardware. * '''[#CiscoGENIRacks Cisco GENI]''' - A dual data plane fabric expandable GENI Rack solution, that combines ExoGENI software with Cisco UCS-B and -C series servers, UCS disk and !NetApp FAS 2240 storage, and Nexus 3548 dataplane switches. These racks support !OpenFlow, virtual topologies, and multi-site cloud applications. All GENI Racks have layer 3 connections to the Internet and layer 2 connections to the GENI core networks (Internet2 ION and AL2S). 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'' Additional information is available for various aspects of the GENI racks life cycle: - '''[wiki:GENIRacksAdministration GENI Racks Administration]''' page highlights tasks for each of these rack solutions to provide some insight into the effort required by a participant. - '''[wiki:GENIRacksHome/Security GENI Racks Security]''' page provides some information about security in the context of the various GENI racks. - '''[wiki:GENIRacksHome/AcceptanceTests GENI Racks Acceptance Tests]''' page provides insight into how the GPO validates these racks solutions before broad campus deployment. - '''[wiki:GENIRacksHome/ConfirmationTests Sites Confirmation Tests]''' page provides insight into how the GPO validates each rack as it is deployed for production or as network stitching support is introduced for a site. - '''[wiki:GENIRacksHome/GENIRacksDeploymentSites GENI Racks Deployment Sites]''' page captures the sites planned to have an ExoGENI or InstaGENI rack. The '''[wiki:GENIProduction GENI Production]''' page captures the sites that are now operational and are available to GENI experimenters. - '''[wiki:GENIRacksHome/RacksChecklist Rack Checklist]''' page provides high level steps for installing a GENI rack site. - '''[wiki:GENIRacksHome/RacksChecklistStatus Rack Checklist Status]''' page provides the status of each GENI site for completing the rack checklist. - '''[wiki:GENIRacksHome/ExogeniRacks ExoGENI Rack Project]''', '''[wiki:GENIRacksHome/InstageniRacks InstaGENI Rack Project]''', and '''[wiki:GENIRacksHome/OpenGENIRacks OpenGENI Rack Project]''' overview pages provide insight into each project's activity. There is not yet a project page for Cisco GENI Racks. - '''[wiki:GENIResources GENI Resources]''' page captures experimenter information for ExoGENI, InstaGENI and other GENI aggregates that provide resources for experimenters. - '''[wiki:GENIRacksInteroperability GENI Racks Interoperability Experiment]''' page captures an interoperability experiment with ExoGENI, InstaGENI and Meso-scale !OpenFlow resources that was run in the initial stages of GENI Racks acceptance. = 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 !OpenFlow and WiMAX resources. 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 an [https://code.renci.org/gf/download/docmanfileversion/13/691/ExoGENIDesignv1.02.pdf ExoGENI Design] document and an [http://www.cs.duke.edu/~chase/exogeni.pdf ExoGENI white paper]. For a more details see the '''[http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks ExoGENI Rack Project]''' overview page. The up-to-date technical information about ExoGENI Racks is located on [http://wiki.exogeni.net ExoGENI Wiki]. == ExoGENI Components == '''IMPORTANT:''' For the most up-to-date information about GENI Racks configurations and features please visit http://wiki.exogeni.net An [http://wiki.exogeni.net 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, NLR) 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 == '''IMPORTANT:''' For the most up-to-date information about GENI Racks configurations and features please visit http://wiki.exogeni.net 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 Resources__'' 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) Up-to-date details about the configuration and setup of ExoGENI racks can be found in [http://wiki.exogeni.net ExoGENI wiki]. == 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 '''[https://wiki.exogeni.net/doku.php ExoGENI Wiki]''' page 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. == 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 [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. ------ = 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/geni/attachment/wiki/GENIRacksHome/InstaGENI%20Design%20Document%20Rick%202-15%282%29.doc?format=raw InstaGENI Design] document is available. For more details see the '''[http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks InstaGENI Rack Project]''' overview page. == InstaGENI Components == Each InstaGENI racks delivers a small ProtoGENI cluster with !OpenFlow networking and FOAM aggregate management. This rack includes the following types of systems: * Control Node - Xen Server that runs 3 VMS to provide: * PG boss node, web server, monitoring, and GENI AM 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. * !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 Resources__'' 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 ''__Network Components__'' 2 network components to provide access to GENI core networks and commodity Internet: * HP !ProCurve 2620 Switch (J9623A), 24 10/100/100 Mb/s ports, 2 1 Gb/s ports * HP !ProCurve 5406zl Switch (J8697A) 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 == Configuration and run-time requirements for InstaGENI rack systems are documented here. Following are a list of available configuration details for the rack setup: * [http://www.protogeni.net/wiki/RackSetupQuestions Questionnaire] used to gather initial site configuration data. * [http://www.protogeni.net/wiki/rack-deployment Rack Deployment] page detailing how rack software is deployed. * [http://www.protogeni.net/wiki/RackAdminAccounts Administrative Accounts] instructions for creating new accounts. * FOAM Aggregate setup details are not documented at this time. * [http://www.protogeni.net/wiki/InstaGeni/ILO HP Integrated Lights-Out 3] information to configure, update, and operate servers remotely. For help or questions about configuration settings or run-time requirements, please contact [mailto:help@geni.net help@geni.net]. Some examples are available to get insight into '''[wiki:GENIRacksAdministration#InstaGENIAdministration InstaGENIRacks Administration]''' tasks. == InstaGENI Monitoring == 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]. == 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. ------ = OpenGENI Racks = The OpenGENI project is mid-range, expandable GENI Racks solution delivering a GENI Compliant aggregate on a Dell rack. OpenGENI racks are currently designated as a [wiki:GENIRacksHome/GENIProvisionalResources GENI Provisional Resource]. An [wiki:GENIRacksHome/OpenGENIRacks/ArchitectureDescription OpenGENI Architecture] document is available and for more details see the '''[wiki:GENIRacksHome/OpenGENIRacks OpenGENI Racks]''' page. == OpenGENI Components == An OpenGENI rack includes the following types of systems: * Control Node - !OpenStack Server that runs the GENI AM API Server and the [wiki:OperationalMonitoring GENI Operational Monitoring] function. * Experiment Nodes - Nodes managed by GRAM software, to provide boot services, account creation, experimental management, etc. * !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 OpenGENI rack: [[Image(GENI-OpenGENI-components.jpg)]] == OpenGENI Specifications == The current hardware components specification for the OpenGENI Racks includes: ''__Compute Resources__'' - 3 !PowerEdge Dell R620XL rack server hosts that provide the VM Server, Monitoring, Storage, and Application functions: * Control Node - 1 Dell !PowerEdge R620XL server Server with 32 GB of RAM and 300 GB hard drive. * Experiment Nodes - 2 Dell !PowerEdge R620XL server Server with 32 GB of RAM, and 300 GB hard drive. More compute nodes are possible. * Bare Metal Node - Not supported at this time. ''__Network Components__'' 2 network components to provide access to GENI core networks and commodity Internet: * Dell Force10 S4810P !Openflow Switch supports 48 dual-speed 1/10 Gb ports and four 40 Gb ports * Dell !PowerConnect Switch with up to 48 ports of GbE and optional 4x 10Gb ''__Misc. Components_'' General purpose hardware also included: * Dell Remote Access Controller - iDRAC == OpenGENI Implementation == Configuration and run-time requirements for OpenGENI rack systems are documented here. Following are a list of available configuration details for the rack setup: * [wiki:GENIRacksHome/OpenGENIRacks/OpenGENICheckList Site Checklist] used to gather initial site configuration data. * [wiki:GENIRacksAdministration/OpenGENIRacksAdminAccounts Administrative Accounts] instructions for creating new administrative accounts. For help or questions about configuration settings or run-time requirements, please contact [mailto:help@geni.net help@geni.net]. == OpenGENI Monitoring == OpenGENI Racks are [wiki:GENIRacksHome/GENIProvisionalResources GENI Provisional Resources]. Development is taking place to meet [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements] by implementing [wiki:OperationalMonitoring GENI Operational Monitoring]. == OpenGENI Site Requirements == OpenGENI 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 all rack devices. * 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. ------ = Cisco GENI Racks = **These racks are currently undergoing GENI Acceptance Testing. Please contact [mailto:help@geni.net help@geni.net] if you are interested in their current status.** These dual fabric interconnect expandable GENI Racks combine ExoGENI software with Cisco UCS-B and C series servers, UCS and !NetApp FAS 2240 storage, and Nexus 3548 dataplane switches. All equipment is physically located in one cabinet, but the rack operates as two separate but related GENI aggregates. Cisco racks support !OpenFlow, virtual topologies, data centers, and multi-site cloud applications. == Cisco GENI Rack Components == A Cisco GENI rack includes the following types of systems: * Control Node - Server that runs the GENI AM API server * Experiment Nodes - Nodes managed by ExoGENI software, to provide boot services, account creation, experimental management, etc. * Experimenter Storage - Slicable storage for experimenters from the UCS onboard disks and !NetApp FAS 2240 storage * !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) See the attached [http://groups.geni.net/geni/raw-attachment/wiki/GENIRacksHome/NCSU%20GENI%20RACK%20Certification%20v1.0.pdf NCSU GENI RACK Certification v1.0] for high-level information on the components, wiring, and network connections for an example Cisco GENI rack at NCSU. == Cisco GENI Rack Specifications == The main hardware components undergoing acceptance testing are shown in the attached Cisco presentation and Bill of Materials files (see end of page). == Cisco GENI Rack Implementation == Configuration details, run-time requirements, and design documents for the Cisco GENI rack are not yet available. == Cisco GENI Monitoring == Development is taking place to meet [wiki:GeniRacks#D.MonitoringRequirements monitoring requirements] by implementing [wiki:OperationalMonitoring GENI Operational Monitoring]. GENI monitoring is not yet available for the system undergoing acceptance testing. == Cisco GENI Site Requirements == Cisco GENI 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 all rack devices. * 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. {{{ #!html Email help@geni.net for GENI support or email me with feedback on this page! }}}