On 17 March 2011 15:37, J Coles <[log in to unmask]> wrote:
> Ewan/Henry/Stephen
>
> Thanks for the discussion so far. I at least need to find out exactly what is meant by an "in-place installation". Meanwhile so far I only pick up the SEs being a major problem and the rest inconvenient.
That's purely because SEs are the only things that maintain long-term
state (the files and file metadata they store).
I think *any* service would be hard to "upgrade", and would probably
be easier to junk and reinstall (which is potentially problematic).
The issue with SEs is that you can't really do that unless you can
guarantee that the database schema will remain consistent (so you can
dump your database backup you made pre-"junk and reinstall" back into
the new empty database). I have seen nothing to make me believe that
this won't be the case, but it is a worry. And, of course, while your
SE is down, you can't access any of the files on it. When a CE is
down... you can use the other CEs to run jobs at the site.
Sam
> If you are aware of really specific problems please add them. If we were to go back with requests for upgrade paths to be made available we would need to specify any priorities.
>
> Thanks,
> Jeremy
>
>
>
> On 17 Mar 2011, at 15:25, Stephen Burke wrote:
>
>> Testbed Support for GridPP member institutes [mailto:TB-
>>> [log in to unmask]] On Behalf Of Ewan MacMahon said:
>>> These are RPMs. This is what package managers do; you upgrade from foo-
>>> 1.0
>>> to foo-2.0 and it removes all the old foo-1.0 files and installs the
>>> new
>>> foo-2.0 files. And it runs pre- and post- install scripts to fix up any
>>> oddities.
>>
>> But in this case you also have yaim creating or changing things after installation, plus any customisation added by the admin. (Of course yaim itself also has to change in lots of ways to accommodate this.)
>>
>>> The other option if that can't be managed is "don't do that then"
>>
>> That's no longer an option, it was decided a year ago when EMI started.
>>
>>> Or we could do something less breakage prone and more incrementalist?
>>
>> Except that EMI is a new project, and as always decided to stamp its mark on everything by restructuring it.
>>
>> Stephen
>
|