13:01:30 #startmeeting meeting 13:01:31 Meeting started Mon Jun 20 13:01:30 2016 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:01:31 The meeting name has been set to 'meeting' 13:01:35 .hello dperpeet 13:01:36 dperpeet: dperpeet 'None' 13:01:37 .hello mvo 13:01:40 mvollmer: mvo 'Marius Vollmer' 13:01:43 .hello stefw 13:01:46 stefw: stefw 'Stef Walter' 13:01:59 .hello larsu 13:02:00 larsu: larsu 'Lars Uebernickel' 13:02:12 .hello harish__ 13:02:13 harish__: Sorry, but you don't exist 13:02:55 i'm back as well 13:03:16 oh! 13:03:36 :) 13:03:40 that's strange 13:03:52 i dont get it. any idea why? 13:04:02 harish__, you need to register a nick with the server 13:04:07 nope, but the fedora bots can be annoying 13:04:20 freenode my nick is harish__ 13:04:54 then think nothing more of it, we believe you exist 13:04:56 it's .hello fedora-account-id 13:05:11 queue at thecoffee machine, sorry 13:05:19 #topic agenda 13:05:43 * teaming 13:05:51 thanks mvollmer 13:05:55 * gsoc 13:06:10 * network bond default settings 13:06:17 harish__, I don't know why we do the .hello thing, tbh 13:06:38 hehe :D 13:06:57 because we've always done it this way! 13:07:21 :-D 13:07:24 yes, traditions must be preserved 13:08:11 okay, ready? 13:08:47 #topic teaming 13:09:04 I was trying to get more feedback about how people actually use teaming 13:09:26 and there is actually a bond configuration wizard kind of thing 13:09:43 constructed from real feedback 13:09:51 so I will look at that closely 13:10:22 but it's clear to me already that we can't get away with zero widgets 13:10:53 that's ok, as long as users don't have to paste or write json code 13:11:13 one insight is that people actually need to make nested teams to implement their requirements... 13:11:50 like, load balance over these four ports, and fall back to these other three ports when all of the other four fail 13:12:28 you need one team for each group of ports to do the balancing, and one team to do the fallover, iiuc 13:12:49 so, yeah, endless fun... :-) 13:13:22 the use cases in the e-mail discussion were interesting 13:14:25 eot from me 13:14:31 no real code for this yet 13:15:13 should we do the bonding now? 13:15:17 seems to fit 13:15:27 #topic network bond default settings 13:16:22 sure 13:16:46 do we know yet if bonds will be replaced by teaming in cockpit? 13:17:28 right now bonding seems to default to round-robin, and someone filed a bug stating that "dynamic link aggregation" or "active backup" would be safer 13:17:30 https://bugzilla.redhat.com/show_bug.cgi?id=1348066 13:17:48 I would be happy to pick the dynamic aggregation 13:18:12 mvollmer, was there any reason to pick round robin? 13:18:39 dperpeet, if so, not a good one 13:18:50 i think I copied the UI from GNOME, basically 13:19:24 ok 13:19:41 the reasoning sounds sane, so I would just change it without digging deeper 13:19:42 heh, the reported sits opposite of me here... 13:19:46 *reporter 13:19:54 yes 13:20:11 eot then :) 13:20:47 #topic gsoc 13:21:11 dperpeet like u have commented in https://github.com/cockpit-project/cockpit/pull/4503 13:21:25 I will create an integration test to check that it shows unknown when timestamp is not available. 13:21:47 rest of the correction work i finished now. 13:21:52 great 13:22:06 do i need to rebase and push now? 13:22:14 that would probably help 13:22:25 because of tests? 13:22:40 just ping someone to start them again after the rebase 13:22:54 how's the other work progressing, creating timers? 13:22:59 okay i will do now 13:23:07 wrk done so far in timer playground app : https://medium.com/@harishanand95/gsoc-week-4-timer-playground-app-6b6f77ca1003#.bunzje33q 13:23:25 are we going to have timer playground app as part of cockpit? 13:24:03 I think we can have it directly as part of systemd, bcoz playground app code has redundant code from systemd/init.js 13:24:58 The extra addition needed to include in systemd is service.html will need createtimer modal (from timer.html) and init.js will have timer.js code 13:25:17 yes, it will go into the systemd package 13:25:18 right, it should be port of the systemd package when it gets merged 13:25:27 part* 13:25:33 the playground is a good place to try it out 13:25:45 yea now that i have all functions 13:25:51 it just integrating it 13:25:57 I suggest opening a WIP pull request 13:26:05 and let andreasn play with it a bit 13:26:09 i tried that on systemd files it worked 13:26:23 WIP work in progress? 13:26:50 okay i will do that. 13:26:56 dperpeet ,petervo any particular suggestion u have for me to improve as mid-evaluations are up 13:27:32 I think we will cover that part outside of the meeting, harish__ 13:27:43 yes, WIP is short-hand for work in progress 13:27:56 oh sure fine 13:28:01 eot 13:28:10 as a convention in our project we add that to the title 13:28:18 so we know that it isn't ready yet for a detailed review 13:28:24 just a high-level one 13:28:43 good progress! 13:28:51 okay sure, 13:28:57 thanks :D 13:29:21 mvollmer, eot 13:29:31 okay! 13:30:12 #topic any other biz 13:32:23 alright! 13:32:28 thanks everyone! 13:32:31 #endmeeting