Changes between Version 2 and Version 3 of ProductionRelease
- Timestamp:
- 08/26/13 15:07:01 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProductionRelease
v2 v3 19 19 1. When a new GENI rack has been installed, integrated, and tested, the GPO will create a request ticket with the rack's common name to transition the rack resources to production. (Development teams who would like to receive these notifications should email their request to help@geni.net.) 20 20 21 2. Software developers who want to support production resources configure their systems to list the new production rack. This includes at least the GENI portal, OMNI (in the GCF), and GPO-configured monitoring displays. 21 2. Software developers who want to support production resources configure their systems to list the new production rack. This includes at least the GENI portal, OMNI (in the GCF), and GPO-configured monitoring displays. (Note that GCF software is not released as frequently as racks move to production, so experimenters can download the current OMNI config file attached to http://trac.gpolab.bbn.com/gcf/wiki/Omni or downloaded directly via http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/Omni/omni_config.sample in the interim.) 22 22 23 23 3. When the required configuration updates to the portal, OMNI, and GPO-configured monitoring have been made, the GPO will update [wiki:GENIProduction] with the new rack information.