1 / 10

DIRAC Configuration Service

DIRAC Configuration Service. R. Graciani Casajus I. Stokes-Rees. Overview. Introduction Architecture Client Local Configuration Master Server Slave Server Outlook. Introduction. Evolution from InformationService Aims:

riordan-nyhan
Download Presentation

DIRAC Configuration Service

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. DIRAC Configuration Service R. Graciani Casajus I. Stokes-Rees

  2. Overview • Introduction • Architecture • Client • Local Configuration • Master Server • Slave Server • Outlook DIRAC Configuration Service

  3. Introduction • Evolution from InformationService • Aims: • Allow DIRAC applications to get configuration parameters and locate resources. • High reliability and remove single point of failure. DIRAC Configuration Service

  4. Architecture • Clients: • Merge Local and Remote Configurations. • Keep local cache of Remote. • Local Configuration: • .ini files • Remote Configuration: • Configuration Servers • Master-Slave paradigm for servers. DIRAC Configuration Service

  5. Client (I) • From DIRAC.InformationServices.ConfigurationService.CSClient import cfgSvc • cfgSvc initialized from dirac.ini. • cfgSvc.reinitialize( iniList ) • cfgSvc.getSections() • cfgSvc.getOptions( Section ) • cfgSvc.getValue( Section, Option, Default ) DIRAC Configuration Service

  6. Client (II) • These methods always return S_OK or S_ERROR dictionaries (never raise exceptions). • Uses [ConfigurationService]/List to find Remote configuration Servers • Merges Local Data with Remote Data, keeping local more pre-emptive. • Keeps on memory cache of Remote Data. DIRAC Configuration Service

  7. .ini files • Data Format: • Organized in Key-Value Options grouped in Sections. [Dirac] Site = LCG.CERN.ch Mode = test … • One or more .ini files can be merged into a Local Configuration. • $DIRACROOT/etc/dirac.ini is default. DIRAC Configuration Service

  8. Master Server • Remote Configuration is kept on a 1-Master:n-Slaves setup. • Master: • Has Read and Write interfaces. • Keeps versioned master copy of Remote Configuration. • Updates version when data is changed. • Includes: • HGSE CLI to write. • HGSE (unsecure) and Web Interfaces to read. DIRAC Configuration Service

  9. Slave Servers • Have only Read interface. • Get a copy of the Remote Configuration. • Check Master for current version and updates. • Include: • HGSE (unsecure) and Web Interfaces to read. DIRAC Configuration Service

  10. Outlook • Complete migration from old InformationService methods to new ConfigurationService ones. • Uniform treatment of .ini files in CLI’s and scripts (arguments). DIRAC Configuration Service

More Related