summaryrefslogtreecommitdiffstats
path: root/puppet
AgeCommit message (Collapse)AuthorFilesLines
2017-04-11Merge "Replace references to the 192.0.2 network"Jenkins2-3/+3
2017-04-10Merge "Remove yaql call when building logging_groups"Jenkins1-7/+4
2017-04-10Merge "sensu: fix upgrade case when service is added"Jenkins1-1/+1
2017-04-10Replace references to the 192.0.2 networkGiulio Fidente2-3/+3
Following change I1393d65ffb20b1396ff068def237418958ed3289 the ctlplane network will be 192.168.24 by default and not 192.0.2 anymore. This change removes old references left to 192.0.2 network from the overcloud templates. Change-Id: I1986721d339887741038b6cd050a46171a4d8022
2017-04-10Merge "Timeout early on pcs cluster status check0 during upgrade."Jenkins1-0/+2
2017-04-10Remove yaql call when building logging_groupsThomas Herve1-7/+4
yaql calls are fairly expensive. Let's try to not nest them when we can avoid it. Change-Id: I5e7dbc42be625bbfe7989867794a67ebae08687d
2017-04-07Merge "Update ceph-rgw acccepted roles to fix OSP upgrade"Jenkins1-1/+1
2017-04-07sensu: fix upgrade case when service is addedEmilien Macchi1-1/+1
When service is added during an upgrade, fix the ansible syntax to use the right variable for return code. Change-Id: I974699fb8b0dcbe5ffa6935c394df4ac8e7b21d4
2017-04-07Timeout early on pcs cluster status check0 during upgrade.Sofer Athlan-Guyot1-0/+2
There is a windows for the pcs cluster status to hang forever[1]. We add a timeout during check0 to avoid this situation. 2 minutes should be more than enought to get all the pcsd nodes to reply. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1292858 Closes-Bug: #1680477 Change-Id: Icb3dc76e031a3d4f26294f37d169f2f61d30973e
2017-04-07Merge "Add password to authtoken section in congress.conf"Jenkins1-0/+1
2017-04-07Merge "Add support for "neutron" Ironic networking plugin"Jenkins1-0/+21
2017-04-07Merge "ovn: Add missing configurations required"Jenkins2-0/+7
2017-04-07Add password to authtoken section in congress.confTomofumi Hayashi1-0/+1
Current puppet module miss password section hence congress is not available due to missing password in congress.conf. This fix is to add password. Change-Id: I277c03ca93130a0337d5085f09c375fb0ac9331d Signed-off-by: Tomofumi Hayashi <s1061123@gmail.com>
2017-04-07Merge "Fix conntrack proto sctp module"Jenkins1-1/+1
2017-04-06Merge "Adds Horizon secure cookie map."Jenkins1-0/+5
2017-04-06Merge "Add trigger to setup a LDAP backend as keystone domaine"Jenkins1-0/+27
2017-04-06Merge "Adds service for managing securetty"Jenkins1-0/+36
2017-04-06Fix conntrack proto sctp moduleAlex Schultz1-1/+1
ip_conntrack_proto_sctp is the old name for the module and it is now nf_conntrack_proto_sctp. In order for the kmod module to not keep trying to modprobe the module, we need to use the correct name. Change-Id: Ieaed235e71e9e6e41a46d9be0e02beb8f4341b1a Closes-Bug: #1680579
2017-04-06Merge "Disable ceilometer API"Jenkins1-1/+1
2017-04-06Adds service for managing securettylhinds1-0/+36
This adds the ability to manage the securetty file. By allowing management of securetty, operators can limit root console access and improve security through hardening. Change-Id: I0767c9529b40a721ebce1eadc2dea263e0a5d4d7 Partial-Bug: #1665042 Depends-On: Ic4647fb823bd112648c5b8d102913baa8b4dac1c
2017-04-06Merge "Add manual ovs upgrade script for workaround ovs upgrade issue"Jenkins4-26/+100
2017-04-06Merge "Enforce upgrade_batch_tasks before upgrade_tasks order"Jenkins1-19/+12
2017-04-06Merge "add configurable timeouts for DB sync"Jenkins2-0/+11
2017-04-06Merge "Add network sysctl tweaks for security"Jenkins1-0/+18
2017-04-06Merge "Ensure upgrade step orchestration accross roles."Jenkins1-8/+6
2017-04-06ovn: Add missing configurations requiredNuman Siddique2-0/+7
This patch adds - setting nova config param 'force_config_meta' to True as metadata service is not supported by OVN yet. - Add the necessary iptables rules to allow ovsdb-server traffic for Northbound and Southboud databases. - Update the release notes for OVN. Change-Id: If1a2d07d66e493781b74aab2fc9b76a6d58f3842 Closes-bug: #1670562
2017-04-06Add trigger to setup a LDAP backend as keystone domaineCyril Lopez1-0/+27
It is using a trigger tripleo::profile::base::keystone::ldap_backend_enable in puppet-tripleo who will call a define in puppet-keysone ldap_backend.pp. Given the following environment: parameter_defaults: KeystoneLDAPDomainEnable: true KeystoneLDAPBackendConfigs: tripleoldap: url: ldap://192.0.2.250 user: cn=openstack,ou=Users,dc=redhat,dc=example,dc=com password: Secrete suffix: dc=redhat,dc=example,dc=com user_tree_dn: ou=Users,dc=redhat,dc=example,dc=com user_filter: "(memberOf=cn=OSuser,ou=Groups,dc=redhat,dc=example,dc=com)" user_objectclass: person user_id_attribute: cn user_allow_create: false user_allow_update: false user_allow_delete: false ControllerExtraConfig: nova::keystone::authtoken::auth_version: v3 cinder::keystone::authtoken::auth_version: v3 It would then create a domain called tripleoldap with an LDAP configuration as defined by the hash. The parameters from the hash are defined by the keystone::ldap_backend resource in puppet-keystone. More backends can be added as more entries to that hash. This also enables multi-domain support for horizon. Closes-Bug: 1677603 Co-Authored-By: Juan Antonio Osorio Robles <jaosorior@redhat.com> Depends-On: I1593c6a33ed1a0ea51feda9dfb6e1690eaeac5db Change-Id: I6c815e4596d595bfa2a018127beaf21249a10643 Signed-off-by: Cyril Lopez <cylopez@redhat.com>
2017-04-06Merge "Add parameters for internal TLS for swift proxy"Jenkins1-2/+31
2017-04-05add configurable timeouts for DB syncMike Bayer2-0/+11
This patch integrates with the db_sync_timeout parameter recently added to puppet-nova and puppet-neutron in I6b30a4d9e3ca25d9a473e4eb614a8769fa4567e7, which allow for the full db_sync install to have more time than just Pupppet's default of 300 seconds. Ultimately, similar timeouts can be added for all other projects that feature db sync phases, however Nova and Neutron are currently the ones that are known to time out in some environments. Closes-bug: #1661100 Change-Id: Ic47439a0a774e3d74e844d43b58956da8d1887da
2017-04-05Merge "Add l2gw neutron service plugin support"Jenkins1-0/+54
2017-04-05Merge "Addition of firewall rules for Nuage"Jenkins2-6/+11
2017-04-05Merge "Disable core dump for setuid programs"Jenkins1-0/+2
2017-04-05Add parameters for internal TLS for swift proxyJuan Antonio Osorio Robles1-2/+31
This adds the necessary parameter for swift proxy to be terminiated internally by a TLS proxy. bp tls-via-certmonger Change-Id: I3cb9d53d75f982068f1025729c1793efaee87380 Depends-On: I6e7193cc5b4bb7e56cc89e0a293c91b0d391c68e
2017-04-05Merge "Add params to tweak memory limit on mongodb"Jenkins1-0/+5
2017-04-04Enforce upgrade_batch_tasks before upgrade_tasks ordermarios1-19/+12
If we really want upgrade_batch_tasks before the upgrade_tasks as described in the README then we should enforce the ordering Noticed this working on bug 1671504 upgrade tasks were being executed before batch upgrade tasks. Closes-Bug: 1678101 Change-Id: Iaa1bce960a37c072b5f8441132705a6bb6eb6ede
2017-04-04Ensure upgrade step orchestration accross roles.Sofer Athlan-Guyot1-8/+6
Currently we don't enforce step ordering across role, only within role. With custom role, we can reach a step5 on one role while the cluster is still at step3, breaking the contract announced in the README[1] where each step has a guarantied cluster state. We have to remove the conditional here as well as jinja has no way to access this information, but we need jinja to iterate over all enabled role to create the orchestration. This deals only with Upgrade tasks, there is another review to deal with UpgradeBatch tasks. [1] https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst Closes-Bug: #1679486 Change-Id: Ibc6b64424cde56419fe82f984d3cc3620f7eb028
2017-04-04Merge "Add ceilometer ipmi agent"Jenkins1-0/+77
2017-04-03Add params to tweak memory limit on mongodbPradeep Kilambi1-0/+5
The puppet-tripleo change was added in Ie9391aa39532507c5de8dd668a70d5b66e17c891. Closes-bug: #1656558 Change-Id: Ibe2e4be5b5dc953d8d4b14f680a460409db95585
2017-04-03Add support for "neutron" Ironic networking pluginDmitry Tantsur1-0/+21
This enabled a lot of advanced networking features (see the release note). Related to blueprint ironic-driver-composition Change-Id: I20ea994fec36d73e618107b5c3594ec1c0f8cb93 Depends-On: I72eb8b06cca14073d1d1c82462fb702630e02de3
2017-04-03Addition of firewall rules for Nuagelokesh-jain2-6/+11
Added VxLAN and metadata agent firewall rules to neutron-compute-plugin for Nuage. Removed a deprecated parameter 'OSControllerIp' as well. Change-Id: If10c300db48c66b9ebeaf74b5f5fee9132e75366
2017-04-03Merge "Qpid dispatch router composable role"Jenkins1-0/+60
2017-04-03Disable ceilometer APIPradeep Kilambi1-1/+1
Ceilometer API has been deprecated since Ocata. lets disable it by default and add an env file to enable it if needed. Closes-bug: #1676968 Change-Id: I571f5467466c29271e0235e8fde6bdae07c20daf
2017-04-03Merge "Change heat and mistral to use v3/ec2tokens url"Jenkins2-2/+10
2017-04-03Merge "Fixes port binding controller for OpenDaylight"Jenkins1-0/+45
2017-04-02Merge "Setting keystone region for tacker"Jenkins1-0/+1
2017-04-02Merge "Set auth flag so ceilometer auth is enabled"Jenkins1-0/+7
2017-03-31Merge "Don't check haproxy if external load-balancer is used."Jenkins1-1/+13
2017-03-31Set auth flag so ceilometer auth is enabledPradeep Kilambi1-0/+7
Ceilometer Auth should be enabled even if ceilometer api is not. Lets decouple these, this flag will be used in puppet-tripleo where ceilometer::keystone::auth class is initialized. Change-Id: Iffebd40752eafb1d30b5962da8b5624fb9df7d48 Closes-bug: #1677354
2017-03-31Update ceph-rgw acccepted roles to fix OSP upgradeKeith Schincke1-1/+1
This patch updates ceph::keystone::auth::roles to remove "member" and add "Member". The previous entry breaks OSP N to O upgrades when ceph-rgw is enabled. This patch fixes: https://bugs.launchpad.net/tripleo/+bug/1678126 Closes-bug: 1678126 Change-Id: I2e442eda98e2e083d6f4193fb38a0484919a6d33
2017-03-31Add manual ovs upgrade script for workaround ovs upgrade issueMathieu Bultel4-26/+100
When we upgrade OVS from 2.5 to 2.6, the postrun package update restart the services and drop the connectivity We need to push this manual upgrade script and executed to the nodes for newton to ocata The special case is needed for 2.5.0-14 specifically see related bug for more info (or, older where the postun tries restart). See related review at [1] for the minor update/manual upgrade. Related-Bug: 1669714 Depends-On: I3227189691df85f265cf84bd4115d8d4c9f979f3 Co-Authored-By: Sofer Athlan-Guyot <sathlang@redhat.com> [1] https://review.openstack.org/#/c/450607/ Change-Id: If998704b3c4199bbae8a1d068c31a71763f5c8a2