Mostly the way you seem to be doing it as well I guess... I have various customers where I'm implementing ansible on existing infra. I start with the basics, getting information on various systems and using group_vars and host_vars to enable/disable bits of configuration from ansible. Lots of running ansible with --check and --diff on small sets of hosts and trying to minimize (functional) diffs. Then slowly getting the systems all in line with eachother.
Greenfields would be nice.... but most customers aren't up for it.... but it's fine either way. On Thu, Jun 16, 2016 at 2:15 PM, Dick Davies <[email protected]> wrote: > I've had great success using Ansible to build up multiple environments > (devs, staging, prod) from kickstart to production, and I imagine > that's how most folks here would use it. > > My current mission is to add some automation onto a lot of 'handbuilt' > environments that have grown up from scripts. As you'd expect, each > new environment has learned from the lessons of the previous one and > the scripts have evolved. > > Unfortunately, that means each environment is different, sometimes > radically - not just in scale of a given service but often in the > presence or absence of it. There's a lot of commercial software > deployed too, which results in the inevitable "we don't have enough > licenses for $TECHNOLOGY to run it in all the dev. environments" and > more drift. > > Basically "a maze of twisty environments, non alike" .. > > I'm making some headway in getting inventories written up to at least > start to use adhoc tasks for some of the routine tasks. Next phase is > "roads and sewers" - fairly straightforward services that are simple > to setup but essential (e.g. NTP, SNMP, yum repos). > > I'm hoping to tackle some of the inconsistencies with liberal use of > $inventory/group_vars folders to enable/disable roles based on where > I'm running. > > I had a look around but haven't seen much discussion about > retrofitting Ansible to try to tame this kind of sprawl. Would be > interested in how others have tackled the challenge - "nuke the site > from orbit" and "run away screaming" excluded. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAK5eLPQao_NYjxGxU4eB0hkuGJifWSbTr7pm2HYYar9d%2BrOS1g%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Mark Janssen -- maniac(at)maniac.nl Unix / Linux Open-Source and Internet Consultant Maniac.nl Sig-IO.nl Vps.Stoned-IT.com -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKs9mshmRGOkWVjBuD4rGKNvvU4jdtGTN%3D9xn%3Dy4Q%2B32jUO4-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
