summaryrefslogtreecommitdiffstats
path: root/ci/environments/scenario001-multinode-containers.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-11-09Merge "Temporarily disable fluentd from scenario001-multinode-containers" ↵Zuul1-2/+6
into stable/pike
2017-11-08Merge "Add all services to container scenarios" into stable/pikeZuul1-7/+20
2017-11-08Temporarily disable fluentd from scenario001-multinode-containersMichele Baldessari1-2/+6
Mixing containers and BM is currently not working. Once the master promotion will take place we will have a fluentd container and can readd fluentd as a container and the problem should not re-occurr. Change-Id: Iad97f7e0e4de56f46a46d2381fc1ea5822a2114a Related-Bug: #1726891 (cherry picked from commit 35d91ddc6d11bb2696321fff4593d5cca3b0cba8)
2017-11-02Add all services to container scenariosMartin André1-7/+20
This commit brings the multinode containers scenario files closer to their BM variants to add missing services and turning pacemaker on. These require refactorings in OOOQ in order to support non-containerized to containerized upgrade jobs across releases. Ceph-ansible is also going to be switched separately. Co-Authored-By: Jiri Stransky <jistr@redhat.com> Depends-On: Ie0e8de54794a9259c0aeb8c67ae0f6a908844093 Change-Id: Icb659509b38575534be27a1881dbe671c40a5436 Related-Bug: #1714905 Related-Bug: #1712070 (cherry picked from commit c504f83c28b986ceb2b92cc0077959158bd11df7)
2017-10-30Switch scenario004-containers to use ceph-ansibleJiri Stransky1-10/+2
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-19Merge "Remove monitor_interface from ceph-ansible parameters" into stable/pikeZuul1-1/+0
2017-10-14Remove monitor_interface from ceph-ansible parametersGiulio Fidente1-1/+0
We should not pass any hardcoded value for monitor_interface and rely on monitor_address_block only instead. Also removes journal_collocation which is not consumed by newer (and stable) builds of ceph-ansible. Change-Id: Idf213a1f43a66506f76d07102f122839b5096948 Closes-Bug: #1715246 (cherry picked from commit 3e90ae3df5a7c5491672254733ceac163b34a395)
2017-10-12Hardcode tag-stable-3.0-jewel-centos-7 in scenario001-containersJohn Fulton1-1/+1
Change-Id: I88f622c0b7a92ab75c2523fdc0d4d9ac1a2a2560 Closes-Bug: #1722908 (cherry picked from commit 06331a830e8923a9dc2ef8c15f2f1bf9d1d58ba1)
2017-10-09Containerized Fluentd clientJuan Badia Payno1-1/+3
Change-Id: Ia350e4899aa499cf27efffd9d2243e7e95fa1d65 Depends-On: I60796063fa9ebe0d98030fb982d22dabe2593ea0 Depends-On: I585b6877074353b5de62e5efaabfbe62432c473d (cherry picked from commit f37fe4f903f429b43d22b485c29547f576ec7269)
2017-10-05Pin scenario001-multinode-containers to earlier ceph docker containerJohn Fulton1-1/+1
Change-Id: I122a246a559e07ed74c69e3eb172a4bbb801aeb7 Closes-Bug: #1721239 (cherry picked from commit 3e8de70bd5a8c43389432d484189d4de5fc0ae2f)
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-12Add CephConfigOverrides to allow arbitrary configs in ceph.confGiulio Fidente1-0/+1
We need to reuse the ceph_conf_overrides structure provided by ceph-ansible for both user provided configs and TripleO managed configs. This change merges the special user facing parameter with the TripleO generated configs. Also adds osd_scenario and osd_objectstore params for compatibility with newer ceph-ansible versions. Change-Id: I29c689c6c689590da5b6a3f581fdbec98a52e207 Closes-Bug: #1715321 (cherry picked from commit 32bc2abf14af4ca1449e18b848e2be3cff013987)
2017-09-06Unset default value for the DockerCephDaemonImageGiulio Fidente1-0/+1
We do not want a default value for the container image name parameters and expect deployers to set this value instead. Change-Id: I9377b7c3564360353aa6da2d2457b2cfacd4e9d6 Closes-Bug: #1714221 (cherry picked from commit fcc3259891ee67956d63c37217acdb999bc4bb65)
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-09-01Remove tacker from containers scenario001John Trowbridge1-2/+0
The containerized implementation of tacker is incomplete in THT, and relies on the pre-pike single "tacker" container. Container builds using the final pike release of kolla build three tacker containers to have seperate conductor and server containers. According to this bug[1], tacker does not even work without this conductor. Our scenario job needs to be updated to actually test tacker is working. This will need to be backported to pike, and we can work on better supporting tacker in containers in queens. [1] https://bugs.launchpad.net/tripleo/+bug/1710874 Change-Id: I7cab33687a05bf6ba5c6fb70ba21f3250d3ef381 Partial-Bug: 1714270
2017-08-31Telemetry specific config for scenario001Pradeep Kilambi1-0/+3
- Set gnocchi archivepolicy in scenario001 job to high - Set polling interval to 15 seconds instead of 300 Change-Id: Ie12abe1f03d000824c5fb1a46d74b94ce49d7876 (cherry picked from commit 0855d4c7b12d27721044ab09ca0d6e8f188d2e90)
2017-08-25Enable ceilometer compute agentArx Cruz1-0/+1
This service isn't being started by default and it's required in order to ceilometer collect data about cpu, which is required to run tempest integration tests Closes-Bug: #1713038 Change-Id: I79ba7744db78636fba78e041443148c91e06f940 (cherry picked from commit a2ce6d238cd7e72029fdd6e6364a0501f3bfc835)
2017-08-23Do not install additional CentOS packages via ceph-ansibleGiulio Fidente1-0/+1
EPEL is required by the Ceph RPM repo maintained at ceph.com but not by the CentOS SIG repo. The other packages should be already installed in the infra image. This change overrides the list of required packages in ceph-ansible so that it does not install epel-release nor additional unneeded packages [1]. 1. https://github.com/ceph/ceph-ansible/blob/master/group_vars/all.yml.sample#L67 Change-Id: I7b6d2794ebfc0df5b3d5ad9de1d1d55740a38ae0 Closes-Bug: #1712599
2017-08-18Convert scenario001-multinode-containers job to ceph-ansibleGiulio Fidente1-6/+16
Updates ci/environments/scenario001-multinode-containers.yaml to use ceph-ansible instead of puppet-ceph. Change-Id: Idbd02a3c7404daecdc6e2c45ea6d3478bf70552c Depends-On: Ifa4937624ed14a3ece48dd92ba4f69b5e4928e77
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-24Merge "Add support for nova live/cold-migration with containers"Jenkins1-0/+2
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-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-07-07Rename CongressApi to Congress (docker)Emilien Macchi1-1/+1
Before it was Congress, let's stay consistent and stop using CongressApi in Docker service, because we release. Change-Id: Id939b3d70e185da4279f3860812fa5dce27d64dd
2017-06-29scenario001: containerize services for CIEmilien Macchi1-5/+7
Change-Id: I4308032891f0f9f5e93159f4a7ca29dada5850be
2017-05-26Container-specific variants of scenarios 001-004Jiri Stransky1-0/+134
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