On Fri, 20 Oct 2006 12:11:21 +0100
Greig A Cowan <[log in to unmask]> wrote:
> Hi Matt (cc storage),
>
> I'm just having a play aroung with the new dCache version now. I've
> upgraded from a fresh YAIM installed 1.6.6-5 dCache to 1.7.0-16 from
> the DESY repository. Here is a list of things that that I've noticed
> so far:
>
> 1. Make sure (I mean really make sure) that you're running postgres
> pnfs and not gdbm pnfs, otherwise the upgrade will break things and
> it will be a bit of a hassle to fix them. I think all GridPP dCache
> sites are running postgres pnfs already.
OK my fault for poor documentation,
<quote>
Yaim method
For admin nodes run the following command:
/opt/glite/yaim/scripts/install_node ~/site-info.def glite-SE_dcache_admin_postgres
For pool nodes run the following command:
/opt/glite/yaim/scripts/install_node ~/site-info.def glite-SE_dcache_pool
</quote>
Should have pointed out that if you are running gdbm use the line
/opt/glite/yaim/scripts/install_node ~/site-info.def glite-SE_dcache_admin_gdbm
> 3. Related to this, there are java processes listening on ports that
> weren't previously being used. I'm looking to find out which ones
> should be firewalled off.
Oh dear, I shall have to look too.
> 5. Still trying to figure out what's going on with gPlazma (i.e.
> dCache VOMs compatibility). I can copy files into and out of the
> system, but I need to try using different VO roles. There are also
> some options set in some gPlazma config files that are puzzling me.
> There _might_ be some information in the documentation that I need to
> look at.
VOM's grid map intergration is coming real soon. (I have to test and package it)
> 6. I've only updated the head node so far, and it's working with
> 1.6.6-5 door and pool nodes (so far, things might change if gPlazma
> config changes).
This is rearly not a good idea, D-cache does serialise objects and transfer them across nodes. This may produce a less stable system, we at D-cache do not feel we can support sites doing this in prodcution.
> 8. Couple of issues with the dCacheSetup file:
>
> clientDataPortRange=50000:52000
>
> even though I set range to 20000-25000 in site-info.def.
> performanceMarkerPeriod=180
>
> appears twice.
Hmm, I found the clientDataPortRange bug yesterday, (I felt so stupid asking help and then getting the aswer have you checked the firewall)
The config option performanceMarkerPeriod being in thier twice is not important for functioning but nasty in asthetic, THis will have to be fixed. (I belive last takes presidence.)
> Assuming you check point 1 above the upgrade should not take you that
> long for the head node. I'm just about to upgrade the pool/door nodes,
> but I don't forsee any problems there. I'll let you know what else I
> find over the next couple of days.
>
> Cheers,
> Greig
Thanks Greig
Owen
>
>
>
>
> On Fri, 20 Oct 2006, Matt Doidge wrote:
>
> > Heya,
> > How's the testing going for the upgrade? If you think things are
> > good to go I'm planning on putting a scheduled downtime for an hour
> > on Tuesday morning and upgrading our dcache then. An hour should
> > hopefully be more then enough time.
> >
> > Have a good weekend,
> > Matt
> >
>
> --
> =====================================================================
> === Dr Greig A Cowan
> http://www.ph.ed.ac.uk/~gcowan1
> School of Physics, University of Edinburgh, James Clerk Maxwell
> Building
>
> TIER-2 STORAGE SUPPORT PAGES:
> http://wiki.gridpp.ac.uk/wiki/Grid_Storage
> =====================================================================
> ===
|