14:08:19 #startmeeting 14:08:19 Meeting started Mon Feb 2 14:08:19 2015 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:08:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:08:29 #meetingname Cockpit 14:08:29 The meeting name has been set to 'cockpit' 14:08:40 #topic Agenda 14:09:06 * Short hubbot update 14:09:12 * Metrics archives 14:09:34 jscotka, anything to report? 14:10:28 mvollmer, nothing new, more info will be when devconf to have some suprise aviable :-) 14:10:37 ok! :-) 14:10:44 pvolpe, are you here? 14:10:52 yes 14:11:05 ok! 14:11:20 Andreas and Stef are travelling, I guess, or otherwise off-line 14:11:35 * Docker storage 14:11:54 * Permission UI 14:12:01 yep 14:12:08 sub-mod, awake? 14:12:28 yep 14:12:44 ok, you want to add something to the agenda? 14:12:59 no nothing new from me 14:13:05 ok 14:13:13 let's start then 14:13:26 #topic hubbot update 14:13:32 that's me. 14:13:50 so, I can't stop playing with hubbot, and now it should be in good enough shape to rely on it. 14:14:21 of course, the tests themselves are still unreliable, but the bot should at least run them properly 14:15:01 it can also make images now, which is mostly nice for me 14:15:25 I have documented it a bit in thr Workflow wiki page. 14:15:39 https://github.com/cockpit-project/cockpit/wiki/Workflow 14:16:09 Check the section about "trigger-hubbot" 14:16:23 Anybody should be able to trigger a retry for a failed pull request. 14:16:43 docs are here: https://github.com/mvollmer/hubbot/blob/master/README 14:16:53 ok! 14:16:56 next topic? 14:17:08 yep 14:17:33 #topic Metrics archives 14:17:41 has been merged 14:17:59 nice 14:18:04 works ok, but pmlogger is weird. 14:18:14 we have a tracker bug for this 14:18:33 https://bugzilla.redhat.com/show_bug.cgi?id=1185740 14:19:00 biggest regression re pre-pcp is that the graphs reset themselves to be empty very often 14:19:14 if you don't have any archives, that is. 14:19:25 I'll try to fix that before stefs demo. 14:19:32 looks good so far 14:19:49 but there are artifacts still 14:20:03 sometimes there is overlap etc 14:20:12 I'll make a pull request soonish 14:20:20 (eot) 14:21:08 next? 14:21:21 docker storage 14:21:23 #topic Docker storage 14:21:37 i opened i PR with them 14:21:42 https://github.com/docker/docker/pull/10474 14:22:09 for now we just have the warning 14:22:38 andreas isn't here but i was wondering if we should expose the metadata space as well 14:22:48 but the design might need to change if we do that 14:23:20 also that's only really applicable for the devicemapper backend 14:23:30 metadata is a bit like "number of inodes" with traditional storage, right? 14:23:44 you might run out of it, but it is not normally displayed. 14:23:58 what about only showing it when it is close to running out? 14:24:16 i'd be ok with that 14:24:50 so would you say the storage display is useful as it is? 14:25:06 or is it rather meaningless? 14:25:21 if you underlying storage has more than 100gbs 14:25:33 or if you did something special with your docker setup 14:25:35 then yes 14:25:41 right 14:25:45 if everything is default 14:25:53 and you have less, no 14:26:02 hmm 14:26:10 any followup plans? 14:26:10 but that's why the warning 14:26:27 can we figure out whether the warning applies? 14:26:28 get a response from the docker guys on my PR 14:26:53 we can, but i'd need to modify the bridge to allow me to run file stats and statfs 14:27:22 at that point we might as well show the correct value 14:27:26 there might be something in pcp, actually. 14:27:31 we also have the fsys monitor. 14:27:35 stef said he'd prefer not doing that for now 14:27:43 ok 14:28:26 i didn't know pcp could help though 14:28:34 i can look into that a little 14:28:34 yeah, maybe the warning will tickle people into improving the info reported by docker 14:28:51 pvolpe, try "pminfo -L" 14:30:10 pminfo -L | grep filesys 14:30:48 ok, good stuff. 14:31:00 next? 14:31:26 sure 14:32:15 #topic Permissions UI 14:32:30 just wanted to get a review on that one 14:32:55 code or UI? 14:33:06 both 14:33:28 it's marked as "WIP", is it ready? 14:33:40 * mvollmer should read... 14:33:44 ok, I see 14:34:09 #action mvollmer review #1744 14:36:24 ok, done! :-) 14:36:36 that was fast 14:36:39 #topic Open Floor 14:36:53 Fedora 22... 14:37:46 I'll make a milestone and issues etc 14:38:21 and then we can make some decisions about what to include 14:38:31 e.g., events on the dashboard? 14:38:52 k8? 14:38:58 stuff like that. 14:39:10 also, some serious manual testing needs to be done 14:39:13 what's the deadline on that? 14:39:35 yeah, I can never remember 14:39:40 something march 14:39:43 ok 14:39:59 https://fedoraproject.org/wiki/Releases/22/Schedule 14:40:48 we'll discuss F22 in Brno and at the hackfest, I guess. 14:41:25 i think we have managed to keep Cockpit reasonably working during all this rearchitecting. 14:41:48 so I am quite optimistic that we can make a nice release with what we have on master 14:42:18 ok, are we done? 14:43:10 think so 14:43:25 my last thing is if there is anything you want me to pick up 14:43:47 nothing comes to mind immediately... 14:43:57 if not i'll keep grabbing stuff from trello/issues 14:44:01 yep 14:44:06 ok 14:44:08 * mvollmer should check trello 14:44:18 ok 14:44:24 #endmeeting