Difference between revisions of "EGI-InSPIRE:SiteAdminUserGuide"
Jump to navigation
Jump to search
Line 60: | Line 60: | ||
*General procedures | *General procedures | ||
**How and where to get the repo files | **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 | ***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) | **Dedicated RSS channel for publication of products into the UMD Production repository (TBC) | ||
**Release notes | **Release notes | ||
***Where to get them | ***Where to get them | ||
Line 67: | Line 67: | ||
*Production Sites | *Production Sites | ||
** | ** The Production Service sites will need to configure the following repositories | ||
*** | ***The Main OS Repository e.g for SL5 | ||
***EPEL repository | ***EPEL repository | ||
***UMD Repository | ***UMD Repository |
Revision as of 12:55, 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
- Where is the release schedule hosted
- http://repository.egi.eu
- Changes in the schedule will be published as RSS feeds
- 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
- Major versions
- 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
- 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)
- How and where to get the repo files
- Production Sites
- The Production Service sites will need to configure the following repositories
- The Main OS Repository e.g for SL5
- EPEL repository
- UMD Repository
- The Production Service sites will need to configure the following repositories
- 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
- Necessary repositories