[ovirt-users] Request for oVirt Ansible modules testing feedback
Nathanaël Blanchet
blanchet at abes.fr
Tue Jan 3 18:40:46 UTC 2017
Le 30/12/2016 à 20:53, Dan Yasny a écrit :
> I personally found that she'll isn't as useful as the python sdk. I
> usually open up ipython, load the sdk and interact with ovirt
> directly. This is faster and much more powerful than the shell could
> ever be.
okay, I suppose you to be a regular python user. Can you imagine how
much time I spent just to understand how it works?
That is to say:
* installing pip and not pip3 because provided
python-ovirt-engine-sdk4 is default installed to /usr/lib64/python2.7,
* installing ipython,
* importing the good modules,
* finding pertinent examples,
* understand differences between sdk3 and 4
* correcting some wrong examples
* adapting example to my need?
I can't see how it can be fast for the newbie.
What's the first goal of a CLI? to abstract all this stuff for the
python newbie. If you want a easy-to-use webadmin for attracting a large
public, you should provide easy-to-use CLI as well. Ovirt-shell was a
part of my choice to use ovirt.
Yes we can learn to use SDK (I dit it), but I don't think a lot people
who chose ovirt for simplicity wll use it except advanced users.
A new time, thank you for the great stuff for the great oVirt project,
but I find there is too much distance between devs and users.
What do really think the community about this?
>
> On Dec 30, 2016 11:22 AM, "Nathanaël Blanchet" <blanchet at abes.fr
> <mailto:blanchet at abes.fr>> 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 at 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 <http://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 <http://snaphot.id> variable.... but:
> o 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_snapshots_module.htm
> <http://ovirt-ansible-modules.readthedocs.io/en/latest/_modules/ovirt_snapshots_module.htm>,
> but it is not available on the main ansible git tre.
> o 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
>> <https://github.com/machacekondra/ovirt-tests/releases/tag/0.1>
>> [2] https://github.com/ansible/ansible-modules-extras/issues
>> <https://github.com/ansible/ansible-modules-extras/issues>
>> [3] https://github.com/ansible/ansible
>> <https://github.com/ansible/ansible>
>> [4] https://github.com/machacekondra/ovirt-tests
>> <https://github.com/machacekondra/ovirt-tests>
>> [5]
>> https://github.com/machacekondra/ovirt-tests/tree/master/examples
>> <https://github.com/machacekondra/ovirt-tests/tree/master/examples>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org <mailto:Users at ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>> <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 at abes.fr <mailto:blanchet at abes.fr>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org <mailto:Users at ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
> <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 at abes.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170103/af680d3b/attachment.html>
More information about the Users
mailing list