summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-02-17Merge "xinetd: bind only on mysql network"Jenkins1-0/+1
2017-02-16Update reno for stable/ocataOpenStack Release Bot2-0/+7
Change-Id: I2e67879bb790d4e2d11ed39cdde0fb402453ecda
2017-02-16Merge "Fix a typo in mysql.pp"Jenkins1-1/+1
2017-02-16Merge "tuning: manage keystone resources only at step3"Jenkins3-15/+7
2017-02-15Add missing release notes for Ocata RC1Emilien Macchi1-0/+64
Change-Id: I95f7b57a6cb0811af324996bd00580732503ed28
2017-02-15Merge "Make quotes consistent to match the sample config"Jenkins2-21/+35
2017-02-14tuning: manage keystone resources only at step3Emilien Macchi3-15/+7
1. Manage Keystone resources only at step 3. Don't verify them at step 4 and 5, it's a huge loss of time. 2. Don't require Keystone resources for Gnocchi services, they are already ready at Step 5. Related-Bug: #1664418 Change-Id: I9879718a1a86b862e5eb97e6f938533c96c9f5c8
2017-02-14Make quotes consistent to match the sample configMikeG4512-21/+35
Per project conventions, should use single quotes. Also, update comments and defaults to match sample. Change-Id: I82ddcec230e7a03965d753db60968912b8d7da5c Closes-Bug: #1663624
2017-02-14Merge "Add ::ironic::config to Ironic base profile"Jenkins1-0/+1
2017-02-13Merge "nova: move placement credentials config at step 3"Jenkins2-1/+5
2017-02-13nova: move placement credentials config at step 3Emilien Macchi2-1/+5
nova placement credentials in nova.conf need to be configured at step 3 so Nova services can use them as soon as they start. Change-Id: I0abdd305b7e6c8d83f23e25b3872e98eb56dd299
2017-02-13Uncomment internal TLS options for placement APIJuan Antonio Osorio Robles1-1/+1
Placement API is still running over wsgi which can run with TLS on the internal network; These options were commented from haproxy and doing this breaks the TLS-everywhere setup. Change-Id: I1194f1f487cdcf45541c0d139806aa3dc4456d6e
2017-02-12Merge "Add support to changing the Rabbitmq password on update"Jenkins2-0/+30
2017-02-11Merge "nova/api: more cleanup"Jenkins2-27/+53
2017-02-10Merge "Add module to support ScaleIO backend in Cinder"Jenkins3-0/+127
2017-02-10Merge "Rebranding of Eqlx to Dell EMC PS Series"Jenkins4-28/+28
2017-02-10Merge "Run nova-cell_v2-discover_hosts at step 5"Jenkins6-7/+14
2017-02-10nova/api: more cleanupEmilien Macchi2-27/+53
- transform nova_api_wsgi_enabled in a parameter - update rspec tests - fix TLS to run at step 1 Change-Id: I4d3f9c92f0717ae8c3bc8d71065fab281de82008
2017-02-09Run nova-cell_v2-discover_hosts at step 5Emilien Macchi6-7/+14
We need to run nova-cell_v2-discover_hosts at the very end of the deployment because nova database needs to be aware of all registred compute hosts. 1. Move keystone resources management at step 3. 2. Move nova-compute service at step 4. 3. Move nova-placement-api at step 3. 5. Run nova-cell_v2-discover_hosts at step 5 on one nova-api node. 6. Run neutron-ovs-agent at step 5 to avoid racy deployments where it starts before neutron-server when doing HA deployments. With that change, we expect Nova aware of all compute services deployed in TripleO during an initial deployment. Depends-On: If943157b2b4afeb640919e77ef0214518e13ee15 Change-Id: I6f2df2a83a248fb5dc21c2bd56029eb45b66ceae Related-Bug: #1663273 Related-Bug: #1663458
2017-02-09Merge "nova: disable API in WSGI by default"Jenkins1-1/+3
2017-02-09Add module to support ScaleIO backend in CinderGiulio Fidente3-0/+127
Also adds an initial spec file for basic testing of the module. Change-Id: I5534aab53b70de215336a076d25263c73b8d7b5b Partial-Bug: #1661316
2017-02-09Rebranding of Eqlx to Dell EMC PS Seriesrajinir4-28/+28
This changes rebrands Dell Eqlx to Dell PS series and matches the tripleo-heat-templates. Change-Id: I3536147a06b426ace18cf415e99361c47b4cf5d9
2017-02-09start nova-compute when keystone resources are createdEmilien Macchi3-8/+9
1. Move keystone resources management at step 4. 2. Move nova-compute startup at step 5. That way, we make sure nova-compute will start when all Keystone resources are ready. Change-Id: I6e153e11b8519254d2a67b9142bf774a25bce69d Closes-Bug: #1663273
2017-02-09nova: disable API in WSGI by defaultEmilien Macchi1-1/+3
Cleanup patch once the THT patch is merged. Change-Id: Iba439a4758a4728197d7620b764a4f0f2648ee0f Depends-On: I09b73476762593642a0e011f83f0233de68f2c33
2017-02-08Disable midonet unit testsEmilien Macchi2-63/+1
'https://github.com/midonet/puppet-midonet' doesn't exist anymore, we need to migrate to 'https://github.com/openstack/puppet-midonet' but tests will fail. We need to work with Midokura to get them fixed. In the meantime, let's disable it. Change-Id: Id39bc5a8cd229df3e9b597a0a0f3eada838f4953
2017-02-07Merge "Proxy API endpoints that UI uses"Jenkins5-64/+160
2017-02-06Merge "nova/libvirt: switch vnc server binding"Jenkins2-12/+8
2017-02-06nova/libvirt: switch vnc server bindingEmilien Macchi2-12/+8
On compute nodes, instead of binding vnc server on 0.0.0.0, use the IP address provided by libvirt's t-h-t profile (hiera). Co-Authored-By: Juan Antonio Osorio Robles <jaosorior@redhat.com> Depends-On: Ie377c09734e9f6170daa519aed69c53fc67c366b Change-Id: If6b116b238a52144aad5e76c9edc7df6aa15313c Closes-Bug: #1660099
2017-02-06Stop deploying Nova API in WSGI with ApacheEmilien Macchi3-24/+25
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. Related-Bug: 1661360 Co-Authored-By: Juan Antonio Osorio Robles <jaosorior@redhat.com> Change-Id: Ia87b5bdea79e500ed41c30beb9aa9d6be302e3ac
2017-02-06Merge "Revert "Revert "set innodb_file_per_table to ON for MySQL / Galera"""Jenkins3-7/+29
2017-02-04Add ::ironic::config to Ironic base profileDan Prince1-0/+1
I have ExtraConfig settings that need to be set in ironic.conf. Adding the ::ironic::config module to our base Ironic profile should allow users to customize Ironic if needed. Change-Id: I93e9b3b5d4def1d8fa42b77b611b7d9d6cb7963b
2017-02-03Proxy API endpoints that UI usesDan Trainor5-64/+160
Add support to enable the UI to use paths via mod_proxy to access API endpoints instead of connecting to each endpoint directly on a port other than where the UI is served from. This is necessary to prevent certificate acceptance errors from non-Chrome browsers which take exception to connections made to other ports on the same hostname, using one SSL certificate. This change extends the UI's Apache configuration to create one mod_proxy location for each of the API endpoints that UI calls upon. These mod_proxy (using ProxyPass, ProxyPassReverse) endpoints are configured using new heira variables provided in the dependent commit. Additionally, this change modifies the default UI configuration file to include endpoint URLs formatted to use the new endpoint paths that are created. Removed puppet variables which were previously used to generate the contents of the tripleo_ui_config.js template, since they are no longer used to generate this file, replaced with the new endpoint URLs formatted to use the new endpoint paths that are created. Change-Id: I55e375ad462fa98e181277ec0bd88658e620e8ad Implements: blueprint proxy-undercloud-api-services Depends-On: Ib20f4b0891563ae90ec80675635a64c39bd2fdb7
2017-02-03Revert "Revert "set innodb_file_per_table to ON for MySQL / Galera""Alex Schultz3-7/+29
This reverts commit 3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e. After identifying how to workaround the performance issues on the undercloud, let's put this back in. Enabling innodb_file_per_table is important for operators to be able to better manage their databases. Change-Id: I435de381a0f0e3ef221e498f442335cdce3fb818 Depends-On: I77507c638237072e38d9888aff3da884aeff0b59 Closes-Bug: #1660722
2017-02-03Add support to changing the Rabbitmq password on updateSaravanan KR2-0/+30
Rabbitmq Password is set on the fresh deployment, but during update, if the password is changed, it is modified in all config files including rabbitmq config. But the rabbitmq connection fails because the new password is not successful applied to rabbitmq. Setting the rabbitmq_user will invoke 'rabbitmqctl change_password'. Scenario: The password change is applied on Step1 when configuring Rabbitmq. Other services may be updated on different Steps. Till other services config is updated with new rabbitmq password, and restarted, the connections will get Access Denied response. It has cyclic dependency. So the passwords will be changes at Step1 and once all services are updated, the connections will work as is. Partial-Bug: #1611704 Change-Id: I44865af3d5eb2d37eb648ac7227277e86c8fbc54
2017-02-03Merge "Use transport_url for rabbitmq connection parameters in heat"Jenkins1-12/+43
2017-02-03Merge "Add initial profiles for rest of Octavia services"Jenkins4-0/+105
2017-02-03Merge "add cache to object-expirer pipeline"Jenkins1-0/+1
2017-02-03Merge "Delete the unnecessary word in numvfs_persistence.pp"Jenkins1-1/+1
2017-02-03Merge "Fix style nits in contrail manifests"Jenkins4-85/+47
2017-02-02Revert "set innodb_file_per_table to ON for MySQL / Galera"Alex Schultz3-29/+7
This reverts commit 621ea892a299d2029348db2b56fea1338bd41c48. We're getting performance problems on SATA disks. Change-Id: I30312fd5ca3405694d57e6a4ff98b490de388b92 Closes-Bug: #1661396 Related-Bug: #1660722
2017-02-02Prepare 6.2.0 releaseEmilien Macchi2-3/+3
6.2.0 will be Ocata RC1. Change-Id: Ie26ab89ea9c90f6c5d01697459855fd8c32b075f
2017-02-02Merge "set innodb_file_per_table to ON for MySQL / Galera"Jenkins3-7/+29
2017-02-01set innodb_file_per_table to ON for MySQL / GaleraMike Bayer3-7/+29
InnoDB uses a single file by default which can grow to be tens/hundreds of gigabytes, and is not shrinkable even if data is deleted from the database. Best practices are that innodb_file_per_table is set to ON which instead stores each database table in its own file, each of which is also shrinkable by the InnoDB engine. Closes-Bug: #1660722 Change-Id: I59ee53f6462a2eeddad72b1d75c77a69322d5de4
2017-02-01Fix style nits in contrail manifestsCarlos Camacho4-85/+47
There are some style nits in the recently merged contrail puppet manifests. Change-Id: Ice5935105e0323cb55e0d018190e6471ade7324a
2017-02-01Use transport_url for swift-proxy instead of rabbitmq paramsJuan Antonio Osorio Robles1-25/+52
These parameters are being deprecated, so we should be using the transport_url format instead. Change-Id: I8b7457b6233c4f88af2d7bc1b9304fcccb6edf61
2017-01-31Merge "Re-organizes Contrail services to the correct roles"Jenkins11-318/+1857
2017-01-31Fix test failure caused by change to puppet-octaviaBrent Eagles1-0/+3
Fixes a test failure caused by Ic38d4f9f9a8e69ffcee6ccc4bba9a9ab0f161d0e which pulls in a class with a required parameter. Change-Id: I0740290bff0ea7c4af6e3420775ac3e72871d372
2017-01-27Merge "Fix MySQL service name parameter"Jenkins1-3/+3
2017-01-27Merge "Add a default rule for dhcpv6 traffic"Jenkins1-0/+6
2017-01-27Merge "Clean TLS proxy-related setup for neutron-server profile"Jenkins2-16/+21