13:01:08 #startmeeting meeting 13:01:08 Meeting started Mon Jul 4 13:01:08 2016 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:01:08 The meeting name has been set to 'meeting' 13:01:15 .hello mvo 13:01:16 mvollmer: mvo 'Marius Vollmer' 13:01:27 .hello andreasn 13:01:28 andreasn: andreasn 'Andreas Nilsson' 13:01:37 .hello harishanand 13:01:38 harish__: harishanand 'Harish Anand' 13:02:05 #topic Agenda 13:02:13 * teaming 13:02:19 * timers 13:02:31 * fedaor-24 via virt-builder 13:03:01 * vm-management 13:03:51 okay, let's start 13:03:55 #topic teaming 13:04:18 so when I was young and naive I didn't want to put any config settings into the team UI 13:04:37 now that I am older I am afraid we need to put them all there more or less 13:04:46 similar to bonds 13:04:57 a lot of edge cases? 13:04:57 so not super massive, but still 13:05:04 well 13:05:07 .hello mlibra 13:05:09 mlibra: mlibra 'Marek Libra' 13:05:28 for example, there are real tradeoffs with themonitoring 13:05:47 it's not something where the software can do the right thing 13:06:32 the mode of the team also depends on what other hardware you have 13:06:38 so what ones would we need to add? And what cases would they solve? 13:07:12 right, so you'll need a very specific switch to use a certain team mode, right? 13:07:17 the runner mode (load balance vs active backup mostly) 13:07:24 port priorities 13:08:10 link monitoring (sending pings acress the whole network vs just checking the local cable) 13:08:24 link monitoring is on/off? 13:08:34 andreasn, no, i's always on 13:08:43 it's one method vs the other 13:09:06 andreasn, should we plan that from the top, also for bonds? 13:09:59 yes, I think that would be best. Ideally as proper use cases 13:10:05 or should I just bring teams to about the same level as bonds` 13:10:16 andreasn, okay, let's do that. 13:10:27 "John has X type of hardware in his network, so he needs to be able to set this" 13:11:15 yeah, it'll be a bit of reverse engineering the use cases out of the existing teamd features... 13:12:13 I wish we had some data on what settings affected almost everyone, what applies to 50% of users and what is applicable to only 1 in 1000 13:12:36 to get some sense of what are the most important things to expose 13:12:39 yeah, I was asking but didn't get much, but I have some contacts now 13:12:44 that's good 13:13:14 what I saw on some of the discussions was "here is a really odd thing that can happen in very extreme situations" 13:13:32 really? 13:13:55 tbh, we don't have anything for actually monitoring what's going on 13:13:57 maybe I just read it like that by the way it was phrased 13:14:09 like, did the link actually fail and is in backup now? 13:14:18 it's all very thin 13:14:30 we might need multi hour meetings in brno... 13:15:30 okay, next? 13:15:50 #topic timers 13:17:42 harish__, your turn 13:18:03 oh sorry i lost connection in between 13:18:14 https://medium.com/@harishanand95/gsoc-week-4-timer-app-design-changes-caf1de4bfafa#.gsg2upxig 13:18:33 andreasn, i have updated the #4645 timers pr 13:18:49 https://github.com/cockpit-project/cockpit/pull/4645 13:18:51 I only saw the mockups so far, will try in action shortly 13:18:59 the changes looks good I think 13:19:22 okay. the changes were basically on making the inputs inside tables 13:19:36 which I think is what is followed throughout cockpit 13:20:01 yup 13:20:34 andreasn, please do test out invalid inputs as well 13:20:40 I will! 13:21:55 invalid input msgs causes changes in some elements positions 13:22:03 rest i think is okay 13:22:19 eot 13:23:40 okay 13:23:56 #topic fedora-24 via virt-builder 13:24:08 so Fedora 24 is out and virt-builder has templates for it 13:24:19 so we should use that instead of virt-install to make our images 13:24:23 I'll work on that 13:25:12 either way should be fine, but virt-builder is faster and much easier for others to reproduce, imo 13:25:40 eot 13:26:05 #topic vm-management 13:26:52 so, I'll begin by saying that I unfortunatley failed to build this still 13:27:08 but I'll keep poking at it 13:27:32 andreasn, let's build it together after the meeting 13:27:35 the PR is updated to recent master 13:27:49 thanks! 13:27:54 and I tryed to build it on top of fresh upstream/master clone 13:28:40 yeah, something is weird with my setup somehow 13:28:47 but we'll figure it out I'm sure 13:28:51 we'll succeed (I'm sure), anyway I can still send screenshots so it can give you clue 13:29:01 yeah, that's a good backup 13:29:51 more general question: how far is the webpack in other packages? 13:30:18 I'll align the VM management PR accordingly 13:31:18 mlibra, I think there is nobody here that can answer that 13:31:20 unfortunately 13:31:26 *who 13:31:28 mlibra: good progress. stef put up a pr last week with webpack stuff 13:31:32 hah 13:32:02 and lots of infrastructure that we need led for it landed as well (moving libraries around a bit, mostly) 13:32:30 how can I help? :-) 13:33:12 I think we're good for now thanks 13:33:26 once we have one or two in, we'll need help converting the other ones 13:33:38 but we're still figuring out how to do things 13:34:05 ok 13:36:57 I think that's it on VMs? 13:37:28 yes from my side 13:37:40 alright 13:37:56 yep I think so too 13:38:09 #topic other stuff 13:40:37 nothing from me 13:41:07 okay, thanks everyone! 13:41:10 #endmeeting