Fix Swift proxy pipeline ordering
authorChristian Schwede <cschwede@redhat.com>
Fri, 28 Oct 2016 11:23:32 +0000 (13:23 +0200)
committerChristian Schwede <cschwede@redhat.com>
Fri, 28 Oct 2016 11:33:31 +0000 (13:33 +0200)
The Ceilometer middleware is in the wrong place; actually any middleware
should be deployed after catch_errors to catch any errors that would
otherwise crash the proxy service. Additionally the ceilometer
middleware should be deployed after any authentication middleware.

Closes-Bug: 1637471
Co-Authored-By: Thiago da Silva <thiago@redhat.com>
Change-Id: I710ff2f51271a78582fa502e7eecfa687800c664

puppet/services/swift-proxy.yaml

index de8daea..35e2118 100644 (file)
@@ -88,7 +88,6 @@ outputs:
               - ResellerAdmin
             swift::proxy::versioned_writes::allow_versioned_writes: true
             swift::proxy::pipeline:
-              - 'ceilometer'
               - 'catch_errors'
               - 'healthcheck'
               - 'proxy-logging'
@@ -101,6 +100,7 @@ outputs:
               - 'keystone'
               - 'staticweb'
               - 'versioned_writes'
+              - 'ceilometer'
               - 'proxy-logging'
               - 'proxy-server'
             swift::proxy::account_autocreate: true