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"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* Software Delivery | * 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 | * Verification | ||
* StageRollout | * StageRollout | ||
| Line 58: | Line 60: | ||
** Which of that software is taken into the Software Provisioning workflow | ** Which of that software is taken into the Software Provisioning workflow | ||
** What happens when the software has been approved by SR? | ** What happens when the software has been approved by SR? | ||
Revision as of 11:12, 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 Schedule
- The exact process of reconciliation
- Open issue!
Software Provisioning
- 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)
Release Schedule
- 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
- 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