Ansible 2.6: Your Time Has Come!
Guess what!? Another release has come upon us! Your time has come to upgrade to Ansible 2.6-”Heartbreaker.” Utilize some great updates to automate to your heart’s desire, and avoid being heartbroken. See what I did there?
Let’s dive right into some of the changes.
Deprecation
One little bit of house cleaning before getting into the rest of the fun. The deprecated task option always_run has been removed, please use check_mode: no instead.
For any more information on behavioural changes from Ansible 2.5 to Ansible 2.6, please check out the Porting Guide.
Memory Utilization Improvements
In the development cycle of 2.6, we started to tackle a memory utilization problem that some of our users experienced in Dynamic Includes. In some cases, we have seen “roughly a drop of 50% memory consumption,” and in one scenario we had seen execution times of 21 seconds down to 8 seconds after the change was applied. Cool little bit, a bunch of these fixes were also back-ported to Ansible 2.5 as well as Ansible 2.4! In a future blog post, we plan to go into more detail of what was done to improve upon Dynamic Includes. Also, Continue reading
The trial used a Voyager device running a network operating system from Cumulus Networks, Zeetta Networks’ NetOS Software Defined Network orchestration, and architecture help from ADVA.
Reliance says the acquisition will accelerates Reliance Jio’s growth in the areas of 5G, IoT, and open source architecture adoption.
Ericsson prevails in EPC; Kubernetes preps to replace OpenStack, VMware; AT&T dumps its data center assets.
Under the agreement, Dell Technologies will buy VMware tracking stock. This will allow Dell to go public (again) and pay down its debt.