11–20 of 42 posts
I've learned with Ansible never to be quick to update. There's always something that will break. I've been on 1.7.2 for a while, and will probably think about updating later this year.
Does there exist a good playbook for setting up a production-ready mailserver? Thanks!
For me, YAML files and fantastic documentation made more sense than the DSLs of the other two.
Currently we use it to setup our 12-factor app in production, staging, and development environments. (Django, Elasticsearch on Ubuntu)
Earlier quoted context omitted.
"Production-ready mailserver" is horribly broad (for starters, outgoing mail or incoming mail?), but Ansible Galaxy has lots of mail-related roles. For example, Zabbix: https://galaxy.ansible.com/list#/roles/1879
zabbix is a monitoring solution, I am sure this sets up some kind of outgoing mail, but I was looking for a solution similar to iredmail.
I don't see an iredmail role, but having used Ansible previously, if you can install it chances are you can write an Ansible playbook for it.
Have spent the past few months heavily working with Ansible and would totally recommend it for anyone wanting simple configuration management and orchestration. The barrier to entry is extremely low, because it uses ssh and there are no remote agents, so you can get going pretty quickly. I have an introductory screencast on in @ https://sysadmincasts.com/episodes/43-19-minutes-with-ansibl...
The problem of something like Ansible is that you have to do a web search to figure out how to do anything, rather than just writing the shell command you already know to do it.
The only major advantage is that it can tell you whether a configuration step changed the machine or not in a standardized format, which is something that shell cannot do without manually writing the code to do so.
Ansible in particular is also much slower than shell, since it seems to do a network roundtrip for each command. This is pretty surprising, since the #1 performance concern in writing such a tool is of course precisely not doing that.
Do they have any plans to support python3? I want to use it on Arch and Ubuntu. FAQ says they will address this issue by python3 becomes mainstream, but what does the mainstream exactly mean? When RHEL set python3 as default? Python2 maintenance continues until 2020, so seems have to wait for more several years.