aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments/scenario004-multinode-containers.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-10-30Switch scenario004-containers to use ceph-ansibleJiri Stransky1-14/+22
Use ceph-ansible to match the non-containerized variant of scenario004. Depends-On: I137ca9a005df6e95a59a4d629eb94bda6ef00d3a Depends-On: I6acac1826271efcd4d1acf6633bde6eb8a653f44 Co-Authored-By: Martin André <m.andre@redhat.com> Co-Authored-By: Giulio Fidente <gfidente@redhat.com> Change-Id: I1b3c57a2cfda9e74457f17504f51d5b30c5d381d (cherry picked from commit 4e85813d368b94f588471d9bdc4a04d04d3be541)
2017-10-07Default Ceph pg_num and pgp_num to 128Giulio Fidente1-0/+3
As per Ceph docs [1] we should default pg_num and pgp_num to 128 when using less than 5 OSDs. This same change was applied to the ceph-ansible profiles with [2]. Also updates the CI environment files to continue using 32 where we deploy a single OSD. 1. http://docs.ceph.com/docs/master/rados/operations/placement-groups/ 2. Ibd9fb23e04576e95e24af58f856663397886a947 Change-Id: I1920bc8f5251f362af38ad3bd6f46dda42c6ee93 Closes-Bug: #1718756 (cherry picked from commit e17ae7620e03790da0d29092ab42e8089b2e8d11)
2017-09-27Add all services to scenario004-containersJiri Stransky1-12/+27
This commit brings the scenario004 file closer to its BM pendant. We need to start with this one to address a chicken-and-egg issue with featureset files. Change-Id: Ia5c0cefb7051ca42b4d470f5a000eb446d18be30 Co-Authored-By: Martin André <m.andre@redhat.com> Related-Bug: #1714905 Related-Bug: #1712070 (cherry picked from commit b4d0a81e55ad51ecdaf2e923f794418ac77cfc57)
2017-09-05Merge "Remove bgp-vpn from scenario004-multinode-containers" into stable/pikeJenkins1-5/+3
2017-09-05Remove bgp-vpn from scenario004-multinode-containersEmilien Macchi1-5/+3
See full context on https://bugs.launchpad.net/bugs/1713612 but this service isn't containerized yet, so the plan is: - in Pike, we'll run scenario004 (baremetal) and test bgp-vpn and l2gw - in Queens, we'll run scenario004 (baremetal at the beginning) but scenario004-container will be the default and we'll re-add the 2 services when containerized. Change-Id: I04c2a9fb63420b7d8d3616a8ef7a50d2aadc6165 (cherry picked from commit fde4ff2c64f374e109dbb7da87cc7d72da5e0ef5)
2017-09-05Switch manila-share to pacemaker version in scenario004/containersGiulio Fidente1-1/+1
Change-Id: Iefc0d04b19953ece60cf5c886258ed794e5c795d Depends-On: Iba97c0a6a4b4b0529c6434d58275a3d362b74947 Related-Bug: #1712070 (cherry picked from commit 02cd34d148d6abf11cc64852f7931cbd4bccf767)
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-16Set default OSD pool size to 1 in scenario 001/004 containersGiulio Fidente1-0/+1
When the OSD pool size is unset it defaults to 3, while we only have a single OSD in CI so the pools are created but not writable. We did set the default pool size to 1 in the non-containerized scenarios but apparently missed it in the containerized version. Change-Id: I1ac1fe5c2effd72a2385ab43d27abafba5c45d4d Closes-Bug: #1710773
2017-07-26Merge "Add containerized manila-share to CI"Jenkins1-2/+1
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-19Add containerized manila-share to CIVictoria Martinez de la Cruz1-2/+1
Manila Share THT has been merged, so it should be added to the containerized multinode environment in CI. Change-Id: I6bb28e1f5e57b427aafb152d41ec40c807eaa7fa
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-23scenario004: containerize services for CIEmilien Macchi1-2/+5
Change-Id: I025ed07ce97132bce3fa7a15d170fc62e17e07a4
2017-05-26Container-specific variants of scenarios 001-004Jiri Stransky1-0/+92
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