ansible/test/integration/targets/prepare_vmware_tests/vars/vcenter_2esxi.yml

---
esxi_hosts:
  - esxi1.test
  - esxi2.test
rw_datastore: rw_datastore
ro_datastore: ro_datastore
esxi_password: '{{ esxi1_password }}'
esxi_user: '{{ esxi1_username }}'
infra:
  datastores:
    rw_datastore:
      type: nfs
      server: datastore.test
      path: /srv/share/vms
      ro: false
    ro_datastore:
      type: nfs
      server: datastore.test
      path: /srv/share/isos
      ro: true
virtual_machines:
  - name: DC0_H0_VM0
    folder: '{{ f0 }}'
  - name: DC0_H0_VM1
    folder: '{{ f0 }}'
virtual_machines_in_cluster:
  - name: DC0_C0_RP0_VM0
    folder: '{{ f0 }}'
    cluster: '{{ ccr1 }}'
  - name: DC0_C0_RP0_VM1
    folder: '{{ f0 }}'
    cluster: '{{ ccr1 }}'
cluster_tag: test_cluster_tag_0001
cluster_category: test_cluster_cat_0001
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			`---`
			`esxi_hosts:`
vmware: test-suite fixes Minor fixes for the test-suite found during the integration with the CI. 6 years ago			`- esxi1.test`
			`- esxi2.test`
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`. 5 years ago			`rw_datastore: rw_datastore`
			`ro_datastore: ro_datastore`
prepapre_vmware_tests: add a common vars file Add a new file to record the variables that are shared with the two scenarios (real_lab and vcsim). The goal is to reduce the the amount of boilerplate configuration from a user perspective. 6 years ago			`esxi_password: '{{ esxi1_password }}'`
vmware_vmotion/test: ensure we can run tests Some adjustments to be able to run the test-suite properly: - Starts with the ESXi out of the cluster to be able to deploy the VM on a proper host consistently - Ensure the resource pool exists - The resource pool is called `DC0_C0_RP1`, not `Resources` - Avoid an exception if we try to move a non existing VM. Put the test in the zuul/vmware/vcenter_2esxi group. 5 years ago			`esxi_user: '{{ esxi1_username }}'`
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			`infra:`
			`datastores:`
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`. 5 years ago			`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 6 years ago			`type: nfs`
prepare_vmware_tests: datastore host is datastore.test Use an alias to access the datastore host. This way, it's easier to use an existing NFS server. We can also disable the `write` access on the iso datastore. 5 years ago			`server: datastore.test`
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`. 5 years ago			`path: /srv/share/vms`
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. 5 years ago			`ro: false`
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`. 5 years ago			`ro_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 6 years ago			`type: nfs`
prepare_vmware_tests: datastore host is datastore.test Use an alias to access the datastore host. This way, it's easier to use an existing NFS server. We can also disable the `write` access on the iso datastore. 5 years ago			`server: datastore.test`
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`. 5 years ago			`path: /srv/share/isos`
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. 5 years ago			`ro: true`
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			`virtual_machines:`
			`- name: DC0_H0_VM0`
			`folder: '{{ f0 }}'`
			`- name: DC0_H0_VM1`
			`folder: '{{ f0 }}'`
			`virtual_machines_in_cluster:`
			`- name: DC0_C0_RP0_VM0`
			`folder: '{{ f0 }}'`
			`cluster: '{{ ccr1 }}'`
			`- name: DC0_C0_RP0_VM1`
			`folder: '{{ f0 }}'`
			`cluster: '{{ ccr1 }}'`
VMware: add facts about tags in vmware_cluster_facts (#56848) Fixes: #46458 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com> 5 years ago			`cluster_tag: test_cluster_tag_0001`
			`cluster_category: test_cluster_cat_0001`