Container-specific variants of scenarios 001-004
authorJiri Stransky <jistr@redhat.com>
Thu, 18 May 2017 12:30:43 +0000 (14:30 +0200)
committerJiri Stransky <jistr@redhat.com>
Fri, 26 May 2017 13:07:55 +0000 (15:07 +0200)
commitf48c10c08b63779e410452c993a118a91d4a44e5
treeda2ce9fadd88014997efdf79d6e32da0f0f6076b
parent8a099a91c250511ed3278e2c3548138a881ba689
Container-specific variants of scenarios 001-004

Add container-specific variants of scenarios. These variants are
supposed to be temporary, as their only purpose is to allow us CIing the
scenarios with containers while we don't have pacemaker containerized
yet. Once we can deploy and upgrade containerized deployment with
pacemaker, these should be deleted and normal scenarios should be used.

Alternative approach would be to edit the scenarios on the fly within
the CI job, to remove the pacemaker parts, which would be more DRY, but
perhaps more surprising when trying to debug issues.

Change-Id: I36ef3f4edf83ed06a75bc82940152e60f9a0941f
ci/environments/multinode-container-upgrade.yaml
ci/environments/scenario001-multinode-containers.yaml [new file with mode: 0644]
ci/environments/scenario002-multinode-containers.yaml [new file with mode: 0644]
ci/environments/scenario003-multinode-containers.yaml [new file with mode: 0644]
ci/environments/scenario004-multinode-containers.yaml [new file with mode: 0644]