The first bug fix release has now been placed on our servers, install is
as in the previous release, but with 2 bug fixes,
2005-12-14 16:20 osynge
* yaim/functions/config_sedcache: The gridmap generation system is
needed to be run before the system works for GSI.
2005-12-14 14:50 osynge
* yaim/functions/config_sedcache: Fixed small globus port range bug.
I also added a warning message to the impatient.
"D-cache takes some time to initialise"
Please note this yaim install WILL NOT upgrade your D-Cache install
automatically and the system still work. Please do not install on a
production box without testing first. I probably will work on adding
this support into future versions, but for now this software is an
installation system not an upgrade path as this is untested, backing
up your configuration files and your PNFS databases is strongly
recommended if you intend to use Yaim as an aid to upgrading, but some
by hand work will be needed particularly with respect to pnfs.
PNFS upgrading is a "by hand" task, and the D-Cache team strongly
believe that PNFS upgrades should not be automated.
At the moment D-Cache has documented the instructions for a by hand
upgrade to the databases in the D_Cache book, and Greg Cowan has also
written notes about his experiences on the D-Cache pages of the GridPP
website.
This version of Yaim upgrades just fine from the last release I made
2 days ago, but people who installed that version should update the
system, set the environment variable and rerun YAIM as below
apt-get update
apt-get upgrade
export RESET_DCACHE_CONFIGURATION=yes
/opt/lcg/yaim/scripts/configure_node ${PATHTO}/site-info.def SE_dcache
I shall be working closely with D-cache to improve the support for
upgrading D-Cache automatically. We are hoping we can upgrade all
sites automatically without upgrading PNFS. D-Cache feel that
upgrading D-cache is a higher priority than upgrading PNFS, as very
few sites have hit the scalability issues that prompted D-Cache to
migrate pnfs to postgres. Once this is done we hope sites will be
able to upgrade to the latest PNFS by hand.
The new GIP integration work should start early next week as the
deployment of the D-Cache information provider is coming out in
the next beta or production release.
Should people wish to use the untested D-Cache upgrade path please
remember that the following 3 environment variables are available.
# Set this to wipe the postgres databases
# Optional:RESET_DCACHE_RDBMS=yes
#
# Set this to reset the PNFS server
# Optional:RESET_DCACHE_PNFS=yes
#
# Set this to reset the D-cache configuration
# Optional:RESET_DCACHE_CONFIGURATION=yes
These options will override Yaims default behaviour for D-cache of not
overwriting files all ready configured. These are often used for
development so may work as expected so don't play with RESET_DCACHE_RDBMS
on production boxes,
Regards
Owen
PS
CVS tag owen_test_release_2005_12_14 for this release
On Tue, 13 Dec 2005 14:11:28 +0000
Owen Synge <[log in to unmask]> wrote:
> I am pleased to announce D-Cache 1.6.6.2 support for YAIM, this
> version of YAIM does not support upgrades from previous releases but
> does support all of the functionality of previous YAIM releases for
> D-Cache.
>
> Road map for YAIM D-Cache
>
> The functionality seems to now match what was available before with
> YAIM but for the new stable release of D-cache, which was the main
> milestone for release version 1, I am going on to test with the beta
> release b3 of D-cache with YAIM, first priority will definitely be
> support of YAIM.
>
> After the new releases of D-cache is installed I shall focus on the
> Glue schemer D-Cache integration, this has been made my second
> priority. This is a more universal than than DMZ's and D-Cache service
> node decomposition that is as yet unexplored and so not asked for by
> many tier 2's.
>
> DMZ support and decomposition of a D-Cache cluster is much less work
> than the BDII integration and will consist of splitting not just pool
> and admin nodes but also pnfs manager and door nodes from their
> default bindings to pool and admin nodes within YAIM format, I shall
> have to chat with Oliver for some style guidance before adding this.
> This code is already implemented but the environment variables
> decoding is not implemented and so this functionality is not "switched
> on" or tested as yet. I hope this allows users to see functionality
> in D-Cache they had not appreciated before such as the advantages of
> decomposing services into DMZ's and better load balancing as node
> selection of the PNFS-manager will eventually be a YAIM environment
> variable so it can be placed upon a separate host from the SRM node.
>
> The code changes was implemented after studying the bash
> implementation of debconf, and should take very little code (And as
> usual a lot of testing) to insert the YAIM for D-cache into dpkg and
> debconf making D-Cache native support for debian and also a highest
> common denominator for most config engines (Who knows EDG/EGEE seems
> to average 1-2 per year). All that is required to support debian
> nativity is to isolate the environment parsing code and replace it
> with calls to debconf or what ever higher level system is needed, the
> CVS tag of YAIM is called (owen_test_release_2005_12_12) and is ready
> for testing.
>
> The apt repository preproduction has been prepared. Install is as in
>
> http://storage.esc.rl.ac.uk/documentation/html/D-Cache-Howto/ch02.html
>
> and so essentially unchanged from previous versions but the section
>
> "Create the relevant pointers to the rpm repositories"
>
> should contain the revised content
>
> echo 'rpm http://storage.esc.rl.ac.uk/ apt/datastore/sl3.0.4
> preproduction' \
> > /etc/apt/sources.list.d/gpp_storage.list
>
> echo 'rpm http://grid-deployment.web.cern.ch/grid-deployment/gis
> apt/LCG-2_6_0/sl3/en/i386 lcg_sl3 lcg_sl3.updates' \
> > /etc/apt/sources.list.d/lcg.listhttps://savannah.cern.ch
>
> echo 'rpm http://grid-deployment.web.cern.ch/grid-deployment/gis
> apt/LCG_CA/en/i386 lcg' \
> > /etc/apt/sources.list.d/lcg-ca.list
>
> note line 1 changes to have "stable obsolete" replaced by
> "preproduction" this is increase any tier 2 has left the stable
> version in their apt-sources by mistake and suddenly are faced with an
> unplanned D-Cache upgrade.
>
> Attached is a specimen site-info.def and a Dcache install log for a
> pool node, I hope they help.
>
> Some of the steps in the HOWTO are also obsolete and this will have to
> wait until I have time to document such things. (SRM wiki is to me a
> higher priority as D-Cache is much better documented than SRM sad but
> true).
>
> Please send all bugs to "LCG Operations" and assign D-Cache related
> bugs to me
>
> https://savannah.cern.ch
>
> Regards to all
>
> Owen
>
|
