Changes between Version 6 and Version 7 of ProductionRelease


Ignore:
Timestamp:
03/04/14 16:44:49 (6 years ago)
Author:
hdempsey@bbn.com
Comment:

Update the note about dev racks to remove UtahDDC, per Rob Ricci

Legend:

Unmodified
Added
Removed
Modified
  • ProductionRelease

    v6 v7  
    1111At any point in GENI, there are always new features in development.   The rack integration and release procedures only cover production GENI capabilities, which are verified as part of each site's confirmation tests ([http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks/SiteConfirmationTests] and [http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks/SiteConfirmationTests]).  Certain racks may be configured to support early integration or trials of new features, but those features are not required for the rack to be released.  Neither should testing those features make the racks unavailable to experimenters for an extended period.
    1212
    13 The racks at the GPO, RENCI, the University of Utah (both racks) and the University of Kansas all support experimenters, but are also used for early development and integration of new features.  Scheduled maintenance and upgrades are likely to be more frequent for these racks than for other GENI racks, which may be relevant to some experimenters.
     13The racks at the GPO, RENCI, the University of Kansas, and one of the racks at University of Utah (UtahInstaGENI, but NOT UtahDDCInstaGENI) all support experimenters, but are also used for early development and integration of new features.  Scheduled maintenance and upgrades are likely to be more frequent for these racks than for other GENI racks, which may be relevant to some experimenters.
    1414
    1515The rest of this page describes the GPO procedure for releasing a rack to production.