Bug 1631009 - Customers cannot configure additional settings on the undercloud if the config is not exposed
Summary: Customers cannot configure additional settings on the undercloud if the confi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z3
: 13.0 (Queens)
Assignee: Alex Schultz
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks: 1734551
TreeView+ depends on / blocked
 
Reported: 2018-09-19 17:10 UTC by Andreas Karis
Modified: 2021-12-10 17:43 UTC (History)
3 users (show)

Fixed In Version: instack-undercloud-8.4.3-5.el7ost
Doc Type: Enhancement
Doc Text:
In prior versions, undercloud hieradata overrides could be used to tune some service configurations using the <service>::config options similar to the overcloud. However, this functionality was not available for all deployed OpenStack services. With this version, any configuration values not currently available can be updated via the <service>::config hieradata.
Clone Of:
: 1631012 1734551 (view as bug list)
Environment:
Last Closed: 2018-11-13 22:28:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1793361 0 None None None 2018-09-19 18:02:09 UTC
OpenStack gerrit 604800 0 None MERGED Include missing config classes 2020-08-27 09:42:58 UTC
Red Hat Issue Tracker OSP-11651 0 None None None 2021-12-10 17:43:34 UTC
Red Hat Product Errata RHBA-2018:3587 0 None None None 2018-11-13 22:29:51 UTC

Description Andreas Karis 2018-09-19 17:10:16 UTC
Description of problem:
Requesting the following feature enhancement: custom configuration for the undercloud

The undercloud allows us to push custom hierdata to make configuration
persistent:
~~~
undercloud.conf:
hieradata_override = /home/stack/custom_hiera.yaml
~~~

However, for https://access.redhat.com/articles/3597351 , I need to modify a custom ironic parameter for which no
puppet manifest exists yet (at least by grepping, I cannot find it):
~~~
ironic::config::ironic_config:
  DEFAULT/rpc_thread_pool_size:
    value: 8
~~~
However, for this to work, I need class ironic::config to be loaded.

The overcloud offers an elegant way to include custom classes, e.g.:
~~~
[stack@undercloud-7 ~]$ cat
/usr/share/openstack-tripleo-heat-templates/puppet/manifests/overcloud_controller_pacemaker.pp
# Copyright 2015 Red Hat, Inc.
# All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

if hiera('step') >= 4 {
  hiera_include('controller_classes', [])
}

$package_manifest_name =
join(['/var/lib/tripleo/installed-packages/overcloud_controller_pacemaker',
hiera('step')])
package_manifest{$package_manifest_name: ensure => present}
~~~

And then use:
https://access.redhat.com/solutions/2328671
~~~
parameter_defaults:
  controllerExtraConfig:
    neutron::config::server_config:
      quotas/quota_port:
        value: '-1'
      quotas/quota_subnet:
        value: '-1'
      quotas/quota_network:
        value: '-1'

    controller_classes:
      - ::neutron::config
~~~

According to Alex Schulz, this is currently not supported and this would be a simple patch to
always include the various ::<class>::config methods but we need to
understand what is required for customers and why.

Comment 1 Shelley Dunne 2018-10-12 15:36:34 UTC
Updating Target Milestone to z3 for all Modified low bugs

Comment 10 errata-xmlrpc 2018-11-13 22:28:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3587


Note You need to log in before you can comment on or make changes to this bug.