On Thu, Aug 20, 2009 at 9:26 PM, Ohad Levy wrote:
>
> I would recommend you not to allow autofs to restart, but rather force a
> reload (if your OS supports it).
> (it would be similar to pulling the plug out of the machine :))
>
> Just as a side note, do you have any software that manages your c
On Fri, Aug 21, 2009 at 2:22 AM, Charles Johnson wrote:
>
> The size of the files we serve are, typically, tiny: sudoers, hosts,
> hosts.equiv, and eight or ten others. They do not change often, but when
> they do, they need to be synched across the cluster. Our big bug-a-boo is
> seeing that new
Thanks to everyone for his/her replies. I appreciate it. We will be adding
RAM to the box.
We are using puppet 0.24.8. We are not using storeconfig at the moment, and
if we were we would be using our postgres server for that. I appreciate that
pointer.
The size of the files we serve are, typically
On Thu, Aug 20, 2009 at 9:02 PM, Larry Ludwig wrote:
>
> If the puppetmaster is x86_64 based, I would recommend 4+ GB based
> upon your node count and they way ruby scales on x86_64 arch.
>
I install 32bit distributions on my 64bit hardware, as a single
passenger/mongrel doesn't (usually) pass the
On Aug 19, 2009, at 10:06 AM, cnjohnson wrote:
>
> I have deployed puppet on our test cluster -- 20 identically
> configured x86_64 and ppc64 compute nodes and their gateways. I now
> want to move to our production cluster with (say) 800 compute nodes
> and their gateways. My question is about t
On 8/19/09 10:06 AM, "cnjohnson" wrote:
> Any thoughts about what sort of puppet-box I need to manage a cluster
> of 800 boxes?
How often will puppet "wake up" on each client? If only once an hour
normally, a decent "normal" server (say 8GB RAM, dual dual-core CPU's)
should be fine. At least
