17:00:12 #startmeeting fedora_cloud_wg 17:00:12 Meeting started Wed Sep 7 17:00:12 2016 UTC. The chair is trishnag. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:12 The meeting name has been set to 'fedora_cloud_wg' 17:00:22 #topic Roll Call 17:00:32 .hellomynameis kushal 17:00:33 kushal: kushal 'Kushal Das' 17:00:37 .hello maxamillion 17:00:38 maxamillion: maxamillion 'Adam Miller' 17:00:39 .hello trishnag 17:00:41 trishnag: trishnag 'Trishna Guha' 17:00:42 .hello tflink 17:00:42 .fas rtnpro 17:00:47 .hellomynameis sayanchowdhury 17:00:47 tflink: tflink 'Tim Flink' 17:00:50 rtnpro: rtnpro 'Ratnadeep Debnath' 17:00:53 sayan: sayanchowdhury 'Sayan Chowdhury' 17:00:58 .hello vvaldez 17:00:59 vvaldez: vvaldez 'Vinny Valdez' 17:01:20 #chair kushal rtnpro sayan vvaldez maxamillion tflink jberkus 17:01:20 Current chairs: jberkus kushal maxamillion rtnpro sayan tflink trishnag vvaldez 17:02:06 Should we wait for few minutes? 17:02:21 trishnag, yes, let us wait for 1 minute :) 17:02:27 sure :) 17:03:16 .hello jberkus 17:03:17 jberkus: jberkus 'Josh Berkus' 17:03:42 #topic Action items from last meeting 17:03:55 #topic rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image 17:04:13 yeah 17:04:14 .hello smilner 17:04:17 ashcrow: smilner 'None' 17:04:22 .hello bowlofcloud 17:04:23 bowlofeggs: Sorry, but you don't exist 17:04:27 .hello dustymabe 17:04:27 .hello bowlofeggs 17:04:27 dustymabe: dustymabe 'Dusty Mabe' 17:04:30 bowlofeggs: bowlofeggs 'Randy Barlow' 17:04:43 so, I had a fair amount of success to run the test cases manually using tunir 17:04:57 #chair bowlofeggs dustymabe ashcrow 17:04:57 Current chairs: ashcrow bowlofeggs dustymabe jberkus kushal maxamillion rtnpro sayan tflink trishnag vvaldez 17:05:04 I was also able to find out a way to log the motd messages on SSH login 17:05:25 however, this will require me to run the test cases remotely on the atomic VM 17:05:50 currently, tunir does not allow running remote commands on the VM 17:06:16 I spoke to kushal on that and he has a plan to implement HOST command to support that 17:06:43 rtnpro, on another note, can you find that out by sshing into the same box from the vm? 17:06:46 I've volunteered to work on this tunir feature 17:06:47 that will be faster :) 17:06:54 .hello jasonbrooks 17:06:55 jbrooks: jasonbrooks 'Jason Brooks' 17:07:01 #chair jbrooks 17:07:01 Current chairs: ashcrow bowlofeggs dustymabe jberkus jbrooks kushal maxamillion rtnpro sayan tflink trishnag vvaldez 17:07:01 rtnpro++ 17:07:01 dustymabe: Karma for rtnpro changed to 3 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:07:53 kushal, that will require me to copy the private key file 17:08:12 rtnpro, create a temporary key inside the vm 17:08:23 kushal, yeah, that can be done 17:08:24 and copy it to authorized_keys 17:08:35 kushal, sounds like a work around 17:08:36 rtnpro, that we can test it in our current system only 17:08:46 kushal, cool, sounds like a plan 17:09:15 so, I will write the test cases and push to git for others to review 17:09:20 that's all from me 17:09:49 rtnpro: Shall I add it to action item? 17:09:56 trishnag, yes 17:09:59 okay 17:10:43 #action rtnpro to write testcases for testing fedora-motd on F24 atomic image and push to git for others to review 17:11:10 #topic kushal to test new cloud-init on openstack 17:11:12 I could not work on it yesterday, will try to look into it this week. 17:11:24 readd the action item 17:11:41 kushal: okay 17:12:25 kushal: I am adding to action again. 17:12:45 #action kushal to test new cloud-init on openstack 17:13:07 #topic jberkus will draft spec for IRC bot for blocker bugs 17:13:23 trishnag: yeah, so there's a ticket for this 17:13:29 yeah let me find it 17:13:53 https://fedorahosted.org/cloud/ticket/169 17:14:01 I've only gotten a little bit of feedback on it 17:14:15 I'd like any comments from this team if the essential spec is correct 17:14:55 jberkus, 2 points. 17:15:25 jberkus, When we say blocker bug, we mean blocker for Atomic 2 Week release, those bugs are different than the blocker bugs for acutal Fedora release. 17:16:04 jberkus, so when bugyou file automated bugs, it files for 2WA in pagure, but not in bugzilla. 17:16:26 So, we have to make it clear to others. 17:16:33 kushal: ok, can you add that to the ticket? 17:16:40 I will, wanted to update here first. 17:16:41 jberkus: that looks like a good start 17:17:03 we still need to make sure we have people that are going to track down the issues 17:17:12 and get them fixed or find someone who can fix them 17:17:13 Then do you want to have the bot adding all the current failed bugs in the channel topic? (just a question). 17:17:35 IMO the bot is only a band-aid 17:17:40 yeah 17:17:42 kushal: all the bugs? no, just the ones that block release 17:18:10 sayan, can you please how bugyou handle bugs? 17:18:41 just as a side note, according to my datagrepper query, there were no successful vagrant libvirt images in the last two weeks which is why we didn't release Two Week Atomic yesterday 17:19:05 yeah, that's exactly the kind of thing which should be in our face ... 17:19:34 jberkus, maxamillion yes, https://bugzilla.redhat.com/show_bug.cgi?id=1353688 is the cause 17:19:39 yeah that is because the journal logging issue I guess 17:19:43 maxamillion: I don't see an email to cloud@ about that 17:19:45 That is failing our automated tests. 17:19:55 jberkus: there wasn't one 17:20:04 jberkus: I forgot 17:20:05 bugyou has a autocloud plugin that handle the failed messages 17:20:19 jberkus: I meant to this morning and got side tracked ... I'll get an email out soon 17:20:34 maxamillion: I was thinking more an automated email ... 17:20:37 and the successfull messages and then it updates pagure automatically 17:21:16 jberkus: we have an automated mail for success ... I'll add a patch to send an automated failure message, this script wasn't meant to have all these features because it was supposed to have been replaced by now but we just keep duct taping things on the side instead 17:21:31 maxamillion: what's holding up the replacement? 17:21:47 jberkus: https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkflowEngine 17:21:50 On the journal bug, there was this https://pagure.io/fedora-atomic/c/9c4b3cb0e437de9af14d7134a58c5caf04eaa308?branch=f24 17:22:07 But maybe there hasn't been a new stable pkg, so there hasn't been a new tree made? 17:22:12 jberkus: it's in flight, but behind schedule because of atomic and osbs taking up so much time 17:22:56 Only new pkgs from bodhi trigger a new tree compose, as far as I can tell 17:23:31 maxamillion: well, given that I'd say let's defer non-essential changes 17:23:41 including this oje 17:23:43 one 17:23:48 jberkus: alright 17:24:43 maxamillion: I'll throw together a triage on the wiki? Kushal, can you help with this? Or someone else? 17:25:06 jberkus, Okay 17:25:57 and in the meantime, if someone could share how we search for failures 17:26:03 jberkus, btw, https://github.com/kushaldas/tunirtests/issues/48 17:26:05 a few of us will need to do that manually, every day 17:26:30 jberkus, we are asking pagure upstream so that we can send out mails to cloud list on failed automated tests 17:26:37 jberkus, meanwhile you can just have a look at https://apps.fedoraproject.org/autocloud/jobs 17:26:42 ok 17:27:06 jberkus: +1 17:28:37 Should we move forward? 17:28:41 yes 17:28:49 ok 17:29:02 #topic vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 17:29:31 jberkus, btw, https://pagure.io/pagure/issue/1258 is the ticket for getting mails in the list 17:30:06 Looks like imcleod is not here. 17:30:21 yeah i think imcleod has new responsibilities 17:30:30 if anyone else wants to pick this up that would be great 17:30:35 praveenkumar, and lalatenduM is supposed to be the new upstream 17:30:35 or I guess we can just drop it 17:30:39 s/is/are 17:30:49 yeah, but they are probably swamped as well 17:31:01 dustymabe, yes :) 17:31:59 trishnag, move ahead please :) 17:32:04 * kushal has two major open floor topics 17:32:04 kushal: okay :) 17:32:09 #topic Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 17:32:22 dustymabe: This is for you. 17:33:38 kushal: is that ticket targeting the new infra, or the old? 17:34:18 jberkus, that is to send out mails for failed tests in autocloud, bugyou files/comments on pagure for fails 17:34:30 ah, it's a paguire issue. ok 17:34:32 trishnag: that's on me, I have a pull request in and it's merged ... we should be able to close that ticket next successful release of Atomic 17:34:48 Two-Week Atomic Host * 17:35:00 maxamillion: okay Thanks 17:35:17 kushal, it'd be nice to have it hooked up to fedora notifications, autocloud, that is -- unless I'm just missing it? 17:35:38 maxamillion, awesome 17:35:55 #topic design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 17:36:01 jbrooks, it is hooked into fedmsg (if you are asking about that), after meeting sayan will help you out with that. 17:36:22 jberkus: this one is for you :) 17:36:23 kushal, ok, I'll ping, I'm just not seeing it in the list of rules 17:36:24 trishnag: scollier isn't here, and i have no updates on that due to ContainerCon 17:36:47 I'll have to follow up with scollier offline and find out where we are; there was a blocker, but not sure if it got resolved 17:37:13 jberkus: okay 17:37:32 jberkus: if the blocker is install related and not hardware/infra, let me know how I can help unblock 17:37:44 jdetiber: thanks! 17:38:11 okay moving to next 17:38:16 #topic make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 17:38:29 On this topic. 17:38:56 robyduck from the websites team needs to know when do we want to move to atomic as the default WG download page. 17:39:06 So that all the improvements can go in there,. 17:39:28 jberkus, we also have mizmo here, she can answer our queries related to design. 17:39:29 we do, don't we? 17:39:39 * mizmo waves 17:40:27 jberkus, Yes, we do. 17:40:28 * dustymabe waves 17:40:56 jberkus, but there has to be new work done to have a persistent URL for 2WA download URL 17:40:57 etc 17:41:04 So, they need a plan for us. 17:41:06 2WA? 17:41:11 2 week atomic 17:41:13 2 Week Atomic 17:41:16 ah, ok 17:41:27 jberkus, sorry for the short form. 17:41:30 so, I know what I want to see from a user perspective, but I don't know the technical requirements 17:41:37 who does? 17:42:18 jberkus, there is a thread currently in the websites list 17:42:35 jberkus, also about making the page clear, you can talk to mizmo about your ideas. 17:43:14 * mizmo really needs copy for the new site 17:43:14 eg 17:43:15 https://github.com/fedoradesign/nextweb-assets/blob/master/Mockups/Brochure%20Site/brochure-mock-atomic_WIP.png 17:43:24 "$CHANGEME" hehe 17:44:41 mizmo: hmmm, can we talk about this later? 17:44:51 mizmo: set up a chat or something? 17:44:59 jberkus, sure 17:45:53 okay moving to the next topic 17:46:01 #topic Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 17:46:21 wait so no plan for websites? 17:46:46 Sorry mizmo 17:46:52 #topic make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 17:46:57 mizmo: next step is to have a content discussion 17:47:03 mizmo: what TZ are you? 17:47:10 i think the schedule discussion has to happen independent of that 17:47:27 bc if you guys want it for f25 ga theres not a whole lot of time 17:47:34 ah, ok 17:47:49 im east coast but robyduck who is the websites lead is in europe (rome i think) 17:47:53 mizmo: how's your availability today? 17:48:03 or does he need to be included? 17:48:12 trishnag, no update on this I guess, we can move on. 17:48:13 im free after 3 17:48:23 he should be included for scheduling but for content im sufficient 17:48:26 kushal: okay 17:49:46 #topic Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 17:50:09 jberkus: update on this? 17:50:16 trishnag: in review right now 17:50:22 jberkus: cool 17:50:26 I need to make some technical changes and retest 17:50:55 jberkus, can I pass the whole network config (static) in that kickstart file? 17:51:05 Then I can actually use it. 17:51:18 kushal: not sure; that's beyond my experience. dustymabe ? 17:51:50 * lalatenduM reading the logs 17:51:58 kushal: somehow you'd need a network to get the KS file in the first place 17:52:15 Oh yeah, not helpful for me then :( 17:52:43 I was trying to boot with the ks file on the USB key, but I ran into issues with EFIboot I couldn't figure out 17:52:54 kushal: you can pass information about network setup 17:53:07 dustymabe, okay, I will ask more later after meeting. 17:53:17 you probably need to provied them on the command line though 17:53:18 trishnag, we can move on :) 17:53:21 dustymabe, Okay. 17:53:22 not in the kickstart 17:53:28 dustymabe, Okay. 17:53:28 kushal: sure :) 17:53:39 dustymabe, good to know that there is an option. 17:53:46 #topic Decide a process about failed tests for Autocloud https://fedorahosted.org/cloud/ticket/167 17:53:55 kushal: dustymabe ^ 17:54:39 We are working to get the mails to the cloud list for that/ 17:54:49 Also the IRC bot as discussed before. 17:55:05 kushal: okay thanks 17:55:12 we can move on then 17:55:32 Ignoring #168 https://fedorahosted.org/cloud/ticket/168 since scollier is not here. 17:55:51 #topic Finish new Fedora Cloud PRD https://fedorahosted.org/cloud/ticket/170 17:56:08 Could not look into that :( 17:56:12 We need more help. 17:56:23 Looks like no one is assigned to this. 17:56:52 any notes from flock? 17:57:14 jberkus: ^ 17:57:15 it didn't get discussed at flock, they ran out of time 17:57:28 Only note was about changing name. 17:57:29 yah, otherwise it would be done 17:58:10 okay we are running out of time. 17:58:14 #topic Open Floor 17:58:19 I have a point. 17:58:29 I will start testing out to move our trac into Pagure. 17:58:42 in advance of osbs being ready, do we have any official fedora images other than the base image? 17:58:50 kushal: sounds good 17:58:54 2017-02-28 is the deadline of closing of fedorahosted. 17:59:03 If anyone has a project there, move :) 17:59:41 that is it from my side. 18:00:04 I have one. 18:00:07 Does anyone want to discuss about this https://github.com/kushaldas/tunirtests/pull/43 ? 18:00:19 dustymabe: ^ 18:00:24 I guess we are out of time. 18:00:32 kushal: moving trac into pagure? 18:00:34 trishnag, we can do this over a mail in the list 18:00:37 kushal: okay. I will start a thread then :) 18:00:44 dustymabe, yes, 2017-02-28 is the sunset date for the trac. 18:00:53 does trac solve the need we have for fedora cloud? 18:00:57 nirik, announced it few minutes back. 18:01:14 i mean does pagure sole the issues we have? 18:01:17 ok, let's take this to #fedora-cloud 18:01:24 yes 18:01:25 3 18:01:26 2 18:01:28 1.4 18:01:29 #endmeeting