Good morning all,
I'm looking at foreman as possibly replacing our home-grown kickstart
management solution (as well as getting me all the wonderful things of
puppet). I have offices at multiple locations that I need to manage. Is
there a way to have one "master" foreman where all the configuration
changes get made and then proxy/slave/read-only/caching foremans at each of
the offices that provide that content (kickstart scripts, control of local
smart-proxies, etc.) to the local network? I need a site to be able to
provision even when disconnected from the main foreman instance, and then
sync back up when connectivity is restored. What I don't want to do is
manage 10-15 different foreman instances, each a king of their own castle.
I saw the video on locations/organizations on the foreman website, but
it seems this is only half the battle (centralized management, but not
offline support). I realize that this may seem like an odd question ("why
in the hell is this guy worried about provisioning servers when his WAN
link is offline…"), but trust me in that it is part of my job to
provide this service and it's not something I can change. The solution
doesn't have to be pretty, it could be as nice as "Navigate to this
submenu, add the remote instance as a smart proxy!", or it could be "rsync
these three directories". I don't care how ugly or pretty it is, as long
as its a sustainable process using standard tools (to linux, or foreman).
Thoughts?
Deff