From f48c10c08b63779e410452c993a118a91d4a44e5 Mon Sep 17 00:00:00 2001 From: Jiri Stransky Date: Thu, 18 May 2017 14:30:43 +0200 Subject: 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 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'ci/environments/multinode-container-upgrade.yaml') diff --git a/ci/environments/multinode-container-upgrade.yaml b/ci/environments/multinode-container-upgrade.yaml index 89970419..24bb1f49 100644 --- a/ci/environments/multinode-container-upgrade.yaml +++ b/ci/environments/multinode-container-upgrade.yaml @@ -1,7 +1,7 @@ -# NOTE: This is an environment specific for containers upgrade -# CI. Mainly we deploy non-pacemakerized overcloud, as at the time -# being containerization of services managed by pacemaker is not -# complete, so we deploy and upgrade the non-HA services for now. +# NOTE: This is an environment specific for containers CI. Mainly we +# deploy non-pacemakerized overcloud. Once we are able to deploy and +# upgrade pacemakerized and containerized overcloud, we should remove +# this file and use normal CI multinode environments/scenarios. resource_registry: OS::TripleO::Controller::Net::SoftwareConfig: ../common/net-config-multinode-os-net-config.yaml -- cgit 1.2.3-korg