About switching to SL5, essentially from scratch, I am about to install alongside our SL4/gLite 3.1 server nodes a set of equivalent SL5/gLite 3.2 ones, with node types:
BDII
CREAM
DPM mysql
DPM disk (3 of them)
TORQUE_server
The APEL and UI servers and the WNs are already on SL5.
I may be able to copy several configuration files across from the SL4 version to the SL5 one, but the SL4/gLite 3.1 systems have a number of hand-made somewhat hacked configurations.
Each service will be installed in its own SL5 VM, except for the DPM disk servers which will be on real hw.
The installation will be manual (no QUATTOR/Cfengine/..., just install and then sort out later).
Assuming I do nothing else and work nominal hours (neither will happen :->, but I need a baseline):
* How long do you think it will take to provision and setup the OS layer and then the middleware layer for all?
* Additionally to commission the lot into a smoothly running system?
Because there is the possibility of just declaring a site downtime and then at risk time for the duration, to avoid having to maintain the old set, and to avoid having both sets of VMs running at the same time on the same hosts.
Any suggestions, shortcuts, tips welcome. My main sources will be the main installation page:
> https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320
and the (always useful) ScotGrid (and others) blogs.
I am tempted to be brave and install EMI 1 instead of gLite 3.2, as the latter will be obsoleted in around 10 months time, but I wonder how risky it would be.
|