glusterfs-containers-tests.git/deployment, branch master

Delete 'deployment' dir as obsolete and not supported

2019-12-20T18:45:18+00:00

'deployment' directory contains obsolete and unsupported
approach for deploying OpenShift and GlusterFS storage.
Separate deployment approach has already been used for significant
amount of time.
So, delete local 'directory' as it makes no sense to keep it.
Moreover, it may be confusing for people who may try it out
and see unpredictable errors.

Change-Id: Ibf353500bab59853f597304cb9c1990102c000ef

Fix pep8 errors in the files of the 'deployment' dir

2019-09-03T12:29:24+00:00

Change-Id: I4b469969a041eaf4ccb6d95a59d6d2332c6c845c

Fix playbook for generation of config file

2019-07-19T12:33:11+00:00

'playbooks/generate-tests-config.yaml' playbook fails when
cluster has 'glusterfs-registry' nodes. So, fix it by using proper
filtering in shell commands.

Change-Id: I884f57e646a513b1ceddc5345099fcd8379fce72

[Deployment] Create ~/.ssh/config file if absent

2019-06-19T11:14:48+00:00

Ansible will use this file and fail if it is absent.
So, create empty SSH config file if it is absent.

Change-Id: I86f424c30229e72eaf2e6a50a194988d5d6ac528

Add 'generate-tests-config.yaml' playbook

2019-05-24T11:24:33+00:00

With this playbook it is now possible to generate config file
for automated test cases.

Example of it's usage:
  $ tox -e ocp3.11 -- ansible-playbook -i
    ocp-master-node-hostname-or-ip, \
    playbooks/generate-tests-config.yaml \
    -e output_filepath=foo-tests-config.yaml \
    -e additional_devices=/dev/sdf

Change-Id: I53df756deb7c1a01ea47db2a9328b567b5a1ebaf

[Deployment] Fix compatibility check for image tag and RPM repo versions

2019-05-24T11:21:09+00:00

Change-Id: I19d737f8cfef569897ec6ece1389c1849538e0df

[Deployment] Set proper Heketi dc and svc names in config file for tests

2019-05-20T13:27:51+00:00

Before, it was hardcoded. So, fix it by reading those values
dynamically.

Change-Id: Ibab2de8b4f349db4ad6f4bb1afeddc79af444c53

[Deployment] Fix OCP3.6 and 3.7 installation

2019-04-04T11:13:35+00:00

By doing following changes:
- Fix the deployment logic using separate set of vars for
  installation of OCP3.6 and 3.7, which were broken by the too new
  config options, which started being supported only since OCP3.9.
- Add waiters for oc services after nodes reboot.
- Do not update docker for OCP3.6 and 3.7 versions. Because,
  docker version should be fixed for it.
- Add all cluster nodes to the 'OSEv3' Ansible host group,
  because it is required in some places.
- Do not specify 'openshift_use_crio' option for all OCP versions
  except OCP3.11 for 2 reasons:
-- It is supported only for this OCP version
-- Other versions try to run some CRI-O plays just having this option
   defined. In other words - avoid bugs.

Change-Id: I7ab3db30a828f0e965c907282a54b2ae9aead00a

[Deployment] Add playbook for gathering logs from cluster nodes

2019-03-18T10:47:12+00:00

For case when it is needed to provide info for bugreport
or debug in general.
It can be run anytime, separately from the deployment logic.

Example command for running this new playbook:

$ tox -e ocp3.11 -- ansible-playbook -i 127.0.0.1, \
    playbooks/gather_logs.yaml \
    -e config_filepath=/path/to/the/cns-automation-config.yaml \
    -e output_artifacts_dir=../cluster_logs_ocp310_ocs311/

NOTE: 'tox -e ocp3.11' can be omitted only in case you enable
'yedit' (yaml edit) module by other means.

Change-Id: Icb6bf442c07d8d949c930747e8131231a2ff112c

[Deployment] Add CRI-O support

2019-03-18T10:46:37+00:00

To enable or disable CRI-O just define following option:

    openshift_use_crio = true/false

In the "ocp-on-vmware.ini" config file.

Change-Id: Ibd3843d8aa13bfacb0d927142786dc5599e65315