VOMS Configuration

All the configuration is set via Puppet. Refer to the lcgvoms hostgroup and voms module for more info.

Upgrade procedure for a VOMS-admin release

For the VOMS-admin releases that change some of the existing functionality and/or add new features, we don't upgrade the software directly in production. Instead, we upgrade the voms-admin testing cluster (i.e. https://voms-testing.cern.ch:8443) first and then we notify the members of the experiments.

For doing so, we usually send a mail to the e-groups of VO-admins of the main four experiments:

And also opening a GGUS ticket to the aforementioned people.

It's also useful to set a date for the migration to get things going, e.g. a couple of week after upgrading the testing cluster.
The upgrade on production needs to be announced on the SSB and the C5 (via SNOW).

Topic attachments
ISorted ascending Attachment History Action Size Date Who Comment
Unknown file formatgz scripts.tar.gz r1 manage 3.8 K 2008-03-18 - 16:51 RemiMollon Several useful small scripts

This topic: LCG > LCGSecurity > VomsCern > VomsConfiguration
Topic revision: r30 - 2016-01-13 - AlbertoRodriguezPeon
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback