Page MenuHomePhabricator

Replicate CentralNotice tables to Labs
Closed, ResolvedPublic

Event Timeline

scfc renamed this task from Replicate CN related tables at labs to Replicate CentralNotice tables to Labs.Jun 11 2016, 7:46 PM

The tables in the desc looks like indeed the most useful ones, but I would like all the extension's tables to be replicated.

The tables in the desc looks like indeed the most useful ones, but I would like all the extension's tables to be replicated.

Yes, it makes most sense to replicate all of them. Thx in advance!!!

I suppose some views just need to be added to maintain-replicas for these

Reedy updated the task description. (Show Details)

Change 374875 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/puppet@production] Add centralnotice tables to maintain-views.yaml

https://gerrit.wikimedia.org/r/374875

Hi,

Just to make sure I am getting this right, centralnotice database means metawiki database, right?
I have checked the tables added to Reedy's patch, and they do already exist on labsdb servers.
So as Krenair points out at: T135405#2585246 this is just missing the views

Hi,

Just to make sure I am getting this right, centralnotice database means metawiki database, right?
I have checked the tables added to Reedy's patch, and they do already exist on labsdb servers.
So as Krenair points out at: T135405#2585246 this is just missing the views

Yeah. Well, they are on testwiki too (it's setup as a "central wiki" for itself), so might be worth exposing those at the same time, for usefulness of testing purposes (more people can create banners/notices on testwiki than metawiki)

So my patch above being merged, and the script being run on the labsdb servers should be enough to make the magic happen?

Marostegui moved this task from Triage to Blocked external/Not db team on the DBA board.

Hi,

Just to make sure I am getting this right, centralnotice database means metawiki database, right?
I have checked the tables added to Reedy's patch, and they do already exist on labsdb servers.
So as Krenair points out at: T135405#2585246 this is just missing the views

Yeah. Well, they are on testwiki too (it's setup as a "central wiki" for itself), so might be worth exposing those at the same time, for usefulness of testing purposes (more people can create banners/notices on testwiki than metawiki)

Thanks! :-)

So my patch above being merged, and the script being run on the labsdb servers should be enough to make the magic happen?

Yes, that should be it. I will leave cloud-services-team to review the patch and merge it, so they can run the maintainviews script.
I have checked and the labsdbuser (on the new labs servers) already have grants for metawiki_p views, so there should be no issues from the DBA side.

The tables in the desc looks like indeed the most useful ones, but I would like all the extension's tables to be replicated.

Yes, it makes most sense to replicate all of them. Thx in advance!!!

Just to confirm, @AndyRussG we can just replicate all the tables? I had a quick scan of them.. And can't see any obviously private data. See the patch listing the tables to be exposed 1:1

Change 374875 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/puppet@production] Add centralnotice tables to maintain-views.yaml

https://gerrit.wikimedia.org/r/374875

Yes, everything in the CentralNotice schema can be visible to the public. Most of it is already visible via https://meta.wikimedia.org/wiki/Special:CentralNotice and its subpages, even for logged-out users.

Change 374875 merged by Madhuvishy:
[operations/puppet@production] Add centralnotice tables to maintain-views.yaml

https://gerrit.wikimedia.org/r/374875

@Marostegui @Reedy Merged and ran maintain-views in all the labs replicas (1001/3/9/10/11)

madhuvishy claimed this task.

I'm closing this as resolved since running the maintain-views script for the new views went fine. Please reopen if there are any issues. Thanks!