cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
49418 commits 47 branches 390 tags 440 MiB
Commit graph

16 commits

Author SHA1 Message Date
Gonéri Le Bouder
802cc60242 vmware_guest_tools_wait: add timeout parameter 
Add a new `timeout` parameter to `vmware_guest_tools_wait`.

Also, a functional test to cover the module.
 2020-02-07 17:48:29 -05:00
Gonéri Le Bouder
4a1115785f vmware_guest_network/test: disable the test 
The test fails in the CI with a timeout of vmware_guest_tools_wait. It's
still unclear if this comes from:

- the ESXi environment
- the VM configuration, e.g: the amount of the RAM
- the ISO image itself

Ideally, we should have a light VM with the vmware-tools.
 2020-02-06 19:59:23 -05:00
Gonéri Le Bouder
ae6317004e vmware_guest_network/test: create the dvswitch 
Ensure the DVSwitch and the portgroup are created by
`prepare_vmware_tests`.
 2020-01-17 16:56:13 -05:00
Abhijeet Kasurde
afb71c14bd
VMware: Use existing DVPG network in vmware_guest_network (#65994) 
* Handle all cases of networks

Fixes: #65968

Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
 2020-01-15 21:56:19 +05:30
Gonéri Le Bouder
8d6b9cf6e0 prepare_vmware_tests: add scenario with one ESXi 
Add the ability to test with just one vcenter instance and a single
ESXi. This allow us to cover 90 modules.
 2019-12-19 11:30:00 -05:00
Gonéri Le Bouder
0aa59ce9ab vmware/test: use better name for datastores 
In the VMware tests, we call the datastores `ds1` and `ds2`. The first
one is read-only, the second is read-write and can be used to deploy
VMs. The naming convention was not clear enough and source of a lot
confusion and mistake.

We now have two better names:

- ro_datastore, which is ... read-only
- rw_datastore, the one that we can use to deploy new VM.
 2019-11-14 16:55:05 -05:00
Anusha Hegde
3a9650df98 Merging conflicts and updating PR 
Signed-off-by: Anusha Hegde
 2019-11-13 16:12:52 -05:00
Anusha Hegde
4e7c0b3e21 Fixed review comments 
Signed-off-by: Anusha Hegde
 2019-11-13 16:12:52 -05:00
Anusha Hegde
907c66c082 Resolved merge conflicts 2019-11-13 16:12:52 -05:00
Gonéri Le Bouder
424f9f0dac vmware_guest_network/test: fix name of test VM 
The test VM is called `test_vm1` since
https://github.com/ansible/ansible/issues/63302.

Also, avoid the `00:50:56` prefix for the MAC address, since it's known
for being source of problem: https://github.com/ansible/ansible/issues/63302
 2019-10-17 17:38:42 -04:00
Pavan Bidkar
b6ea43efc3 VMware: Support instance_uuid to find the vm for vmware_guest_network module (#62818) 2019-10-17 12:23:13 +05:30
Gonéri Le Bouder
add74fd24b vmware_guest_network: avoid functional test failure 
- Avoid the 00:50:56 MAC prefix, See: https://github.com/ansible/ansible/issues/63302
- Create an Ad-Hoc VM for the test and wait until the VMware tools are
  ready
 2019-10-10 13:26:47 -04:00
pratikgadiya12
8ee7d9f598 VMWare - Rename _facts to _info (#57474) 
Deprecate vmware's _facts modules and add new modules.

Fixes: #57278
 2019-08-26 14:45:34 -04:00
Gonéri Le Bouder
ef59dd2ca2 vmware_guest_network: fix the network look up 
Before this fix, the module was not able to look up a `VM Network` located at
`/DC0/network/VM Network`. As a consequence, the test module was failing
with a real environment (Non-govcsim).
 2019-07-25 14:02:52 +02:00
Abhijeet Kasurde
617972499f
VMware: Correct network_exists_by_name API call (#59006) 
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
 2019-07-12 11:22:06 +05:30
Diane Wang
9c140d26d5 VMware: add new module vmware_guest_network (#52075) 2019-07-08 07:54:54 +05:30