| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Closes-Bug: #1629671
Change-Id: I946ee89d9f078e2a766a2b0c89141d067c483cfa
|
| |
|
|
|
|
| |
TrivialFix
Change-Id: I71b6996c084a47f46268a9929ba1d527c178240d
|
| |
|
|
| |
Change-Id: Ic2d3dcadbaaaa2819f2c84b23778a2e407a9b127
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some application inherits from our middleware class
When we homogenize the signature and configuration handling
of all middlewares we break them.
This change fixes that.
Closes-bug: #1486735
Change-Id: I40c3d59110c6f8c5a1b3d3ccc734dc441069b025
|
| |
|
|
|
|
|
|
| |
This change allows any middleware that use oslo.config to
be configured via paste-deploy, like the cors does.
Related-bug: #1482086
Change-Id: Ibb3e951b45b51c9bc602c9113df18a58226d92d1
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently application that doesn't use the global configuration object
have to rely on hack to setup the global oslo config object for each middleware
it want to use.
For example, gnocchi have its own middleware loader and add crap to load
keystonemiddleware:
https://github.com/openstack/gnocchi/blob/master/gnocchi/rest/app.py#L140
And it can't use oslo.middleware that relies on the global conf object.
Also aodh (use 'paste' for middleware) have to hack the global
configuration object for each middlewares it want to use by code...
https://review.openstack.org/#/c/208632/1/aodh/service.py
But middleware are optional deployer stuffs, we should not write any
code for them...
This change allows application to use paste-deploy (or any middleware
loader) without enforcing the application to use the global oslo.config object.
If the middleware want to use oslo.config it should load the
configuration file himself (and fallback to the global one if any)
The proposed paste configuration to allow this is:
[filter:cors]
paste.filter_factory = oslo.middleware:cors
oslo_config_project = aodh
So the cors middleware can find and load the aodh config and
what is it interested in.
Also, some of them use oslo.config local, some other the global object.
Some can be loaded by an middleware loader like paste, some other not.
This change make consistent the way we bootstrap all middlewares.
Closes-bug: #1482086
Change-Id: Iad197d1f3a386683d818b59718df34e14e15ca5c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Oslo libraries have moved all of their code out of the 'oslo'
namespace package into per-library packages. The namespace package was
retained during kilo for backwards compatibility, but will be removed by
the liberty-2 milestone. This change removes the use of the namespace
package, replacing it with the new package names.
The patches in the libraries will be put on hold until application
patches have landed, or L2, whichever comes first. At that point, new
versions of the libraries without namespace packages will be released as
a major version update.
Please merge this patch, or an equivalent, before L2 to avoid problems
with those library releases.
Blueprint: remove-namespace-packages
https://blueprints.launchpad.net/oslo-incubator/+spec/remove-namespace-packages
Change-Id: Id86fa35bc81d9d24211d8553ac2ef9e91949ba7a
|
|
|
This change defines SSLMiddleware middleware which enables OpenStack
services behind SSL termination proxies to return urls with original
protocol scheme.
SSLMiddleware is based on heat SSLMiddleware class.
Change-Id: I72f8da160ced6ac80fdac743c00ea3f7ffb1f57c
Closes-Bug: #1444490
|
