Timeline for How is Ansible different from simply running a provisioning bash shell in Vagrant?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8 at 11:24 | comment | added | ᴍᴇʜᴏᴠ | Impressive. Bravo. | |
| Apr 25, 2020 at 15:29 | history | edited | Michaël Le Barbier | CC BY-SA 4.0 |
As this answer seems to enjoy a relative popularity I fixed a few syntax errors and typos to make it easier to read. Since I also have experienced ansible and would share a word of this experience without changing my text, I added a short postscriptum at the end to do so.
|
| Mar 21, 2019 at 12:14 | comment | added | Daniel | @MichaelLeBarbierGrünewald, I have to agree overall, when I worked with Ansible, it was a real pain to get running and its work that takes weeks to get a playbook together to connect to the infrastructure at my former cloud-based company, provision the linux distro, install LAMP/LEMP or whatever. Once it was completed, it saved us time, but it took like a month just to get it up and running. None of us were master bash scripters so that was not an alternative. | |
| Mar 17, 2019 at 2:31 | comment | added | Levi | @Andreas I agree you still have many cases where you need to fall back to the shell or command modules that doesn't mean your ansible play can't be idempotent. The core modules themselves maintain idempotency by just checking if the action should be done. You can do the same thing your self with shell or command module by first running a task that checks if something should be done and registering its output, then doing a conditional on the second task based on the output from the first task. | |
| Sep 24, 2018 at 15:03 | review | Suggested edits | |||
| Sep 24, 2018 at 21:42 | |||||
| Mar 28, 2018 at 9:28 | comment | added | Michaël Le Barbier | After using ansible thoroughly I can confirm all the points I made a priori. Idempotency is possible but not enforced by ansible (see module vmware_guest for a bad citizen), working with their macro system is a real pain and it is incredenly hard to perform even the most basic treatments on structured data, some basic things are doing just wrong (the playbook format cannot eat a Unix file mode without a therapy) and the only real good thing the the load of useful functions written for ansible. So if it were not for Red Hat pushing that product, I cannot understand the wide adoption. | |
| Apr 16, 2017 at 10:34 | comment | added | Andreas | I couldn't agree more. We used Ansible for over 1 year now and are now using Docker containers, built with good, plain old bash scripts. Defining the state is also in my opinion by far the most interesting feature, but as you mentioned it already - there are so many services that don't have a corresponding Ansible module, so you always have to fallback to bash commands anyway. And yes, we also only deploy immutable containers to servers, so defining the state is not really any advantage in this case. | |
| Mar 9, 2017 at 15:41 | vote | accept | Evgeny Zislis | ||
| Mar 7, 2017 at 18:46 | comment | added | Pierre.Vriens♦ | This seems like a manual ... impressive! | |
| Mar 7, 2017 at 0:29 | history | answered | Michaël Le Barbier | CC BY-SA 3.0 |