| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ia778b3fbde857888dee29b54215f63ca2abb2c70
|
|
|
|
| |
Change-Id: I853d618046d9df130074b97d92cd3d57709e9ef4
|
|
|
|
| |
Change-Id: Iafdbe5f8b12b5d25acc447e3d8d043b5a0faa018
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A number of configuration errors prevent the successful creation of code
coverage. This corrects the .coveragerc source/omit setup and the tox
package name generation.
http://lists.openstack.org/pipermail/openstack-dev/2015-October/076193.html
Change-Id: I2ee48d5b987cc26fe2de6d538ab278821100b278
|
|/
|
|
|
|
|
| |
We can remove openstack-common.conf as we don't
sync any code from oslo-incubator any more.
Change-Id: Ic915216c74966abc43c4a4d39d3ae42d42db64fa
|
|
|
|
| |
Change-Id: Ic2d3dcadbaaaa2819f2c84b23778a2e407a9b127
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This middleware is supposed to be placed in front of any WSGI
application. It will translate the WSGI environment to an environment
mimicking the environment of the reverse proxy placed in front of it.
It supports translating:
- Protocol via X-Forwarded-Proto
- Host via X-Forwarded-Host
- Prefix via X-Forwarded-Prefix (not standard, but already used in other
projects)
- Forwarded header (RFC7239)
Change-Id: I9e66e17a343fc454016415375bcd5a1285334f5a
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
The current value is launchpad url which is not
appropriate and so changed to Oslo wikipage
Change-Id: I2a324a072869471d8e7f1ece5e1fdadc1bea568f
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: Ib0c385eceaa15103def2720d8d875c7b218d842f
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add on information about the active threads and active
greenthreads and some basic server information to be able
to show this to operators (or others) that have detailed
mode enabled and can benefit from this information being
output.
This addition makes it so that basic diagnostic information
can be obtained from the response of the healthcheck middleware
and not just OK or NOT OK; making the eventlet backdoor feature
that oslo.service provides less needed for operators.
Change-Id: I469c56586597561633921ebf3916585646f45373
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Instead of creating a body for a request that is known
to be a HEAD request avoid creating any body in the first
place and just return the status code determined from
the health evaluation.
Closes-Bug: #1494533
Change-Id: I39abee3cdfff4af40355f91d22607e3a2aa52e29
|
|\ \ \ \
| |/ / /
| | / /
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It can be quite useful to have admin endpoints for healthcheck
middleware provide more information about the health of the system.
To enable this kind of information this initial step starts to
add a jinja2 template that will produce the existing simple case
by default, but when setup with detailed mode it can then produce
more information about which checks were performed and there results.
It can be expanded in the future to provide more information as
desired (possibly showing more useful application level info when
in detailed mode).
Closes-Bug: #1494531
Change-Id: I9c6dae848985d950c3cf6798695c7669eb245ccb
|
| |
| |
| |
| |
| |
| | |
TrivialFix
Change-Id: Icaa184373cb1a7775950295863bb8bbd663d875c
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I5b2a3002d91ed9b6634d8a43c80e896fd66628d3
|
| | |
| | |
| | |
| | | |
Change-Id: I89f8cdc4b396680ced7d1e0da1f072e369fb275b
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I07466e16af96b99c9db2ed431da7cdbeb36966c7
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per:
http://lists.openstack.org/pipermail/openstack-dev/2015-August/073338.html
The point behind the addition of the stevedore.sphinxext extension is
"to document drivers and other types of plugins to make the available
sets built into projects easier to discover" (dhellman).
Change-Id: If24f70704dd4840c44e6e72928157078fea80b51
|
| | |
| | |
| | |
| | |
| | |
| | | |
Needed for coverage 4.0
Change-Id: Id112f4abb0c3eb75ebfa9c7462759949f88b6085
|
| | |
| | |
| | |
| | | |
Change-Id: I43586e6f065846a7217bdb0d5461fc414433d839
|
| |/
|/|
| |
| |
| |
| |
| | |
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: Ibda8436eb29ef110b14f88da9c5d35da6338baa9
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, the code only handle * (wildcard) in allowed_origins when
using OPTIONS. When doing the actual request, * is not handled at all
and therefore the request is denied.
This patch fixes that by handling the wildcard the same way in both code
path.
Change-Id: I7c19b818b5845baca2a999b714ca6ebb90d9633d
|
|/
|
|
|
|
|
|
| |
Current paste filter of cors middleware require allowed_origin.
But it should be required only if oslo_config_project is unset.
Change-Id: I85ae5d5984ea9b2401563c30ba5a83dc8d88acbf
Closes-bug: #1491293
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Create separate option discovery functions for each piece of middleware,
so an application that only uses one piece can include only those
options in its sample configuration file.
Test the results with some unit tests that simply ensure the functions
do not raise exceptions, and by adding configuration options to the
documentation for the library, using the new integration of oslo.config
with sphinx.
Change-Id: I4c777cd70c063441f430c48ab1f9c9cac2c1fc75
|
|/
|
|
| |
Change-Id: I4b9778404f5653ab439c83707f5b7978d972d05b
|
|
|
|
| |
Change-Id: I462b2e36ec561f31858bcb5da82237c29d119768
|
|
|
|
|
|
|
|
|
|
| |
Some useful comments have been done on review
https://review.openstack.org/#/c/209817 after it have
been merged.
This change fixes them.
Change-Id: I4e36c354576510665d8aa1c95d8e82696d80ce0c
|
|
|
|
|
|
|
|
|
| |
It turns out that the simple header list outlined by the CORS
specification includes additional headers that were missed
during the initial implementation. This patch adds those
headers, and includes a test to enforce it moving forward.
Change-Id: I06f28102d1fa59d7c647fd08d69ea60e277a653f
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If verbose is true, the class definition is printed just
before being built. We don't really need to print this into
our logs, so we should drop the verbose parameter (as it
defaults to False anyway).
Closes-Bug: #1482744
Change-Id: Ic6cb7fe9c87151bb0c318d060fd88bb2e1977404
|
|/
|
|
| |
Change-Id: Ia836ea531b965f562a8afff4b5b197ec35946788
|
|
|
|
|
|
| |
This hash is private, this patch marks it as such.
Change-Id: Ia334f18b7db847c6b2cbb98a6462744530ed59ad
|
|
|
|
|
|
|
|
|
|
|
|
| |
Latent properties allow a consumer of this middleware to declare
system-required headers and methods options. For instance, if an
API exposes version-negotiation headers, these may be hard coded
when the middleware is attached.
This only works when the middleware is explicitly used. It does
not work in paste configuration.
Change-Id: Ic55b1af23603a0d83a32d20054c18e50367be8fb
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Some methods are actually static, so declare them as such.
Change-Id: Ic76fd10e2d043bdbe5bdca48d82a341454c1a7d4
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|
|
|
|
|
|
| |
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: Id61bd8bffb05c3d07b2656b4fa7364a86150239e
|