summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-08-31Merge "Add DockerPuppetProcessCount defaults to 3" into stable/pikeJenkins2-0/+7
2017-08-30Merge "Add missing Docker service" into stable/pikeJenkins5-0/+5
2017-08-30Merge "Set docker-puppet --health-cmd = /bin/true" into stable/pikeJenkins1-0/+1
2017-08-30Merge "container ovs-agent, ensure br-ex exists" into stable/pikeJenkins2-2/+33
2017-08-30Merge "Use integers for rabbitmq ports" into stable/pikeJenkins1-2/+2
2017-08-30Merge "Update UPPER_CONSTRAINTS_FILE for stable/pike" into stable/pikeJenkins1-1/+1
2017-08-30Merge "Update .gitreview for stable/pike" into stable/pikeJenkins1-0/+1
2017-08-30container ovs-agent, ensure br-ex existsSteve Baker2-2/+33
Currently the container neutron-ovs-agent is stuck in a restart loop in many environments because the bridge br-ex is missing. This bridge is created by running the puppet class neutron::agents::ml2::ovs but limiting that run to tag neutron::plugins::ovs::bridge. The hiera neutron::agents::ml2::ovs::bridge_mappings should already exists to create the bridge with the required settings. This change should ensure br-ex exists after step 3. Since br-ex is created regardless of the chosen network config, environments/docker-network.yaml is not longer required. It can be deleted once there are no more references to it in CI and documentation. Change-Id: Ie425148b0ad0f38e149c5fa0a97d98ec35d0a5bb Closes-Bug: #1699261 Closes-Bug: #1691403 Closes-Bug: #1689556 (cherry picked from commit 76f130d6e8f7434433b2602af9794f1e9c742e1f)
2017-08-30Use integers for rabbitmq portsJuan Antonio Osorio Robles1-2/+2
They should be integers as specified in the parameter definition of the class. Else it'll fail. Change-Id: I06b6e46c0722516e28e8bff4d481fb4b7a08bd61 Closes-Bug: #1713659 (cherry picked from commit 4bea8cf918463c43c7d5f4e46984ab54271ea3e5)
2017-08-30Add missing Docker serviceAlex Schultz5-0/+5
The example composable roles are missing the docker service declaration so they currently do not work when trying to deploy with containerized services. Change-Id: I986ae561b950e74aacea10bce84673e8d0c9bd97 Closes-Bug: #1713755 (cherry picked from commit 50c975d1590930e6ce453942f99759a25ec08703)
2017-08-30Use Python to compute release notes versionEmilien Macchi1-2/+2
Leave the version fields blank, since the release notes document applies to all versions. That will avoid manual changes in the future like we did until now. Change-Id: Ibb33ade808c9866b5314b7dda60a44000089a467 (cherry picked from commit 4782394044a8f66de63db7772b7a5992a781cc57)
2017-08-30Merge "Support deploying OVN as container services" into stable/pikeJenkins5-0/+420
2017-08-30Merge "Make archive policy configurable" into stable/pikeJenkins1-1/+5
2017-08-29Add DockerPuppetProcessCount defaults to 3Dan Prince2-0/+7
docker-puppet.py is very aggressive about running concurrently. It uses python multiprocessing to run multiple config generating containers at once. This seems to work well in general, but in some cases... perhaps when the registry is slow or under heavy load can cause timeouts to occur. Lately I'm seeing several 'container did not start before the specified timeout' errors that always seem to occur when config files are generated (docker-puppet.py is initially executed. A couple of things: -when config files are generated this is the first time most of the containers are pulled to each host machine during deployment -docker-puppet.py runs many of these processes at once. Some of them run faster, other not. -docker daemon's pull limit defaults to 3. This would throttle the above a bit perhaps contributing the the likelyhood of a timeout. One solution that seems to work for me is to set the PROCESS_COUNT in docker-puppet.py to 3. As this matches docker daemon's default it is probably safer at the cost of being slightly slower in some cases. Change-Id: I17feb3abd9d36fe7c95865a064502ce9902a074e Closes-bug: #1713188 (cherry picked from commit 949d367ddeb42eff913cdbed733ccf6239b4864b)
2017-08-29Set docker-puppet --health-cmd = /bin/trueDan Prince1-0/+1
Change-Id: Idf627a348cad8d5287c82cb393367210f1c760cf Closes-bug: #1713185 (cherry picked from commit 20e1f0e8c9a2bbc3734f6eec0ee9ac2d5156f166)
2017-08-29manila: set "host" to "hostgroup"Tom Barron2-0/+12
when running manila-share under control of pacemaker, as is done for cinder-volume service in the same circumstance. Change-Id: Ic97f01913bae2a388c962a38fa175eb1d763cdcb Depends-On: Ie31f2d5ccf458f5fcfe8bec5f2c37f45070cfde2 Closes-Bug: #1712842 (cherry picked from commit 8fa6c6e58c7ac0d32bf2f0dfb586683cf006e3bf)
2017-08-29Merge "Enable ceilometer compute agent" into stable/pikeJenkins2-0/+2
2017-08-28Merge "Handle failure of carrier check in configure_safe_defaults()" into ↵Jenkins1-3/+4
stable/pike
2017-08-28Merge "Add panko publisher in the event pipeline" into stable/pikeJenkins1-1/+1
2017-08-28Support deploying OVN as container servicesNuman Siddique5-0/+420
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-28Make archive policy configurablePradeep Kilambi1-1/+5
Change-Id: I603ce6922130fe32aa1a154df8146ee582bf1a45 (cherry picked from commit b1d7887ce710a98f061100e2878a54c06a5d09e2)
2017-08-26Handle failure of carrier check in configure_safe_defaults()Bob Fournier1-3/+4
Configure_safe_defaults() should handle carrier check failures in the same way as the change that was made to dhcp-all-interfaces.sh in https://review.openstack.org/#/c/419527/. That is, it should ignore failures when cat'ing the carrier file. Change-Id: I100a40835d0ccecee9b4851aae6366c6ab4813a5 Closes-Bug: 1712687 (cherry picked from commit ed976d285caab1858f0b6e74e14a723113d27052)
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-25Add panko publisher in the event pipelinePradeep Kilambi1-1/+1
Even though panko is deprecated, we still enable it by default. So lets keep it in pipeline as well until its fully dead. Change-Id: Idac89820a66c59b921551857cccae6dbc38241c3 (cherry picked from commit 3dbd5bfe86c2d6864c5678774fc7f910ab846300)
2017-08-25Containarise Barbican APIJanki Chhatbar3-6/+160
This containerises Barbican API in TripleO Change-Id: Icc5e9841ea48c806af4db61cd6de5e9a7a40a988 Partial-Bug: 1668924 Depends-On: I6b5ec18ccdd51b90ff27ff7d4341260dfba71e4e (cherry picked from commit 6d338b809accea4d3ba09ca8363b1a97ed79b658)
2017-08-24Update UPPER_CONSTRAINTS_FILE for stable/pikeOpenStack Release Bot1-1/+1
Change-Id: If1376a7d802d79c2b7533c8f315f47c21f896476
2017-08-24Update .gitreview for stable/pikeOpenStack Release Bot1-0/+1
Change-Id: I62443317bb2a7fbe84f6bb2aa769053b66edb022
2017-08-24Merge "Remove baremetal cron jobs on docker upgrade"Jenkins4-0/+16
2017-08-24Merge "Docker: Enable TLS in the internal network for libvirt"Jenkins2-1/+21
2017-08-24Merge "Specify the start count to 0 for the update step loop"Jenkins1-5/+5
2017-08-24Merge "Do not install additional CentOS packages via ceph-ansible"Jenkins1-0/+1
2017-08-23Merge "More fixes for the Ceph docker images url parsing"Jenkins1-2/+2
2017-08-23Merge "Configure listen_address for libvirtd when TLS is enabled"Jenkins1-0/+2
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-23Merge "docker: Stop all active ceilometer services during compute upgrade"Jenkins1-1/+16
2017-08-23Specify the start count to 0 for the update step loopMathieu Bultel1-5/+5
Force the count start to 0 to ensure that the update step loop will start to 0 and execute the update step0 Closes-Bug: #1712498 Change-Id: I71be55c1f56e53e5c565bec281795d63e5845ff6
2017-08-23Configure listen_address for libvirtd when TLS is enabledJuan Antonio Osorio Robles1-0/+2
It wasn't being configured, and the default is to listen on all interfaces. This fixes that. Change-Id: I00da25474fb1544eabdedaf126e67d5a6617f02f Closes-Bug: #1712475
2017-08-23Docker: Enable TLS in the internal network for libvirtJuan Antonio Osorio Robles2-1/+21
Bind mounts the necessary certs and keys to enable live migrations using TLS. bp tls-via-certmonger-containers Depends-On: I26a7748b37059ea37f460d8c70ef684cc41b16d3 Change-Id: I81efa85d916823f740bf320c88a248403743a45b
2017-08-23Merge "Accept multiple registries in DockerInsecureRegistryAddress"Jenkins1-5/+5
2017-08-23Merge "Add Ceilometer API and Collector service to roles_data"Jenkins4-0/+6
2017-08-22Merge "Render port templates via j2"Jenkins30-1396/+91
2017-08-22Merge "Zaqar: Match service name with service-net-map"Jenkins6-6/+12
2017-08-22Merge "Fix configuration files path for logrotate container"Jenkins1-1/+1
2017-08-22Zaqar: Match service name with service-net-mapJuan Antonio Osorio Robles6-6/+12
This is required for t-h-t to generate the appropriate hieradata. Change-Id: I9b451eac4427a52ad8eec62ff89acc6c6d3ab799 Closes-Bug: #1712328
2017-08-22Merge "Add nova metadata to TLS everywhere/docker services list"Jenkins1-3/+4
2017-08-22Merge "change sriovnicswitch to be first with openvswitch"Jenkins1-1/+1
2017-08-22Fix configuration files path for logrotate containerMartin André1-1/+1
The config_volume is named 'crond', and so must me the path to puppet-generated directory. Change-Id: I13b4ad7642ddf3bc5d1f4aa979b4a91a89605fb1 Closes-Bug: #1712300
2017-08-21Merge "TLS everywhere/haproxy: Remove empty postsave command"Jenkins2-2/+0
2017-08-21Render port templates via j2Steven Hardy30-1396/+91
Remove these from the j2 excludes and instead render all the networks to avoid duplication. Change-Id: Id8e14e06ffe959c50456b4c88fef306046a8b478 Partially-Implements: blueprint composable-networks
2017-08-21Merge "Add logrotate with crond service"Jenkins22-0/+118