Foreman module management and smart proxies

Support
1

Hi All,

I'm trying to wrap my head around module management in Foreman when
having environments managed by different smart-proxies. When I add a
new smart-proxy that manages another Puppet server and want to import
modules Foreman wants to remove all the modules I've added from my
main Puppet serveras well as the environment. The only way to get
around this is to either checkout my modules to all Puppet masters and
create the environments on each Puppet Master, ignore the removal
process by deselecting the modules that I don't want removed or add
modules manually to Foreman. How do others manage Puppet modules
within Foreman when you have multiple smart-proxies for different
environments?

Regards,
Gareth

2

That's the question that I've puzzled over as well. Don't have an answer yet.
Would love for others to chime in. In practice though, I found that in
my environment
the situation where I'd have 2 or more servers dedicated to the same function
(puppet master, tftp, etc.) would almost always be for scalability/HA and hence
the state on these servers is presumed to be identical. Hence picking one and
running a smart proxy over there seems to suffice.

Thanks,
Roman.

··· On Sun, Jan 20, 2013 at 9:03 AM, Gareth Allen wrote: > Hi All, > > I'm trying to wrap my head around module management in Foreman when > having environments managed by different smart-proxies.
3

> > Hi All,
> >
> > I'm trying to wrap my head around module management in Foreman when
> > having environments managed by different smart-proxies.
>
> That's the question that I've puzzled over as well. Don't have an answer
> yet.
> Would love for others to chime in. In practice though, I found that in
> my environment
> the situation where I'd have 2 or more servers dedicated to the same
> function
> (puppet master, tftp, etc.) would almost always be for scalability/HA and
> hence
> the state on these servers is presumed to be identical. Hence picking one
> and
> running a smart proxy over there seems to suffice.
>

It seems to me if I understand the behavior you guys are describing, then
the class import process needs to be tweaked for a
multimaster/multienvironment use case.

I'm just not 100% sure what would be the desired behaviour. IE: We could
NOT prompt for removing classes in an environment that isn't part of the
current puppet master import, but we would need to provide an alternate
method to remove environments, if that was the actual goal. Or, we could
tag environments with an array of associated puppetmasters, so that Foreman
could make a more educated guess on whether or not prompting to remove
those classes makes sense?

Thanks,

··· On Sun, Jan 20, 2013 at 3:30 PM, Roman Shaposhnik wrote: > On Sun, Jan 20, 2013 at 9:03 AM, Gareth Allen > wrote: > Roman. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en. > >

–
http://aws.amazon.com/solutions/solution-providers/brandorr/

4

> Hi All,
>
> I'm trying to wrap my head around module management in Foreman when
> having environments managed by different smart-proxies. When I add a
> new smart-proxy that manages another Puppet server and want to import
> modules Foreman wants to remove all the modules I've added from my
> main Puppet serveras well as the environment. The only way to get
> around this is to either checkout my modules to all Puppet masters and
> create the environments on each Puppet Master, ignore the removal
> process by deselecting the modules that I don't want removed or add
> modules manually to Foreman. How do others manage Puppet modules
> within Foreman when you have multiple smart-proxies for different
> environments?
>

I agree this is a limitation today, partly handled by the assumption that
you need to keep your masters in sync.

for the cases where you have development puppetmasters, or multiple
puppet tenants i think this is where the new organization features in 1.1
can come in handy.

You should be able to split your different puppet masters to different
organizations, and we should be able to compare only in the context of that
organization.

would you mind adding that as a feature request?

Thanks,
Ohad

··· On Sun, Jan 20, 2013 at 7:03 PM, Gareth Allen wrote:

Regards,
Gareth

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.