I noticed this and we developed a playbook using the same technic used by
LinuxArchitects. Unfortunately, it makes a playbook very loaded which goes
against the philosophy of Ansible to keep playbook light and easy to read.
By example, having to manage the bearer token instead of abstracting
Hey Ivan,
Did you find something? I found this today while searching for an Ansible
module that will request base OS blueprints from VRA. Let me know.
https://github.com/LinuxArchitects/Ansible-VMware-vRealize-Automation
On Friday, September 29, 2017 at 5:24:12 AM UTC-7, Ivan Pacheco wrote:
>
Got your point, but we rely heavily on vCenter automation using ansible and
would like to continue doing so, that's why a vRA module make sense for us,
to abstract all the vRA REST API logic into simple ansible role/playbook.
What is the industry approach at automating VM provisioning with vRA
Well for me, vRA (vRealize Automation) and Ansible are doing the same job.
vRA is here to automate the provisoning of whole platforms, from VMs
deployment, network conf, to app deployment, etc... With the possibility to
have a portal to propose users to do it based on blueprints.
Ansible module
