My understanding on this :
- client server switch:
Quick answer would be : you can't, because the puppet CA would be different.
Unless you've got a dedicated puppet CA server (or your own CA…).
Now, it is possible to have several puppet masters and slaves, you just have to change the puppet server in the file /etc/puppet/puppet.conf - but then you must make sure your different puppet servers correctly point to the ENC (forman) that's in production…
Actually, the foreman updates also are quite 'frightening' for me too, because I don't want to break what I have, so I'd be glad hearing about others 2 cents on this foreman/puppetmaster upgrade procedure.
For now, I would surely install a VM with my current setup, attempt an upgrade on it, and if working, roll out the upgrade in production.
2)c) I would say : database dump on old foreman, database restore on new foreman, schema upgrade on the new foreman ?
If the question is "how to migrate from sqlite to mysql/postgres" : I read ruby is db agnostic and it should be fairly "easy" to "read the db on one backend, then write it on another" - but I did not succeed in finding such a (working) tool, and I'm no ruby programmer. I found one tool that said it could do that, but failed at recreating tables…
De : email@example.com [mailto:firstname.lastname@example.org] De la part de Jean-Michel Barbet
Envoyé : mardi 17 septembre 2013 10:33
À : email@example.com
Objet : [foreman-users] How to replace an existing Forman/Puppet server by a new one
I am new on this group, so, hello everybody and please forgive me if
I break some cultural rules…
I started with Puppet/Foreman late spring and I now have a small
cluster installed and managed this way. Now I would like to secure
things a bit : first replay the installation of the Puppet/Foreman
server and make sure I am able to reinstall everything in a controlled
manner, second back-up all data that has to be.
First question is how to switch my Puppet clients from one server
to a new one (same puppet/foreman versions for the moment, but
this is also a use case to switch to a more up-to-date server)
Installing (foreman-installer) my new server I came across a few
a) foreman-installer uses the lastest foreman version (1.2) while
I wanted to install 1.1. I think I have understood how to
use params.pp files to obtain what I want.
b) How to tell foreman-installer to use MySQL backend rightaway ?
I set use_sqlite to false but it does not seem to be enough.
There are no params for that…
c) What is the best way to transfer DB data from one server to
another given that if the Foreman versions do not match, the
schema could be different ?
If some of you have been already in this situation, thanks for
Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: firstname.lastname@example.org
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.