I created 2 diagrams about RCStream and IRC change logs. Those are meant to be a medium for my analysis of those flow [1], they are not meant to be reference documentation. They are much uglier than the other diagrams I have seen, but who knows, maybe they will interest someone...
* https://wikitech.wikimedia.org/wiki/File:Irc-rcstream-sequence.svg * https://wikitech.wikimedia.org/wiki/File:Irc-rcstream-deployment.svg
[1] https://phabricator.wikimedia.org/T126472
On Thu, Feb 25, 2016 at 8:16 AM, Chad Horohoe chorohoe@wikimedia.org wrote:
You may also find these diagrams useful:
https://commons.wikimedia.org/wiki/File:Wikipedia_webrequest_flow_2015-10.pn...
https://wikitech.wikimedia.org/wiki/File:Infrastructure_overview.png
-Chad
On Feb 24, 2016 6:58 PM, "Mukunda Modell" mmodell@wikimedia.org wrote:
On Feb 17, 2016 1:50 AM, "Guillaume Lederrey" glederrey@wikimedia.org wrote:
- I still have not found a global architecture schema (something like
a high level component or deplyoment diagram). But I have never seen any company having those...
I made a diagram of the scap (mediawiki) deployment architecture a while back: https://commons.wikimedia.org/wiki/File:Scap-diagram.png ..
That does not exactly apply to the new scap3 architecture but it's not too far off.
....
On Thu, Feb 18, 2016 at 10:37 AM, Giuseppe Lavagetto glavagetto@wikimedia.org wrote:
About cherry-picks in beta: the problem is not cherry-picking (I think it's a reasonable way to test things) but persistent cherry-picking to monkey patch problems is. I think if we follow the flow of:
- writing a patch
- testing it on beta with a cherry-pick
- get it merged on ops/puppet and production
There are a lot of patches on beta these days and there have been a lot of different people cherry-picking without much coordination. This has lead to breakage quite often. Patches also get lost regularly. I assume this usually happens because someone has rebased the HEAD and accidentally dropped a patch.
It can be really difficult to get a patch merged in ops/puppet within a week (or even a month). I've seen a lot of patches sit around for weeks and even now with the Puppet SWAT windows, it's still sometimes unrealistic to expect patches get merged into production that quickly. (+CC Tyler)
Without a system to manage things, and with very little coordination between everyone who is working on beta, I don't expect the situation to improve too much.
I intend to propose a solution for beta & puppet patch cherry-picks very soon, however, I haven't fully formulated my proposal yet. I will write to the ops list when I have something written in a clear and presentable way.
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops