|mediawiki/vagrant||master||+1 K -1||Add the RESTBase and Cassandra roles to MW-Vagrant|
|Open||None||T91787 Have a MediaWiki vagrant role "production" which mirrors WMF production|
|Resolved||mobrovac||T91661 Have a RESTbase vagrant role|
|Resolved||dduvall||T92549 Allow roles to effect pre-provision changes to MW-Vagrant settings|
|Resolved||dduvall||T89919 Services in Vagrant should not be cloned into root|
|Resolved||dduvall||T92311 Hiera-ize all service installation directories|
- Mentioned In
- rMWVAe651ca5dcba7: Add the RESTBase and Cassandra roles to MW-Vagrant
T94050: Generate current MediaWiki-Vagrant ISO image for Lyon USB sticks
T92549: Allow roles to effect pre-provision changes to MW-Vagrant settings
T89919: Services in Vagrant should not be cloned into root
- Mentioned Here
- T89066: Parsoid performance: Use RESTBase from the MediaWiki Virtual Rest Service on group1/group2 wikis
T89481: RESTBase beta release (revision storage / content API)
Current status: the RESTBase and Cassandra roles are in place, but due to memory constraints for Cassandra, it is currently not possible to start the vbox VM. Concretely, JobRunner's HHVM is not left with enough RAM to create the translation cache (it needs approx 200MB for that). I'm trying to find a work-around for this.
@mobrovac, there are some tips on how to configure Cassandra to run within only ~200-300m of memory at http://opensourceconnections.com/blog/2013/08/31/building-the-perfect-cassandra-test-environment/. I have used those before with success.
We should also consider switching to the sqlite backend once that's ready.