From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ansible, puppet and chef
Date: Wed, 17 Sep 2014 09:34:48 +0200 [thread overview]
Message-ID: <10772793.3d0ROZOBlq@andromeda> (raw)
In-Reply-To: <5418A0E6.4080204@gmail.com>
On Tuesday, September 16, 2014 10:43:18 PM Alan McKinnon wrote:
> Anyone here used ansible and at least one of puppet/chef?
>
> What are your thoughts?
>
> I've made several attempts over the years to get puppet going but never
> really got it off the ground. Chef I stay away from (likely due to the
> first demo of it I saw and how badly that went....)
>
> Puppet seems to me a good product for a large site with 1000 hosts.
> Not so much for ~20 or so. Plus puppet's language and configs get large
> and hard to keep track of - lots and lots of directory trees with many
> things mentioning other things. (Nagios has the same problem if you
> start keeping host, services, groups and commands in many different files)
>
> I've stumbled upon ansible, it seems much better than puppet for
> smallish sites with good odds I might even keep the whole thing in my
> head at any one time :-)
>
> Anyone care to share experiences?
No experiences yet, but I have been looking for options to quickly and easily
create (and remove) VMs lab environments.
I agree with your comments on Chef and Puppet.
Ansible looks nice and seems easy to manage. I miss an option to store the
configuration inside a database, but I don't see an issue adding the
generation of the config-files from database tables to the rest of the
environment I am working on.
I like that Ansible also seems to support MS Windows nodes, just too bad that
requires enabling it after install. But with this, cloning VMs and changing
the network configs afterwards seems easier to manage.
--
Joost
next prev parent reply other threads:[~2014-09-17 7:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:43 [gentoo-user] Ansible, puppet and chef Alan McKinnon
2014-09-17 1:30 ` Alec Ten Harmsel
2014-09-17 2:56 ` [gentoo-user] " James
2014-09-17 7:07 ` [gentoo-user] " Alan McKinnon
2014-09-17 5:46 ` [gentoo-user] " Hans de Graaff
2014-09-17 8:06 ` Alan McKinnon
2014-09-17 7:07 ` [gentoo-user] " Tomas Mozes
2014-09-17 8:08 ` Alan McKinnon
2014-09-17 12:46 ` Tomas Mozes
2014-09-17 13:24 ` Alan McKinnon
2014-09-17 7:34 ` J. Roeleveld [this message]
2014-09-17 8:12 ` Alan McKinnon
2014-09-17 8:55 ` J. Roeleveld
2014-09-17 9:19 ` Eray Aslan
2014-09-17 9:34 ` J. Roeleveld
2014-09-17 12:07 ` Alan McKinnon
2014-09-17 12:36 ` Tomas Mozes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10772793.3d0ROZOBlq@andromeda \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox