Re: [ovirt-users] Request for oVirt Ansible modules testing feedback

ovirt_vms_facts module returns list of vms which match the pattern, so something like this should work (I didn't try): - name: print shell: echo "{{ item.name }} >> vms_name" with_items: "{{ ovirt_vms }}"

Oh right, the snapshots module wasn't merged, I will fix up, thank you. Yes I agree, that Ansible modules can't currently fully replace the CLI. On Fri, Dec 30, 2016 at 5:22 PM, Nathanaël Blanchet <blanchet(a)abes.fr&gt; wrote: > Interesting work and thank you for this stuff. I played with some modules > (ovirt_vms_facts) to get some vms name for example. > > [root@acore ovirt]# ansible-playbook All_Vms_list.yml > with > - name: List vms > ovirt_vms_facts: > auth: "{{ ovirt_auth }}" > pattern: name=test_cloud > fetch_nested: true > nested_attributes: name > register: ovirt_vms > > - shell: echo "{{ ovirt_vms.name }} > vms_name" // doesn't work > > - shell: echo "{{ ovirt_vms }} > vms_name // returns an unicode json file, > that's surely why we can't parse it. Can you help me to solve this into the > ovirt_vms_facts.py file? > > I have no such problem with ovirt_snaphots_module and I can easily get the > snaphot.id variable.... but: > > I had to manually copy the ovirt_snaphsots_module because it is not present > on the git tree. This is very curious: we can find it here > http://ovirt-ansible-modules.readthedocs.io/en/latest/_modules/ovirt_snap..., > but it is not available on the main ansible git tre. > On the doc, return values are not described > > For the moment, my opinion is that ansible can't be as much convinient as > the current CLI, e.g. ovirt-shell -E "list vms", out of the box. Is there a > really reason to deprecate it? > > > Le 02/12/2016 à 14:12, Ondra Machacek a écrit : > > Hello all, > > I would like to kindly ask everyone who is Ansible or oVirt user for > testing of the new Ansible oVirt modules. For everyone who is familiar > with the Ansible and oVirt, this[1] describes the steps you need to do, > to setup oVirt modules library and start using those modules (Most of those > modules will be available in Ansible 2.3, some of them are already in 2.2). > > If you have any issue setting this up, please contact me, I will do the > best to help you. > > If you have an issue, which you think is a bug, please open an issue > here[2]. Please note that Ansible is merging it's repositories, so since > next week it will actually be stored here[3]. If you are missing > anything please open an issue as well, or just contact me, and I will > do fix it. You are also very welcome to sent PR with fixes. > > For those who don't have testing environment which can test against, > I've created an Vagrant project which will deploy you the oVirt instance > using Ansible playbooks. You can find how to use it here[4]. > > The repository also contains few examples[5], so you don't have to > copy-paste them from the source. > > Thanks all for reading this and any feedback, > Ondra > > [1] https://github.com/machacekondra/ovirt-tests/releases/tag/0.1 > [2] https://github.com/ansible/ansible-modules-extras/issues > [3] https://github.com/ansible/ansible > [4] https://github.com/machacekondra/ovirt-tests > [5] https://github.com/machacekondra/ovirt-tests/tree/master/examples > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > -- > Nathanaël Blanchet > > Supervision réseau > Pôle Infrastrutures Informatiques > 227 avenue Professeur-Jean-Louis-Viala > 34193 MONTPELLIER CEDEX 5 > Tél. 33 (0)4 67 54 84 55 > Fax 33 (0)4 67 54 84 14 > blanchet(a)abes.fr