Trace:

Table of Contents


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
blog_tech:one_month_with_ansible [2018/02/05 22:13]
admin
blog_tech:one_month_with_ansible [2018/06/08 14:04] (current)
bflorat
Line 5: Line 5:
 I used Ansible for the first time (2.4.3, last release in early 2018) in an attempt to produce some  quite sophisticated Docker Swarm docker-compose files and others yaml configuration files that includes a significant volume of logic (port number increments, conditional suffixes, variable number of sections according to lists of items, etc.) I used Ansible for the first time (2.4.3, last release in early 2018) in an attempt to produce some  quite sophisticated Docker Swarm docker-compose files and others yaml configuration files that includes a significant volume of logic (port number increments, conditional suffixes, variable number of sections according to lists of items, etc.)
  
-I achieved my goals in about five or six days of effective work, including the reading of most of the official manual. Be able to achieve a real task like this in six days when we have to learn it first is OK IMO but I think I would have made it in one day in bash (that I already know). However, Ansible is much more powerful. My first contacts and real works with Ansible were really enjoyable and I was very surprised to make it work so easy. I also tried to apply all the documented best practices with success. Sadly, I spent the last three days struggling with the last 5% of remaining work, dealing with limitations/​bugs that I found hard to understand and quite irritating. ​+I achieved my goals in about five or six days of effective work, including the reading of most of the official manual. Be able to achieve ​such a real task in six days is acceptable ​when we have to learn it first but I think I would have made it in a single ​day in bash (that I already know). However, Ansible is much more powerful. My first contacts and real works with Ansible were really enjoyable and I was very surprised to make it work so easily. I also tried to apply all the documented best practices with success. Sadly, I spent the last three days struggling with the last 5% of remaining work, dealing with limitations/​bugs that I found hard to understand and quite irritating. ​
  
 ====What I liked==== ====What I liked====
Line 42: Line 42:
 As a conclusion, Ansible is a good product but can become cumbersome when trying to make it run too much logic. It is mainly a declarative system, not imperative. Next time, we'll have a look at salt, it may be a more suitable solution, or maybe not ? As a conclusion, Ansible is a good product but can become cumbersome when trying to make it run too much logic. It is mainly a declarative system, not imperative. Next time, we'll have a look at salt, it may be a more suitable solution, or maybe not ?
  
- 
-~~DISCUSSION~~ 
  
blog_tech/one_month_with_ansible.1517865190.txt.gz · Last modified: 2018/02/05 22:13 by admin