Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:SiteAdminUserGuide"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
Document ToC
Document ToC  


<br> The ToC follows the virtuous cycle of EGI


The ToC follows the virtuous cycle of EGI
=== Defining the release contents (Michel)  ===


=== Defining the release contents (Michel) ===
*Requirements-driven content priorities
**UCB requirements
**OMB Requirements
**Which of that software is taken into the Software Provisioning workflow


* Requirements-driven content priorities
*Reconcile community requirements
** UCB requirements
**Aspired output is an update of the UMD Release Schedule
** OMB Requirements
**The exact process of reconciliation
** Which of that software is taken into the Software Provisioning workflow
***Open issue!


* Reconcile community requirements
=== Software Provisioning (Alvaro)  ===
** Aspired output is an update of the UMD Release Schedule
** The exact process of reconciliation
*** Open issue!


=== Software Provisioning (Alvaro) ===
*Software Delivery
**The sources of software (i.e. EMI, IGE, EPEL, Platform)  
**For TP only their main repository, we never pull from anything else
*Verification
*StageRollout
*UMD Release Building
**Major versions (when and why do we release major versions)
**Minor versions (ditto)
***Explain the concept of roll-up releases)
**What happens when the software has been approved by SR?


* Software Delivery
=== Release Schedule (Enol, Michel) ===
** The sources of software (i.e. EMI, IGE, EPEL, Platform)
** For TP only their main repository, we never pull from anything else
* Verification
* StageRollout
* UMD Release Building
** Major versions (when and why do we release major versions)
** Minor versions (ditto)
*** Explain the concept of roll-up releases)
** What happens when the software has been approved by SR?


=== Release Schedule (Enol, Michel) ===
*When and how often do we release a major
**At most once a year
**Closely located with major releases of EMI and IGE


* When and how often do we release a major
*When and how do we release minor releases
** At most once a year
** Closely located with major releases of EMI and IGE


* When and how do we release minor releases
*Where is the release schedule hosted
**http://repository.egi.eu
**Changes in the schedule will be published as RSS feeds


* Where is the release schedule hosted
*What will the schedule tell you
** http://repository.egi.eu
**Major versions
** Changes in the schedule will be published as RSS feeds
***High-level list of non-backwards compatible changes,
***Addition of new platforms
***New features
***List of products
***Planned release date
**Minor versions (i.e. roll-up updates)
***List of products (new, or updated)
***Planned release date


* What will the schedule tell you
*Flagging and progress
** Major versions
**Green ticks (or so) for successfully provisioned products that are not yet published
*** High-level list of non-backwards compatible changes,
**Yellow exclamation mark for products that are in danger of being delayed
*** Addition of new platforms
**Red crosses for products that failed verification or StagedRollout
*** New features
*** List of products
*** Planned release date
** Minor versions (i.e. roll-up updates)
*** List of products (new, or updated)
*** Planned release date


* Flagging and progress
=== Site Admin's UMD Repository HOWTO (GRNET) ===
** Green ticks (or so) for successfully provisioned products that are not yet published
** Yellow exclamation mark for products that are in danger of being delayed
** Red crosses for products that failed verification or StagedRollout


=== Site Admin's UMD Repository HOWTO (GRNET) ===
*General procedures
**How and where to get the repo files
***The Repo Files for each corresponding Major are availble in the repofiles directory inside their corresponding Major e.g. http://reposiotry.egi.eu/umd/1/repofiles
**Dedicated RSS channel for publication of products into the UMD Production repository (TBC)
**Release notes
***Where to get them
***What they contain (for major and minor)


* General procedures
*Production Sites
** How and where to get the repo files
**Necessary repositories
** Dedicated RSS channel for publication of products into the UMD Production repository
***Platform (such as SL5 64bit)
** Release notes
***EPEL repository
*** Where to get them
***UMD Repository
*** What they contain (for major and minor)


* Production Sites
*Early Adopters (SR) Sites  
** Necessary repositories
**Necessary repositories  
*** Platform (such as SL5 64bit)
***Platform (such as SL5 64bit)  
*** EPEL repository
***EPEL repository  
*** UMD Repository
***UMD Repository  
 
***UMD Early Access  
* Early Adopters (SR) Sites
***PPA repository for the product in StageRollout
** Necessary repositories
*** Platform (such as SL5 64bit)
*** EPEL repository
*** UMD Repository
*** UMD Early Access  
*** PPA repository for the product in StageRollout

Revision as of 12:49, 20 April 2011

Document ToC


The ToC follows the virtuous cycle of EGI

Defining the release contents (Michel)

  • Requirements-driven content priorities
    • UCB requirements
    • OMB Requirements
    • Which of that software is taken into the Software Provisioning workflow
  • Reconcile community requirements
    • Aspired output is an update of the UMD Release Schedule
    • The exact process of reconciliation
      • Open issue!

Software Provisioning (Alvaro)

  • Software Delivery
    • The sources of software (i.e. EMI, IGE, EPEL, Platform)
    • For TP only their main repository, we never pull from anything else
  • Verification
  • StageRollout
  • UMD Release Building
    • Major versions (when and why do we release major versions)
    • Minor versions (ditto)
      • Explain the concept of roll-up releases)
    • What happens when the software has been approved by SR?

Release Schedule (Enol, Michel)

  • When and how often do we release a major
    • At most once a year
    • Closely located with major releases of EMI and IGE
  • When and how do we release minor releases
  • What will the schedule tell you
    • Major versions
      • High-level list of non-backwards compatible changes,
      • Addition of new platforms
      • New features
      • List of products
      • Planned release date
    • Minor versions (i.e. roll-up updates)
      • List of products (new, or updated)
      • Planned release date
  • Flagging and progress
    • Green ticks (or so) for successfully provisioned products that are not yet published
    • Yellow exclamation mark for products that are in danger of being delayed
    • Red crosses for products that failed verification or StagedRollout

Site Admin's UMD Repository HOWTO (GRNET)

  • General procedures
    • How and where to get the repo files
    • Dedicated RSS channel for publication of products into the UMD Production repository (TBC)
    • Release notes
      • Where to get them
      • What they contain (for major and minor)
  • Production Sites
    • Necessary repositories
      • Platform (such as SL5 64bit)
      • EPEL repository
      • UMD Repository
  • Early Adopters (SR) Sites
    • Necessary repositories
      • Platform (such as SL5 64bit)
      • EPEL repository
      • UMD Repository
      • UMD Early Access
      • PPA repository for the product in StageRollout