Changes between Initial Version and Version 1 of GENIRacksHome/RacksChecklist


Ignore:
Timestamp:
10/30/12 16:56:14 (11 years ago)
Author:
tupty@bbn.com
Comment:

Create initial public version of high level GENI rack installation checklist

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/RacksChecklist

    v1 v1  
     1[[PageOutline]]
     2
     3= High level steps for GENI rack installation =
     4Each rack site develops their own installation and test plan, which roughly follows these steps.  Please coordinate with the GPO and the rack development teams when performing the installation.
     5
     6 == Work with rack teams to identify site specific information and shipping ==
     7 * Provide shipping information
     8 * Provide any power requirements
     9  * Provide voltage and connector requirements
     10  * If you need a UPS for your rack, please coordinate with the GPO and the rack team
     11 * Communicate control plane and data plane connectivity requirements
     12  * Work with the GPO to identify your upstream data plane connection
     13  * Coordinate with rack team on procuring the needed data plane optics
     14  * Coordinate with the rack team to understand expectations for control plane connectivity
     15 * Provide rack team with a list of site admins
     16  * Coordinate with rack team to set up operations contacts
     17  * Provide usernames for those who should have administrative access to the rack hosts
     18 * Coordinate with rack teams on network configuration
     19  * Work with rack teams to allocate an block of IP space for the rack
     20  * Work with rack teams to prepare DNS for the rack
     21
     22
     23 == Install hardware ==
     24 * Put the rack in place and set up any needed power connections
     25 * Power up the devices in the rack
     26
     27 == Establish upstream control plane connectivity ==
     28 * Ensure that the management switch's control plane uplink is physically connected to a publicly routable network
     29   * Ensure that the machine on which !FlowVisor is running is reachable over a publicly routed network
     30   * Ensure that all machines on which aggregate manager software is running are reachable over a publicly routed network
     31 * Ensure that any other devices that should be publicly reachable (i.e. VPN appliances) are physically connected to a publicly routable network
     32
     33 == Coordinate configuration and testing of aggregate manager software ==
     34 * Coordinate with the GPO for FOAM configuration and testing
     35 * Coordinate with the rack teams for compute aggregate manager configuration and testing
     36
     37 == Coordinate data plane connection and testing ==
     38 * Coordinate with the GPO to set up upstream mesoscale connections
     39  * Before actually establishing a connection, open a GMOC ticket to track data plane connection and testing
     40  * Coordinate with the GMOC on the date for connection and testing
     41  * Coordinate data plane connectivity testing with the GPO and the GMOC using a GMOC ticket
     42 * Coordinate any other data plane connections with the GPO and other rack teams
     43  * Before actually establishing an additional remote connection, open a GMOC tracking ticket
     44  * Coordinate with the GMOC on the date for connection and testing
     45  * Coordinate data plane connectivity testing with rack teams, the GPO, and the GMOC using a GMOC ticket
     46
     47 == Set up monitoring ==
     48 * Configure active Aggregate Manager monitoring
     49  * Coordinate with the GMOC for setting your site up to submit active monitoring data to the GMOC database Live monitoring data is available on the GMOC pages.
     50  * Configure FOAM monitoring ([http://groups.geni.net/geni/wiki/PlasticSlices/MonitoringRecommendations/FoamConfiguration instructions])
     51  * Configure compute aggregate manager monitoring
     52   * ExoGENI Instructions '''coming soon'''
     53   * InstaGENI Instructions '''coming soon'''
     54 * Coordinate with the GPO to set up passive monitoring (simple API checks)
     55
     56 == Coordinate mesoscale testing ==
     57 Coordinate with the GPO on site confirmation testing
     58 * [http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks/SiteConfirmationTests ExoGENI Tests]
     59 * [http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks/SiteConfirmationTests IntsaGENI Tests]
     60
     61 == Perform administrative steps to move to production ==
     62 * Work with GMOC to complete monitoring, mailing list, and emergency contact handoff procedures for your site. When the procedures are complete, the GMOC begins 24x7 monitoring, tracking and dispatching questions and events that involve your site.
     63 * Review the GENI Aggregate Provider Agreement. Indicate via email to the GPO your intent to abide by the agreement.
     64 * Complete an Aggregate Information GENI wiki page (see template) for your site, which will be automatically linked here. This lets experimenters know how to request and use your !OpenFlow connections in GENI.