Changes between Version 4 and Version 5 of ProductionRelease


Ignore:
Timestamp:
11/21/13 15:20:56 (10 years ago)
Author:
hdempsey@bbn.com
Comment:

update the procedure to reflect the new GCF release mechanism for adding to resource name list

Legend:

Unmodified
Added
Removed
Modified

  • ProductionRelease

    v4 v5  
    19191.  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.)
    2020
    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.)
     212.  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 updates to an agg_nick_cache file are the mechanism to get new racks into Omni.) 
    2222
    23233.  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.