aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-04-02Merge "Set auth flag so ceilometer auth is enabled"Jenkins3-0/+15
2017-04-01Merge "Add special case upgrade from openvswitch 2.5.0-14"Jenkins3-4/+11
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 Kilambi3-0/+15
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-31Add special case upgrade from openvswitch 2.5.0-14marios3-4/+11
In [1] we removed the previously used special case upgrade code. However we have since discovered that for openvswitch 2.5.0-14 the special case is still required with an extra flag to prevent the restart. This adds the upgrade code back into the minor update and 'manual upgrade' scripts for compute/swift. The review at If998704b3c4199bbae8a1d068c31a71763f5c8a2 is adding this logic for the ansible upgrade steps. Related-Bug: 1669714 [1] https://review.openstack.org/#/q/59e5f9597eb37f69045e470eb457b878728477d7 Change-Id: I3e5899e2d831b89745b2f37e61ff69dbf83ff595
2017-03-31Merge "Add missing ec2api::api::keystone_ec2_tokens_url config"Jenkins1-0/+5
2017-03-30Merge "Re-Add bigswitch agent support"Jenkins5-1/+69
2017-03-30Merge "Output service_metadata_settings in docker services.yaml"Jenkins1-0/+2
2017-03-30Merge "Do not install openstack-heat-agents"Jenkins1-1/+0
2017-03-30Merge "[N->O] Fix wrong database connection for cell0 during upgrade."Jenkins2-1/+11
2017-03-30Merge "[N->O] is creating 2 default cell_v2 cells"Jenkins1-4/+4
2017-03-30Merge "Add NodeCreateBatchSize parameter"Jenkins1-0/+8
2017-03-30Don't check haproxy if external load-balancer is used.Sofer Athlan-Guyot1-1/+13
Change-Id: Ia65796b04be9f7cadc57af30ef66788dd8cb7de8 Closes-Bug: 1677539
2017-03-30Merge "Run cluster check on nodes configured in wsrep_cluster_address."Jenkins1-9/+13
2017-03-30Output service_metadata_settings in docker services.yamlJuan Antonio Osorio Robles1-0/+2
This output gets nova metadata into the servers this is deployed to and is necessary for the TLS-everywhere work. bp tls-via-certmonger-containers Change-Id: Iff54f7af9c63a529f88c6455047f6584d29154b4
2017-03-30Merge "Include panko in the default dispatcher"Jenkins2-1/+5
2017-03-30Merge "Allow to configure policy.json for OpenStack projects"Jenkins24-4/+160
2017-03-30Do not install openstack-heat-agentsSteve Baker1-1/+0
Installing openstack-heat-agents is unnecessary since it has the same effect as installing python-heat-agent-* which happens on the next line. Installing openstack-heat-agents is causing issues when mixing ocata and master repos, since there hasn't been a release on master since ocata was branched. Change-Id: I1a75e16810b6a89cf1dd9ff4f4b3b5dccfc0466e Closes-Bug: #1677278
2017-03-29Merge "Modify pci_passthrough hiera value as string"Jenkins2-2/+10
2017-03-28Allow to configure policy.json for OpenStack projectsEmilien Macchi24-4/+160
For both containers and classic deployments, allow to configure policy.json for all OpenStack APIs with new parameters (hash, empty by default). Example of new parameter: NovaApiPolicies. See environments/nova-api-policy.yaml for how the feature can be used. Note: use it with extreme caution. Partial-implement: blueprint modify-policy-json Change-Id: I1144f339da3836c3e8c8ae4e5567afc4d1a83e95
2017-03-28Include panko in the default dispatcherPradeep Kilambi2-1/+5
panko is enabled by default, we might as well make it the default dispatcher along with gnocchi. Closes-bug: #1676900 Change-Id: Icb6c98ed0810724e4445d78f3d34d8b71db826ae
2017-03-28Merge "Remove 'Controller' role references from overcloud.j2.yaml"Jenkins1-6/+6
2017-03-28Merge "N->O upgrade, blanks ipv6 rules before activating it."Jenkins1-0/+6
2017-03-28Merge "N->O Upgrade, make sure all nova placement parameter properly set."Jenkins1-3/+6
2017-03-28Merge "Stop openstack-nova-compute during nova-ironic upgrade"Jenkins1-0/+4
2017-03-28Merge "Only set EnableConfigPurge on major upgrades"Jenkins7-9/+13
2017-03-28Merge "Updated from global requirements"Jenkins2-2/+2
2017-03-28Merge "Swift auth url should use a suffix"Jenkins1-1/+1
2017-03-28Updated from global requirementsOpenStack Proposal Bot2-2/+2
Change-Id: I86fd68da7b2d96590f21a8511fa1a23dcf1a6dda
2017-03-28Merge "MySQL: Use conditional instead of nested stack for TLS-specific bits"Jenkins4-56/+26
2017-03-28Merge "Apache: Use conditional instead of nested stack for TLS-specific bits"Jenkins4-82/+39
2017-03-28Merge "Rabbitmq: Use conditional instead of nested stack for TLS-specific bits"Jenkins4-59/+27
2017-03-28Run cluster check on nodes configured in wsrep_cluster_address.Yurii Prokulevych1-9/+13
Attempt to check galera's cluster status fails when galera service is not running on the same node. Change-Id: I27fb0841d85cd0dc86e92ac2e21eedf5f8f863ab
2017-03-28Merge "Remove kolla_config copy from keystone service."Jenkins1-47/+3
2017-03-28Merge "Nic config mappings for deployed-server"Jenkins2-4/+11
2017-03-28Modify pci_passthrough hiera value as stringSaravanan KR2-2/+10
Hiera value of nova::compute::pci_passthrough should be a string. It has been modified to JSON with the heira hook changes. Modifying it again back to string. Closes-Bug: #1675036 Change-Id: I441907ff313ecc5b7b4da562c6be195687fc6c76
2017-03-28Merge "Restrict Access to Kernel Message Buffer"Jenkins2-0/+13
2017-03-27Add missing ec2api::api::keystone_ec2_tokens_url configSven Anderson1-0/+5
Change-Id: I9a19aff24dede2bea3bf2959afa7adde00817ee0 Related-Bug: #1676491
2017-03-27Merge "Sort ResourceGroup resource list"Jenkins1-1/+1
2017-03-27Remove 'Controller' role references from overcloud.j2.yamlDan Prince1-6/+6
This patch again removes hard coded role references to the overcloud.yaml template that was added in fd15a091f7ab6927833275df17b96ecacc2b1827. This breaks the composable undercloud work (undercloud-containers ci job as well). Change-Id: Ie30b2573dc4d2b45ebc0afc0e0d73bfdf41e4d4b Closes-bug: #1676528
2017-03-27Remove kolla_config copy from keystone service.Ian Main1-47/+3
Simplify the config of the keystone service by mounting in the configurations instead of specifying them all in kolla config. This is change is useful to limit the side effects of generating the config files and running the container is two separate steps as config directories are now bind-mounted inside the container instead of having files being copied to the container. We've seen examples of Apache's mod_ssl configuration file present on the container preventing it to start when puppet configured apache not to load the ssl module (in case TLS is disabled). Co-Authored-By: Martin André <m.andre@redhat.com> Change-Id: Ie33ffc7c2b1acf3e4e505d38efb104bf013f2ce6
2017-03-27Merge "Run nova-api hosts discovery after nova-compute start"Jenkins1-1/+2
2017-03-27Merge "docker/keystone: Bind mount entire fernet keys repository"Jenkins1-10/+5
2017-03-27Swift auth url should use a suffixPradeep Kilambi1-1/+1
gnocchi metricd and statsd are broken due to recent change to support keystone v3. see I2feed8b1219069128faa1a1e8dcd2ddfbae7e40a We need swift auth url to have suffix so it knows what endpoint to use. Change-Id: I753f37e121b95813e345f200ad3f3e75ec4bd7e1
2017-03-27Merge "Pick dynamically the first node for stack validation"Jenkins1-6/+18
2017-03-27MySQL: Use conditional instead of nested stack for TLS-specific bitsJuan Antonio Osorio Robles4-56/+26
Usually a nested stack is used that contains the TLS-everywhere bits (config_settings and metadata_settings). Nested stacks are very resource intensive. So, instead of doing using nested stacks, this patch changes that to use a conditional, and output the necessary config_settings and metadata_settings this way in an attempt to save resources. Change-Id: Ib7151d67982957369f7c139a3b01274a1a746c4a
2017-03-27Apache: Use conditional instead of nested stack for TLS-specific bitsJuan Antonio Osorio Robles4-82/+39
Usually a nested stack is used that contains the TLS-everywhere bits (config_settings and metadata_settings). Nested stacks are very resource intensive. So, instead of doing using nested stacks, this patch changes that to use a conditional, and output the necessary config_settings and metadata_settings this way in an attempt to save resources. Change-Id: Ia7ee632383542ac012c20448ff1b4435004e57e3
2017-03-27Rabbitmq: Use conditional instead of nested stack for TLS-specific bitsJuan Antonio Osorio Robles4-59/+27
Usually a nested stack is used that contains the TLS-everywhere bits (config_settings and metadata_settings). Nested stacks are very resource intensive. So, instead of doing using nested stacks, this patch changes that to use a conditional, and output the necessary config_settings and metadata_settings this way in an attempt to save resources. Change-Id: Ic25f84a81aefef91b3ab8db2bc864853ee82c8aa
2017-03-27N->O upgrade, blanks ipv6 rules before activating it.Sofer Athlan-Guyot1-0/+6
When the firewall is enabled with ipv6, the default rules set is taken as not ipv6 firewall was present for Newton. This make communication impossible until puppet is run again. This ensures that no rules are loaded when the firewall is enabled. This mimic this patch[1] [1] https://github.com/openstack/tripleo-heat-templates/commit/ae8aac36143d5dadb08af0d275f513678909dcc7 Change-Id: Id878b5caae666a799c89c8466ce46b9ecb86d9f7 Closes-Bug: #1675782
2017-03-27docker/keystone: Bind mount entire fernet keys repositoryJuan Antonio Osorio Robles1-10/+5
Previously only the first two intial fernet keys were mounted into the container. This is not practical, however, as doing key rotation will generate more entries in this repository. So instead we mount the whole directory, which would allow us to do rotation in the base host and seamlessly affect the container as well. Change-Id: I7763a09e57fe6a7867ffd079ab0b9222374c38c8