Difference between revisions of "GOCDB/Release4/Development/CentralUnification"

From EGIWiki
Jump to: navigation, search
(Extra Load)
(Extra Load)
Line 32: Line 32:
 
In this plan, the load on the read/write portal and the read-only portal would be placed on the same machine. The graphs below show one week's worth of CPU load for both machines. As this load is so low we don't see this being an issue.
 
In this plan, the load on the read/write portal and the read-only portal would be placed on the same machine. The graphs below show one week's worth of CPU load for both machines. As this load is so low we don't see this being an issue.
  
[[File:Read Only CPU.png|200px|thumb|left|GOCDB's Read Only Instance CPU Usage for a Week]] [[File:Read Write CPU.png|200px|thumb|left|GOCDB's Read/Write Instance CPU Usage for a Week]]
+
[[File:Read Only CPU.png|200px|thumb|left|A week's worth of CPU usage on GOCDB's Read Only Instance]] [[File:Read Write CPU.png|200px|thumb|left|A week's worth of CPU usage on GOCDB's Read/Write Instance]]

Revision as of 14:21, 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 (including PI) 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

  1. Bring up the planned changes at JRA-1 (Done 24.05.12)
  2. 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.
  3. Agree on a date
  4. Widely disseminate the change
    1. No more gocdb4.esc.rl.ac.uk
  5. 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
  • Change the front page to refer to only one "GOCDB"
  • 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

Concerns

Extra Load

In this plan, the load on the read/write portal and the read-only portal would be placed on the same machine. The graphs below show one week's worth of CPU load for both machines. As this load is so low we don't see this being an issue.

A week's worth of CPU usage on GOCDB's Read Only Instance
A week's worth of CPU usage on GOCDB's Read/Write Instance