1 / 10

The DCS Databases Peter Chochula ALICE DCS Workshop February 28, 2005 Geneva

The DCS Databases Peter Chochula ALICE DCS Workshop February 28, 2005 Geneva. Two DCS databases are required Configuration database Archive Both databases are running on Oracle 10g CERN provides services on 9i Work has started on transition to 10g. Present Status – Configuration DB.

nysa
Download Presentation

The DCS Databases Peter Chochula ALICE DCS Workshop February 28, 2005 Geneva

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The DCS DatabasesPeter ChochulaALICE DCS WorkshopFebruary 28, 2005Geneva

  2. Peter Chochula, DCS Workshop Geneva, February 28, 2005 • Two DCS databases are required • Configuration database • Archive • Both databases are running on Oracle 10g • CERN provides services on 9i • Work has started on transition to 10g

  3. Peter Chochula, DCS Workshop Geneva, February 28, 2005 Present Status – Configuration DB • The JCOP FW configuration database has been revised, new version available as a integral part of framework • Next FW release (scheduled for the next week) will be compatible with to 10g client (Instantclient) • Performance tests need to be done • We need to know the exact DCS operation during the detector calibration • Main concern – performance of the device configuration (e.g. during the voltage scan)

  4. Peter Chochula, DCS Workshop Geneva, February 28, 2005 Present Status – the DCS Archive • The first release of the RDB archiving is available • Prototype installed in the DCS lab since 2 weeks • We are learning how to use it • Prototype project configured • Tested connectivity through the DCS application gateway (client and server running on different domains)

  5. Peter Chochula, DCS Workshop Geneva, February 28, 2005 The DCS archive • First tests will focus on performance (modifying existing projects) • We need to understand and test • Data backup and retrieval • Connection to services provided by IT • Configuration of the cache operating in P2 (Oracle Data guard?) • Access policies and privilleges

  6. Peter Chochula, DCS Workshop Geneva, February 28, 2005 RDB archiving principles Online – Available for browsing Offline Online 0010 Online 0009 Offline 0006 Backup 0003 Online 0011 Online 0008 Offline 0005 Backup 0002 Current 0013 Online 0012 Online 0007 Offline 0004 Backup 0001 PVSS External Media • Archive groups can contain several tables • Each group uses its own tablespace • All archiving aspects can be parametrized

  7. Peter Chochula, DCS Workshop Geneva, February 28, 2005 • For the pre-installation we assume that all archives can be stored online • We will develop/test connectivity to IT and archive backups • We need to know what are the requirements • How long the data needs to stay online • What data needs to be copied to offline and where (AliEn, gLite…)

  8. Peter Chochula, DCS Workshop Geneva, February 28, 2005 DCS Database Servers • Development server running in DCS lab • Hardware available for pre-installation server • Available disk space on the file server 2TB • Are some DCS activities foreseen in some other places at CERN (e.g. silicon lab etc.)? • If yes, we need to provide a service • Remember that the database installed in P2 will be unreachable from outside • What are the requirements for this service?

  9. Peter Chochula, DCS Workshop Geneva, February 28, 2005 Database planningConfiguration and Archive

  10. Peter Chochula, DCS Workshop Geneva, February 28, 2005 Explanations to planning • The user requirements complement the requirements as requested in the FERO talk • We need information on requested access patterns, archive parametrization, full list of data to be stored • IT requests 3months pre-notice for PRO installations • This must be preceded by tests on the DEV servers • We need to prove that databases to be installed on PRO servers are stable and optimized • The presented schedule is valid for the final service. The pre-installation will be used as a test bed

More Related