On 18 October 2016 at 04:28, Austin Smith <smith.aus...@gmail.com> wrote:
> On Friday, October 14, 2016 at 5:36:35 PM UTC-4, steved0ca wrote:
>> It looks like it is not possible to add Katello to an existing Foreman
>> installation. http://projects.theforeman.org/issues/7605
>> Are there any recommended methods of migrating from an existing Foreman
>> only install, to a fresh Foreman+Katello installation? The puppet modules
>> and existing puppet certificates should be easy enough to copy over, but
>> what about my templates/hosts/host groups etc? Any way I can dump this data
>> and import it into the new host?
There's a few things you can try - if you want to play with these, start
with a sandbox you can break :)
For any Foreman objects, like Hostgroups, you can probably do something
with hammer-csv (https://github.com/Katello/hammer-cli-csv) to dump objects
from one host and import them to another. Assuming you have both Foreman
instances set up to handle orchestration to the same proxies, I *think*
that'll work for DNS/DHCP etc
For classes assigned to Hosts *only* there's also an ENC importer. To be
honest, hammer-csv is probably better, as this rake task flattens the
hostgroup structure, but as an alternative, look at "foreman-rake -T | grep
For templates, there's no good way to get them *out* (except maybe
hammer-csv again) as they're stored in the db - but for managing them in
general, you could look to the foreman_templates plugin (
https://github.com/theforeman/foreman_templates) which enables you to use a
git repo as a source of templates. It's a one-way sync though, so you'll
have to populate the repo first.
Hope that helps - do let us know how you get on!
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 post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.