summaryrefslogtreecommitdiffstats
path: root/ci/environments/scenario002-multinode-containers.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-09-27Stop mapping docker to OS::Heat::None in scenariosJiri Stransky1-6/+0
This was needed to make the upgrade job on Ocata->Pike passing, and we now need to remove this to improve the argument order in OOOQ for deployments with scenarios. This shouldn't be backported to Ocata (at least not before we make the split between deploy scenario and upgrade scenario). Change-Id: Ie08bbe08530bd48a0ca58667f0704f360e0a4dd7 Co-Authored-By: Martin André <m.andre@redhat.com> Related-Bug: #1714905 Related-Bug: #1712070 (cherry picked from commit 31550b42027588d82f01db6956c1efaf02d58558)
2017-09-07Use containerized mongodb in scenario002-multinode-containersMartin André1-0/+1
The containerized mongodb service was removed from the default service list from 'environments/docker.yaml' in Ie09ce2a52128eef157e4d768c1c4776fc49f2324. This commit re-enable the containerized mongodb in scenario002-multinode-containers. Change-Id: I57958c94022ccac3ec2ebf7c9438b9e47cbad337 Closes-Bug: #1715391 (cherry picked from commit 13d2bdf41ca3b726acff0b94dae6d394dab4af23)
2017-09-04Add clustercheck to service list for scenariosJiri Stransky1-0/+1
This service is necessary when we containerized TripleO with Pacemaker. The service is added also to non-containerized scenario lists, because the aim is to get rid of the -containers.yaml variants eventually. This shouldn't affect any jobs that don't include docker-ha.yaml. The resource registry entry is mapped to OS::Heat::None by default, and docker-ha.yaml maps it to actual containerized clustercheck. Change-Id: I342e29de52cb6ce069a05a2dbfb0501a2da200e6 Partial-Bug: #1712070 (cherry picked from commit 5b805cb37eec3097552314c6ce43c02c2a604d81)
2017-08-25Containarise Barbican APIJanki Chhatbar1-6/+2
This containerises Barbican API in TripleO Change-Id: Icc5e9841ea48c806af4db61cd6de5e9a7a40a988 Partial-Bug: 1668924 Depends-On: I6b5ec18ccdd51b90ff27ff7d4341260dfba71e4e (cherry picked from commit 6d338b809accea4d3ba09ca8363b1a97ed79b658)
2017-08-22Zaqar: Match service name with service-net-mapJuan Antonio Osorio Robles1-1/+1
This is required for t-h-t to generate the appropriate hieradata. Change-Id: I9b451eac4427a52ad8eec62ff89acc6c6d3ab799 Closes-Bug: #1712328
2017-08-17scenario002/multinode: do not run containerized ZaqarEmilien Macchi1-1/+3
It doesn't work yet, see: https://bugs.launchpad.net/tripleo/+bug/1710959 Change-Id: I05d5325aa704f8e18737e98d3bd6b4d00fc1dca6
2017-08-17scenario002/container: run Barbican non-containerizedEmilien Macchi1-0/+1
... until https://review.openstack.org/#/c/474327 is merged. In the meantime, let's test the scenario with Barbican like before. Depends-On: Ib5c99482f62397fc5fb79a9dc537dfb06ee7f4df Change-Id: Ia96736ad3ddabd33c5ee4518a3f63bafeffcf391
2017-07-24Merge "Add support for nova live/cold-migration with containers"Jenkins1-0/+2
2017-07-24Merge "Refactor iscsi initiator-name reset into separate service"Jenkins1-0/+1
2017-07-23Add support for nova live/cold-migration with containersOliver Walsh1-0/+2
Updates hieradata for changes in https://review.openstack.org/471950. Creates a new service - NovaMigrationTarget. On baremetal this just configures live/cold-migration. On docker is includes a container running a second sshd services on an alternative port. Configures /var/lib/nova/.ssh/config and mounts in nova-compute and libvirtd containers. Change-Id: Ic4b810ff71085b73ccd08c66a3739f94e6c0c427 Implements: blueprint tripleo-cold-migration Depends-On: I6c04cebd1cf066c79c5b4335011733d32ac208dc Depends-On: I063a84a8e6da64ae3b09125cfa42e48df69adc12
2017-07-17Refactor iscsi initiator-name reset into separate serviceOliver Walsh1-0/+1
This currently assumes nova-compute and iscsid run in the same context which isn't true for a containerized deployment Change-Id: I11232fc412adcc18087928c281ba82546388376e Depends-On: I91f1ce7625c351745dbadd84b565d55598ea5b59 Depends-On: I0cbb1081ad00b2202c9d913e0e1759c2b95612a5
2017-07-14CI/scenarios: set NotificationDriver to 'noop'Emilien Macchi1-0/+1
So we don't waste RabbitMQ resources since nothing will actually consume the messages sent on the queue. Note: we don't change scenario001, since it's a Telemetry scenario and the services require notifications enabled. Change-Id: I7d1d80da4eda7c0385461fe62b1d3038022973c6
2017-07-08Disable network validation in multinode jobsBen Nemec1-0/+3
Sometimes the infracloud gateway refuses to ping even though everything else is working fine. Since we have coverage of this functionality in the OVB jobs it should be safe to turn it off here so it stops spuriously failing our jobs. We can't just set the resource to OS::Heat::None because there are other resources with dependencies on it. Instead, this adds a noop version of the validation software config that always returns true. Change-Id: I8361bc8be442b45c3ef6bdccdc53598fcb1d9540 Partial-Bug: 1680167
2017-06-23scenario002: containerize services for CIEmilien Macchi1-3/+4
Change-Id: I9f9a9dcf1666b5b0475bc8fae5b785747480b7d6
2017-05-26Container-specific variants of scenarios 001-004Jiri Stransky1-0/+70
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