Configuration Monitoring Use Cases and a Draft Architecture - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Configuration Monitoring Use Cases and a Draft Architecture

Description:

Software/hardware package and installation configuration: ... Scaling problem from EDG: 'System jammed up with increasing query rate and hence ... – PowerPoint PPT presentation

Number of Views:8
Avg rating:3.0/5.0
Slides: 17
Provided by: yuj3
Category:

less

Transcript and Presenter's Notes

Title: Configuration Monitoring Use Cases and a Draft Architecture


1
Configuration Monitoring Use Cases and a Draft
Architecture Yujun Wu
2
Why do we continue this work?
  • A lot of new use cases
  • New requirements
  • No client-side servers
  • DPE
  • Possible connection with the service/resource
    management

3
New use cases (I)
  • Software/hardware package and installation
    configuration
  • Job submission Job generator, e.g. MOP,
    need to know a list of configurations on a
    computer resource (e.g., CMS DAR software
    location, scratch area path, etc.) for generating
    and submitting. Same applies to general users
  • Software/hardware distribution sources
    User can browser whats available in the
    distribution source and download the need
    components, e.g., Pacman cache, Rocks DB.

4
New use cases (II)
  • Available Services/Resources
  • Available services their configuration
    User may want to know what kind of services
    available within an organization (e.g., DPE) and
    the corresponding configurations, for example
  • - gatekeeper, port number and
    available job managers
  • - gridftp server, port number,
    capacity
  • Access right who can access these
    services/resources priorities
  • Availability of the services Services
    may be temporally not available for upgrades
    and/or emergency repairmen.

5
New use cases (III)
  • Virtual Organization authentication and
    authorization configuration info
  • Which certificate is able to and/or needed
    to use the resources
  • Local system hardware/software configuration
    info
  • Installation configuration
  • Service configuration

6
Two possible architectures
  • Full Globus MDS Style
  • - Purely use the Globus MDS to track the
    site configuration information
  • - Hierarchy GRIS/GIIS
  • Semi-MDS Style
  • - For the local sites, continue to use the
    GRIS for site information publishing
  • - At the higher-level, put the information
    into a relational database

7
Full Globus MDS style (I)
  • Architecture

USCMS GIIS
Clients
GSI
GSI register info
Site GIIS/GRIS
8
Full Globus MDS style (II)
  • Advantages
  • Fast setup, almost ready to use
  • Disadvantages
  • No log info
  • Scaling problem from EDG System jammed
    up with increasing query rate and hence could not
    give reliable information to clients such as
    RB---- Stephen Burke, EDG WP8
  • Confusion can be caused if a site begins
    to stop sending info to the GIIS---which sometime
    happens.

9
Semi-MDS style (I)
  • Architecture

DB Server
Clients
GSI
GSI Pull info
Site GIIS/GRIS
10
Semi-MDS style (II)
  • Architecture

1. Configuration info 2. VO Service
Certificates 3. Access rights (which group can
access) 4. Services/resources Availability 5.
Resource registration/verification 6. Possibly
resource reservation?
DB Server
Clients
GSI
GSI Pull info
Site GIIS/GRIS
11
Semi-MDS style (III)
  • Advantages
  • Info are logged
  • Sites are controlled and tracked
  • More scalable---depending on the DB
    server, LDAP is famous for its slow
    writing.
  • Possibly be able to expand it as the a
    service/resource management server (we can put
    additional info into the database, query the DB
    server to get all these additional info).

12
Semi-MDS style (IV)
  • Disadvantages
  • Slower when retrieving data---comparing
    with LDAP
  • Need some coding and design (we have a
    summer student who can work on it)

13
Where are we?
  • A first version of schema has been done
  • A first version of server-side information
    provider for MDS has been finished
  • A client-side has been written for use by MOP
  • We are ready to test with GRIS, at least for MOP
    production.

14
Deployment plan
  • Begin to test locally with MOP
  • If the feedback is positive, we will ask to put
    it into DPE Pacman and test it on the DGT
  • Using the MDS web by Jenny Schopf to show the
    info on the web (with restriction access).
  • In the meantime, we will try with the new
    architecture and web services

15
We need your help!
  • We may need your help to start the GLOBUS MDS
    with the proper configuration
  • We also need your feedback!

16
Acknowledgement
  • Rick has long been wanting a configuration
    monitoring tool Rick and Greg have been giving a
    lot support on this.
  • It has been very beneficial from the discussion
    with Greg, Rick, Anzar and many others.
Write a Comment
User Comments (0)
About PowerShow.com