On Tue, Oct 26, 2004 at 09:52:44PM +0100 or thereabouts, Henry Nebrensky wrote:
> On Tue, 26 Oct 2004, Steve Lloyd wrote:
> > RB. Since I couldn't find any info I copied
> > /opt/edg/etc/atlas/edg_wl_ui.conf to my home space, edited it by hand
> > and included it via the --config-vo option on edg-job-submit. This
> > surely can't be how it's supposed to be for a mere user like me.
You can get a list of RBs that support atlas with the
$ ldapsearch -x -H ldap://lcgbdii02.gridpp.rl.ac.uk:2170 \
-b 'Mds-vo-name=local,o=Grid' \
GlueServiceURI GlueServiceHostingOrganization GlueServicePrimaryOwnerContact
This shows trimmed down.
A couple of points here though are that having the RB publishing
an end point was only added in LCG2_2_0 and also the not
advertised fact that were retaggings of LCG2_2_0
once it has been realised this had been screwed up. This is why
your see gram and https above. They should all be https.
Of course you should not have to really manage all of this
your self and the edg-job-* commands could look up in
the information system when you use it what RBs you can
and should use.
This has been mentioned many times and was a while ago proposed
to be added. To my knowledge this has not been done but there
is currently a lot changes queued up in the next release.
> /opt/edg/etc/atlas/edg_wl_ui.conf should already include the Atlas RB -
> if it doesn't, moan at the UI's sysadmin...
> ... of course, as a UI sysadmin myself, I have no idea where to find out
> these things for arbitrary experiments.
> It's possible to use an EDG_WL_UI_CONFIG_VO environment variable
> to specify a config file rather than --config-vo each time, but it's not
> mentioned in the current edg-job-submit man page and I've never tried it.
> [Section 5.2.6 of the LCG2 User Guide. I found it by searching for
> EDG_WL_UI_CONFIG_VAR, which I knew about already...]
> Dr. Henry Nebrensky [log in to unmask]
> "The opossum is a very sophisticated animal.
> It doesn't even get up until 5 or 6 p.m."
[log in to unmask]