16:30:39 #startmeeting fedora_atomic_wg 16:30:40 Meeting started Wed Nov 29 16:30:39 2017 UTC. The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:30:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:40 The meeting name has been set to 'fedora_atomic_wg' 16:30:43 #topic roll call 16:30:47 .hello2 dustymabe 16:30:48 dustymabe: dustymabe 'Dusty Mabe' 16:30:52 .hello roshi 16:30:53 .hello2 16:30:53 roshi: roshi 'Mike Ruckman' 16:30:56 strigazi: strigazi 'Spyros Trigazis' 16:31:04 * coremodule is here! 16:31:07 .hello coremodule 16:31:08 coremodule: coremodule 'Geoffrey Marr' 16:31:32 hi coremodule :) 16:31:45 .hello sinnykumari 16:31:46 ksinny: sinnykumari 'Sinny Kumari' 16:32:49 .hello jberkus 16:32:50 jberkus: jberkus 'Josh Berkus' 16:32:51 .hello2 16:32:53 miabbott_: Sorry, but you don't exist 16:32:58 .hello walters 16:32:59 haha 16:32:59 walters: walters 'Colin Walters' 16:32:59 #chair strigazi roshi ksinny jberkus miabbott_ walters 16:32:59 Current chairs: dustymabe jberkus ksinny miabbott_ roshi strigazi walters 16:33:00 .hello miabbott 16:33:02 miabbott_: miabbott 'Micah Abbott' 16:33:21 * miabbott waves to roshi 16:33:22 * dustymabe wonders if we are missing jbrooks today 16:33:58 .hello rubao 16:33:59 rubao: rubao 'rubao' 16:34:10 #chair rubao 16:34:10 Current chairs: dustymabe jberkus ksinny miabbott_ roshi rubao strigazi walters 16:34:17 o/ miabbott :D 16:34:31 ok will get started in a minutes 16:34:41 sorta here 16:34:49 welcome puiterwijk 16:34:52 #chair puiterwijk 16:34:52 Current chairs: dustymabe jberkus ksinny miabbott_ puiterwijk roshi rubao strigazi walters 16:35:05 ok I'll get it started 16:35:10 #topic previous meeting action itmes 16:35:15 if I can spell :( 16:35:18 sigh. so I'm not going to have stats from the survey during the meeting 16:35:18 .hello2 16:35:19 maxamillion: maxamillion 'Adam Miller' 16:35:27 welcome maxamillion 16:35:32 encountered a docker bug, which ate my stats in progress 16:35:36 #chair maxamillion 16:35:36 Current chairs: dustymabe jberkus ksinny maxamillion miabbott_ puiterwijk roshi rubao strigazi walters 16:35:42 there's some kind of irony there 16:35:57 jberkus: is that the new "the dog ate my homework"? 16:36:06 ok here are the action items from last meeting 16:36:09 * jbrooks to retest asciibinder rpm 16:36:11 * jberkus to propose new quorum rules based on scheduled online votes 16:36:47 looks like jbrooks is not with us 16:36:54 #action jbrooks to retest asciibinder rpm 16:37:01 jberkus: any updates? 16:37:05 ok, for mine I;ve had zero mental energy to devote to it 16:37:15 realistically won;t be able to until after kubecon 16:37:31 if someone else wants to tackle it, please volunteer 16:37:59 jberkus: should we drop it from action items for now? 16:38:05 otherwise, reschedule for mid-dec 16:38:24 ok 16:38:31 moving on 16:38:39 #topic announcements 16:38:59 #info we now have updates available for fedora atomic workstation 16:39:23 woo 16:39:29 #info there is a candidate atomic host release for tomorrow (sent mailing list for details) 16:39:51 now that we have updates for FAW we should be able to publish that fedora magazine post 16:40:32 anyone with any other announcements? 16:41:06 ok tickets then 16:41:30 #topic help.md file for each container 16:41:38 .fas jasonbrooks 16:41:41 jbrooks: jasonbrooks 'Jason Brooks' 16:41:56 #link https://pagure.io/atomic-wg/issue/354 16:42:02 welcome jbrooks 16:42:10 sorry for lateness 16:42:21 o/ jbrooks 16:42:22 so for this ticket ashcrow and phracek were working on a solution 16:43:03 since ashcrow isn't around I'll punt to next meeting unless anyone else objects 16:43:50 welcome ashcrow :) 16:44:03 sorry, my fedora cal import says this starts in 15 minutes :-/ 16:44:08 current topic is https://pagure.io/atomic-wg/issue/354 16:44:37 * ashcrow nods 16:44:47 basically i'm willing to "let ashcrow run with it" on this one 16:45:00 Chatting seems to have died down in there and I'm happy to move it forward unless there is strong opposition 16:45:10 do you think you can take your proposal and make it happen? 16:45:38 dustymabe: yes, there may be some changes here and there but the general proposal should be doable 16:45:43 cool 16:46:08 #action ashcrow will take proposal in #354 and try to get the ticket resolved 16:46:15 ^^ acceptable? 16:46:19 yup 16:46:36 #topic Decide strategy for including container runtimes in Atomic Host 16:46:44 #link https://pagure.io/atomic-wg/issue/360 16:46:55 #info waiting on survey data from jberkus, should be coming real soon 16:47:06 dustymabe: per above, I was hoping to have some stats to present here, but a docker bug just ate my data and I'm starting over 16:47:16 k 16:47:48 i'm going to skip over the quorum tickets because you mentioned earlier you haven't had a chance to look at them 16:48:00 #topic Fedora version agnostic location for container images 16:48:05 #link https://pagure.io/atomic-wg/issue/376 16:48:19 #info we agreed last time the proposal in this ticket is valid 16:48:29 maxamillion has agreed to do the work. I'll remove meeting label. 16:48:38 \o/ 16:49:03 maxamillion: any chance you'll be able to complete that before you 'transition' 16:49:17 dustymabe: I've technically already transitioned 16:49:36 maxamillion: ahh. /me thought it wasn't until dec 16:49:52 everyone maxamillion is now talking to us from the 'afterlife' 16:49:57 dustymabe: yeah, not officially but I went over early so I can "come back" in Jan to help train someone who's taking over OSBS 16:50:22 it's called the afterlife now? 16:50:27 and he can 'come back' as well. sounds jesus-like 16:50:34 heh 16:50:41 badjokes 16:50:54 lol 16:50:58 lazarus 16:50:59 so. any idea on being able to complete this task? 16:51:20 or maybe show another of us some of the ropes and how to do it ourselves? 16:51:40 i have to admit this is one part I have not been involved in (intentionally because of everything else on my plate) 16:51:46 but would be good to have some more people involved 16:52:15 dustymabe: I'll try to get it done in the next couple days 16:52:15 Well, the management of the registry is going to transition to Bodhi. Current plan for that is before F28 GA 16:52:47 dustymabe: that's a good idea. Having more folks able to do handle stuff is rarely a bad thing 16:52:49 (the initial Bodhi code is actually already done, but now needs a bunch of other things due to rebuilds) 16:53:03 puiterwijk: that sounds nice 16:53:08 maxamillion: thanks 16:53:26 https://github.com/fedora-infra/bodhi/projects/2 16:53:38 #action maxamillion to try to implement the (hopefully trivial) work for #376 16:54:28 ok that's it for items 16:54:32 #topic open floor 16:55:01 jberkus: we should probably re-look at the articles we were going to post for f27 and see which ones of those are outstanding 16:55:07 and clean up the tickets in the repo 16:55:11 dustymabe: point 16:55:17 glad to see things still are still moving along :D 16:55:20 i also need to clean up some other things 16:55:25 dustymabe: the only ones still outstanding were the ones with external dependancies 16:55:28 roshi: :) you are missed 16:55:32 like AWS and FAW 16:55:41 :D thanks 16:55:41 there was one on azure too 16:55:41 woot! shameless self plug regarding atomic test days 16:55:45 and one on cockpit 16:55:55 oh, right 16:55:58 hiya coremodule :) 16:55:58 once I get my feet under me I expect to be able to contribute more 16:56:28 we're planning on running some test days here soon 16:56:28 * ksinny wants to discuss about growpart issue on aarch64 16:56:34 probably not before the first of the year 16:56:49 coremodule: how soon in the f28 cycle are you planning to run test days? 16:57:06 usually we have done right before or right after beta 16:57:14 but I just want to put some feelers out as to what you guys think should get tested 16:57:41 dustymabe, I was thinking an initial "alpha" test, then a few more after, but I don't want to shake things up too much if there's already a set way 16:57:58 we can do @beta 16:58:18 coremodule: ehh. i'm ok with whatever. we don't really have a set way, but I would like one around beta time. If we do more than one then I'm ok with doing more earlier as well 16:58:58 dustymabe, gotcha, I like the idea of more, more test days for more coverage, if you're cool with it. 16:59:09 coremodule: roshi should be of some help if we need any help/ideas 16:59:14 when is f28 beta? 16:59:40 coremodule: fine with me 16:59:49 for testdays? sure 16:59:52 march 13 for beta freeze 16:59:54 * jberkus also has an open floor item 16:59:55 https://fedoraproject.org/wiki/Releases/28/Schedule 16:59:57 I can at least proof pages and whatnot 17:00:03 ksinny: want to go ahead? 17:00:08 sure 17:00:11 the QA wiki is pretty clear on the steps 17:00:11 #link https://pagure.io/atomic-wg/issue/386 17:00:57 ksinny: what about? 17:00:59 growpart is part of cloud-utils package and in Fedora we have cloud-utils-0.27 17:01:01 just looking for any ideas on what might be good to test in a test day 17:01:13 ksinny: I think you linked to wrong issue? 17:01:23 dustymabe: I further digged into commits done between 0.27 and 0.28 of cloud-utils 17:01:34 anything new 17:01:40 is a good thing to test 17:01:52 coremodule: miabbott might be able to help us come up with a list 17:01:55 and it seems, fix lies in big commit done in http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/revision/267#bin/growpart 17:02:14 we do automated testing too, but it's always good to have users execute tests at least once or twice during a cycle 17:02:29 There are lot of changs done torelated to sfidsk and it seems difccult to figure out what might have fixed it 17:02:38 dustymabe: coremodule: happy to help out 17:02:45 sorry about wrong link 17:02:48 #link https://pagure.io/atomic-wg/issue/382 17:02:52 ksinny: no worries 17:02:55 dustymabe, miabbott, that would be great 17:03:25 dustymabe: I just wonder what would be best way here. can't we just update to newer cloud-utils? 17:03:35 ksinny: that depends on the maintainer 17:03:41 here is my suggestion 17:03:44 * ksinny don't know what all packages in fedora relies on growpart 17:03:53 .hello sayanchowdhury 17:03:54 sayan: sayanchowdhury 'Sayan Chowdhury' 17:03:56 we try to track down maintainer and suggest we move to newer version 17:04:04 that's option 1 17:04:06 option 2 17:04:16 we find what patch fixes issue and open pull request to dist-git repo 17:04:26 still needs maintainer 17:04:34 if maintainer is unresponsive we'll escalate the issue 17:04:41 ksinny: how does that sound? 17:04:44 dustymabe: any idea what is the IRC nick of mantainer? 17:04:49 dustymabe: so it's option 1, then if no response, option 2? 17:04:59 dustymabe: sounds fine to me 17:05:03 ashcrow: yeah. we can wait a day or two for option 2 17:05:08 SGTM 17:05:19 ksinny: i'll try to help you find IRC nick of maintainer 17:05:27 welcome sayan 17:05:29 dustymabe: that will be great 17:05:33 hi jberkus did you have an item? 17:05:37 * ksinny is done 17:05:44 yes 17:05:51 as I mentioned in the atomic-general meeting 17:06:19 we're going to have a new community manager, hired by Red Hat, involved with Fedora Atomic 17:06:26 jberkus: woot 17:06:32 awesome! 17:06:35 sanja actually attended last meeting 17:06:39 her name is Sanja Bonic 17:06:46 oh? damn 17:06:50 and I introduced her as someone who would be hanging around very soon 17:06:51 and I didn't because thanksgiving 17:06:54 ok 17:07:22 she's great! 17:07:27 can't wait to have her on board 17:07:37 anyway, lately I've been dividing my time between Atomic and Kubernetes 17:07:46 which has resulted in not enough time for anything 17:07:56 so Sanja and I will be splitting up responsibilities 17:08:25 she officially starts on Friday 17:08:49 I won't be in the meeting next week, though 17:08:54 fin 17:09:26 cool 17:09:28 thanks josh 17:09:36 anyone else with anything for open floor? 17:09:46 nothing from me 17:09:53 good here 17:11:05 cool 17:11:08 #endmeeting