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

33 lines
714 B
YAML
Raw Normal View History

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
---
esxi_hosts:
vmware: test-suite fixes Minor fixes for the test-suite found during the integration with the CI.
2019-06-08 00:34:20 +02:00
- esxi1.test
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`.
2019-11-29 16:23:57 +01:00
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.
2019-06-17 16:28:30 +02:00
esxi_password: '{{ esxi1_password }}'
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
infra:
datastores:
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`.
2019-11-29 16:23:57 +01:00
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
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.
2019-10-26 18:15:01 +02:00
server: datastore.test
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`.
2019-11-29 16:23:57 +01:00
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.
2019-11-13 16:37:31 +01:00
ro: false
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`.
2019-11-29 16:23:57 +01:00
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
2019-05-16 15:36:48 +02:00
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.
2019-10-26 18:15:01 +02:00
server: datastore.test
vmware/test: switch the `ro` of the two datastore (#65356) The `ro_datastore` was actually using the value of `rw_datastore`.
2019-11-29 16:23:57 +01:00
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.
2019-11-13 16:37:31 +01:00
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
2019-05-16 15:36:48 +02:00
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>
2019-07-24 12:15:15 +02:00
cluster_tag: test_cluster_tag_0001
cluster_category: test_cluster_cat_0001
Reference in a new issue Copy permalink