path: root/ci
AgeCommit message (Collapse)AuthorFilesLines
2017-11-09Re-enable containerized fluentdMartin André1-6/+1
Now that we got a promotion, there is a container image for fluentd in tripleomaster registry. We can finally re-enable the containerized fluentd service in scenario0001. Change-Id: I636e63f9b66dd47267fa40febf49a6ec9a6b7ef3 Related-Bug: #1721723 Closes-Bug: #1726891 (cherry picked from commit c795e748d2e0fe1299919872250d6951246c1365)
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/pikeZuul4-27/+74
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-08Merge "Switch scenario004-containers to use ceph-ansible" into stable/pikeZuul2-24/+24
2017-11-02Add all services to container scenariosMartin André4-27/+74
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 Stransky2-24/+24
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-27Disable MongoDB in scenario002Michele Baldessari2-4/+4
We have disabled mongo by default in containers via: Id2e6550fb7c319fc52469644ea022cf35757e0ce Disable mongodb by default Ie09ce2a52128eef157e4d768c1c4776fc49f2324 Containerized mongodb, disable by default, fix upgrade Let's not use it in scenario002 either. NB: Not entirely clean cherry-pick due to scenario002-multinode-containers.yaml having many more services in master than in pike. Change-Id: I0d2df25ed797ffb8425ba81736526d3688e5de5c Closes-Bug: #1724679 (cherry picked from commit 900416d9809bf4446c0c037128edb033ab9b3bcc)
2017-10-23ci-ovn: Disable Swift services in scenario 007 container jobNuman Siddique1-0/+3
Closes-bug: #1722758 Change-Id: I0161c534807ca45e2d2b6fcace5fc3e26eb450a2 (cherry picked from commit 7e398bf18910e062415ce4e70236ce98577aed13)
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-07Merge "Default Ceph pg_num and pgp_num to 128" into stable/pikeJenkins5-0/+15
2017-10-07Default Ceph pg_num and pgp_num to 128Giulio Fidente5-0/+15
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-10-07Use sub_nodes_private instead of node_privateSagi Shnaidman1-2/+2
node_private file doesn't exist anymore, use sub_nodes_private instead Change-Id: Ifb3af18733c0e1fd6895c270bb39199acaa98968
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 Stransky6-31/+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-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-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-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-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-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 Stransky15-0/+15
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 Kilambi2-0/+6
- 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-30Merge "Support deploying OVN as container services" into stable/pikeJenkins1-0/+82
2017-08-29Merge "Enable ceilometer compute agent" into stable/pikeJenkins2-0/+2
2017-08-28Support deploying OVN as container servicesNuman Siddique1-0/+82
This patch adds the support to containerize OVN services for the base profile. OVN db servers do not support active-active mode yet. It does support master-slave mode supported through pacemaker, which will be supported in a later patch. Presently the tripleo container framework doesn't allow to start a container in only controller 0 (or bootstrap node). OVN db servers and ovn-northd are started on all the controllers, but only the OVN db servers running in the boot strap controller are configured to listen on the tcp ports 6641 and 6642. OVN neutron mechanism driver and ovn-controller's use the ovn_dbs_vip to connect to the OVN db servers. Haproxy configures all the controllers as back ends, but only OVN db servers running on controller 0 respond since only they are configured properly. The OVN containers running on other controller nodes do not interact any way, but are wasteful resources. This patch also adds the scenario007-multinode-containers CI template. Partial-bug: #1699085 Change-Id: I98b85191cc1fd8c2b166924044d704e79a4c4c8a (cherry picked from commit e7cd03d2f0fcd8e3069246ced94f1a83869b8bea)
2017-08-25Enable ceilometer compute agentArx Cruz2-0/+2
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-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-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-22Merge "Zaqar: Match service name with service-net-map"Jenkins2-2/+2
2017-08-22Zaqar: Match service name with service-net-mapJuan Antonio Osorio Robles2-2/+2
This is required for t-h-t to generate the appropriate hieradata. Change-Id: I9b451eac4427a52ad8eec62ff89acc6c6d3ab799 Closes-Bug: #1712328
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-19Merge "Convert scenario001-multinode-containers job to ceph-ansible"Jenkins1-6/+16
2017-08-19Merge "ci: don't deploy swift on basic multinode job"Jenkins3-9/+3
2017-08-18Merge "scenario002/multinode: do not run containerized Zaqar"Jenkins1-1/+3
2017-08-18Merge "scenario002/container: run Barbican non-containerized"Jenkins1-0/+1
2017-08-18ci: don't deploy swift on basic multinode jobEmilien Macchi3-9/+3
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-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-17Merge "Render IP map and host maps according to network_data.yaml"Jenkins2-4/+4
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-08-16Render IP map and host maps according to network_data.yamlDan Sneddon2-4/+4
This change renders the network IP maps and hostname maps for all networks defined in network_data.yaml. This should make it possible to create custom networks that will be rendered for all applicable roles. Note that at this time all networks will be rendered whether they are enabled or not. All networks will be present in all roles, but ports will be associated with noop.yaml in roles that do not use the network. This is in accordance with previous behavior, although we may wish to change this in the future to limit the size of the role definitions and reduce the number of placeholder resources in deployments with many networks. Note that this patch is a replacement for original patch https://review.openstack.org/#/c/486280, which I was having trouble rebasing to current. Change-Id: I445b008fc1240af57c2b76a5dbb6c751a05b7a2a Depends-on: I662e8d0b3737c7807d18c8917bfce1e25baa3d8a Partially-implements: blueprint composable-networks
2017-08-16Set default OSD pool size to 1 in scenario 001/004 containersGiulio Fidente2-0/+2
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-08-02Add Telemetry services to scenario002Pradeep Kilambi1-0/+13
We need to test gnocchi with swift backend. So adding telemetry to scenario002 job to cover that. Change-Id: I284de61bbefac9e9b37390650016643ffe38b5cc
2017-07-27Add 'ovn-controller' serviceNuman Siddique1-2/+3
Presently the ovn-controller service (puppet/services/neutron-compute-plugin-ovn.yaml) is started only on compute nodes. But for the cases where the controller nodes provide the north/south traffic, we need ovn-controller service runninng in controller nodes as well. This patch - Renames the neutron-compute-plugin-ovn.yaml to ovn-controller.yaml which makes more sense and sets the service name as 'ovn-controller'. - Adds the service 'ovn-controller' to Controller and Compute roles. - Adds the missing 'upgrade_tasks' section in ovn-dbs.yaml and ovn-controller.yaml Depends-On: Ie3f09dc70a582f3d14de093043e232820f837bc3 Depends-On: Ide11569d81f5f28bafccc168b624be505174fc53 Change-Id: Ib7747406213d18fd65b86820c1f86ee7c39f7cf5