So, after looking at Foreman it seems to do a lot of what our system intendeds to do but I'm having trouble grasping how I should configure hosts/proxies to make it work the way we'd like.
What we have now is a puppet master for each esxi host. So that any VM on that esxi host uses the puppet master on that esxi. vh01: - va01 (puppet master) - vm1 - vm2 - vm3 vh02: - va02 (puppet master) - vm1 - vm2 - vm3 Something like that. The puppet modules and configurations are sourced from the primary va01 and synced to va02/va03/etc (via lsync/svn) What I'd like to do is setup a primary Foreman server that manages puppet/provisions hosts and then the "local" master manages the host once it's up. I've been looking over these documents "https://theforeman.org/manuals/1.12/index.html#3.2.3InstallationScenarios"; trying to understand what they are saying but I am unsure. Does foreman have a method of making a "local" master mirror the primary foreman setup? Am I not understanding how Foreman should be configured? The cert section is quite confusing, it mentions /var/lib/puppet/ssl but 4 doesn't seem to store there so wondering if thats just old documentation? I'm open to actually restyling our design (the current was not my choice and seems quite overkill) to a more "local cluster" where all the vms on all the local vhosts (vhXX) in say dllstx09 are served from a puppet master in dllstx09 cluster (we currently have some 20+ vhosts in dllstx09 pop) and pop mlpsca01 has it's own master, etc. I guess my problem is understanding just how foreman links to other foreman smartproxies/puppet masters. Again I'm happy to read/watch any videos that you might find helpful on this topic for the current version of Foreman. -- 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 protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
