14:00:54 #startmeeting weekly meeting 14:00:54 Meeting started Mon Feb 1 14:00:54 2016 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:54 The meeting name has been set to 'weekly_meeting' 14:01:01 .hello mvo 14:01:02 mvollmer: mvo 'Marius Vollmer' 14:01:37 .hello dperpeet 14:01:38 dperpeet: dperpeet 'None' 14:01:54 .hello stefw 14:01:55 stefw: stefw 'Stef Walter' 14:02:39 #topic Agenda 14:03:05 * new sink (low prio) 14:03:09 * Devconf presentation 14:03:44 * test image size (virtual machines) 14:03:58 * iscsi update 14:05:32 * weekly images 14:05:37 let's go 14:05:46 #topic Devconf presentation 14:06:06 i've added a folder here with some work on the Devconf presentation 14:06:06 https://github.com/stefwalter/cockpit-slides 14:06:17 and am waiting for contributions from Peter and Dominik for their parts of the slides 14:06:23 actually here: https://github.com/stefwalter/cockpit-slides/tree/master/devconf 14:06:50 since the tuned stuff landed, and now with mvollmer's work on weekly image updates 14:07:04 I'm working on writing and recording video, should have something to add soon 14:07:05 we're in a pretty good place to be talking about things that people would like to contribute to or interact with 14:07:18 I've updated the Hackfest tutorials so they work with the new CSP changes 14:07:30 I think I will add something on tuned later tonight or tomorrow morning 14:07:31 and i think we'll want to do a 0.94 release tomorrow to have things in good shape 14:07:58 dperpeet, are you thinking someone else will write the selinux related stuff? 14:08:13 stefw, no, that's coming too 14:08:27 oh good, i guess we should talk about whether we want to practice tomorrow 14:08:57 talk tomorrow or talk about practicing tomorrow? 14:09:12 actually practice 14:09:40 we can do that early tomorrow, if you wish 14:09:47 ok cool 14:10:15 the other thing remaining is that we need to give karma to https://bodhi.fedoraproject.org/updates/cockpit-0.93-1.fc23 14:10:51 i can post the commands used 14:10:52 if that helps 14:11:29 what is the rpmlint failure?' 14:11:32 I can't access the log 14:11:46 not sure 14:11:52 rpmlint always has broken failures 14:13:06 ok 14:13:19 that's probably it on that topic 14:14:08 nice multihost demo 14:14:20 #topic test image size (virtual machines) 14:14:34 I talked about this with mvollmer on irc 14:14:59 and we can reduce the sparse image size a bit, about 700MiB for f23 14:15:28 at the cost of increasing the non-sparse image size (reported size) 14:15:42 how does that look after compressing? 14:15:45 is this something we want to do? I believe so 14:15:54 I didn't check that 14:15:59 it shouild also help 14:16:06 since compression looks at everything 14:16:25 https://github.com/dperpeet/cockpit/commit/f40817fdd09a2aafb35510dc8c299a5be3a14bcd 14:16:34 it should be faster, at the least 14:17:02 mvollmer and I believe this is a good reason to port our setup scripts to be more modular 14:17:14 some already support that, they're in test/lib 14:17:16 yes 14:17:34 I wouldn't want to add libguestfs to the vm creation anymore 14:17:40 this should be inside the setup script, in my opinion 14:17:47 and a per configuration choice 14:18:35 no objections here. 14:18:47 ok 14:19:13 this is rather low priority, let me know if it becomes more important suddenly 14:19:16 end of topic 14:19:34 #topic iscsi update 14:19:47 so I have been poking at #2807 a bit 14:19:56 rebased, etc 14:20:12 the necessary versions of everything are in F23 updates-testing now 14:20:21 and the test passes 14:20:31 nice 14:20:42 storaged should go to fedora-23 stable any day now, I think. 14:21:07 https://bodhi.fedoraproject.org/updates/FEDORA-2016-6dcf004b0e 14:21:11 let's see what happens 14:21:21 the iscsi patch needs to go, too, I guess. 14:21:56 so I will be monitoring this 14:23:19 eot 14:23:30 #topic weekly images 14:23:52 we are pretty close to automatically making weekly images 14:24:00 yay on that 14:24:12 and it was nice to see the bots opening so many branches and pull requests last week 14:24:21 yup 14:24:23 i have been running this on my laptop, but the real test comes when we merge to master 14:25:19 the new sink has been deployed, so yeah, looks like we finally get this! :-) 14:25:35 let's see how this behaves in practice 14:25:51 how we deal with changes that need to go along with the new images, for example 14:26:17 well, I think we can probably cherry pick the commit and roll with it 14:26:30 and how fast we overflow our quota 14:26:41 quota can be added :) 14:26:51 well... 14:27:03 okay, a quick summary how this goes in practice? 14:27:18 when github-task decides to refresh a a image: 14:27:24 - opens a issue with "bot" label 14:27:30 - description has link to log 14:27:47 - when done with image or when it fails, adds a comment 14:27:55 - turns issue into pull request 14:28:04 - explicitly triggers some tests that are relevant 14:28:36 when image creation fails, the pull request is still created, with a deliberately broken image link 14:28:43 so all tests should fail quickly 14:28:44 the trigger is notable: e.g. a fedora 23 image will also trigger a fedora-atomic check 14:29:37 yeah, because fedora-atomic builds on fedora-23 14:29:56 i wasn't sure when to trigger the "image/..." tests 14:30:05 do they use any of the regular images? 14:30:42 i think so 14:30:45 we need to rename those 14:30:55 otherwise they get confusing 14:31:04 even though it was nice to call them container "images" 14:31:10 they're really better called "containers" 14:31:36 yeah, that's what the test dir is called anyways 14:32:03 they use fedora-23 built rpms 14:32:10 should we move the old tests into a directory as well? 14:32:33 mv check-verify verify/run-tests 14:33:19 I think this would make sense 14:33:49 better grouping than filename magic 14:34:06 yeah 14:34:22 okay, I can take that action point 14:35:10 #action mvo to move old 'verify' tests into their own directory 14:35:55 okay, next? 14:36:17 hmm, nothing left, really. 14:36:21 #topic new sink 14:36:29 so there is a new sink version 14:36:39 and master will start using the new API soon 14:36:44 I hope :-) 14:37:17 now the sink can make pretty arbitrary REST requests to github 14:37:21 which is pretty cool 14:37:45 so if you are using your own sink, you need to update it 14:38:14 now all we need to do is get rid of the badge-related code 14:38:20 yeah 14:38:50 monitoring github would be more consistent than hijacking the logging service 14:38:58 with the rest of Cockpit 14:39:11 and as stefw said, it would be nice to use http://shields.io/ 14:39:41 so, we want a service that takes a github url to a commit and a context and returns a badge png, right? 14:39:56 (it also takes some text, color etc for the badge I guess) 14:40:48 yeah, and either scanning or with github hooks 14:40:57 can we cobble together something on fedorapeople ourselves? 14:41:27 hmm, why scanning? 14:41:40 to go from "master" -> sha1? 14:41:42 github hooks are preferable 14:41:51 that get called when master changes 14:41:57 or we have results 14:42:11 I think we can push this issue back a bit 14:42:19 yes 14:42:21 and discuss it when it's implementation time 14:45:41 here is an issue that should soon turn into a pull request: https://github.com/cockpit-project/cockpit/issues/3651 14:46:00 half of the time is spent compressing and uploading the image 14:46:06 with no visible progress 14:46:11 we could improve that, too 14:46:34 it's probably a question of flushing 14:46:38 among other things 14:46:49 also, let's see how the real CI machines do this 14:47:02 they hopefully have a fatter pipe to our image store 14:48:45 #topic open floor 14:50:18 Be sure to give karma to: https://bodhi.fedoraproject.org/updates/cockpit-0.93-1.fc23 14:50:39 already on it 14:51:52 it's stable 14:52:08 or rather, it has enough karma 14:58:17 okay 14:58:20 #endmeeting