aboutsummaryrefslogtreecommitdiffstats
path: root/puppet/services
AgeCommit message (Collapse)AuthorFilesLines
2017-02-17Merge "docker: new hybrid deployment architecture and configuration"Jenkins1-6/+2
2017-02-16Merge "Configuring a default ntp server."Jenkins1-2/+4
2017-02-16Merge "Remove unused nova_url from neutron config"Jenkins1-2/+0
2017-02-16Merge "Remove deprecated metering_secret"Jenkins1-1/+0
2017-02-16Merge "OVN bridge mappings for tripleo"Jenkins1-0/+11
2017-02-15Merge "Add nova service support for composable upgrades"Jenkins8-4/+160
2017-02-15docker: new hybrid deployment architecture and configurationDan Prince1-6/+2
This patch implements a new docker deployment architecture that should us to install docker services in a stepwise manner alongside of baremetal puppet services. This works by using Yaql to select docker specific services (docker/services/*.yaml) vs the puppet specific ones and then applying the selected Json to relevant Heat software deployments for docker and baremetal puppet in a stepwise fashion. Additionally the new architecture leverages new composable services interfaces from Newton to allow configuration of per-service container configuration sets (directories that are bind mounted into kolla containers) by using the Kolla containers themselves. It does this by spinning up a throw away "configuration only" version of the container being configured itself, then running the puppet apply in that container and copying the generated config files into /var/lib/config-data. This avoids having to install all of the OpenStack dependency packages in the heat-agent-container itself (our previous approach) and should allow us to configure a much wider variety of container config files that would otherwise be impossible with the previous shared approach. The new approach (combined) should allow us to configure containers in both the undercloud and overcloud and incrementally add CI coverage to services as we containerize them. Co-Authored-By: Martin André <m.andre@redhat.com> Co-Authored-By: Ian Main <imain@redhat.com> Co-Authored-By: Flavio Percoco <flavio@redhat.com> Change-Id: Ibcff99f03e6751fbf3197adefd5d344178b71fc2
2017-02-15Merge "OVN plugin configuration fixes"Jenkins2-10/+23
2017-02-14Add nova service support for composable upgradesSteven Hardy8-4/+160
Co-Authored-By: Mathieu Bultel <mbultel@redhat.com> Co-Authored-By: Oliver Walsh <owalsh@redhat.com> Change-Id: Iafad800a6819d7e75fdaab60d328999d3d3c037f Partially-Implements: blueprint overcloud-upgrades-per-service Related-Bug: #1662344
2017-02-14Merge "Reduce memcached memory configuration"Jenkins1-0/+7
2017-02-14Merge "Add upgrade tasks for opstools services"Jenkins3-0/+27
2017-02-14OVN bridge mappings for tripleoBabu Shanmugam1-0/+11
This patch adds an additional configuration setting for OVN bridge mappings Co-authored-by: Numan Siddique <nusiddiq@redhat.com> Change-Id: I99f2c0c8e633e63273e2469d95fbabbbc665c87c Depends-On: Ia6d66fa954571328c0ac3542af17303def382c1a
2017-02-14Add upgrade tasks for opstools servicesMartin Mágr3-0/+27
This patch adds upgrade tasks for sensu-client, fluentd and collectd Change-Id: I3a8096159664b1934b34f6c79b8afb4a3dc645c8
2017-02-14Configuring a default ntp server.Carlos Camacho1-2/+4
Adding a default NTP server by default will keep all Pacemaker and non-Pacemaker deployments aligned with the same server by default. Also useful for keeping time diff controlled for Keystone and Ceph. Change-Id: I8a26bae15cbfb83e3abd6b9ef9d12b57467e6258
2017-02-14Use Keystone internal endpoint instead of admin for nova-ironicGiulio Fidente1-4/+4
As per I1213a83ef8693c1cca1d20de974f7949a801d9f1 this moves to using KeystoneInternal for the nova-ironic template and updates some deprecated hiera keys. Change-Id: Ib1103c00ddb7d6d624f4911147197d8355a3a6dd
2017-02-14Use Keystone internal endpoint instead of admin for servicesJuan Antonio Osorio Robles23-24/+24
The admin endpoint is listening on the ctlplane network by default; services should ideally be using the internal api network for this kind of traffic, as the ctlplane network is mostly for provisioning. On the other hand, the admin endpoint shouldn't be as relevant with services switching to keystone v3. Change-Id: I1213a83ef8693c1cca1d20de974f7949a801d9f1
2017-02-14Merge "Configure the placement API's interface to use the internal endpoint"Jenkins1-0/+6
2017-02-13Merge "Enables support for configuring Cinder with Dell EMC ScaleIO storage ↵Jenkins1-0/+111
backend."
2017-02-13Merge "nova-placement: support upgrade"Jenkins1-0/+4
2017-02-13Merge "placement: switch service to use NovaPlacementNetwork"Jenkins1-2/+2
2017-02-13Merge "Remove [heat,glance,ironic,cinder,keystone] db sync from ansible"Jenkins5-15/+0
2017-02-13Merge "Fix Neutron region in nova.conf"Jenkins1-0/+1
2017-02-13nova-placement: support upgradeEmilien Macchi1-0/+4
Upgrade nova-placement service with Ansible. Change-Id: I43cac37afbc8b39708389895d9f7350b6bd4bcfd
2017-02-13Remove [heat,glance,ironic,cinder,keystone] db sync from ansiblemarios5-15/+0
These are handle by puppet as usual (puppet run comes after the ansible steps) so remove them from these remaining upgrade_tasks Change-Id: Ic341f31251622ccb11a5f7818b2edf7a82391560
2017-02-13Remove the ansible neutron-api db sync as for other servicesmarios1-3/+0
In line with other service we leave the db sync to puppet unless needed for some workaround/upgrade related reason. Change-Id: I9ae463cda19ffdd66f9ccbae40e85551841ab938
2017-02-13Configure the placement API's interface to use the internal endpointJuan Antonio Osorio Robles1-0/+6
Due to the keystoneauth library's defaults, it uses the public interface currently. This is not desirable in most cases (specially when using network isolation); so we set it to use the internal one. Change-Id: Ic222a2b734f4d512349fd8556aa2864b13a1eb07 Depends-On: I1c7fd3a32d04e2fafb3820d1c1f221f45c613c83 Closes-Bug: #1663187
2017-02-12Merge "adding Congress Support"Jenkins1-0/+90
2017-02-12Reduce memcached memory configurationAlex Schultz1-0/+7
Previously the memcached configuration was set to use the defaults which would be 95% of the avaiable ram in the system. This can lead to memory contention issues if memcache is heavily utilized. This change reduces the default to 50% and exposes the ability to tune this configuration. Change-Id: Ie8a48ff4cf509e93d7c1487813d5feed5e5131a4 Closes-Bug: #1662941
2017-02-12Merge "Adds cluster status check_and_fail before running upgrade (step0)"Jenkins1-0/+3
2017-02-12placement: switch service to use NovaPlacementNetworkEmilien Macchi1-2/+2
... instead of using NovaApiNetwork. Change-Id: I34043c68c24b05bac98f864bc2ac2fc4743617ab
2017-02-12Fix Neutron region in nova.confEmilien Macchi1-0/+1
Default in puppet-neutron is 'RegionOne', so let's override it with the right parameter in TripleO. Change-Id: I3f1693b91178027c8e05288aeba72b7d6bd042be
2017-02-10Merge "Remove gnocchi db sync from the ansible upgrade step"Jenkins1-3/+0
2017-02-10Merge "Remove unused SR-IOV parameter NeutronSupportedPCIVendorDevs"Jenkins1-7/+0
2017-02-10Remove gnocchi db sync from the ansible upgrade stepMathieu Bultel1-3/+0
Since gnocchi db sync for upgrade is made by puppet we need to remove it from ansible tasks Change-Id: I4a26513c3e3d0dcf77c007ea865364e38da3a94a
2017-02-10Adds cluster status check_and_fail before running upgrade (step0)marios1-0/+3
This depends on a change in the pacemaker_cluster resource https://review.gerrithub.io/#/c/307078/ Change-Id: Iaf50e27607b159173190912604198b6a471fe35f
2017-02-10Merge "Add pacemaker composable upgrade steps"Jenkins1-0/+15
2017-02-10adding Congress SupportDan Radez1-0/+90
Depends-On: Ic74ccd5fa7b3b04ca810416e5160463252f17474 Implements: blueprint congress-service-integration Change-Id: Ie60540c340c0eb71ff376aba65507a8bb3e909b6 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-02-10Remove aodh db sync from ansible upgradeMathieu Bultel1-3/+0
The db sync won't be run by ansible but by puppet as part of the converge step Change-Id: Ie868a92ece020e5749a401e0897be5ab80f13559
2017-02-09Adding Tacker SupportDan Radez1-0/+91
Depends-On: Ide0e60f3b7a3733788af4337c1c39b4a956c876f Depends-On: I3d6bbc05644e840395f87333ec80e3b844f69903 Depends-On: Idf6abcb7fe766546cb362ad4afe54f4bccd9c994 Implements: blueprint tacker-service-integration Change-Id: Ibddc81561f6e6ba671bd01a9251c57d3ad67ba8c Signed-off-by: Dan Radez <dradez@redhat.com>
2017-02-09Merge "Re-organizes Contrail services to the correct roles"Jenkins13-237/+344
2017-02-08Remove deprecated metering_secretPradeep Kilambi1-1/+0
use telemetry_secret instead which is already set. Change-Id: I1815ba16519a529c6b7cbdf164e8853857692d73
2017-02-08Re-organizes Contrail services to the correct rolesMichael Henkel13-237/+344
In current setup some Contrail services belong to the wrong roles. The Contrail control plane can be impacted if the Analytics database has problems. Change-Id: I0d57a2324c38b5b20cc687c6217a7a364941f7e6 Depends-On: Id0dd35b95c5fe9d0fcc1e16c4b7d6cc601f10818 Closes-Bug: #1659560
2017-02-08Merge "Remove openstack-ceilometer-expirer check"Jenkins1-4/+0
2017-02-08Merge "Composable service support for Cinder Dell EMC Storage Center"Jenkins1-0/+85
2017-02-08Merge "implement a collectd composable service"Jenkins3-0/+124
2017-02-07Merge "Add registry and role service list entries for Octavia"Jenkins1-1/+3
2017-02-07Merge "Stop deploying Nova API in WSGI with Apache"Jenkins1-20/+31
2017-02-07Merge "Introduce Octavia implementation services"Jenkins3-0/+233
2017-02-07Merge "Stop setting bind_address on nova db uri."Jenkins1-6/+0
2017-02-07Stop deploying Nova API in WSGI with ApacheEmilien Macchi1-20/+31
It was suggested by Nova team to not deploying Nova API in WSGI with Apache in production. It's causing some issues that we didn't catch until now (see in the bug report). Until we figure out what was wrong, let's disable it so we can move forward in the upgrade process. Change-Id: I09b73476762593642a0e011f83f0233de68f2c33 Related-Bug: 1661360