Hi Greig (and Jens, info system guru...)
Back to bug you, I'm afraid.
So, I am using Michel's script from https://twiki.cern.ch/twiki/bin/
view/LCG/GSSDDPMInfo. I found two bugs in it, but quite easy to fix.
For the record:
1. If you specify the database in DPMINFO, e.g.
[log in to unmask]
then this is set as the database for DPM and DPNS, so it breaks the
query to DPM for space tokens. Obviously a new syntax is required if
you have to specify both database names, like
@svr018.gla.scotgrid.ac.uk/cns_db/dpm_db. However, for most sites not
specifying is safest. Unfortunately, some fool who wrote the YAIM
config_DPM_info function decided to code in the default name.
2. On my machine the Net::Domain module is broken and gets the wrong
hostname (internal). It's safe to set
my $this_host = `hostname -f`;
chomp($this_host);
my $this_domain = $dpm_domain;
Assuming that hostname has been set to the correct public interface,
as it should have been.
(Plus the issue about dpminfo user not having access to dpm_db you
noted.)
OK, so now it works:
svr018:~# /opt/lcg/var/gip/provider/lcg-info-dpm-space-tokens
gla.scotgrid.ac.uk svr018.gla.scotgrid.ac.uk gla.scotgrid.ac.uk
dn:
GlueSALocalID=atlas:ATLASDATADISK:online,GlueSALocalID=atlas,GlueSEUniqu
eID=svr018.gla.scotgrid.ac.uk,mds-vo-name=resource,o=grid
objectClass: GlueSATop
objectClass: GlueSA
objectClass: GlueSAPolicy
objectClass: GlueSAState
objectClass: GlueSAAccessControlBase
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueSARoot: atlas:/dpm/gla.scotgrid.ac.uk/home/atlas
GlueSAPath: /dpm/gla.scotgrid.ac.uk/home/atlas
GlueSAType: permanent
GlueSALocalID: atlas:ATLASDATADISK:online
GlueSAName: Replica online storage for VO atlas
GlueSATotalOnlineSize: 10995116
GlueSAUsedOnlineSize: 0
GlueSAFreeOnlineSize: 10995116
GlueSAReservedOnlineSize: 0
GlueSATotalNearlineSize: 0
GlueSAUsedNearlineSize: 0
GlueSAFreeNearlineSize: 0
GlueSAReservedNearlineSize: 0
GlueSARetentionPolicy: replica
GlueSAAccessLatency: online
GlueSAExpirationMode: neverExpire
GlueSACapability: unset
GlueSAPolicyMaxFileSize: 10000
GlueSAPolicyMinFileSize: 1
GlueSAPolicyMaxData: 100
GlueSAPolicyMaxNumFiles: 10
GlueSAPolicyMaxPinDuration: 10
GlueSAPolicyQuota: 0
GlueSAPolicyFileLifeTime: permanent
GlueSAStateAvailableSpace: 10995116277760
GlueSAStateUsedSpace: 0
GlueSAAccessControlBaseRule: atlas
GlueChunkKey: GlueSEUniqueID=svr018.gla.scotgrid.ac.uk
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 3
dn:
GlueVOInfoLocalID=atlas:ATLASDATADISK,GlueSALocalID=atlas,GlueSEUniqueID
=svr018.gla.scotgrid.ac.uk,mds-vo-name=resource,o=grid
objectClass: GlueSATop
objectClass: GlueVOInfo
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueVOInfoLocalID: atlas:ATLASDATADISK
GlueVOInfoName: atlas:ATLASDATADISK
GlueVOInfoPath: /dpm/gla.scotgrid.ac.uk/home/atlas
GlueVOInfoTag: ATLASDATADISK
GlueVOInfoAccessControlBaseRule: VO:atlas
GlueChunkKey: GlueSALocalID=atlas:ATLASDATADISK:online
GlueChunkKey: GlueSEUniqueID=svr018.gla.scotgrid.ac.uk
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 3
And it also works when I run /opt/lcg/libexec/lcg-info-wrapper.
However, the BDII stubbornly ignores it! Query
$ ldapsearch -x -H ldap://svr018.gla.scotgrid.ac.uk:2170 -b mds-vo-
name=resource,o=grid
and the space tokens are absent.
So, do I have to tweak the BDII in some way? It looks like it's in
the huff with glue 1.3 information and just ignores it?
(And will this also apply to the site level BDII?).
Thanks
Graeme
On 30 Jan 2008, at 15:04, Greig Alan Cowan wrote:
> Hi Graeme,
>
> See my email to the list from yesterday which covered this stuff
> (SAM availabilty... ).
>
> Cheers,
> Greig
>
> On 30/01/08 15:01, Graeme Stewart wrote:
>> Which prompts me to ask, how do I publish this? Do I need to
>> upgrade to glue 1.3 publishing?
>> Cheers
>> Graeme
>> On 30 Jan 2008, at 15:00, Graeme Stewart wrote:
>>> http://scotgrid.blogspot.com/2008/01/srm22-configuration-for-
>>> fdrccrc.html
>>>
>>> Cheers
>>>
>>> Graeme
>>>
|