Hacker News Reader

Comment by aidos | Hacker News Reader

Oh really — what sort of things have you run into? I'll look at upgrading soon and I'm hoping 14.04 to 16.04 won't be too bad.

View on HN

We're moving from 14.04 to 16.04 and are about done with our migration development - the biggest difference I saw was systemd by default, although for the simple things we do with startup weren't too hard to migrate over. The other only other thing that impacted us was some changes in how the apt and puppet versions that are included by default act, a few things were either more strict or the (previously deprecated) things had actually been removed.

Python 2 is not there. If you run on AWS, either have a task to download and install Python 2, or in your EC2's user data to install Python 2 (this is necessary for Ansible users).

Ironic since Ansible's lack of Python 3 support was due to vociferous insistence by key Ansible developers that it would be wrong even to allow the use of Ansible with Python 3 as long as popular CentOS versions did not have it.

I have to read it backward. Ansible is now part of RedHat. CentOS doesn't have Python 3, and some key Ansible developers have strong opinion on Ansible not supporting Python 3 in the near future. Am I reading it right?

Ansible has preliminary py3 support now. It works well enough for me on Ubuntu 16, only py3 installed.

Which version?

I think the bigger reason was Ansible needed to support Python 2.4 and 2.5 for old CentOS versions, making simultaneous Python 3 support very hard. They've now dropped 2.4 and 2.5, thus allowing Python 3 compatibility.

https://github.com/ansible/ansible/pull/22721/files

(Though, it's worth noting that CentOS still does not have Python 3 support out of the box.)

Upstart is gone and systemd is here instead. It's a huge change.

You can always switch back to upstart if you rely on it. It's a simple process: https://wiki.ubuntu.com/SystemdForUpstartUsers

Thank you for this.

Reply on news.ycombinator.com