I have gone through https://wikitech.wikimedia.org/view/How_to_deploy_code and updated it to describe the Magical Git Universe. Specifically, there is a lot of documentation surrounding the submodules that we now use for deploying extensions, and surrounding the process and mechanics of extension deployment branches.
Everything in the deployment guide SHOULD be correct, but some things may be wrong, either because I made a mistake or because I documented the way things should work before actually making them work that way in reality. Either way, if something's wrong, poke me or Chad.
Roan
Am 18.04.2012 04:24, schrieb Roan Kattouw:
I have gone through https://wikitech.wikimedia.org/view/How_to_deploy_code
Why is this there and not on http://www.mediawiki.org ?
On Wed, Apr 18, 2012 at 3:50 PM, Thomas Gries mail@tgries.de wrote:
Am 18.04.2012 04:24, schrieb Roan Kattouw:
I have gone through https://wikitech.wikimedia.org/view/How_to_deploy_code
Why is this there and not on http://www.mediawiki.org ?
Because its about the WMF cluster admin and/or documentation and not MW in general.
On Apr 17, 2012 10:54 PM, "K. Peachey" p858snake@gmail.com wrote:
Why is this there and not on http://www.mediawiki.org ?
Because its about the WMF cluster admin and/or documentation and not MW in general.
And because the documentation for "I just broke mediawiki.org, how do I fix this" shouldn't be on mediawiki.org :-)
Roan
On 18.04.2012, 18:29 Roan wrote:
On Apr 17, 2012 10:54 PM, "K. Peachey" p858snake@gmail.com wrote:
Why is this there and not on http://www.mediawiki.org ?
Because its about the WMF cluster admin and/or documentation and not MW in general.
And because the documentation for "I just broke mediawiki.org, how do I fix this" shouldn't be on mediawiki.org :-)
What about "How not to break mediawiki.org"? :)
On 18/04/12 04:24, Roan Kattouw wrote:
I have gone through https://wikitech.wikimedia.org/view/How_to_deploy_code and updated it to describe the Magical Git Universe. Specifically, there is a lot of documentation surrounding the submodules that we now use for deploying extensions, and surrounding the process and mechanics of extension deployment branches.
Everything in the deployment guide SHOULD be correct, but some things may be wrong, either because I made a mistake or because I documented the way things should work before actually making them work that way in reality. Either way, if something's wrong, poke me or Chad.
Roan
What about making (and publishing) a git repo of wikipedia/common? That would allow a) Easily reproduce the configuration on wmflabs b) Distribute cleanup of that messy folder tree.
Yes, passwords should not be committed. No, waiting two months for doing that is not a good idea.
On Wed, Apr 18, 2012 at 10:40 AM, Platonides Platonides@gmail.com wrote:
What about making (and publishing) a git repo of wikipedia/common? That would allow a) Easily reproduce the configuration on wmflabs b) Distribute cleanup of that messy folder tree.
Yes, passwords should not be committed. No, waiting two months for doing that is not a good idea.
Yes, I've been meaning to put wmf-config into git, but never really got around to it. The reason it hasn't gotten done in the past two months is not because we like sitting on our asses or think it can wait, it's because we're busy doing three million other things that also need to get done :)
Roan
On 18/04/12 19:51, Roan Kattouw wrote:
Yes, I've been meaning to put wmf-config into git, but never really got around to it. The reason it hasn't gotten done in the past two months is not because we like sitting on our asses or think it can wait, it's because we're busy doing three million other things that also need to get done :)
Roan
Well, "two months" was a random timeframe. I'm not that you had other things to do. Deployment changes was a good time to include this wmf-config thing. I also know that there was some block because it "contains sensitive stuff", I'm a bit skeptical about the time it would be needed to read the configs and remove passwords (we are happy to show other things like server names, ips, roles...), but heh, you could argue that they are written in Klingon and I wouldn't be able to prove you wrong ;) Maybe a good first task for Chris Steipp?
Regards
On Wed, Apr 18, 2012 at 3:40 PM, Platonides Platonides@gmail.com wrote:
Well, "two months" was a random timeframe. I'm not that you had other things to do. Deployment changes was a good time to include this wmf-config thing. I also know that there was some block because it "contains sensitive stuff", I'm a bit skeptical about the time it would be needed to read the configs and remove passwords (we are happy to show other things like server names, ips, roles...), but heh, you could argue that they are written in Klingon and I wouldn't be able to prove you wrong ;) Maybe a good first task for Chris Steipp?
We don't need to audit most of it because most files are already exposed through noc.wikimedia.org . We do, however, need to refactor the common/ directory structure a bit. We could do that once the biweekly deploy schedule is running nicely I guess. It's up to RobLa to prioritize this task, one of his devs (probably Aaron or Chad) would work on this I imagine.
Roan
On 19/04/12 00:46, Roan Kattouw wrote:
We don't need to audit most of it because most files are already exposed through noc.wikimedia.org . We do, however, need to refactor the common/ directory structure a bit. We could do that once the biweekly deploy schedule is running nicely I guess. It's up to RobLa to prioritize this task, one of his devs (probably Aaron or Chad) would work on this I imagine.
Roan
Release early, release often. It can be committed in ugly format, and be prettified later (maybe with community help, as I pointed).
On Wed, Apr 18, 2012 at 3:57 PM, Platonides Platonides@gmail.com wrote:
Release early, release often. It can be committed in ugly format, and be prettified later (maybe with community help, as I pointed).
Sure, but there will be some effort required to 1) disentangle the private files (even though we can easily identify them, they currently live in the same repo) and 2) switch over the cluster to use the git repo. We don't want the config to live in two different repos at once and have them get out of sync.
Roan
Thanks a ton Roan!
On Tue, Apr 17, 2012 at 7:24 PM, Roan Kattouw roan.kattouw@gmail.comwrote:
I have gone through https://wikitech.wikimedia.org/view/How_to_deploy_code and updated it to describe the Magical Git Universe. Specifically, there is a lot of documentation surrounding the submodules that we now use for deploying extensions, and surrounding the process and mechanics of extension deployment branches.
Everything in the deployment guide SHOULD be correct, but some things may be wrong, either because I made a mistake or because I documented the way things should work before actually making them work that way in reality. Either way, if something's wrong, poke me or Chad.
Roan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org