> > I'm planning on upgrading our Spacewalk server from CentOS 5 to CentOS 6 > > and updating from spacewalk 1.4 to 1.5 (maybe 1.6 by the time I get > > around to this). My plan is to build a new CentOS 6 server and install > > whichever version of Spacewalk I end up using and then just copying over > > database, config files, and /var/satellite from the old server. I'll > > also have to be sure the hostname is the same for SSL purposes. Is > > there a quick laundry list of things that will need to be brought over? > > Is this a sound approach? > > Yes, this approach is sound. > > Appart from database and /var/satellite from the old server, you should > also backup & restore ~nocpulse/.ssh/nocpulse-identity* files and content > of /root/ssl-build directory. > > In short, during your upgrade, you will: > > 1. Install a new CentOS 6 and new Spacewalk (this may or may not > be done on a new hostname, both will work) > 2. Restore and upgrade the db schema > 3. Resotore /var/satellite & ~nocpulse/.ssh/nocpulse-identity* > 4a. If you're keeping your original hostname: > > * Restore content of /root/ssl-build > * cd /root > * rhn-ssl-tool --gen-server --rpm-only > * rpm -Uvh /root/ssl-build/<MACHINE_NAME>/rhn-org-httpd-ssl-key-pair- > <VERSION>.noarch.rpm > * rhn-deploy-ca-cert.pl \ > --source-dir=/root/ssl-build \ > --target-dir=/var/www/html/pub/ > > > 4b. If you're switching to a new hostname: > > * rhn-ssl-dbstore -vvv --ca-cert=/root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT > * spacewalk-hostname-rename <NEW-IP-ADDRESS>
I forgot to add that you won't be restoring any configuration files from the previous installation. -MZ _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
