16:59:36 #startmeeting fedora_cloud_wg 16:59:36 Meeting started Wed Aug 31 16:59:36 2016 UTC. The chair is trishnag. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:59:36 The meeting name has been set to 'fedora_cloud_wg' 16:59:37 scollier, yet to start :) 16:59:41 #topic Roll Call 16:59:48 .hellomynameis kushal 16:59:48 .hello scollier 16:59:49 kushal: kushal 'Kushal Das' 16:59:50 .hello trishnag 16:59:52 scollier: scollier 'Scott Collier' 16:59:55 trishnag: trishnag 'Trishna Guha' 16:59:58 .hello mmicene 16:59:59 nzwulfin: mmicene 'Matt Micene' 17:00:11 .hello jberkus 17:00:12 jberkus: jberkus 'Josh Berkus' 17:00:19 .hello jasonbrooks 17:00:19 .hello bowlofeggs 17:00:20 jbrooks: jasonbrooks 'Jason Brooks' 17:00:23 bowlofeggs: bowlofeggs 'Randy Barlow' 17:00:32 .hello vvaldez 17:00:35 vvaldez: vvaldez 'Vinny Valdez' 17:00:55 #chair kushal scollier nzwulfin jberkus bowlofeggs jbrooks dustymabe vvaldez sayan rtnpro 17:00:55 Current chairs: bowlofeggs dustymabe jberkus jbrooks kushal nzwulfin rtnpro sayan scollier trishnag vvaldez 17:01:31 #topic rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:01:34 .hello sayanchowdhury 17:01:36 sayan: sayanchowdhury 'Sayan Chowdhury' 17:01:43 .hello walters 17:01:44 walters: walters 'Colin Walters' 17:01:56 .hello maxamillion 17:01:57 maxamillion: maxamillion 'Adam Miller' 17:02:02 #chair walters maxamillion gholms 17:02:02 Current chairs: bowlofeggs dustymabe gholms jberkus jbrooks kushal maxamillion nzwulfin rtnpro sayan scollier trishnag vvaldez walters 17:02:13 Hi vvaldez 17:02:15 * gholms waves hello 17:02:26 Hi everyone :) 17:02:28 * vvaldez waves at scollier 17:02:45 #topic Action items from last meeting 17:02:48 .fas rtnpro 17:02:49 rtnpro: rtnpro 'Ratnadeep Debnath' 17:03:01 #topic rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:03:19 rtnpro: Any update on this? 17:03:28 I started working on the test cases for fedora motd using tunir 17:04:04 okay 17:04:11 It's work in progress, and I need to discuss with kushal on how to write some test cases, e.g., assert the motd message after ssh login, etc 17:04:24 I will take this week to complete it 17:04:35 17:04:50 trishnag, you can add the action back again on me 17:04:57 rtnpro: you can add me in regarding test :) 17:04:59 was the concern about not triggering an update if one hasn't been initiated before been addressed? 17:05:00 if e.g. my systems require a proxy server, and i'm booting up a cloud VM to ssh into it the first time via ansible, we shouldn't try an update that isn't using the proxy 17:05:06 trishnag, cool 17:05:11 trishnag++ 17:05:11 rtnpro: Karma for trishnag changed to 13 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:05:15 okay 17:05:38 #action rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:05:49 is this how action works? 17:06:02 yep 17:06:06 ok :) 17:06:25 #topic gholms to test updated cloud-init on f24 for f25 17:06:38 gholms: this is for you 17:06:53 #info cloud-init 0.7.7 now in rawhide, needs testing on more clouds than I have access to 17:07:08 I only have eucalyptus and AWS. 17:07:13 gholms, I am guessing you already tested on AWS, and on EUCA 17:07:17 yup. 17:07:18 #info It's also in f25 updates-testing 17:07:31 gholms, I will try to test on openstack 17:07:40 Yeah, but I tried it on f24 because 25 didn't boot. 17:07:42 But only on Monday 17:07:50 gholms, Okay. 17:07:58 #action kushal to test new cloud-init on openstack 17:08:16 kushal: can I help with that? 17:08:17 I'm a little bummed about this bootloader stuff, but... yeah. 17:08:34 if you mean extlinux, we figured it out. 17:08:36 sayan, I will ping you 17:08:37 gholms, thanks 17:09:20 That's all I have for that topic. 17:09:21 Thanks 17:09:24 ok 17:09:31 rtnpro: Do you want to say anything on walters query? 17:10:49 trishnag, you can go ahead, he may have slept. 17:10:52 ok moving forward 17:10:57 #topic vvaldez to talk with misc, scollier, jberkus about how he can help with FOSP (#153) 17:11:11 vvaldez: Any update? 17:11:24 #chair misc 17:11:24 Current chairs: bowlofeggs dustymabe gholms jberkus jbrooks kushal maxamillion misc nzwulfin rtnpro sayan scollier trishnag vvaldez walters 17:11:26 trishnag: we had a meeting about FOSP setup before LinuxCon. I don't know if there's been any changes since 17:11:42 we've been mailing on a thread back and forth but so far I haven't had any specific contributions yet, there is an update to #153 since last week 17:11:48 no news since last status 17:11:55 one issue is getting the complete set of Fedora-based OS containers tested so that the infra team will use them 17:12:11 misc, are you deploying Origin yet? 17:12:15 which I'll take a stab at as soon as I have HW again (cluster is down) 17:12:17 misc, or still working on infra playbooks? 17:12:25 scollier: we do deploy but it fail 17:12:35 misc, ah, i didn't realize you were that far. 17:12:45 scollier: https://github.com/openshift/openshift-ansible/issues/2294 17:12:49 #link https://fedorahosted.org/cloud/ticket/153 17:13:01 so I got a update on the ansible bug 2h ago, will fix my proposed patch 17:13:06 that's the latest issue misc linked 17:13:56 misc, ack. 17:14:10 (in fact, i may likely fix before the end of the meeting) 17:14:39 ok moving to the next 17:14:53 #topic #125 Fedora-Dockerfiles examples for Kubernetes 17:15:03 #link https://fedorahosted.org/cloud/ticket/125 17:15:21 scollier: jberkus This is for you 17:15:47 OK if I take the meeting tag off that one? It's still on my TODO list, but having it in the meeting every week isn't useful 17:16:47 jberkus: ok so I am moving to the next one 17:17:06 #topic #136 vagrant boxes fixups 17:17:10 #link https://fedorahosted.org/cloud/ticket/136 17:17:11 jberkus: right, removing the tag would be better 17:17:34 kushal: Update on this one? 17:18:04 why me? 17:18:06 that belongs to imcleod 17:18:10 :) 17:18:22 oh he is not here now 17:19:01 moving forward 17:19:28 #topic #147 Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 17:20:15 I need to update that ticket, but I've posted to the mailing list about this, I have a patch in for the releng script and I need to get a patch in for the websites team (waiting on a response for some guideance though) 17:20:57 here's the mailing list thread https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/RIVZOYPJSMTMQXHKXIWNTSWQ2CQAPNXC/ 17:21:43 maxamillion: okay 17:21:50 seems dustymabe is not around 17:22:27 https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/RIVZOYPJSMTMQXHKXIWNTSWQ2CQAPNXC/ 17:22:41 trishnag, yes, he is busy (as informed in the channel). 17:22:58 ticket updated 17:23:09 maxamillion: thanks 17:23:12 kushal: okay 17:23:26 moving next 17:23:51 We can ignore #153 as it is already discussed 17:23:57 #topic #154 make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 17:24:11 jberkus: Any update here? 17:24:30 feh, no, I'll get on that this week. 17:24:38 sorry, too much conference travel 17:25:06 okay 17:25:20 #topic #155 Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 17:25:44 jbrooks: Any update on this? 17:26:06 maxamillion has a proposal for this on the rel-eng list, he's looking for +1's 17:26:14 i'd like to pull in the ADB more as a primary option too 17:26:28 (at some point do an ADB-using-AH too) 17:26:29 I replied LGTM, but I think he's looking for releng affirmation 17:26:35 walters: ADB? 17:26:38 jbrooks: +1 17:26:56 maxamillion, the upstream of CDK. 17:26:59 kushal: ah 17:27:01 maxamillion, https://github.com/projectatomic/adb-atomic-developer-bundle 17:27:05 walters: +1 thanks 17:27:06 (the name is confusing) 17:28:23 okay we can move to the next one 17:28:30 #topic #156 Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 17:28:48 jberkus: This one is for you :) 17:28:54 those are written, just being reviewed, per update 17:29:05 walters: yeah, I see ADB and think of Android :) 17:29:33 walters: (not entirely relevant, but for reference https://developer.android.com/studio/command-line/adb.html) 17:29:45 yeah 17:30:21 jberkus: okay 17:30:33 moving forward 17:30:39 #topic #160 Ship fedora-motd in F24 atomic image https://fedorahosted.org/cloud/ticket/160 17:30:51 I think we just discussed this. kushal ^ 17:31:09 yeah 17:31:16 cool 17:31:36 #topic #167 Decide a process about failed tests for Autocloud https://fedorahosted.org/cloud/ticket/167 17:31:48 kushal: Update on this one? 17:32:09 I just did few hours back. 17:32:16 We need comments from others. 17:32:24 I have a related item. 17:32:33 Like https://bugzilla.redhat.com/show_bug.cgi?id=1353688 17:32:36 walters, ^^ 17:32:52 this is failing for some time, should we have this test as release blocker or not. 17:33:31 commented 17:33:37 walters, thank you. 17:34:09 walters, Thanks once again. 17:34:10 i tend to be most concerned about regressions but it does seem valid to make it a blocker 17:34:11 yeah this will make all atomic images fail 17:34:30 walters, Okay. 17:35:26 Can others please comment to https://fedorahosted.org/cloud/ticket/167 ? 17:35:41 kushal: +1 17:35:51 kushal: sure 17:36:21 okay moving forward 17:36:44 #topic #168 Put OpenShift Origin in Container with Fedora Base https://fedorahosted.org/cloud/ticket/168 17:36:58 scollier: This is for you. 17:37:02 trishnag: regarding 167 17:37:15 we need a way to decide on release blockers which DOESN'T wait for this weekly meeting 17:37:15 jberkus, yes please :) 17:37:20 jberkus: yes 17:37:34 right now, if we hit a release blocker, nothing happens until Wednesday 17:37:43 jberkus, We are going to add fedora-cloud to the issue tracker 17:37:55 so that we get the mails for all failures 17:38:06 kushal: nice 17:38:13 jbrooks: likely so, yes 17:38:17 yah -- however, my experience is that folks don't necessarily read fedora-cloud. so we're going to have to start reading/responding to that 17:38:26 reading 17:38:46 maxamillion: do we have an ability to push stuff to IRC? 17:38:53 trishnag, , i updated the ticket. i think it can merge with what maxamillion is doing, we just won't block on the system containers. 17:38:57 sayan, ^^^ 17:39:18 scollier, Okay, this is more for the host (qcow2, vagrant images) etc 17:39:34 kushal, not for the ticket that trishnag pinged me about. 17:39:43 oops 17:39:46 sorry 17:39:55 kushal: jberkus: I am not sure, but this is something I can look into 17:39:57 scollier: okay. thanks for the update 17:40:19 sayan: if not, IRC bots are simple. the hard part is how do I pull the info that we're blocked? 17:40:21 jberkus: "push stuff to irc"? ... you mean have a bot do notifications or somethign? 17:40:29 maxamillion: yeah, and set the /topic 17:40:46 jberkus, that sounds better, as I do not stay on IRC all the time 17:41:22 jberkus: probably with zodbot somehow, what did you have in mind? 17:41:59 maxamillion: whenever we have a blocker bug, we should (a) sent a notice to fedora-cloud IRC, and (b) change the topic with a link to the bug 17:42:06 a lot of us are logged into that channel all the time 17:42:20 and this team is better about responding to IRC than mail 17:42:25 jberkus: what happens when there are more than one blocker bug? would it queue them or bump the latest? 17:42:36 or if we can do .failure zodbot which will list down notifications? 17:42:37 maxamillion: whatever is easier 17:42:50 maxamillion: we make the fight, and the most blocking win 17:42:54 them 17:42:54 like it happens for .pull zodbot or something that shows recent PRs 17:43:56 misc, :) 17:44:30 jberkus: that's not what I'm asking, we need specific definitions of what is requested ... we as a group are really bad about ambiguous requests and then having rip out a bunch of code because of misunderstandings or miscommunications ... let's draft up an actual requirements specification and someone can then make sure the solution satisfies that specification 17:44:40 maxamillion: sure! 17:45:25 +1 maxamillion 17:45:37 +1 17:45:40 maxamillion, +1 17:45:49 alright, who's going to take on the task of writing the requirements specification? 17:45:54 #action draft spec for IRC bot for blocker bugs 17:46:01 feh, wrong syntac 17:46:09 Is there an example to consult? 17:46:09 #undo' 17:46:10 Removing item from minutes: ACTION by jberkus at 17:45:54 : draft spec for IRC bot for blocker bugs 17:46:10 maxamillion: I'll draft an issue 17:46:22 #action jberkus will draft spec for IRC bot for blocker bugs 17:46:23 jberkus: thanks 17:46:34 kushal: thanks :) 17:47:01 I'll need people to look at it before next week, though, please 17:47:06 will post to fedora-cloud 17:47:26 My laptop battery will die before this meeting :( 17:47:53 #topic Open Floor 17:48:29 I am planning to move the testing part of fedimg where it tests the AMIs to AutoCloud 17:48:40 Nice 17:48:43 I will send a detail plan for the implementation over the mailing list 17:48:53 sayan: +1 17:49:10 sayan, +1 17:49:26 I did a release of fedimg==0.7, which makes it compose-based 17:49:40 I am yet to deploy it. 17:50:12 That's all from my side :) 17:50:37 sayan: Thanks. 17:50:46 I guess I haven't missed any ticket :) 17:50:48 we need to finish the new cloud/atomic PRD 17:50:56 jberkus: +1 17:51:53 sayan++ 17:51:53 maxamillion: Karma for sayanchowdhury changed to 11 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:52:47 kushal, can you take this one? 17:53:19 jberkus, I plate is full, I can comment, but can not write/add things for now. 17:53:59 i have a lot of open questions about the WG rename and all of that but it's a bit more than an open floor topic 17:54:52 walters, feel free to send those the list, so that mattdm can also join in. 17:55:06 walters: I'm still not sure the WG is being renamed 17:55:12 discussion is on Council 17:55:34 jberkus, Oh, I never knew that part. 17:57:48 ok ending the meeting then 17:57:55 5 17:57:57 4 17:58:01 3 17:58:02 2 17:58:02 thanks trishnag 17:58:04 1 17:58:07 #endmeeting