I have made a new release
Here is an example of the new variables for YAIM
# dCache-specific settings
DCACHE_ADMIN="gppse01.gridpp.rl.ac.uk"
DCACHE_POOLS="gppse01.gridpp.rl.ac.uk:/pool dev07.gridpp.rl.ac.uk:/pool dev01.gridpp.rl.ac.uk:/pool dev04.gridpp.rl.ac.uk:/pool"
# Optional
# DCACHE_PORT_RANGE="20000,25000"
# DCACHE_DOOR_SRM="door_node1[:port]"
# DCACHE_DOOR_SRM="dev04.gridpp.rl.ac.uk"
# DCACHE_DOOR_GSIFTP="door_node1[:port] door_node2[:port]"
# DCACHE_DOOR_GSIFTP="dev06.gridpp.rl.ac.uk"
# DCACHE_DOOR_GSIDCAP="door_node1[:port] door_node2[:port]"
# DCACHE_DOOR_DCAP="door_node1[:port] door_node2[:port]"
must rush as dental appointment and will make release notes later,
This installation now works first time after 4 mins on my test box after install finished with srmcp
Please test and state if thier is anything else you think should be done if any of you have time, apart from information system integration, supporting per host port options and per VO db's as these are penciled in already a targets.
Regards
Owen
On Thu, 15 Dec 2005 11:15:30 +0000
Owen Synge <[log in to unmask]> wrote:
> On Wed, 14 Dec 2005 11:05:32 +0000
> Greig A Cowan <[log in to unmask]> wrote:
>
> > Hi Owen,
> >
> > > a followed by changing lines 75 to 79 of
> > > "/opt/d-cache/config/dCacheSetup" to below
> > >
> > > java_options="-server \
> > > -Xmx256m \
> > > -XX:MaxDirectMemorySize=256m \
> > > -Dorg.globus.tcp.port.range=20000,25000 \
> > > -Dnetworkaddress.cache.ttl=600 "
> >
> >
> > Really you want to be able to specify the port range in site-info.def
> > and get dCache to use that. There are a couple of places in
> > dCacheSetup where the port range is used and I'm sure that the
> > previous version of YAIM managed to correctly set one of them to the
> > value specified in site-info.def, but the other remained at the
> > default (20000:25000).
> >
> > Cheers,
> > Greig
>
> Yes the problem now fixed is that I placed a "-" rather than a "," in
> the generated output. See last release notes.
>
> If you have time please verify an install with the latest release from
> the preproduction repository, as site specific issues maybe creeping in,
> I have only tested on dev boxen at RAL.
>
> I am going to work on splitting service until Mathias de Riese gives me
> the information provider door packaged within the D-Cache RPM which was
> produced by the same PHD student who wrote this for DPM, GIP integration
> will continue after this functionality is delivered which should be
> early next week.
>
> I have also been thinking about storing check sums for configuration
> files to prevent the default system from over writing files that have
> been modified post YAIM install so upgrades go smoother, but it seems
> this is moving ahead of other components and since their are other areas
> for improvement have decided to delay this approach (Yes its based upon
> RPM's limited configuration functionality and Debconfs more flexible
> behaviour)
>
> I shall start on the effort to specify door-host relations in the top
> level site-info.def.
>
> Please send feedback for functionality you would expect for D-Cache or
> DPM which is not present in DPM or D-Cache YAIM and this will help me
> pick relevant things to do rather than do the typical developer mistake
> and solve problems only I see as problems.
>
> Regards
>
> Owen
|