Hi Mark,
There is some discussions related to the groups.conf file on ROLLOUT
`what's up with groups.conf file' (Fri 3 Feb 2006) where Marteen says:
`The reason for all this machinery is to allow batch systems to be
configured to give higher priorities to jobs for certain groups/roles.
We did not yet look into how such might be done for Torque, LSF, ...'
So this lead me to believe that this is their but not used by anything in
2_7_0. You can leave as it is and safely run yaim or even use an empty
file and yaim will be fine.
Regarding, the VO info required by yaim you could try using the yaim web
tool VO management:
https://lcg-sft.cern.ch/yaimtool/yaimtool.py
Some information is likely to be missing, though hopefully with time it'll
get better. You can fill in the missing information using your old
site-info.def file and the link on the GridPP wiki Pete sent. There is no
info in the latter about the VO_${VOS}_VOMSES variables which gives
important information such as which port on the voms need to be used.
This lead to the question what is the status of VOMS in 2_7_0? I'd be
interested to know more about this. Though, it doesn't look very healthy!
I've got loads of error messages such as:
/var/log/messages:Feb 13 12:59:42 epgce1 edg-mkgridmap[13893]: voms
search(https://lcg-voms.cern.ch:8443/voms/dteam/services/VOMSCompatibility?method=getGridmapUsers&container=%2Fdteam%2FRole%3Dproduction):
Internal Server Error
in my /var/log/messages. I think that this is related to wrong
certificates files in /etc/grid-security/vomsdir (they are packaged in the
2_7 rpms.) I've solved this (well I hope) for our pre-production service
RB and CE by directly downloading the relevant pem files.
I hope this clarifies things a bit, others may wish to fill in the missing
information/ correct me,
Yves
On Wed, 15 Feb 2006, Mark Nelson wrote:
> --[PinePGP]--------------------------------------------------[begin]--
> Hello
>
> I've been going thought the release notes and have come across the
> groups file. I'm assuming that this is needed for this release, the
> example file only covers alice, atlas, lhcb, dteam, biomed. Does anyone
> know where to find the entries for the other GridPP approved VO's as
> defined by the following wiki entry -
>
> http://wiki.gridpp.ac.uk/wiki/GridPP_approved_VOs
>
> Mark.
>
> --
> -------------------------------------------------------------
> Mark Nelson - [log in to unmask]
>
> IPPP, Department of Physics, University of Durham,
> Science Laboratories, South Road, Durham, DH1 3LE
> Office: +44 (0)191 334 3811, Direct Dial: +44 (0)191 334 3653
>
> PGP Key: http://www.ippp.dur.ac.uk/~mn/pgp_key.txt
> This mail is for the addressee only
> --[PinePGP]-----------------------------------------------------------
> gpg: /home/yrc/.gnupg/options:112: deprecated option "honor-http-proxy"
> gpg: please use "keyserver-options honor-http-proxy" instead
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: Signature made Wed 15 Feb 2006 11:08:48 GMT using DSA key ID ED0C81C1
> gpg: Can't check signature: public key not found
> PinePGP: Encryption backend encountered error.
> --[PinePGP]----------------------------------------------------[end]--
>
|