CERN-IT/DB After-C5 Presentation EDMS Service Migration Monica Marinucci Lopez October 4th 2002 EDMS Document: 341082

CERN-IT/DB

After-C5 Presentation

EDMS Service Migration

Monica Marinucci LopezOctober 4th 2002

EDMS Document: 341082

After-C5: EDMS Service MigrationOctober 4th 2002

EDMS ID: 341082

M. Marinucci Lopez 2

CERN-IT/DB

Overview

BackgroundNew system studyFinal solutionPlan


EDMS ID: 341082


CERN-IT/DB

EDMS Service

Engineering Data Management ServiceIt provides the necessary tools and the support

for the creation and implementation of the Quality Assurance Plans needed to LHC machine and experiments

In the near future: it will have a larger scope as a data management system


EDMS ID: 341082


CERN-IT/DB


EDMS ID: 341082


CERN-IT/DB

Current EDMS Cluster

DEC based cluster (AS4100+DS20)Storage (HSZ70, 80GB mirrored) Mix of home-made and vendor applicationsData under Oracle (2-node SUN Cluster, 18GB)Shared responsibility amongst

EST/ISS IT/ PS IT/ DB


EDMS ID: 341082


CERN-IT/DBCurrent EDMS infrastructure

EDMS Cluster

Central Database Cluster


EDMS ID: 341082


CERN-IT/DB

Current EDMS Service diagram

OPS

OPS

CADIM, File Server, iAS

EDMS Cluster Central Database Cluster

HA service Shared service


EDMS ID: 341082


CERN-IT/DB

Reasons for the migration

HP/Compaq/Digital architecture will not be supported by IT in the future

Increase in the use of Oracle based tools (ie iAS and https support, MP5)

General system performance improvementCentralization and rationalization of EDMS

service


EDMS ID: 341082


CERN-IT/DB

Possible Solutions

Two 2-node clusters

Current central database cluster + a new EDMS cluster

One 3-node cluster

Merge of current central database cluster and a new EDMS cluster


EDMS ID: 341082


CERN-IT/DB

Solutions Pro-Cons

Two 2–node clusters Cheaper purchase of a

new EDMS cluster Simpler migration

High-Maintenance cost over the next years

Overload in the cluster administration

One 3-node cluster Enhance EDMS db

performance and integration

Cheaper maintenance cost Single cluster

administration

More expansive purchase of new EDMS cluster

More complex migration


EDMS ID: 341082


CERN-IT/DB Solution: one 3-node cluster

Sun Fire V880

T3BWG

8-port Switch

To the Backbone

FC 100MB/s

Private Network: Gbit Ethernet

Public Network


EDMS ID: 341082


CERN-IT/DB

New EDMS Service Infrastructure

Nodes: 3 SUN V880 with 2 UltraSparc III CPUs at 750 MHz, 4GB memory, 6 internal disks

Storage: 2 SUN T3 WorkGroup with 324 GB mirrored

Interconnections: 2 Qlogic FiberChannel 8-

port Switches (for T3WG)

2 Gbit Ethernet Switches (for the private network)

Public Network: on Gbit Ethernet


EDMS ID: 341082


CERN-IT/DB

Advantages

Integration: EDMS service + Database services

High-Availability Administration: 1 cluster

instead of 2 clusters + OEM Scalability: possible to add 1

node Performance: database and

networking

Storage: more space Costs (see next slide) Test Platform: the old

current Public database cluster

Expertise: SUN Solaris + 2-node cluster


EDMS ID: 341082


CERN-IT/DB

Costs (Purchase + Maintenance)

Total cost (in thousands Swiss Francs)

2*2nodes 1*2 nodes+1node 1*3nodes 1*3 nodes+1node

2005

2004

2003

2002


EDMS ID: 341082


CERN-IT/DB

Future EDMS Service diagram

HA services

Shared serviceOPS

CADIM, File Server

OPS OPS

iAS


EDMS ID: 341082


CERN-IT/DB

So far …

Hardware is installed and testedA first SUN cluster software installation is

available for testing: Fail-over mechanisms Coexistence of HA services and OPS (Oracle

Parallel Service) Stability


EDMS ID: 341082


CERN-IT/DBFuture EDMS infrastructure

V880 V880

T3WG

Switches


EDMS ID: 341082


CERN-IT/DB

Experience

Some issues related to SUN certification of the requested configuration

Eventually we are satisfied of the outcome and SUN support

Tests run so far are satisfactory, but coexistence amongst different services requires more work and understanding

Other service might be included


EDMS ID: 341082


CERN-IT/DB

Migration Plan (1/2)

Cluster installation and certification

Mainly SUN 1 week

Software Installation + Porting of existing services + High-Availability tests

IT/DB (with IT/PS collaboration)

2 months

Database migration IT/DB 1 month

Application Server migration IT/DB 1 month


EDMS ID: 341082


CERN-IT/DB

Migration Plan (2/2)

EDMS + ACCDB/CERNDB1 databases merge

IT/DB Sometime 2003

Tentative production: 1st Quarter 2003


EDMS ID: 341082


CERN-IT/DB

Responsibilities

Currently (until migration is completed)

IT/PS: Hardware + OS + Cluster + CADIM + File Server + License Server + correspondent data safety

IT/DB: EDMS database and related application server + Oracle data safety

EST/ISS: EDMS Development

Future IT/DB: Hardware + OS +

Cluster + File Server + License Server + EDMS database and related application server + data safety

IT/PS: CADIM Client Support

EST/ISS: EDMS Development


EDMS ID: 341082


CERN-IT/DB

Conclusions

The new EDMS service will merge the existing central database cluster and the current EDMS cluster

More responsibility within IT/DB Tentative production date is 1st Q 2003


EDMS ID: 341082


CERN-IT/DB

Before the questions:

Thanks to my colleagues: In IT/DB: Catherine, Montse, Eric and Nilo In IT/PS: Ignacio, Manuel, Nils In EST/ISS: Thomas, Christophe, Stephan


EDMS ID: 341082


CERN-IT/DB

Questions & Answers

Documents

CERN-IT/DB After-C5 Presentation EDMS Service Migration Monica Marinucci Lopez October 4th 2002 EDMS Document: 341082