aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments/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-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-21Add logrotate with crond serviceBogdan Dobrelya1-0/+1
Add a docker service template to provide containerized services logs rotation with a crond job. Add OS::TripleO::Services::LogrotateCrond to CI multinode-containers and to all environments among with generic services like Ntp or Kernel. Set it to OS::Heat::None for non containerized environments and only enable it to the environments/docker.yaml. Closes-bug: #1700912 Change-Id: Ic94373f0a0758e9959e1f896481780674437147d Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
2017-08-18ci: don't deploy swift on basic multinode jobEmilien Macchi1-3/+1
Swift is already deployed on scenario002, and we want to keep basic multinode as basic as possible with only the minimum so it runs faster and we can use it for early tests in our CI. Change-Id: I6d2f434305d7ca0d704a9454b758670c39a0af4a
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-05-29Containerized nova-compute working with Deployed ServerJiri Stransky1-0/+70
When using the Deployed Server feature, we rely on Puppet to install packages. But nova-compute/libvirt puppet is running in a container, so it cannot install anything on the host. We rely on virtlogd on the host, so we need to install it there some way. This patch uses host_prep_tasks for that, conditionally based on the EnablePackageInstall stack parameter value. Also multinode-container-upgrade.yaml env is copied as multinode-containers.yaml, to remove the naming confusion, as the environment file can be used for more than just upgrades. The old env file will be removed once we make the upgrade job use the new one (catch 22 type of issue). Change-Id: Ia9b3071daa15bc30792110e5f34cd859cc205fb8