summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-02-09Merge "Create linux bridge vlans environments"Jenkins7-0/+649
2016-02-04Merge "Allow the deployer to pick a predefined IP for VIPs"Jenkins1-0/+21
2016-02-04Merge "neutron: delete by default router/dhcp namespaces"Jenkins1-0/+2
2016-01-28Allow the deployer to pick a predefined IP for VIPsGiulio Fidente1-0/+21
Adds three top-level params to allow the deployer pick a predefined IP for the InternalApi, Storage and StorageMgmt VIPs. We had this already for the External network (PublicVirtualFixedIPs) and the ctlplane network (ControlFixedIPs). Change-Id: I1509e1888774ffa72445ed681dd8107eec703d64
2016-01-27Merge "Remove empty value for wsrep_notify_cmd"Jenkins1-1/+0
2016-01-26Merge "Removing Sahara password default"Jenkins1-2/+0
2016-01-25Merge "Allow container template to recognize an update"Jenkins1-6/+0
2016-01-25Remove empty value for wsrep_notify_cmdJohn Trowbridge1-1/+0
This was being silently ignored by the mysql puppet module prior to this commit.[1] However, now that empty values are allowed, the overcloud deploy fails because the option --wsrep_notify_cmd requires an argument. This is not currently failing on master because we are pinned to an old puppet-mysql. We will need to remove that pin in order to get on a newer delorean repo though. Also, this is breaking stable/liberty HA job because we use the packaged OPM there. [1] https://github.com/puppetlabs/puppetlabs-mysql/commit/e30e0bc958761890ea4f06cdd3f1fc7242a00fe2 Change-Id: I9e07efe1650831e81e9a783428554578874aa765 Closes-Bug: 1537720
2016-01-23Merge "puppet: allow config of ad-hoc Neutron settings"Jenkins3-0/+3
2016-01-23Merge "puppet: allow config of ad-hoc Cinder settings"Jenkins2-0/+2
2016-01-22neutron: delete by default router/dhcp namespacesEmilien Macchi1-0/+2
The 'router_delete_namespaces' (L3 agent) and 'dhcp_delete_namespaces' (DHCP agent) configuration settings default to false OpenStack Neutron resulting in network namespaces not being deleted when no longer needed. Disabling automatic namespace cleanup was appropriate for older Linux distributions but is no longer required. TripleO should set the values to true. Change-Id: I39e1a347d24ecc99b6f878807c47103c4b3f85e1
2016-01-22Merge "puppet: allow config of ad-hoc Heat settings"Jenkins2-0/+2
2016-01-22Merge "puppet: allow config of ad-hoc Glance settings"Jenkins2-0/+2
2016-01-22Merge "puppet: allow config of ad-hoc Ceph settings"Jenkins4-0/+8
2016-01-22puppet: allow config of ad-hoc Neutron settingsDan Prince3-0/+3
Including ::neutron::config on the controller and compute roles will allow ad-hoc (non-puppet managed) settings to be made in all the various neutron config files using Hiera. Change-Id: Ifadc77cdcb60b7075d091d778cb92b0dd75bd949
2016-01-22puppet: allow config of ad-hoc Cinder settingsDan Prince2-0/+2
Including ::cinder::config on controller, and volume roles will allow ad-hoc (non-puppet managed) settings to be made in the cinder.conf using Hiera. Change-Id: I519aff02e3cfb7fbf57e89c7a139564df42f8967
2016-01-22puppet: allow config of ad-hoc Heat settingsDan Prince2-0/+2
Including ::heat::config on the controller roles will allow ad-hoc (non-puppet managed) settings to be made in the heat config file using Hiera. Change-Id: I80a39b798869ac330ea8a4d01699f5db47c93d47
2016-01-22puppet: allow config of ad-hoc Glance settingsDan Prince2-0/+2
Including ::glance::config on glance roles will allow ad-hoc (non-puppet managed) settings to be made in the glance config files using Hiera. Change-Id: I7c86ae0e8f1a0a2b46d526598964454cb80319a6
2016-01-22puppet: allow config of ad-hoc Ceph settingsDan Prince4-0/+8
Including ::ceph::conf on ceph roles will allow ad-hoc (non-puppet managed) settings to be made in the ceph.conf using Hiera. Change-Id: I656a0ecde465023d7afad9371aa3c5c270078a67
2016-01-22Merge "Update VNI and TunnelID ranges."Jenkins3-6/+6
2016-01-21Removing Sahara password defaultEthan Gafford1-2/+0
In prior commit, added default for Sahara password in order to avoid circular dependency. Removing this default now in order to force password per other service definitions. Change-Id: I91f98039e520804b25aaededefa25e80992ba6b5 Partially-implements: bp sahara-integration
2016-01-21Merge "Add update yaml backward compatibe with PublicVirtualIP on ctlplane"Jenkins2-0/+5
2016-01-21Merge "Don't write CLOUDNAME to the hosts file."Jenkins2-7/+1
2016-01-21Merge "Rename validate tox env to linters"Jenkins1-2/+2
2016-01-21Merge "Let Puppet update all packages on non-controllers"Jenkins1-8/+5
2016-01-20Rename validate tox env to lintersBen Nemec1-2/+2
This is the new blessed naming scheme for lint-type jobs such as pep8 or the yaml validation job we have in this project. Doing this rename will allow us to use standard infra job templates to run validation on proposed changes. Change-Id: I0a4c4372429a08e0babb4d323f2b027f1d95f3d7
2016-01-20Don't write CLOUDNAME to the hosts file.Ben Nemec2-7/+1
Currently the value of the CloudName param gets written into the /etc/hosts file on each controller, but it turns out this is an invalid configuration. CloudName is supposed to be the DNS name of the overcloud, and the IP being written is (at least in my case) the internal API VIP. This breaks in cases such as SSL because the services are not listening on an SSL port on the internal API network, so if a service tries to talk to another service using a CloudName-defined public endpoint it ends up pointed at a non-existent internal address:port. Since by definition CloudName is supposed to be resolvable by the configured DNS server, we should not need an explicit hosts entry as well. Thus, this patch removes that from the file. Change-Id: I919b42a219d95296f46852dd3266a54d968cf66b
2016-01-20Create linux bridge vlans environmentsJaume Devesa7-0/+649
Define environments to create VLANs attached to a single physical nic as 'single-nic-vlans' does, but using linux_bridge instead of ovs_bridge Change-Id: I8c6fe9ec7028178f783e7d9c0a1cc67a1517eb3d
2016-01-20Allow container template to recognize an updateRyan Hallisey1-6/+0
The deployment resource looks for a change in name when running an update. If there is no change in containers, docker will recognize that and the deployment will return. If there is a new available container, docker will swap out the old running container for a new one. Change-Id: I60d45b5ef45714e6e0140dfc80c14d6a12701f32
2016-01-19Merge "Fix tunnel_types hieradata on compute nodes"Jenkins1-1/+1
2016-01-19Merge "Fix neutron-nova notifications"Jenkins1-1/+2
2016-01-18Fix tunnel_types hieradata on compute nodesBen Nemec1-1/+1
There was a missing : in the hieradata for the compute nodes that caused tunnel_types to not be configured. This also made it impossible to boot instances on tunneled networks because the port binding always failed. Change-Id: Icc2a45aa9514ce62497f91e6abe9261d1c1374ed Partial-Bug: 1534349
2016-01-18Fix neutron-nova notificationsBen Nemec1-1/+2
In our neutron.conf we configure both keystone v2 and v3 options, which confuses the keystoneclient code responsible for deciding which to use. For whatever reason, having it talk to the unversioned keystone endpoint and letting the client decide which version that way makes it happy. Except that we write a wrong value for project_name, which makes it unhappy again. This change fixes both of those issues, which allows notifications to work again. Change-Id: Ic3a329354d0ed071363183b5e06c0a42d2dd84ad Closes-Bug: 1519525
2016-01-18Merge "Set the name property for all deployment resources"Jenkins25-0/+76
2016-01-17Let Puppet update all packages on non-controllersJames Slagle1-8/+5
With I02f7cf07792765359f19fdf357024d9e48690e42[1] in puppet-tripleo, puppet is capable of updating all packages itself on non controller nodes now. This is a safer mechanism than using the exclude logic in yum_update.sh since that can cause depdency problems across sub packages. [1] https://review.openstack.org/#/c/261041/ Closes-Bug: 1534785 Change-Id: I9075a1bb85baa65a9d0afc5d0fd31a1f99a98819
2016-01-14Enable keystone handling of X-Forwarded-Proto headerJuan Antonio Osorio Robles3-6/+9
If the X-Forwarded-Proto header is received by keystone, this option will make the service properly handle it. This is useful, for instance, if TLS is enabled for the admin endpoint. Change-Id: I31a1f51591e8423367e61eafc3af9b2d61278468
2016-01-13Merge "Use pymysql database driver for OpenStack DBs"Jenkins2-8/+8
2016-01-12Merge "Sahara Integration"Jenkins9-0/+152
2016-01-11Use pymysql database driver for OpenStack DBsEmilien Macchi2-8/+8
PyMySQL is a new driver introduced in Liberty. This patch change the MySQL url to use mysql+pymysql like recommanded. Change-Id: I28e14acacba865241a0cc388a879a003181a85f3 Depends-On: I7604cca9e2d7bf0b93c820adec5f937f72b64fa8 Closes-Bug: #1499298
2016-01-08Sahara IntegrationEthan Gafford9-0/+152
Integration of OpenStack data processing service (sahara) with TripleO. - Deploys sahara in distributed mode (separate api and engine processes on each controller node) - Load balancing w/haproxy - RabbitMQ/MySQL supported per current TripleO standard - Minimal configurability at this time Change-Id: I77a6a69ed5691e3b1ba34e9ebb4d88c80019642c Partially-implements: blueprint sahara-integration Depends-On: I0f0a1dc2eaa57d8226bad8cfb250110296ab9614 Depends-On: Ib84cc59667616ec94e7edce2715cbd7dd944f4ae Depends-On: I9fe321fd4284f7bfd55bd2e69dcfe623ed6f8a2a
2016-01-08Switch for Keystone DB cron jobMartin Mágr4-2/+16
- Adds parameter to enable switching off token flush cron job. - Sets destination for deleted rows to /dev/null Change-Id: I9e8aed969e81595d8a1d0a5300da17da6ba15c03 Partial-bug: rhbz#1249106 Depends-On: I5e51562338f68b4ba1b2e942907e6f6a0ab7a61e
2016-01-08Merge "Add ExtraConfig to cinder storage role"Jenkins1-0/+8
2016-01-08Merge "Fix yaml validation errors in multiple-nics templates"Jenkins4-4/+4
2016-01-07Merge "updating enable_ceph conditions for controller"Jenkins3-4/+5
2016-01-07Merge "Adding ManagementIpSubnet to linux bridge net conf"Jenkins1-0/+4
2016-01-07Merge "Use new heat-docker-agents images"Jenkins1-1/+1
2016-01-07Merge "Remove deleted Cinder rows"Jenkins4-5/+21
2016-01-07Merge "Add TimeZone parameter for all node types"Jenkins12-0/+51
2016-01-07Merge "Enable configuration of Neutron QoS"Jenkins3-3/+49
2016-01-06Enable configuration of Neutron QoSBrent Eagles3-3/+49
This change adds support for setting the configuration options required to enable the quality of service feature in Neutron. The default values will enable the feature. Closes-Bug: #1524052 Depends-On: Iefc289a6eee13b9c66f8131c258af982f232df4b Change-Id: I1abf7d37d39e6927e482b56de4ee3d3d7c313a1c