1 |
On Wednesday, September 17, 2014 10:12:52 AM Alan McKinnon wrote: |
2 |
> On 17/09/2014 09:34, J. Roeleveld wrote: |
3 |
> > On Tuesday, September 16, 2014 10:43:18 PM Alan McKinnon wrote: |
4 |
> >> Anyone here used ansible and at least one of puppet/chef? |
5 |
> >> |
6 |
> >> What are your thoughts? |
7 |
> >> |
8 |
> >> I've made several attempts over the years to get puppet going but never |
9 |
> >> really got it off the ground. Chef I stay away from (likely due to the |
10 |
> >> first demo of it I saw and how badly that went....) |
11 |
> >> |
12 |
> >> Puppet seems to me a good product for a large site with 1000 hosts. |
13 |
> >> Not so much for ~20 or so. Plus puppet's language and configs get large |
14 |
> >> and hard to keep track of - lots and lots of directory trees with many |
15 |
> >> things mentioning other things. (Nagios has the same problem if you |
16 |
> >> start keeping host, services, groups and commands in many different |
17 |
> >> files) |
18 |
> >> |
19 |
> >> I've stumbled upon ansible, it seems much better than puppet for |
20 |
> >> smallish sites with good odds I might even keep the whole thing in my |
21 |
> >> head at any one time :-) |
22 |
> >> |
23 |
> >> Anyone care to share experiences? |
24 |
> > |
25 |
> > No experiences yet, but I have been looking for options to quickly and |
26 |
> > easily create (and remove) VMs lab environments. |
27 |
> |
28 |
> Have you tried Vagrant? |
29 |
|
30 |
Nope. |
31 |
|
32 |
> I haven't tried it myself, I'm just reacting to the "VM" keyword ;-) |
33 |
|
34 |
Yes, but it doesn't have support for Xen or KVM and I'd need to write a custom |
35 |
"provider" to make that work. |
36 |
That basically does what I am looking into, but with the products we work |
37 |
with, I need more custom activities in some of the VMs then are easily |
38 |
organised. |
39 |
|
40 |
> > I agree with your comments on Chef and Puppet. |
41 |
> > Ansible looks nice and seems easy to manage. I miss an option to store the |
42 |
> > configuration inside a database, but I don't see an issue adding the |
43 |
> > generation of the config-files from database tables to the rest of the |
44 |
> > environment I am working on. |
45 |
> |
46 |
> Ansible has an add-on called Tower that seems to do this. The marketing |
47 |
> blurb implies you can use almost any storage backend you like from MySQL |
48 |
> and PostGres to LDAP |
49 |
|
50 |
Ok, from a quick scan of that page, it looked like a web frontend for some |
51 |
stuff. I'll definitely look into that part. The rest is more custom, so I |
52 |
might just generate the config files on the fly. |
53 |
|
54 |
> > I like that Ansible also seems to support MS Windows nodes, just too bad |
55 |
> > that requires enabling it after install. But with this, cloning VMs and |
56 |
> > changing the network configs afterwards seems easier to manage. |
57 |
> |
58 |
> I'm lucky, this is a Unix-only shop so I don't have to deal with Windows |
59 |
> servers. The three managers who have Windows laptops for varying reasons |
60 |
> have all been clearly told upfront they will support themselves and I |
61 |
> ain't touching it :-) |
62 |
|
63 |
Not all products we deal with run on non-MS Windows systems, so we are sort-of |
64 |
stuck with it. They only run inside VMs that are only accessible via the LAB |
65 |
network. Which means, no access to the internet unless specifically allowed. |
66 |
(The host and port on the internet needs to be known prior to allowing access) |
67 |
|
68 |
-- |
69 |
Joost |