cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test/integration/targets/prepare_vmware_tests/tasks/setup_virtualmachines.yml

47 lines
1 KiB
YAML
Raw Normal View History

vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
---
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
- name: Create VMs
vmware_guest:
datacenter: "{{ dc1 }}"
folder: '{{ item.folder }}'
name: '{{ item.name }}'
vmware_guest: speed up vmware_guest tests - Use predictable VM name during the tests (test_vm1, test_vm2 and test_vm2). This to simplify the teardown of the newly created resource before the next test. - Update the documentation to explain the new requirement - Avoid VM creation with `with_items` when it's not mandatory. This to: - speed up the test execution, our hypervisors have limited resources - simplify the teardown - Remove `create_d1_c1_f0_env.yml`, the test was just testing how Ansible pass environment variables. - Correct the name for the `f0` variable (`f1`) - Fix the DVS tests, the hosts can now reach the dvswitch1 vswitch - Provision the VM with a poweroff status, this to improve the idempotency and sleep up the tests - Avoid the use of `prepare_vmware_tests` to prepare virtual machines when we just need one machine
2019-07-11 08:12:49 +02:00
state: poweredoff
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
guest_id: debian8_64Guest
disk:
- size_gb: 1
type: thin
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-13 16:37:31 +01:00
datastore: '{{ rw_datastore }}'
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
hardware:
memory_mb: 128
num_cpus: 1
scsi: paravirtual
cdrom:
type: iso
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-13 16:37:31 +01:00
iso_path: "[{{ ro_datastore }}] fedora.iso"
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
networks:
- name: VM Network
with_items: '{{ virtual_machines }}'
vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
- name: Create VMs in cluster
vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
vmware_guest:
datacenter: "{{ dc1 }}"
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
folder: '{{ item.folder }}'
cluster: '{{ item.cluster }}'
name: '{{ item.name }}'
vmware_guest: speed up vmware_guest tests - Use predictable VM name during the tests (test_vm1, test_vm2 and test_vm2). This to simplify the teardown of the newly created resource before the next test. - Update the documentation to explain the new requirement - Avoid VM creation with `with_items` when it's not mandatory. This to: - speed up the test execution, our hypervisors have limited resources - simplify the teardown - Remove `create_d1_c1_f0_env.yml`, the test was just testing how Ansible pass environment variables. - Correct the name for the `f0` variable (`f1`) - Fix the DVS tests, the hosts can now reach the dvswitch1 vswitch - Provision the VM with a poweroff status, this to improve the idempotency and sleep up the tests - Avoid the use of `prepare_vmware_tests` to prepare virtual machines when we just need one machine
2019-07-11 08:12:49 +02:00
state: poweredoff
vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
guest_id: debian8_64Guest
disk:
- size_gb: 1
type: thin
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-13 16:37:31 +01:00
datastore: '{{ rw_datastore }}'
vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
hardware:
memory_mb: 128
num_cpus: 1
scsi: paravirtual
cdrom:
type: iso
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-13 16:37:31 +01:00
iso_path: "[{{ ro_datastore }}] fedora.iso"
vmware: import prepare_vmware_tests The vmware test roles do a lot of similar operation to prepare the environment. This role will be used to reduce the amount of duplicated code. The role can prepare an environment on a baremetal environment, this in addition to vcsim. Original PR: https://github.com/ansible/ansible/pull/54882
2019-04-24 19:02:21 +02:00
networks:
- name: VM Network
vmware: test-refactoring - In order to keep the integration with `ansible-test`, we prefer to avoid any interaction with the Ansible inventory file. - split up the prepare_vmware_tests/defaults/main.yml in two configuration files: one for vcsim and one for a real environment - remove all the access to hostvars - directly interact with the ESXi to mount/umount the datastore https://github.com/ansible/ansible/pull/56516 - record the virtual machine folder in the environment configuration - vmware_guest_move: Use https://github.com/ansible/ansible/pull/55237
2019-05-16 15:36:48 +02:00
with_items: '{{ virtual_machines_in_cluster }}'
Reference in a new issue Copy permalink