Notes on the VOMS/VOMRS Service
Service Components
While a Grid Registration Service has had an implementation based on LDAP, it is now based around a
VOMS/VOMRS application server and a database backend.
The application server consists of:
- VOMS application
- VOMRS web interface for managing VOMS user administration activities
- VOMS grid map generator (voms-admin)
VOMS High Availability
This is covered in
VomsWlcgHa
Equipment required
There is currently no capacity planning information for
VOMS so estimates will have to be made.
A standard 3.00GHz 2 CPU configuration with 4GB of memory will be used. Based on real life production data, this configuration could be revisited.
Engineering required
Development |
Purpose |
Start/Stop/Status procedure |
Scripts for VOMS operations |
Lemon VOMS availability test |
A lemon aware sensor which can be used for reporting availability. This should monitor the number of VOMS processes which are running |
Linux Heartbeat availability test |
A Linux-HA aware sensor which would activate the procedure for automatic switch from master to slave |
Switch procedure |
Automatic switch from master to slave changing the DNS alias, disabling the master, enabling the slave in its new master role |
Capacity Metric |
Capacity metrics defined for Number of renewals / second Number of inits / second |
Quattor configuration for Linux-HA |
NCM component to configure Linux-HA/Heartbeat |
Other Items to Consider
The security for the
VOMS server should be kept carefully controlled since it can be used to obtain additional access rights.
Open Items
Related Documents
--
TimBell - 18 Oct 2005