On Mon, 22 Jun 2015, gord chung wrote:
what's 'long form transport'?
it's not actually using cfg.CONF. to figure out transport url if not present.
cfg.CONF passed in has nothing set and is basically just a bunch of
defaults... the url obviously doesn't have a default so ceilometermiddleware
On 06/22/2015 01:15 PM, Michael Krotscheck wrote:
Having _just_ done this, a couple of suggestions.
- If the middleware is NOT optional - that is, it provides some kind of
a fundamental component or specification of the API, like ETag caching,
CORS, or DB Session management - then the
Having _just_ done this, a couple of suggestions.
- If the middleware is NOT optional - that is, it provides some kind of a
fundamental component or specification of the API, like ETag caching, CORS,
or DB Session management - then the middleware should be added during the
app initialization
Excerpts from Doug Hellmann's message of 2015-06-22 10:50:06 -0400:
Excerpts from Sean Dague's message of 2015-06-22 09:02:02 -0400:
On 06/22/2015 08:58 AM, Doug Hellmann wrote:
Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400:
In extracting the contract for RPC backends in
Excerpts from Sean Dague's message of 2015-06-22 09:02:02 -0400:
On 06/22/2015 08:58 AM, Doug Hellmann wrote:
Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400:
In extracting the contract for RPC backends in devstack (to have most of
them live in plugins) one bit of an edge
On 22/06/15 09:02 AM, Sean Dague wrote:
On 06/22/2015 08:58 AM, Doug Hellmann wrote:
Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400:
In extracting the contract for RPC backends in devstack (to have most of
them live in plugins) one bit of an edge case was discovered.
On Mon, Jun 22, 2015 at 2:43 PM, Doug Hellmann d...@doughellmann.com
wrote:
Excerpts from Sean Dague's message of 2015-06-22 13:30:44 -0400:
On 06/22/2015 01:15 PM, Michael Krotscheck wrote:
Having _just_ done this, a couple of suggestions.
- If the middleware is NOT optional - that
On Mon, 22 Jun 2015, Sean Dague wrote:
Could we deprecate the use of tranport_url in ceilometermiddleware and
move to an actual oslo.config file somewhere instead? That would bring
it in line with the rest of the RPC configuration for services, and
ensure that all connections in a cluster have
On 22/06/15 06:39 PM, Chris Dent wrote:
On Mon, 22 Jun 2015, Sean Dague wrote:
Could we deprecate the use of tranport_url in ceilometermiddleware and
move to an actual oslo.config file somewhere instead? That would bring
it in line with the rest of the RPC configuration for services, and
In extracting the contract for RPC backends in devstack (to have most of
them live in plugins) one bit of an edge case was discovered.
https://github.com/openstack-dev/devstack/blob/master/lib/swift#L388
The connection to the RPC mechanism from ceilometermiddleware inside of
swift uses a
Excerpts from Sean Dague's message of 2015-06-22 13:30:44 -0400:
On 06/22/2015 01:15 PM, Michael Krotscheck wrote:
Having _just_ done this, a couple of suggestions.
- If the middleware is NOT optional - that is, it provides some kind of
a fundamental component or specification of the
Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400:
In extracting the contract for RPC backends in devstack (to have most of
them live in plugins) one bit of an edge case was discovered.
https://github.com/openstack-dev/devstack/blob/master/lib/swift#L388
The connection to the
On 06/22/2015 08:58 AM, Doug Hellmann wrote:
Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400:
In extracting the contract for RPC backends in devstack (to have most of
them live in plugins) one bit of an edge case was discovered.
13 matches
Mail list logo
