[09:48:09] (PS1) Ottomata: Updating Kraken with separate camus meta data dirs for different jobs [analytics/kraken/deploy] - https://gerrit.wikimedia.org/r/133054 [09:48:37] (CR) Ottomata: [C: 2 V: 2] Updating Kraken with separate camus meta data dirs for different jobs [analytics/kraken/deploy] - https://gerrit.wikimedia.org/r/133054 (owner: Ottomata) [11:30:40] (PS1) Gilles: Remove forced index and NOT NULL condition [analytics/multimedia] - https://gerrit.wikimedia.org/r/133061 [11:35:03] (CR) Gilles: [C: 2] Remove forced index and NOT NULL condition [analytics/multimedia] - https://gerrit.wikimedia.org/r/133061 (owner: Gilles) [11:35:22] (CR) Gilles: [V: 2] Remove forced index and NOT NULL condition [analytics/multimedia] - https://gerrit.wikimedia.org/r/133061 (owner: Gilles) [12:03:19] (CR) Nuria: "Still some changes needed in test to ensure bug is indeed fixed." (2 comments) [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/131232 (https://bugzilla.wikimedia.org/64724) (owner: Terrrydactyl) [12:32:21] (PS2) Ottomata: Move currently unneeded oozie util scripts into oozie/archive [analytics/kraken] - https://gerrit.wikimedia.org/r/131311 (owner: QChris) [12:32:28] (CR) Ottomata: [C: 2 V: 2] Move currently unneeded oozie util scripts into oozie/archive [analytics/kraken] - https://gerrit.wikimedia.org/r/131311 (owner: QChris) [12:44:10] qchris: hello! [12:44:36] ottomata: Ahoy! [12:45:35] more naming thoughts! although not about kraken [12:45:41] Noooooo. [12:45:43] haha [12:45:47] webrequest_role [12:45:49] what about [12:45:50] cluster? [12:45:58] or even (god forbid!) 'cache_cluster'? [12:45:58] Cannot we use /dev/random for such tasks? [12:46:01] hahaa [12:46:14] cache_cluster is fine by me. [12:46:32] hmm, but what if we started importing, say nginx logs? [12:46:38] no longer a cache [12:46:38] hm [12:46:42] i guess just 'cluster'? [12:46:51] But cluster is really generic. [12:46:54] i know! [12:46:55] web_cluster? [12:47:01] Mhmmm ... what about "source"? [12:47:01] http_cluster? [12:47:06] webrequest_source [12:47:08] is what we liked [12:47:09] Oh. you want cluster. [12:47:13] i asked faidon what he thought [12:47:16] he liked cluster in the name [12:47:26] If you like cluster, cluster it is. [12:47:29] oh you! [12:47:34] :-P [12:47:43] i need someone with more opinions! :p [12:47:54] No seriously. If both of you like cluster, that's fine. [12:47:57] ahhhhHH [12:48:02] I do not like it too much, but I lack a better suggestion. [12:48:04] i think I do like source [12:48:19] webrequest_source is specific to have meaning, but also generic enough to include future uses [12:48:19] i think [12:48:38] Ok. Let's nuke "webrequest_source". Your argument [12:48:41] is covincing. [12:48:57] nuke? [12:49:07] i was arguing for it! [12:49:13] specific enough to have meaning* [12:49:17] Oh :-) [12:49:20] Hahah. [12:50:06] cluster is way shorter than webrequest_source. [12:50:45] What about "log_source" [12:51:27] Meh. I guess I do not care enough :-( [12:52:37] ottomata: "webrequest_source" is fine by me. [12:52:37] hmmm [12:52:45] log_source [12:52:45] hm [12:53:06] The moment I wrote it ... I thought about EventLogging. [12:53:14] And maybe "log_source" would get confused for it. [12:53:15] yeah, but that is a totally separate table [12:53:17] but yeah [12:53:19] oh yeah mabye so [12:53:26] but yeah, i like that 'webrequest' or omsething like that is in it [12:53:40] makes it clear that it is a delineation between types of webrequests [12:53:41] Will it always be for webrequests? [12:53:48] (and nothing else)? [12:53:52] its on the webrequest table [12:54:22] Sure, but when adding nginx (maybe) ... we'll have two requests for one request. [12:54:29] There /log/_source woud fit better. [12:54:53] As one request may produce more than one log line. [12:55:15] But a single request being counted as two rows in a request table is confusing [13:01:09] ottomata: Do we need "webrequest_" in the column name, if the table name already starts in "webrequest_"? [13:09:36] no, but we talked about that sorta, otherwise the field is kind of ambiguous [13:09:46] its not like every field name is auto-prefixed with webrequest [13:10:03] webrequest_hostname, webrequest_sequence, webrequest_request_uri [13:10:09] request_source? [13:12:07] qchris: ^ [13:12:26] Right. [13:12:50] maybe request_source? [13:12:53] So what's the point in requiring this prefix for "webrequest_source"? [13:13:07] just to disambiguate [13:13:24] between the different columns? [13:13:24] otherwise it isn't really clear what that field is [13:13:29] no [13:13:35] i think its relatively clear what teh other fields are [13:14:01] Mhmmm. [13:14:05] source_cluster? haha [13:14:06] naw [13:14:37] If I look at the table I'll have to associate "host" or "client_ip" with the request. [13:14:56] Just I'd have to do it with "cluster"/"source"/"..." [13:15:09] Well ... no. [13:15:09] hmmmmmmmMMMM [13:15:11] i guess so? [13:15:19] source could mean anything really [13:15:22] I guess you are right. [13:15:28] cluster is a little more specific [13:16:00] Mhmmm. [13:16:07] Ok. Let's have cluster then. [13:16:18] Would that be "text"/"mobile"/.../"nginx" then? [13:16:24] (as values for that column) [13:16:25] yes [13:16:55] So no we cannot see that "text" and "nginx" are fundamentally different things ... [13:16:59] but I guess that is fine. [13:17:05] cluster??? [13:17:17] And we can consider "nginx" a cluster? [13:17:23] man ... [13:17:38] nuria: :-) [13:17:44] nuria: Join the naming fun. [13:18:00] ottomata: "cluster" is fine by me. [13:18:09] ottomata: Now you have to convince nuria :-P [13:18:15] man ..i should have been paying more attention .. but .. cluster really? [13:18:29] as in "cache cluster?" [13:18:34] as in cache cluster yeha [13:18:35] haha [13:18:37] yes! please [13:18:39] more opinions! [13:18:46] ay ... ya , i know [13:18:47] s/cache/machine/ [13:18:48] i don't like any of the options that much! [13:18:52] nginx is no cache really. [13:19:02] or is it? [13:19:05] no [13:19:07] no [13:19:12] currently the only values are for caches [13:19:17] but i'm planning for the future here! [13:19:29] but source or "origin" [13:19:58] is more to the point right? cause we want to identify where request are coming from, right? [13:20:18] yes [13:20:50] "Source" was not like as being too unspecific. [13:21:04] webrequest_source is liked kinda [13:21:04] (Same would hold for "origin" for me) [13:21:05] :) [13:21:14] :-D [13:21:17] ya we cannot use origin as it means something else [13:21:23] but what about "origination" [13:21:48] originator [13:21:48] ehhhhhh.... pretty, i know... [13:21:49] :) [13:21:50] haha [13:22:30] "origiNATIOn" [13:22:31] ... foundry :-) [13:23:56] ... genesis [13:24:14] i would go for genesis before "cluster" [13:24:22] ... synthesis [13:24:22] nawwwwww [13:24:32] which sounds too "cloud-computely" [13:24:50] web_cluster [13:24:50] ? [13:25:00] request_source [13:25:04] webrequest_source [13:25:04] ? [13:25:21] http_source [13:25:21] ? [13:25:34] I'd take any of them, just to not have to think about names any longer :-) [13:25:38] cluster_name [13:25:39] hahaha [13:26:08] cmon you guys spend a days talking about what we will be doing in 5 years :p har har har [13:26:18] jk [13:26:22] They did! (I didn't) [13:26:25] haha [13:26:27] true! [13:26:28] haha [13:26:37] "root" [13:26:54] "fountain" [13:27:03] haha [13:27:31] progenitor [13:27:32] haha [13:28:24] ok voting : 1 http_source or webrequest_source (sounds like 2nd is vetted) 2 http_origination or webrequest_origination (i know, voting for myself, terrible) 3 http_genesis or webrequest_genesis [13:28:51] oof voting! [13:28:52] haha [13:28:53] ok [13:29:01] 1 [13:29:07] 2 and 3 no way! :) [13:29:09] what about cluster? [13:29:14] Cluster is fine. [13:29:16] 4: web_cluster, cluster [13:29:17] I buy cluster. [13:29:24] source_cluster [13:29:25] ! [13:29:26] :) [13:29:26] ha [13:30:25] http_cluster ? [13:30:58] service_group .... as is "service_group=cache_text", "service_group=cache_mobile", "service_group=nginx" [13:32:33] http_cluster is cool w me [13:32:57] service_group? hmm... [13:33:00] at least http_cluster=nginx makes more sense than cluster=nginx [13:33:21] "http_cluster=nginx" seems wrong to me. As no normal http request would go there. [13:33:30] it might! [13:33:31] who knows [13:33:40] if we have an api? [13:33:44] what if oneday we have some misc site that is hosted by nginx [13:33:46] they will right? [13:33:46] or apache even [13:33:51] with no frontend caching by varnish? [13:34:02] it will be fronted by either nginx or apache [13:34:16] like parsoid is, right? [13:34:16] ottomata: oh ... /that/ kind of future proof :-) [13:34:51] doesn't parsoid do that now? [13:35:01] so it is not so far a distant future [13:36:14] configuration of caches is currently in $active_nodes ... so maybe ... "node_group"? [13:38:14] mehhhh [13:38:35] ottomata: I trust you to use the right name :-) [13:39:20] WP:BB [13:39:26] WP:BB? [13:40:02] https://en.wikipedia.org/wiki/WP:BB [13:42:25] ah ha [13:45:35] GRRR OOZIE [13:45:38] why are you not running my jobs [13:45:40] sighhhh [13:57:37] Hey folks. Anyway available to help me with a github repo I just moved from my account to "wikimedia"? [13:58:38] https://github.com/wikimedia/MediaWiki-OAuth [13:58:48] halfak we have standup in 1 min, we can help you after? [13:58:57] Sounds great. Thank you! [13:59:46] nuria: Having problems to join. I'llbe there soon. [14:00:23] me too [14:16:47] qchris [14:16:53] yes,sir! [14:16:58] i think I can't use arbitrary strings in SimpleDateFormat [14:17:09] You have to quote them. [14:17:10] hmmmmMMM [14:17:11] or maybe [14:17:12] hm [14:17:13] yeah [14:17:22] quoting is weirdhere though... [14:17:24] hm ok lemme try [14:21:42] ok yeah! that is working qchris! [14:21:44] phew! [14:21:47] awesome [14:21:50] \o/ [14:21:57] That's awesome! [14:22:01] Dobre! Dobre! [14:22:19] OOOo, wait, no, I have a partition but the date is way wrong [14:22:26] AH [14:22:27] no its ok [14:22:29] i see why [14:22:30] cool yeha [14:26:18] yes, awesome. [14:32:01] (PS4) Ottomata: Adding oozie files to control addition and deletion of webrequest table partitions [analytics/kraken] - https://gerrit.wikimedia.org/r/131208 [16:47:43] (PS1) Terrrydactyl: [WIP] Add ability to tag a cohort [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/133091 [17:57:19] milimetric: hey, where should people go to take a first look at the Vega extension? [17:59:51] sumanah: https://github.com/milimetric/WikiViz [18:00:00] thx milimetric [18:00:28] sumanah: it's using ContentHandler properly now, but there are some pretty major TODOs in there [18:00:37] * sumanah nods [18:00:38] I'll also move it to gerrit sometime soon [18:01:20] Thank you! For me it's useful if it is somewhere where http://hexm.de/mw-search will pick it up if I search for the right strings :-) [18:05:04] ha, we’re running out of useful names with a wiki prefix, WikiViz was the name of a visualization context we organized in 2011 ;) [18:05:09] milimetric ^ [18:05:20] oh and hi everyone [18:05:33] DarTar: I know, I want to rename it to Limn but didn't want to confuse people [18:06:16] sumanah: could I rename that repo mediawiki-extensions-Limn? [18:09:06] milimetric: Is Limn a MediaWiki extension? [18:09:10] milimetric: AFAIK it is not [18:09:46] ah, sumanah: Limn as it exists now is going to perish at some point [18:10:00] or be re-written with Vega [18:10:01] ohhhhhh I see, this is the new Limn kindaaaaa [18:10:19] either way, I'll be using the work/libraries that come out of this for any new visualization work [18:10:33] yep, this is a proof of concept for the new Limn [18:10:49] because whatever the new Limn does, it should easily integrate with MediaWiki at least [18:11:18] Mukunda, new Release Manager person, will be the person to consult on naming-y stuff; for now, I suggest Quim in case you want more advice :) [18:11:33] k [18:11:48] also, was nice to see you in Zurich and I look forward to seeing the work progress :) [18:12:09] thank you, nice to see you too :) [18:46:32] (CR) MarkTraceur: [C: 2 V: 2] "Cool beans, I'll push it out now" [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/131954 (owner: Gilles) [18:50:30] milimetric: Hey, limn click-and-drag for zoom stopped working for me...oh, maybe because the graphs are manually configured now and need to be marked as zoomable? [18:51:31] marktraceur: yes, you need to add the zoom node like... hang on finding example [18:52:02] marktraceur: http://reportcard.wmflabs.org/graphs/active_editors.json?pretty [18:52:06] zoom-brush is what you want [18:52:23] 'kay [19:07:59] (PS1) MarkTraceur: Add zoom-brush to all the graphs [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133112 [19:10:44] (CR) MarkTraceur: [C: 2 V: 2] Add zoom-brush to all the graphs [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133112 (owner: MarkTraceur) [19:13:07] (PS1) MarkTraceur: Missed one graph for zoom-brush [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133114 [19:14:03] (CR) MarkTraceur: [C: 2 V: 2] Missed one graph for zoom-brush [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133114 (owner: MarkTraceur) [20:18:51] (CR) QChris: [C: -2] "I understand that this change is mostly here to get" (1 comment) [analytics/kraken] - https://gerrit.wikimedia.org/r/132108 (owner: Ottomata) [20:46:58] milimetric: I suspect it's illegal to put zoom nodes in the map graphs [20:47:01] Confirm? [20:47:10] illegal? [20:47:12] ah, for that you'll need... one second [20:47:21] yeah YuviPanda, the cops gonna get you if you do that [20:47:23] oh, right. not like a 'legal' problem [20:47:33] YuviPanda: No, like, illegal operation [20:47:42] right, right [20:47:52] marktraceur: http://reportcard.wmflabs.org/graphs/pageviews_mobile_by_manufacturer [20:47:55] marktraceur: zoom-pan [20:48:00] http://reportcard.wmflabs.org/graphs/pageviews_mobile_by_manufacturer.json?pretty [20:48:30] 'kay [20:48:50] Oh wow [20:49:31] (PS1) MarkTraceur: Add file page to zoomable, fix maps [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133165 [20:49:43] (CR) MarkTraceur: [C: 2 V: 2] Add file page to zoomable, fix maps [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133165 (owner: MarkTraceur) [20:50:50] Ugh, fail [20:51:43] hehe [20:52:11] (PS1) MarkTraceur: Fix a thinko in the geoperf and perf definitions [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133166 [20:52:20] Luckily nobody really cares. [20:52:28] (CR) MarkTraceur: [C: 2 V: 2] Fix a thinko in the geoperf and perf definitions [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133166 (owner: MarkTraceur) [20:53:50] marktraceur: are you guys deploying from gerrit to limn1 now instead of from your gitorious repo? [20:53:54] I should update the deployer if so [20:54:20] (PS1) MarkTraceur: Didn't actually enable zoom-pan [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133167 [20:54:26] milimetric: Yeah, it's from gerrit. [20:54:30] https://github.com/wikimedia/limn-deploy/blob/master/fabfile/stages.py#L293 [20:54:41] (CR) MarkTraceur: [C: 2 V: 2] Didn't actually enable zoom-pan [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133167 (owner: MarkTraceur) [20:54:52] so I'll change that to this gerrit repo that you're wrestling with? ;) [20:54:55] Sure [20:55:02] BODY SLAM [20:56:05] ....hm, it didn't work [20:57:05] but it *did* work in that it gave me a hilarious mental image [20:57:19] milimetric: http://multimedia-metrics.wmflabs.org/graphs/mmv_geoperformance_api_global.json looks like the same thing but with a different order... [20:57:27] Oh, order matters, doesn't it [20:58:20] shouldn't... [20:58:21] hm [20:58:57] ah, marktraceur, zoom-pan needs to be in geo-map's children [20:59:04] Ahhhh. [20:59:36] silly stuff... I can't wait to replace it with vega [21:00:04] (PS1) MarkTraceur: Move zoom-pan to geo-map's children [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133169 [21:00:24] (CR) MarkTraceur: [C: 2 V: 2] Move zoom-pan to geo-map's children [analytics/multimedia/config] - https://gerrit.wikimedia.org/r/133169 (owner: MarkTraceur) [21:05:02] I so totally want to build Jenkins jobs for this repository...I just don't want to spend any time on it. :) [21:10:25] marktraceur: i don't know of any meaningful jenkins job you could build to lint "limn-speak" but if you find one, that'd be interesting. Also - if we had vega the jenkins job would be trivial :) [21:10:59] milimetric: I would probably make it something simple like "lint the json, lint the php" [21:11:17] milimetric: My dream jenkins setup would also build all of the SQL and JSON files from the templates [21:11:25] Because I hate having built things in git. [21:11:42] ah, fair enough - I have json linting in vim with syntastic [21:11:53] but yeah, jenkins would be nice [21:13:05] marktraceur: i'm out, limn-deploy should work for you now, but it seems like you're just git-pulling from limn1 anyway [21:13:15] I am [21:13:15] ping me on email if you need help [21:13:25] 'kay :) [23:59:24] (PS4) Terrrydactyl: Fixes problem with deleting empty cohorts. [analytics/wikimetrics] - https://gerrit.wikimedia.org/r/131232 (https://bugzilla.wikimedia.org/64724)