Commit Graph

17 Commits

Author SHA1 Message Date
David Vallee Delisle 0f7ce2cfa6 Adding oslo.config entry points for yaql and cache opts
To assist with automated configuration validation, we need entry points
for oslo.config.opts for yaql and cache options.

Change-Id: I228282d2c05f6583fe972470b326e7182f635b39
2024-01-09 10:39:46 +09:00
Takashi Kajinami ede6032e5d Fix missing oslo.versionedobjects library option
This ensures the options for oslo.versionedobjects library are
included in the file generated by oslo-config-generator.

Change-Id: I79ab4a6168b7931b783d542e44d9f3cae3351396
2023-08-08 06:05:21 +00:00
Zuul ccef13782a Merge "Add missing [oslo_reports] options" 2021-09-21 02:15:31 +00:00
Takashi Kajinami 605b10c31b Add missing oslo.cache options
This change ensures options of the oslo.cache library are included in
heat.conf generated by oslo-config-generator.

Change-Id: I89efa955e9321e246c9d339a6e5a18d44282eca6
2021-08-23 11:34:33 +09:00
Takashi Kajinami 4154029eb0 Add missing [oslo_reports] options
The oslo.reports library provides some options under the [oslo_reports]
section. This change ensures these parameters are rendered by
the oslo-config-generator command.

Change-Id: Ibcd7ec68138f4061f358aff456fc8ac029bcff41
2021-08-14 23:23:04 +09:00
Rico Lin 8daa7e9389 Allow using database configs on db retry
Allow following db configs when calling wrap_db_retry:
    * database.db_max_retries
    * database.db_retry_interval
    * database.db_inc_retry_interval
    * database.db_max_retry_interval
So database cofig can now control db retries.
Please reference [1] for what each config options can do.

[1] https://opendev.org/openstack/oslo.db/src/branch/master/oslo_db/options.py

Change-Id: I034625733c2d22f0f5635f58e9df3d5785e58cf5
2021-02-27 15:42:07 +08:00
yatin befafa3328 Remove SSLMiddleware from oslo.config namespace
Change [1] removed SSLMiddleware from code but
missed removal of oslo-config namespace, this
patch cleans it up.

[1] https://review.openstack.org/#/c/506900/

Change-Id: Ibeeece25a13706e3ce0b58dbb9746090d881b909
2017-11-27 13:05:00 +05:30
Matthew Edmonds 1d02822c0f fix heat_keystoneclient config gen
This corrects the entrypoint for heat_keystoneclient so that
oslo-config-generator can find it.

Change-Id: I366589c30626232771714394ed6d9353db6f04ba
Closes-Bug: #1711445
2017-08-18 09:00:02 -04:00
rabi e0e92b9d6d Move heat_keystoneclient to clients package
This moves the heat_keystoneclient wrapper to
heat.engine.clients package.

Change-Id: I39636abb946a7608014145d9edca5297d9f929d0
Related-Bug: #1554533
2016-06-01 16:27:01 +05:30
Steven Hardy 67f12e5e24 Add trustee config group to sample config
Some time ago, we added support for a new "trustee" config section,
aimed at allowing independent configuration of the credentials used
to obtain trust-scoped tokens for deferred authentication.  One of the
main reasons for this was to avoid incorrectly using the keystone
auth_token section, and as such a deprecation warning was added when
we fall back to using that config section for heat.

Unfortunately we didn't capture this new section in the sample config
because it's registered via keystoneclient.auth, so this adds support
for this section to the sample config generated via tox -e genconfig,
and adds some notes clarifying usage to the auth_plugin option.

To move to the new config syntax, but maintain the current behavior,
which is to delegate to the heat service user, you can add this section
to your heat.conf

[trustee]
auth_plugin = password
auth_url = http://<keystone hostname or IP>:35357
username = heat
password = password
user_domain_id = default

The generated config documents many more options, all of those supported
by the keystoneclient v3 Password auth plugin, but these are the minimum
to enable delegation to the heat service user in the default domain.

In new deployments this could be set to some other user (such as one created
in the heat domain), but note that the trustee should not be changed for
existing deployments where stacks exist, as the trust stored inside heat
defines a relationship between the stack owner (trustor) and a specific
trustee (which will be the heat service user if the deployment is using
the deprecated path that steals credentials from keystone auth_token).

Change-Id: I30aeb765a2246ce54b10972ae7187655d85cde1f
Partial-Bug: #1300246
2015-12-07 17:42:17 +00:00
Michael Krotscheck 1d94dd4f2a Added CORS support to Heat
This adds the CORS support middleware to Heat, allowing a deployer
to optionally configure rules under which a javascript client may
break the single-origin policy and access the API directly.

For heat, the paste.ini method of deploying the middleware was
chosen, because it needs to be able to annotate responses created
by keystonemiddleware. If the middleware were explicitly included
as in the previous patch, keystone would reject the request before
the cross-domain headers could be annotated, resulting in an
error response that was unreadable by the user agent.

OpenStack CrossProject Spec:
   http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html
Oslo_Middleware Docs:
   http://docs.openstack.org/developer/oslo.middleware/cors.html
OpenStack Cloud Admin Guide:
   http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html docimpact

Change-Id: I185f0d9f85617dd2f482cac4994ccc0a4cb6cf16
2015-10-19 09:18:20 -07:00
tengqm b05dcd8d06 Fix config generator for oslo.service
Patch #196106 has added oslo.service.service to the config generator
configuration file. However, due to problems in oslo.service, there are
still two modules missing for configuration generation.

This patch adds another two modules that contain config options from the
oslo.service package.

Change-Id: I7bb823f62bf9125bbd9cf071b5acb3f59f997c66
Closes-Bug: 1468955
2015-06-27 05:33:07 -04:00
Sergey Vilgelm a390b54371 Use right oslo.service entry points
Use oslo.service.service entry point to generate a sample configuration
file. oslo.service library doesn't have an oslo.service entry point.

Change-Id: Ibb6872dd8e19ec15d72a174d94ca64b7aa489d36
Closes-Bug: 1468955
2015-06-26 17:22:18 +02:00
Sergey Vilgelm 432430d2c6 Switch to oslo.service
oslo.service has graduated, so heat should consume it.

Change-Id: I9c1899eb37505e64967e9cb77da23bb169498aba
Closes-Bug: #1466851
2015-06-23 08:30:39 +02:00
Javier Pena b02805bea5 Fix config file generation
After commit 4154ce7578, it is no
longer possible to generate heat.conf because
heat.openstack.common.policy was still listed in
config-generator.conf

Change-Id: Ib81e8f3b4b80f51025ccda1173b03f6f65387b62
2015-06-01 13:37:25 +02:00
Steven Hardy 70112c103a Move logging to use oslo_log library
The oslo-incubator log modlule has been removed, so port to the oslo_log
library.  Note this uses the new (non namespaced, e.g oslo.log) import
convention, we'll need to align other imports in a future commit.

Some import reordering was required due to pedantic H30[57] checks, and
the services have all been converted to initialize the oslo_log library
as this is done differently to the log.py in incubator.

Change-Id: Ib5a97123fe1b287bc531e42d7887c13ba6205628
2015-02-17 09:23:34 +00:00
Thomas Herve ec6ff6f670 Use oslo.config generator
Replace usage of old incubator configuration generator by the
oslo.config tool.

tools/config/generate_sample.sh has been replaced by tox -egenconfig.

heat_integrationtests/generate_sample.sh has been replaced by
oslo-config-generator
--config-file=heat_integrationtests/config-generator.conf

Change-Id: I6d95df203b556c8ec2088d40a446427f7087b9a7
2015-01-02 13:14:20 +01:00