Swift backend for Librarian storage

[Stuart Bishop]

Improve availability by using the Swift object store as the Librarian storage layer.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r16864 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/16864>.

[Stuart Bishop (stub)]

On staging now.

For an initial test, I notice that the following URLs are returning obviously different headers (staging librarian is returning a document the browser is rendering as text). qastaging returns the same as production and I think is still running the old code.

https://launchpadlibrarian.net/35805788/docky.png
https://staging.launchpadlibrarian.net/35805788/docky.png

[William Grant (wgrant)]

On 06/12/13 00:33, Stuart Bishop wrote:
> On staging now.
>
> For an initial test, I notice that the following URLs are returning
> obviously different headers (staging librarian is returning a document
> the browser is rendering as text). qastaging returns the same as
> production and I think is still running the old code.
>
> https://launchpadlibrarian.net/35805788/docky.png
> https://staging.launchpadlibrarian.net/35805788/docky.png

qastaging seems to be running the new code, and I've confirmed that
dogfood with the new code returns the correct Content-Type. I suspect a
squid misconfiguration on arsenic for staging.launchpadlibrarian.net.

[Stuart Bishop (stub)]

https://code.launchpad.net/~stub/launchpad/large-swift-files/+merge/198222 needs landing for full Swift code path QA.

[Stuart Bishop (stub)]

Staging is currently running with Swift enabled. I have successfully uploaded files, fed them to swift (removing them from disk to force serving from Swift), and served them back from the Librarian.