On Fri, Sep 28, 2012 at 11:10 AM, Arthur Richards
<arichards(a)wikimedia.org>wrote;wrote:
Chris, this sounds really cool. Can you point us to
some specs about how
the test environment is set up (what is the architecture like, what
services are running, etc)? How closely does it emulate the production
environment? Does the beta labs environment provide load balanced
squid/varnish caching layers, configured similarly to the produciton
cluster? If not, is that something we can hope to see? Is the setup
something that we can package up and easily deploy to new instances in
labs?
This is somewhat out of date and in the queue to be updated, so take it
with a grain of salt, but most of that is documented here:
https://labsconsole.wikimedia.org/wiki/Deployment/Overview
I have to admit I am still learning my way around, I'll defer to Antoine
for any detailed answers on the configuration.
Also, how can other projects/extensions start getting
automatically pushed
to the beta labs setup?
The rule of thumb so far is that any code with a scheduled deployment date
may (and probably should) be deployed to beta labs beforehand. In practice
this has so far meant AFTv5, NewPagesFeed + Curation Toolbar, and to some
extent TimedMediaHandler (testing TMH was the original motivation to get
this environment in place). For example, AFTv5 is about to undergo some
back end changes, I want to have an automated end-to-end test in place for
it to be sure the front end is not changed by accident.
This is still early days though, if you have a project that could benefit
from the beta labs test env, I'm open to discussing anything along those
lines.