Difference between revisions of "EGI-InSPIRE:SiteAdminUserGuide"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
The ToC follows the virtuous cycle of EGI | |||
== | === Defining the release contents === | ||
* Requirements-driven content priorities | |||
** UCB requirements | |||
** OMB Requirements | |||
* Reconcile community requirements | |||
** Aspired output is an update of the UMD Release Shhedule | |||
=== Software Provisioning workflow === | === Software Provisioning workflow === | ||
* Software Delivery | * Software Delivery | ||
* Verification | * Verification | ||
Line 14: | Line 23: | ||
*** Explain the concept of roll-up releases) | *** Explain the concept of roll-up releases) | ||
Revision as of 10:40, 14 April 2011
Document ToC
The ToC follows the virtuous cycle of EGI
Defining the release contents
- Requirements-driven content priorities
- UCB requirements
- OMB Requirements
- Reconcile community requirements
- Aspired output is an update of the UMD Release Shhedule
Software Provisioning workflow
- Software Delivery
- 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)
- The sources of software (i.e. EMI, IGE, EPEL, Platform)
- Which of that software is taken into the Software Provisioning workflow
- What happens when the software has been approved by SR?
PART 2: Using the UMD Repository
- Where do Site Admins find information?
- How do I configure a server?
- When and how do I update?
- Necessary repositories for site admins
- Platform (such as SL5 64bit)
- EPEL repository
- UMD Repository
- Necessary repositories for Early Adopters
- Platform (such as SL5 64bit)
- EPEL repository
- UMD Repository
- UMD Early Access
- PPA repository for the product in StageRollout