Jdforrester-WMF added a comment.
In T197616#4876226, @MusikAnimal wrote:
Don’t think anyone has filed a task requesting the views on labs to be created. It doesn’t happen automatically, so hence it not working
I'm aware :) I saw T213295 so wasn't sure if we intentionally were skipping this step
jcrespo added a comment.
First of all, I am only commenting because I have more information, but access handling is owned by the cloud team.
It probably should be treated as automatically required by procedure for all non-private wikis
This is on purpose done not-automatically so a human has to
Krenair added a comment.
In T197616#4876222, @Reedy wrote:
In T197616#4876205, @MusikAnimal wrote:
Is this intentionally missing from the replicas?
MariaDB [testwiki_p]> USE testcommonswiki_p;
ERROR 1044 (42000): Access denied for user 's52657'@'%' to database 'testcommonswiki_p'
MariaDB
Reedy added a comment.
In T197616#4876205, @MusikAnimal wrote:
Is this intentionally missing from the replicas?
MariaDB [testwiki_p]> USE testcommonswiki_p;
ERROR 1044 (42000): Access denied for user 's52657'@'%' to database 'testcommonswiki_p'
MariaDB [testwiki_p]> SELECT * FROM meta_p.wiki
MusikAnimal added a comment.
Is this intentionally missing from the replicas?
MariaDB [testwiki_p]> USE testcommonswiki_p;
ERROR 1044 (42000): Access denied for user 's52657'@'%' to database 'testcommonswiki_p'
MariaDB [testwiki_p]> SELECT * FROM meta_p.wiki WHERE url LIKE "%test-commons%";
Empty
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-08T17:37:00Z] Finished deploy [restbase/deploy@503b29c]: Add test-commons and nap.wikisource - T210752 T197616 (duration: 96m 50s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
jcrespo added a comment.
By the way, are people aware that a shard called "test-s4" has 2 dedicated large hosts and ready to be used for production? I think it was used by Anomie and DanielK to test MCR, could it be shared for whatever testcommonswiki is being used?TASK
Marostegui added a comment.
The database is still present at the s4 servers, and I would like to clean it up.
It cannot be done directly on the master, as it would break the multisource slaves (dbstore1002 and labs hosts).
I can delete it on a host by host, that is fine, but I would like
gerritbot added a comment.
Change 482274 merged by Mobrovac:
[mediawiki/services/restbase/deploy@master] Config: Add test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482274TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482139 abandoned by Jforrester:
Set $wgMultiContentRevisionSchemaMigrationStage = SCHEMA_COMPAT_WRITE_BOTH | SCHEMA_COMPAT_READ_OLD
Reason:
Not needed.
https://gerrit.wikimedia.org/r/482139TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Marostegui added a comment.
Waiting for one hour only is not realistic, specially if asked at 19:00 UTC.
The 4th I was on holidays (I am still on holidays) but I replied to it as I didn't want to block this so long. So we replied in less than 24h, but I didn't notice it was already done.TASK
Jdforrester-WMF added a comment.
In T197616#4859717, @Marostegui wrote:
I wonder why was this created in s4 if we were asked if we preferred s3 and I replied a day after that question that s3 would be the best place from our point of view?
Question was asked at ~19:00 UTC on 2019-01-03, you
jcrespo added a comment.
I've been told there was some breakage based on assuming s4 ==> commons, or commons ==> s4. I am not too worried, as I said, about a temporary project, but the assumption of that on code or configuration is worrying, as it would not be unthinkable we move commonswiki in
Marostegui added a comment.
I wonder why was this created in s4 if we were asked if we preferred s3 and I replied a day after that question that s3 would be the best place from our point of view?TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Jdforrester-WMF added a comment.
In T197616#4859391, @jcrespo wrote:
Based on comments that removing the wiki is going to happen, I won't ask to move it, but please not removing wikis is also not a trivial task due to out of band changes (ES, wikidata, etc.). I would recommend strongly to at the
jcrespo added a comment.
I agree with Manuel T197616, I would have preferred creating it on s3 for isolation reasons- enwiki, commons and wikidata require more resources than the typical high-throughput project and they were on purpose set on dedicated hardware. I understand that you want a setup
gerritbot added a comment.
Change 482257 merged by jenkins-bot:
[mediawiki/services/parsoid@master] Add test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482257TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Marostegui added a comment.
In T197616#4853038, @Reedy wrote:
In T197616#4853024, @greg wrote:
Status?
https://test-commons.wikimedia.org/ is live (DNS and apache are up)
James looks to have made the mw-config patch. Just addWiki.php to run at this point
He was trying to nerd snipe me into
gerritbot added a comment.
Change 482274 had a related patch set uploaded (by Mobrovac; owner: Mobrovac):
[mediawiki/services/restbase/deploy@master] Config: Add test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482274TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482257 had a related patch set uploaded (by Reedy; owner: Reedy):
[mediawiki/services/parsoid@master] Add test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482257TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482139 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/mediawiki-config@master] Set $wgMultiContentRevisionSchemaMigrationStage = SCHEMA_COMPAT_WRITE_BOTH | SCHEMA_COMPAT_READ_OLD
https://gerrit.wikimedia.org/r/482139TASK
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:24:29Z] Synchronized wmf-config/db-codfw.php: T197616 (duration: 00m 44s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:23:31Z] Synchronized wmf-config/db-eqiad.php: T197616 (duration: 00m 44s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
gerritbot added a comment.
Change 482135 merged by jenkins-bot:
[operations/mediawiki-config@master] Add testcommonswiki to db-*.php
https://gerrit.wikimedia.org/r/482135TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482135 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/mediawiki-config@master] Add testcommonswiki to db-*.php
https://gerrit.wikimedia.org/r/482135TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482134 merged by jenkins-bot:
[operations/mediawiki-config@master] Remove excess wiki suffix
https://gerrit.wikimedia.org/r/482134TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 482134 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/mediawiki-config@master] Remove excess wiki suffix
https://gerrit.wikimedia.org/r/482134TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:13:37Z] Synchronized wmf-config/InitialiseSettings.php: T197616 (duration: 00m 44s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:12:25Z] Synchronized multiversion/MWMultiVersion.php: T197616 (duration: 00m 44s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:11:08Z] rebuilt and synchronized wikiversions files: T197616TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: StashbotCc:
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T20:09:31Z] Synchronized dblists/: T197616 (duration: 00m 45s)TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: StashbotCc:
gerritbot added a comment.
Change 482019 merged by jenkins-bot:
[operations/mediawiki-config@master] Initial configuration for test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482019TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Reedy added a comment.
In T197616#4853024, @greg wrote:
Status?
https://test-commons.wikimedia.org/ is live (DNS and apache are up)
James looks to have made the mw-config patch. Just addWiki.php to run at this point
He was trying to nerd snipe me into creating the wiki, which is when I made
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T15:43:19Z] Enabled puppet on mw servers after merging 481796 - T197616TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
gerritbot added a comment.
Change 481796 merged by Effie Mouzeli:
[operations/puppet@production] Add test-commons.wikimedia.org to prod_sites.pp
https://gerrit.wikimedia.org/r/481796TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2019-01-03T15:31:01Z] Disabling puppet on mw servers to test 481796 - T197616TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: StashbotCc:
gerritbot added a comment.
Change 481795 merged by Effie Mouzeli:
[operations/dns@master] Add test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/481795TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
gerritbot added a comment.
Change 482019 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[operations/mediawiki-config@master] Initial configuration for test-commons.wikimedia.org
https://gerrit.wikimedia.org/r/482019TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 481796 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/puppet@production] Add testcommons.wikimedia.org to prod_sites.pp
https://gerrit.wikimedia.org/r/481796TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
gerritbot added a comment.
Change 481795 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/dns@master] Add testcommons.wikimedia.org
https://gerrit.wikimedia.org/r/481795TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL
Jdforrester-WMF added a comment.
In T197616#4543890, @greg wrote:
After speaking with @MarkTraceur we agreed to setup Beta Cluster in such a way to mirror what you'll be doing in production. Happy to help think that through.
Is there a task for this? I'd be interested to read what the plan is
Abit added a comment.
@MarkTraceur , any movement on this after you talked to Greg? Anything I can do to help?TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AbitCc: Smalyshev, MarkTraceur, Ramsey-WMF, Tgr,
Krinkle added a comment.
In T197616#4461712, @daniel wrote:
Do you believe that the test wikis on the live cluster should be removed [..]
Yes and no.
Yes, I'd prefer we not see test-wikis as ways to catch regressions during normal deployments, because almost none of our procedures (apart from
greg added a comment.
In T197616#4462171, @daniel wrote:
In T197616#4462111, @greg wrote:
So, summary: given those limitations of the production testwiki setup (mostly lack of real user traffic) what is the plan for testing against this wiki and could it also (or instead of) be done in Beta
greg added a comment.
In T197616#4461721, @daniel wrote:
The reason to also do this on group0 is parity with the staging we do for the wikipedia setup. In other words, if it's unnecessary to have a staging version of commons on the live cluster, it should also be unnecessary to have a staging
daniel added a comment.
In T197616#4456669, @Fjalapeno wrote:
From what is being said, it sounds like the main question that needs to be answered is:
"Why not do this in beta instead of as part of group 0?"
We should definitely also do it on beta. Which means setting up Wikibase change
daniel added a comment.
@Krinkle In my mind, the purpose of testwiki and friends is to have an early warning for a train deploy breaking something on the production cluster. For that to work, we need one test wiki per significantly different wiki setup. Commons will in the future be the only wiki
Krinkle added a comment.
In T197616#4429492, @Krinkle wrote:
In T197616#4297600, @daniel wrote:
The beta setup is probably not going to cover all the angles for e.g. wikibase change propagation.
@Krinkle Can you clarify what angles you think aren't going to covered and [..]
This was a
greg added a comment.
In T197616#4456742, @CCicalese_WMF wrote:
In T197616#4456657, @Fjalapeno wrote:
In T197616#4409174, @greg wrote:
(if it blocks then it should be a sub-task of the SDC deployment, not the other way around, right? ;) )
@CCicalese_WMF can you make sure the task tree is
CCicalese_WMF added a comment.
In T197616#4456657, @Fjalapeno wrote:
In T197616#4409174, @greg wrote:
(if it blocks then it should be a sub-task of the SDC deployment, not the other way around, right? ;) )
@CCicalese_WMF can you make sure the task tree is correct here?
Yes, it is.TASK
greg added a comment.
In T197616#4456665, @Anomie wrote:
In T197616#4456657, @Fjalapeno wrote:
In T197616#4445656, @greg wrote:
Additional question: how would this test commons receive sufficient traffic to expose any potential issues?
@Anomie I believe you have some thoughts here… can you
Anomie added a comment.
In T197616#4456657, @Fjalapeno wrote:
In T197616#4445656, @greg wrote:
Additional question: how would this test commons receive sufficient traffic to expose any potential issues?
@Anomie I believe you have some thoughts here… can you provide some info for @greg?
I
greg added a comment.
Additional question: how would this test commons receive sufficient traffic to expose any potential issues?TASK DETAILhttps://phabricator.wikimedia.org/T197616EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: gregCc: Krinkle,
Krinkle added a comment.
In T197616#4297600, @daniel wrote:
The beta setup is probably not going to cover all the angles for e.g. wikibase change propagation.
Can we fix that in Beta Cluster?
I do not think it is unreasonable to require new projects to work properly in Beta Cluster from day
54 matches
Mail list logo
