icehouse: Move all DLO functionality to middleware

[OpenStack Infra]

https://review.openstack.org/63326

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/swift" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 6acea29fa65e87ca9639172295c611412d7d6148
Author: Samuel Merritt <email address hidden>
Date: Thu Nov 21 17:31:16 2013 -0800

    Move all DLO functionality to middleware

    This is for the same reason that SLO got pulled into middleware, which
    includes stuff like automatic retry of GETs on broken connection and
    the multi-ring storage policy stuff.

    The proxy will automatically insert the dlo middleware at an
    appropriate place in the pipeline the same way it does with the
    gatekeeper middleware. Clusters will still support DLOs after upgrade
    even with an old config file that doesn't mention dlo at all.

    Includes support for reading config values from the proxy server's
    config section so that upgraded clusters continue to work as before.

    Bonus fix: resolve 'after' vs. 'after_fn' in proxy's required filters
    list. Having two was confusing, so I kept the more-general one.

    DocImpact

    blueprint multi-ring-large-objects

    Change-Id: Ib3b3830c246816dd549fc74be98b4bc651e7bace

[Peter Tran (pete-tran02)]

Hello!

I'm a bit unclear as to what is required to close this bug.

My best guess is that relevant content from DLO (http://docs.openstack.org/developer/swift/overview_large_objects.html#dynamic-large-objects) needs to be moved to the appropriate section in middleware documentation (http://docs.openstack.org/developer/swift/middleware.html#module-swift.common.middleware.dlo) which is currently empty.

In addition I suppose the Large Object Support (http://docs.openstack.org/developer/swift/overview_large_objects.html) would need to be updated to indicate that this feature is available through middleware.

If possible, can someone confirm this is the objective to close this bug?

Thank you,

Peter

[Gauvain Pocentek (gpocentek)]

Peter,

Sorry for not answering earlier... The objective you've described looks good to me.

[Alexandra Settle (alexandra-settle)]

Reassigning bug to myself to complete for the bugbash on the 3/09/15 as there has been no action for 2 months.

[Lana (loquacity)]

Patch here, waiting on merge: https://review.openstack.org/#/c/219991/

[Alexandra Settle (alexandra-settle)]

Patched has been merged, closing this patch as fixed :)

[Alexandra Settle (alexandra-settle)]

this bug*