jimi_c

6 ms·

1. 1.▲
   by jimi_c 9y ago

   (Ansible lead here) As I responded to a similar comment on Twitter the other day, part of the issue is our volume. When I looked, we had merged 395 PRs in the last month (via github pulse), which is ~33/day, assuming we work every day
2. 2.▲
   by jimi_c 11y ago

   I'd be interested in hearing how this stacks up against simply running the tasks via shell scripts, because the time to install packages/do other tasks is orders of magnitude higher than the connection overhead. Things will always
3. 3.▲
   by jimi_c 11y ago

   This is actually my first stint at Red Hat - as the Cobbler maintainer I just kickstarted RHEL (and some VMware) boxes a lot for my day job.
4. 4.▲
   by jimi_c 11y ago

   There are still a lot of RHEL/CentOS 5 users out there, which run python 2.4. While py3 is moving forward, the number of users stuck on 2.4 is still considerably larger, and we will continue to support that until such a time as it&#x27
5. 5.▲
   by jimi_c 11y ago

   Yes, very sorry about that. The 1.9.1 rc1 will be out today, which will address this.
6. 6.▲
   by jimi_c 11y ago

   Hi ynak, we're planning on supporting py3 in the core engine with the v2 codebase. As for modules, we're still working on the best possible solution there, since we do need to continue supporting python 2.4 for the foreseeable fut
7. 7.▲
   by jimi_c 13y ago

   I'm not quite sure how that's a condemnation of ansible, since the same can be said of any automatic pull-based system. In fact, the same can be said of any automation - it's quite easy to break every system in your environme