The software, home-made automation or third party solution (or a combination of both), should be ready to be deployed on WMF infrastructure and be able to backups 1 file and recover into Swift (or a test Swift installation) that same file. To the point, that it should quickly be able to backup and recover a small wiki such as testwiki.
This will inform us of the following open questions:
* Throughput needed/achieved and parallelization for both backup and recovery
* Actual API used (Swift vs. MediaWiki)
* Querying cache layer for speedup?
* Desired recovery methodology (recover with the same name or different name/location?)
* Overhead on Swift infrastructure/need for expansion to accommodate backup needs
There won’t be any specialized storage for this proof of concept- as it will be small scale, we can just use a directory on a filesystem for temporary storage