ansible/test/integration/targets/prepare_vmware_tests/tasks/setup_virtualmachines.yml

---
- name: Create VMs
  vmware_guest:
    hostname: "{{ vcenter_hostname }}"
    username: "{{ vcenter_username }}"
    password: "{{ vcenter_password }}"
    datacenter: "{{ dc1 }}"
    validate_certs: no
    folder: '{{ item.folder }}'
    name: '{{ item.name }}'
    state: poweredoff
    guest_id: debian8_64Guest
    disk:
    - size_gb: 1
      type: thin
      datastore: '{{ ds2 }}'
    hardware:
      memory_mb: 128
      num_cpus: 1
      scsi: paravirtual
    cdrom:
      type: iso
      iso_path: "[{{ ds1 }}] fedora.iso"
    networks:
    - name: VM Network
  with_items: '{{ virtual_machines }}'


- name: Create VMs in cluster
  vmware_guest:
    hostname: "{{ vcenter_hostname }}"
    username: "{{ vcenter_username }}"
    password: "{{ vcenter_password }}"
    datacenter: "{{ dc1 }}"
    validate_certs: no
    folder: '{{ item.folder }}'
    cluster: '{{ item.cluster }}'
    name: '{{ item.name }}'
    state: poweredoff
    guest_id: debian8_64Guest
    disk:
    - size_gb: 1
      type: thin
      datastore: '{{ ds2 }}'
    hardware:
      memory_mb: 128
      num_cpus: 1
      scsi: paravirtual
    cdrom:
      type: iso
      iso_path: "[{{ ds1 }}] fedora.iso"
    networks:
    - name: VM Network
  with_items: '{{ virtual_machines_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 6 years ago			`---`
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 6 years ago			`- name: Create VMs`
			`vmware_guest:`
			`hostname: "{{ vcenter_hostname }}"`
			`username: "{{ vcenter_username }}"`
			`password: "{{ vcenter_password }}"`
			`datacenter: "{{ dc1 }}"`
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 6 years ago			`validate_certs: no`
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 6 years ago			`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 5 years ago			`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 6 years ago			`guest_id: debian8_64Guest`
			`disk:`
			`- size_gb: 1`
			`type: thin`
			`datastore: '{{ ds2 }}'`
			`hardware:`
			`memory_mb: 128`
			`num_cpus: 1`
			`scsi: paravirtual`
			`cdrom:`
			`type: iso`
vmware: test-suite fixes Minor fixes for the test-suite found during the integration with the CI. 6 years ago			`iso_path: "[{{ ds1 }}] 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 6 years ago			`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 6 years ago
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 6 years ago
			`- 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 6 years ago			`vmware_guest:`
			`hostname: "{{ vcenter_hostname }}"`
			`username: "{{ vcenter_username }}"`
			`password: "{{ vcenter_password }}"`
			`datacenter: "{{ dc1 }}"`
			`validate_certs: no`
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 6 years ago			`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 5 years ago			`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 6 years ago			`guest_id: debian8_64Guest`
			`disk:`
			`- size_gb: 1`
			`type: thin`
			`datastore: '{{ ds2 }}'`
			`hardware:`
			`memory_mb: 128`
			`num_cpus: 1`
			`scsi: paravirtual`
			`cdrom:`
			`type: iso`
vmware: test-suite fixes Minor fixes for the test-suite found during the integration with the CI. 6 years ago			`iso_path: "[{{ ds1 }}] 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 6 years ago			`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 6 years ago			`with_items: '{{ virtual_machines_in_cluster }}'`