René, It is a really good book, so thanks on that. One thing on the next revision is probably hit up vaults a bit more and various authentication procedures. I come from more of the networking side, but creating various vaults for different ops is probably mainstream. IE dev vs prod, BGP vs IGP, et al…
Probably off topic, but thanks for the updates... > On Sep 1, 2017, at 6:47 PM, Rene Moser <[email protected]> wrote: > > Hi Dennis > > On 09/01/2017 10:59 PM, Dennis Meyer wrote: > >> I thought ansible is made to deploy the meaning or behaviour of a vm, and >> not managing its dependencies beyond its space. > > au contraire, my friend. Ansible is _the_ generic IT orchestration engine. > > Ansible literally allows to manage your whole infrastructure, not only > VM and servers, but network devices like cisco nexus, various cloud > providers (aws, cloudstack, openstack), use DNS service providers, > interact with loadbalancers such as netscaler or haproxy, manage system > configurations (windows, linux or unix), orchestrate your docker > containers, handle notifications, interact with monitoring tools, and > deploy app in a rolling updates, rollback on errors, etc while .. and > this is the most important part... keeping things relatively simple and > readable. > > I can recommend a very well written book (shameless self plug) > http://www.ansiblebook.com/ ;) > > René > > > >
