> I've been trying to find information, suggestions, etc. for how to combine
> scaling Puppet with the use of management tools like Dashboard/Foreman and
> MCollective. Our current thinking for an initial deployment is two VMs as
> Puppet Master worker nodes fronted by a pair of NetScalers. However, I'm not
> sure how to go about implementing Dashboard or Foreman and MCollective
> servers in a redundant Puppet Master server environment. Can anyone speak to
> their experience in this matter and/or point me to resources that discuss
> such architectures?
>
To scale out foreman, would be very similar to any rails app, normally
you could:
- use a load balancer across multiple foreman rails instances (e.g.
on multiple machines)
- cluster your db
Foreman already supports both configuration (and has been implemented
by various community members with large scale deployments).
additionally, the enc script keeps a cache on each puppet master, so
in case when foreman is down, it would serve the last good enc data
that came from foreman.
hope this helps,
Ohad
···
On Mon, Oct 24, 2011 at 6:38 PM, Justin Lloyd wrote:
> FWIW, we'll later implement multiple pairs of redundant Puppet servers to
> support environments we want managed separately, e.g. Production vs. Test.
>
> Thanks,
> Justin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>> I've been trying to find information, suggestions, etc. for how to combine
>> scaling Puppet with the use of management tools like Dashboard/Foreman and
>> MCollective. Our current thinking for an initial deployment is two VMs as
>> Puppet Master worker nodes fronted by a pair of NetScalers. However, I'm not
>> sure how to go about implementing Dashboard or Foreman and MCollective
>> servers in a redundant Puppet Master server environment. Can anyone speak to
>> their experience in this matter and/or point me to resources that discuss
>> such architectures?
>>
>
> To scale out foreman, would be very similar to any rails app, normally
> you could:
> 1. use a load balancer across multiple foreman rails instances (e.g.
> on multiple machines)
> 2. cluster your db
>
> Foreman already supports both configuration (and has been implemented
> by various community members with large scale deployments).
>
> additionally, the enc script keeps a cache on each puppet master, so
> in case when foreman is down, it would serve the last good enc data
> that came from foreman.
>
> hope this helps,
···
On Oct 24, 2011, at 11:54 AM, Ohad Levy wrote:
> On Mon, Oct 24, 2011 at 6:38 PM, Justin Lloyd wrote:
----
hmmm... I get catalog errors from time to time (more of an issue of high load factor on my puppet master) but it doesn't ever seem to pull from a cache but I suppose that is likely something in my configuration.
I currently set each client ‘use_cached_catalog = false’ - Is that the reason?
Craig
>
>
>>> I've been trying to find information, suggestions, etc. for how to combine
>>> scaling Puppet with the use of management tools like Dashboard/Foreman and
>>> MCollective. Our current thinking for an initial deployment is two VMs as
>>> Puppet Master worker nodes fronted by a pair of NetScalers. However, I'm not
>>> sure how to go about implementing Dashboard or Foreman and MCollective
>>> servers in a redundant Puppet Master server environment. Can anyone speak to
>>> their experience in this matter and/or point me to resources that discuss
>>> such architectures?
>>>
>>
>> To scale out foreman, would be very similar to any rails app, normally
>> you could:
>> 1. use a load balancer across multiple foreman rails instances (e.g.
>> on multiple machines)
>> 2. cluster your db
>>
>> Foreman already supports both configuration (and has been implemented
>> by various community members with large scale deployments).
>>
>> additionally, the enc script keeps a cache on each puppet master, so
>> in case when foreman is down, it would serve the last good enc data
>> that came from foreman.
>>
>> hope this helps,
> ----
> hmmm… I get catalog errors from time to time (more of an issue of high load factor on my puppet master) but it doesn't ever seem to pull from a cache but I suppose that is likely something in my configuration.
>
not sure, but i was referring to foreman ENC data, not to puppet it self.
the idea is that if foreman is down, puppet can still function in "RO" mode.
Ohad
···
On Mon, Oct 24, 2011 at 9:09 PM, Craig White wrote:
> On Oct 24, 2011, at 11:54 AM, Ohad Levy wrote:
>> On Mon, Oct 24, 2011 at 6:38 PM, Justin Lloyd wrote:
> I currently set each client 'use_cached_catalog = false' - Is that the reason?
>
> Craig
>
> --
> 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.
>
>
