On 5/9/2013 7:42 AM, Martin Langhoff wrote:
On Thu, May 9, 2013 at 12:06 AM, John Warburton <jwarbur...@gmail.com> wrote:
I suppose all HA solutions are difficult
Nah. A service correctly designed to be resilient can be HA with
trivial investment.
DNS is a good example. It may have blemishes but nobody stresses about
its availability. Setup as many tiers of redundancy as you want,
easily.
Puppet has no need to be centralized -- a git-based puppet setup can
handle it just fine.
I am writing some tooling for git+puppet (search for ppg in recent
posts to this list), and it's trivial to add N-tiers of redundant
servers...
Hubris, today thy name is Martin. :-)
I'd argue that people have stressed about DNS availability for just
under three decades and that we are currently enjoying the fruits of
that labor. Personally, I have yet to work at a company where DNS has
not caused a significant outage. I do agree that the tools are there to
build resilience, but implementation matters and it is a hard problem to
solve in a non trivial environment.
Your ppg tooling does look interesting, but there is a large trade off
in functionality. You could use some other systems to collect data and
push it into a repo which is then queried in order to generate data for
clients... starting to sound an awful lot like centralized Puppet to me
and all the problems therein regardless of transport.
Ramin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
