Difference between revisions of "GOCDB/Release4/Development/CentralUnification"
(→Plan) |
|||
Line 21: | Line 21: | ||
== Actions == | == Actions == | ||
Remove the "Portal Instance" user interface element | * Remove the "Portal Instance" user interface element | ||
Remove landing page | * Remove landing page | ||
Switch goc.egi.eu to read/write mode | * Switch goc.egi.eu to read/write mode | ||
Power down gocdb4.esc.rl.ac.uk, save logs | * Power down gocdb4.esc.rl.ac.uk, save logs | ||
Remove gocdb4.esc.rl.ac.uk from DNS | * Remove gocdb4.esc.rl.ac.uk from DNS |
Revision as of 12:52, 31 May 2012
Introduction
As of 31.05.12 the GOCDB service is provided through two portals: a read only instance at goc.egi.eu and a read/write instance at gocdb4.esc.rl.ac.uk. We would like to consolidate these and provide the service through one read/write portal at goc.egi.eu.
History
Two portals were provided to support the deployment of multiple "regional" read/write portals containing different data. These "regional" portals would publish their data to the "central" read-only portal. A central read/write portal was provided for NGIs who didn't want to host their own regional GOCDB instance. However as a regional synchronised GOCDB doesn't yet exist this separation confuses users.
If a regional synchronising GOCDB is developed in future we can revert back to the old model.
Plan
- Bring up the planned changes at JRA-1 (Done 24.05.12)
- Create an RT ticket from the proposal and send it round OTAG/OMB (noc-managers@mailman.egi.eu; otag@mailman.egi.eu), JRA-1 + SA-1.
- Agree on a date
- Widely disseminate the change
- No more gocdb4.esc.rl.ac.uk
- Make the change
Technical Plan
Overview
Switch off gocdb4.esc.rl.ac.uk and switch goc.egi.eu to read/write mode.
Actions
- Remove the "Portal Instance" user interface element
- Remove landing page
- Switch goc.egi.eu to read/write mode
- Power down gocdb4.esc.rl.ac.uk, save logs
- Remove gocdb4.esc.rl.ac.uk from DNS