On Fri, 19 Jul 2013 at 13:22 -0000, Lissa Valletta wrote:
> What release of xCAT are your running now.
2.7.6 to 2.8.x. I could keep the same version and then upgrade if
folks thought that safer. I could possibly upgrade first which might
be even better (the osimage changes have me a little nervous).
> If you move to another machine, then you have the benefit of having
> the old machine around for reference.
Yes, that will be the plan.
> I think I would dumpxCATdb ( please do not just copy files) on the
> old machine. run tabprune auditlog -a before you do. That is
> usually the biggest table, unless you have been pruning it or have
> auditlog turned off.
Planned. I do periodic dumpxCATdb to preserve configuration history
and look for unexpected changes. auditlog is off.
> Another good way to backup your configuration ( including the
> database) is run xcatsnap.
Never looked at it before. It shows one other directory I had not
planned to copy (/root/.xcat).
xcatsnap looks useful, but it appears preserve the ssh and ca private
key files. I don't like the idea of these being sent outside the
cluster, even for diagnostic purposes.
> I would install the new machine with Centos6 and go through the
> process documented for setting up the MN . I expect you might just
> want to copy /etc/hosts and /etc/resolv.conf from the previous MN.
> If hostname and ip address are the same then this should be pretty
> easily. Install xCAT - good time to go the latest release.
> restorexCATdb from your backup.
>
> run makedns -a
> run makedhpc -n
> run makedhcp -a
>
> Run rspconfig to update the MM with the new ssh keys
> run makeconservercf to update with the new credentials
>
> Run xdsh -K to your nodes to put out the new ssh keys.
I want to preserve the old ssh keys (at this time). External systems
have them in various known_hosts files and I don't want to deal with
the fallout at this time.
In the future I want to change the ssh keys but I would rather that be
a separate step. (We also need to periodically change all the other
secrets on the cluster, root password, bmc passwords, switch
passwords, etc).
> Depending on how your nodes are provisioned, There are probably
> directories under /install such as /install/custom you may want to
> copy to the new machine.
I'll probably copy (and cleanup) /install to the new node.
> If these are diskfull installed node, I think this is about all you
> need to do.
>
> If diskless images you might want to use the imgexport/imgimport
> commands, You might want to generate new images for Centos6 thoough.
> You are not going to be able to generate a Centos 5 image on a
> Centos6 MN.
The xCAT node is the last thing in this cluster running CentOS 5.
Everything else has already been upgraded.
Thanks,
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
