aboutsummaryrefslogtreecommitdiffstats
path: root/puppet
AgeCommit message (Collapse)AuthorFilesLines
2017-06-05Merge "Fix the constraints for THT params NeutronDpdkCoreList and HostCpusList"Jenkins1-4/+4
2017-06-05Merge "Remove nova placement config for compute service node on upgrade"Jenkins1-18/+0
2017-06-03Merge "Add support for linuxbridge agent"Jenkins1-0/+83
2017-06-02Merge "Server blacklist support"Jenkins6-1/+116
2017-06-02Merge "Upgrade gnocchi without skip-storage"Jenkins1-1/+1
2017-06-02Merge "Handle upgrading cinder-volume under pacemaker"Jenkins1-0/+15
2017-06-01Increase default for NovaReservedHostMemory to 4096Sven Anderson1-1/+1
Idle compute nodes are found to already consume ~1.5GB of memory, so 2GB is a bit tight. Increasing to 4GB to be on the safe side. Also see https://bugzilla.redhat.com/show_bug.cgi?id=1341178 Change-Id: Ic95984b62a748593992446271b197439fa12b376
2017-05-31Server blacklist supportJames Slagle6-1/+116
Adds the ability to blacklist servers from all SoftwareDeployment resources. The servers are specified in a new list parameter, DeploymentServerBlacklist by the Heat assigned name (overcloud-compute-0, etc). implements blueprint disable-deployments Change-Id: I46941e54a476c7cc8645cd1aff391c9c6c5434de
2017-05-31Fix the constraints for THT params NeutronDpdkCoreList and HostCpusListKarthik S1-4/+4
This fix needs to be backported to ocata. Change-Id: I5938761efa4f56e576f41929e0bc12df246ac81a Signed-off-by: Karthik S <ksundara@redhat.com> Closes-Bug: #1694703
2017-05-31Upgrade gnocchi without skip-storagePradeep Kilambi1-1/+1
When gnocchi-upgrade run, we need to ensure storage is upgraded so we initialize the necessary storage sacks. Closes-bug: #1693621 Change-Id: I84e4fc3b6ad7fd966c4097a29678a0fd5b7a20a5
2017-05-30Merge "Enable arp_accept for all interfaces"Jenkins1-0/+2
2017-05-29ceilometer-expirer: remove the crontab during upgradeEmilien Macchi1-5/+17
When running disabled/ceilometer-expirer.yaml, we want to remove the crontab that used to run ceilometer-expirer binary in periodic way. Let's use Puppet to remove this crontab. We can't easily use Ansible tasks this time, because the Ansible cron module can only remove Crontabs previously managed by Ansible: https://docs.ansible.com/ansible/cron_module.html#examples In this case, Puppet will erase the crontab in Pike. In Queens, we'll be able to remove these environments files since we wouldn't need it anymore. Change-Id: Idb050c3b281d258aea52d6a3ef40441bb9c8bcbe
2017-05-26Handle upgrading cinder-volume under pacemakerAlan Bishop1-0/+15
Add upgrade tasks for cinder-volume when it's controlled by pacemaker: o Stop the service before the entire pacemaker cluster is stopped. This ensures the service is stopped before infrastructure services (e.g. rabbitmq) go away. o Migrate the cinder DB prior to restarting the service. This covers the situation when puppet-cinder (who otherwise would handle the db sync) isn't managing the service. o Start the service after the rest of the pacemaker cluster has been started. Closes-Bug: #1691851 Change-Id: I5874ab862964fadb68320d5c4de39b20f53dc25c
2017-05-25Enable arp_accept for all interfacesIhar Hrachyshka1-0/+2
OpenStack heavily relies on gratuitous ARP updates when moving floating IP addresses between devices. When a floating IP moves, Neutron L3 agent issues a burst of gratuitous ARP packets that should update any existing ARP table entries on all nodes that belong to the same network segment. Due to locktime kernel behavior, some gratuitous ARP packets may be ignored [1], rendering ARP table entries broken for some time. Due to a kernel bug [2], the time may be as long as hours, depending on other traffic flowing to the node. With the current EL7 kernel, the only way to make sure that nodes honor all sent gratuitous ARP updates is to set arp_accept to 1; this will disable locktime mechanism for the packets sent by Neutron L3 agent, and will make sure ARP tables are always updated. [1] https://patchwork.ozlabs.org/patch/762732/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1450203 Related-Bug: #1690165 Change-Id: I863b240e0ab4c4d5bb844f91b607fd0937d5cedf
2017-05-25Add ignore_projects to filter gnocchi eventsPradeep Kilambi1-0/+8
Without this, ceilometer db gets hammered with gnocchi swift events. Keystone creds are required so middleware can query for id. Related change: I5c0f4f1a2c7fe7eb39ea6441970e9ac0946a4ec1 Change-Id: I9a7a80252703e470a69dc10352e7ece45ab23150
2017-05-25Add support for linuxbridge agentBartosz Stopa1-0/+83
Currently TripleO does not support LinuxBridge driver, setting NeutronMechanismDrivers to linuxbridge will not force ml2 plugin to use linuxbridge. This commit adds new environment file which replaces default ovs agent with linuxbridge on Compute and Controller nodes. Change-Id: I433b60a551c1eeb9d956df4d0ffb6eeffe980071 Closes-Bug: #1652211 Depends-On: Iae87dc7811bc28fe86db0c422c363eaed5e5285b Depends-On: Ie3ac03052f341c26735b423701e1decf7233d935
2017-05-25Merge "Enable mistral to run under mod_wsgi"Jenkins1-6/+38
2017-05-24Merge "Role Specific paramaeter support for neutron-ovs-dpdk-agent service"Jenkins1-9/+32
2017-05-23Merge "Remove osd_pool_default_min_size to allow Ceph cluster to do the ↵Jenkins2-2/+5
right thing by default"
2017-05-23Merge "Disable mongodb by default"Jenkins1-0/+38
2017-05-23Merge "Use disabled suffix for disabled service names"Jenkins3-3/+3
2017-05-22Remove osd_pool_default_min_size to allow Ceph cluster to do the right thing ↵Keith Schincke2-2/+5
by default The default value is 0 which has the minimum number be caluclated based on the replica count from osd_pool_defaut_size. The default replica count is 3 and the calculated min_size is 2. If the replica count is 1 then the min_size is 1. ie: min_size = replica - (replica/2) Add CephPoolDefaultSize parameter to ceph-mon.yaml. This parameter defaults to 3 but can be overriden. See puppet-ceph-devel.yaml for an example Change-Id: Ie9bdd9b16bcb9f11107ece614b010e87d3ae98a9
2017-05-22Disable mongodb by defaultJuan Antonio Osorio Robles1-0/+38
It's not used by any service that we enable by default. So instead, I added it to the environment that enables the services that use it. Change-Id: Id2e6550fb7c319fc52469644ea022cf35757e0ce
2017-05-22Use disabled suffix for disabled service namesJuan Antonio Osorio Robles3-3/+3
This changes both the service names and the file names for disabled services, adding the 'disabled' suffix to them. This comes with the reasoning that, if a service requires a disabled service, and checks for the name in the "service_names" hiera entry, it will appear as if the service was enabled, when it's actually not. So changing the name and using this convention prevents that issue. Change-Id: I308d6680a4d9b526f22ba0d7d20e5db638aadb9a
2017-05-22Merge "TLS everywhere: configure mongodb's TLS settings"Jenkins1-0/+37
2017-05-20Merge "Open ports 443 and 80 on haproxy's firewall when horizon is standalone"Jenkins1-0/+7
2017-05-20Merge "Support Redfish hardware in the overcloud Ironic"Jenkins1-1/+13
2017-05-20Merge "Dell SC: Add secondary DSM support"Jenkins1-0/+16
2017-05-19Role Specific paramaeter support for neutron-ovs-dpdk-agent serviceSaravanan KR1-9/+32
Merge the role specific parmaeter with the default parameter with the higher precendece given to role specific parameters. Use the merged settings to the hiera config settings. Change-Id: I500558dfbf4ac4ddcf850064e654c4fab03d141b
2017-05-19Update the template_version alias for all the templates to pike.Carlos Camacho180-180/+180
Master is now the development branch for pike changing the release alias name. Change-Id: I938e4a983e361aefcaa0bd9a4226c296c5823127
2017-05-19Merge "Add l2gw neutron agent support"Jenkins1-0/+106
2017-05-18Merge "neutron: set enable_dvr = False if NeutronEnableDVR is false"Jenkins1-0/+1
2017-05-18Merge "Enable splay for os-collect-config"Jenkins6-0/+60
2017-05-18neutron: set enable_dvr = False if NeutronEnableDVR is falseIhar Hrachyshka1-0/+1
This will make neutron-server stop advertising dvr extension if the cloud is not configured to support this flavor of Neutron routers. Change-Id: I38c8208edff07f7887887918729beb7710068078 Related-Bug: #1450067
2017-05-18Merge "TLS-everywhere: Configure CA for apache"Jenkins1-0/+6
2017-05-18Merge "Default snmp to less verbose logging"Jenkins1-0/+5
2017-05-18Add l2gw neutron agent supportPeng Liu1-0/+106
L2 Gateway (L2GW) is an API framework for OpenStack that offers bridging two or more networks together to make them look at a single broadcast domain. This patch implements the l2gw agent which is one of the backend of the l2 gateway service plugin. Change-Id: I1ae8132ceff9410be7bd82caddf0d14251e720bf Depends-On: If1501c153b1b170b9550cb7e5a23be463fba1fe9 Partially-Implements: blueprint l2gw-service-integration Signed-off-by: Peng Liu <pliu@redhat.com>
2017-05-17TLS-everywhere: Configure CA for apacheJuan Antonio Osorio Robles1-0/+6
This tells apache which CA certificate was used to sign the certs it's using. this setting is useful in case we want to enable OCSP stapling or client authentication via TLS. Change-Id: I97a7e5332aea8377c7662ca98beb71ed5e236640
2017-05-17Only set apache certificates if TLS everywhere is enabledJuan Antonio Osorio Robles1-15/+18
The Apache certs were were being set even if TLS everywhere isn't enabled. This fixes that. Change-Id: If143d1fdeb0102a1c13441f89acaa73af24bf48f
2017-05-17TLS everywhere: configure mongodb's TLS settingsJuan Antonio Osorio Robles1-0/+37
This configures the mongodb server to use TLS in the internal network, while also passing the necessary attributes to generate the needed cert and key. bp tls-via-certmonger Depends-On: I85dda29bcad686372a74bd7f094bfd62777a3032 Change-Id: If6c603b074cfa7e122579cec29d034fd3312868d
2017-05-17Merge "Add params to manage and configure pipeline publisher"Jenkins1-2/+23
2017-05-16Merge "Optimize kernel neighbour table for large scale environments"Jenkins1-0/+29
2017-05-16Optimize kernel neighbour table for large scale environmentsOr Idgar1-0/+29
Changing the default values of neighbor table (also known as ARP table) in the kernel to avoid neighbour table overflow and thus fix communication errors between overcloud nodes. default kernel values support L2 network up to 1024 hosts (/22). The patch will allow up to 4096 hosts (/20). Change-Id: I5fabc766dd75a38cd3d835deee7e168f04dd30ce Closes-Bug: #1690087
2017-05-16Fix resource type in ObjectStorage roleChristian Schwede1-1/+1
The currently used resource type does not exist, therefore changing it. Closes-Bug: 1691021 Change-Id: Iaf18af546817e0cf6cdfafcc5c54ab4d1a0f819d
2017-05-15Add missing type for RoleParameters parameterMartin André1-0/+1
This was forgotten in I72376a803ec6b2ed93903cc0c95a6ffce718b6dc and broke containerized deployment. Change-Id: I599a87bf06efbfefd3067c77ed6ca866505900f9 Closes-Bug: #1690870
2017-05-15Merge "Update the services README documentation"Jenkins1-9/+23
2017-05-15Default snmp to less verbose loggingMichele Baldessari1-0/+5
Currently we just use what puppet-snmp provides in terms of defaults. This means that currently every single snmp query gets logged with the following: May 15 10:51:30 centos.localdomain snmpd[5159]: Connection from UDP: [127.0.0.1]:57799->[127.0.0.1]:161 May 15 10:51:30 centos.localdomain snmpd[5159]: Connection from UDP: [127.0.0.1]:57799->[127.0.0.1]:161 May 15 10:51:32 centos.localdomain snmpd[5159]: Connection from UDP: [127.0.0.1]:50566->[127.0.0.1]:161 The reason is that we use '-LS0-6d' as the default content for /etc/sysconfig/snmpd: https://github.com/razorsedge/puppet-snmp/blob/master/manifests/params.pp#L322 This default means that we are logging from 0 (LOG_EMERG) to 6 (LOG_INFO). The above messages bring nothing in a default installation and only spam the log files, so let's lower the upper log level to 5 (LOG_NOTICE) by default, so we properly do not see every single query in the logs. We add an option so the operator can still configure the desired log level via a Heat parameter. Change-Id: I8d3dfdb4d549cd27131346fc477755ad72313449
2017-05-15Merge "Change neutron-metadata number of workers determination method"Jenkins1-1/+8
2017-05-15Update the services README documentationSaravanan KR1-9/+23
Service template's parameter documentation has been update by correcting few of the wrong informations and added more information with examples. Change-Id: I2d92fd01cbeb6fdc6f030255dc4b71166509b4f6
2017-05-15Add role specific information to the service templateSaravanan KR178-44/+1694
When a service is enabled on multiple roles, the parameters for the service will be global. This change enables an option to provide role specific parameter to services and other templates. Two new parameters - RoleName and RoleParameters, are added to the service template. RoleName provides the role name of on which the current instance of the service is being applied on. RoleParameters provides the list of parameters which are configured specific to the role in the environment file, like below: parameters_default: # Default value for applied to all roles NovaReservedHostMemory: 2048 ComputeDpdkParameters: # Applied only to ComputeDpdk role NovaReservedHostMemory: 4096 In above sample, the cluster contains 2 roles - Compute, ComputeDpdk. The values of ComputeDpdkParameters will be passed on to the templates as RoleParameters while creating the stack for ComputeDpdk role. The parameter which supports role specific configuration, should find the parameter first in in the RoleParameters list, if not found, then the default (for all roles) should be used. Implements: blueprint tripleo-derive-parameters Change-Id: I72376a803ec6b2ed93903cc0c95a6ffce718b6dc