Hi everyone,
My understanding is that some new extensions intended for widespread deployment aren't getting deployed to test2.wikipedia.org before going to other production wikis. As I was discussing this with Chris McMahon, he pointed out that there's no stated policy that this should be done.
test2.wikipedia.org is basically a standard configuration wiki on the production cluster that we use as the final place for testing before going out to other production wikis. Pretty much anything destined for one of our top wikis or to a substantial number of smaller wikis should go to test2. That's especially true now that our QA team is relying on test2 as an automated test target.
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
Rob
On Tue, Dec 18, 2012 at 11:23 AM, Rob Lanphier robla@wikimedia.org wrote:
Hi everyone,
My understanding is that some new extensions intended for widespread deployment aren't getting deployed to test2.wikipedia.org before going to other production wikis. As I was discussing this with Chris McMahon, he pointed out that there's no stated policy that this should be done.
test2.wikipedia.org is basically a standard configuration wiki on the production cluster that we use as the final place for testing before going out to other production wikis. Pretty much anything destined for one of our top wikis or to a substantial number of smaller wikis should go to test2. That's especially true now that our QA team is relying on test2 as an automated test target.
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
test is very similar, only it doesn't run off the full cluster, just a single apache (and uses the nfs copy, so it's good to use before scapping). Whatever policy we come up with should clarify when to use test vs test2.
-Chad
It would be cool if part of that policy was testing on beta cluster which is also supposed to be identicaly configured as production and is even closer to production because the MediaWiki space is cloned from production and on beta cluster we have replicated each production wiki with its custom configuration
On Tue, Dec 18, 2012 at 5:23 PM, Rob Lanphier robla@wikimedia.org wrote:
Hi everyone,
My understanding is that some new extensions intended for widespread deployment aren't getting deployed to test2.wikipedia.org before going to other production wikis. As I was discussing this with Chris McMahon, he pointed out that there's no stated policy that this should be done.
test2.wikipedia.org is basically a standard configuration wiki on the production cluster that we use as the final place for testing before going out to other production wikis. Pretty much anything destined for one of our top wikis or to a substantial number of smaller wikis should go to test2. That's especially true now that our QA team is relying on test2 as an automated test target.
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
Rob
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Dec 18, 2012 at 9:27 AM, Petr Bena benapetr@gmail.com wrote:
It would be cool if part of that policy was testing on beta cluster which is also supposed to be identicaly configured as production and is even closer to production because the MediaWiki space is cloned from production and on beta cluster we have replicated each production wiki with its custom configuration
This would be desirable, and is reflected in this request: https://bugzilla.wikimedia.org/show_bug.cgi?id=43203
-Chris
Until test2.wikipedia.org has a .m domain with an automatic redirect to it for mobile devices, the mobile team will need to continue to use test.wikipedia.org for final testing of MobileFrontend prior to deployment (I opened an RT ticket for setting this up: https://rt.wikimedia.org/Ticket/Display.html?id=4149).
I agree with Chad that it would be great to have better clarity around when test vs test2 is appropriate, and for what.
On Tue, Dec 18, 2012 at 8:29 AM, Chris McMahon cmcmahon@wikimedia.orgwrote:
On Tue, Dec 18, 2012 at 9:27 AM, Petr Bena benapetr@gmail.com wrote:
It would be cool if part of that policy was testing on beta cluster which is also supposed to be identicaly configured as production and is even closer to production because the MediaWiki space is cloned from
production
and on beta cluster we have replicated each production wiki with its
custom
configuration
This would be desirable, and is reflected in this request: https://bugzilla.wikimedia.org/show_bug.cgi?id=43203
-Chris _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
Considering that testwiki has a nice documentation page [0] and test2wiki doesn't [1], I think we should probably clear that up before announcing any policy.
[0] http://wikitech.wikimedia.org/view/Test.wikipedia.org [1] http://wikitech.wikimedia.org/view/Test2.wikipedia.org
On Tue, Dec 18, 2012 at 11:28 AM, Mark Holmquist mtraceur@member.fsf.orgwrote:
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
Considering that testwiki has a nice documentation page [0] and test2wiki doesn't [1], I think we should probably clear that up before announcing any policy.
[0] http://wikitech.wikimedia.org/view/Test.wikipedia.org [1] http://wikitech.wikimedia.org/view/Test2.wikipedia.org
I thought I had an account on wikitech, but apparently I was mistaken. Nor can I create an account on wikitech, nor edit that page. If I could, though, there would not be much to add.
I don't really see the connection between having a docs page on wikitech for test2 and using test2 in a responsible way for staging production code.
-Chris
On 12/20/2012 04:15 PM, Chris McMahon wrote:
Considering that testwiki has a nice documentation page [0] and test2wiki doesn't [1], I think we should probably clear that up before announcing any policy.
[0] http://wikitech.wikimedia.org/view/Test.wikipedia.org [1] http://wikitech.wikimedia.org/view/Test2.wikipedia.org
I thought I had an account on wikitech, but apparently I was mistaken. Nor can I create an account on wikitech, nor edit that page. If I could, though, there would not be much to add.
I don't really see the connection between having a docs page on wikitech for test2 and using test2 in a responsible way for staging production code.
I agree that deployers should be able to document things about the test environments they use in a good place, even if the need is occasional.
Matt Flaschen
On 12/20/2012 05:32 PM, Matthew Flaschen wrote:
On 12/20/2012 04:15 PM, Chris McMahon wrote:
Considering that testwiki has a nice documentation page [0] and test2wiki doesn't [1], I think we should probably clear that up before announcing any policy.
[0] http://wikitech.wikimedia.org/view/Test.wikipedia.org [1] http://wikitech.wikimedia.org/view/Test2.wikipedia.org
I thought I had an account on wikitech, but apparently I was mistaken. Nor can I create an account on wikitech, nor edit that page. If I could, though, there would not be much to add.
I don't really see the connection between having a docs page on wikitech for test2 and using test2 in a responsible way for staging production code.
I agree that deployers should be able to document things about the test environments they use in a good place, even if the need is occasional.
Matt Flaschen
It seems like http://wikitech.wikimedia.org/view/How_to_deploy_code is the canonical "how to deploy code to WMF sites" instructions, so it should include a "stage on test2 before you deploy to the public-facing sites" step. But where?
wikitech-l@lists.wikimedia.org