17:04:49 #startmeeting fedora_cloud_wg 17:04:49 Meeting started Wed May 11 17:04:49 2016 UTC. The chair is jberkus. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:04:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:04:49 The meeting name has been set to 'fedora_cloud_wg' 17:04:58 #topic roll call 17:05:06 .hellomynameis kushal 17:05:07 kushal: kushal 'Kushal Das' 17:05:25 .hello mmicene 17:05:26 nzwulfin: mmicene 'Matt Micene' 17:05:36 .hello trishnag 17:05:37 trishnag: trishnag 'Trishna Guha' 17:05:41 .hello tflink 17:05:42 tflink: tflink 'Tim Flink' 17:06:12 .hellomynameis dustymabe 17:06:13 dustymabe: dustymabe 'Dusty Mabe' 17:06:19 * dustymabe saying hello from vacation land 17:06:45 .fas rtnpro 17:06:45 rtnpro: rtnpro 'Ratnadeep Debnath' 17:07:44 #chair kushal dustymabe nzwulfin trishnag tflink rtnpro 17:07:44 Current chairs: dustymabe jberkus kushal nzwulfin rtnpro tflink trishnag 17:08:18 .hellomynameis sayanchowdhury 17:08:19 sayan: sayanchowdhury 'Sayan Chowdhury' 17:08:52 .hello maxamillion 17:08:56 maxamillion: maxamillion 'Adam Miller' 17:09:05 #chair maxamillion 17:09:05 Current chairs: dustymabe jberkus kushal maxamillion nzwulfin rtnpro tflink trishnag 17:09:13 #chair sayan 17:09:13 Current chairs: dustymabe jberkus kushal maxamillion nzwulfin rtnpro sayan tflink trishnag 17:09:40 ok, action items from last meeting: https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_wg/fedora_cloud_wg.2016-05-04-17.02.txt 17:09:48 in order 17:10:00 * jberkus jberkus to update ticket 115 with current status: DONE 17:10:17 * jberkus kushal to associate the items to owners in ticket 143 17:10:20 kushal? 17:10:37 jberkus, I missed that, worked on the test day mostly. 17:10:41 for the testday 17:10:46 ok 17:10:56 #action: kushal to associate the items to owners in ticket 143 17:11:06 did that work? 17:11:12 #action kushal to associate the items to owners in ticket 143 17:11:15 feh 17:11:49 can someone help me out here? these commands aren't well-documented ... 17:12:03 jberkus: that is the right one 17:12:10 it just doesn't give feedback 17:12:16 mattdm, :) 17:12:23 Don't overwrite download location for 2 week atomic images 17:12:25 kushal? 17:12:34 jberkus, That is not me 17:12:35 iirc 17:12:41 thats maxamillion 17:12:43 yo 17:12:47 it's still on the backlog 17:12:47 for post F24 17:13:09 ok, should we maybe take it off the action list if there's not going to be movement in the next week? 17:13:13 I'll update as soon as I can, I promise I'm not just ignoring the ticket :) 17:13:15 No update about the smoke tests yet, I will write down my ideas to a wiki page to share with the community. 17:13:31 jberkus: yeah, take it off the action list, there's very little chance it will happen in the next weeks time 17:13:39 also, I won't be here next week, I'll be at OSCON 17:14:27 kushal: it's unclear to me whethere the smoke tests are about testing *docker* or testing *containers* 17:14:35 see lots of confusion on the ticket in that regard 17:14:41 jberkus, Should be testing containers 17:15:00 jberkus, in particular, testing the layered images. 17:16:33 kushal: can you step in and make that clear? the ticket is going nowhere because people are confused 17:17:09 jberkus, Okay. 17:17:29 #action kushal to clarify smoke test ticket requirements 17:17:30 .fas chandankumar 17:17:31 chandankumar: chandankumar 'Chandan Kumar' - chandankumar2014 'chandan kumar' - ciypro '' 17:17:44 chandankumar, always use .hellomynameis 17:17:57 .hellomynameis chandankumar 17:17:58 chandankumar: chandankumar 'Chandan Kumar' 17:18:37 Next: Container Packager Guidelines 17:19:35 maxamillion: is the feedback on that one still going on? 17:19:53 jberkus: eh ... seems to have stalled a bit, but the thread is still open 17:19:57 which ticket are we talking about for smoke tests? 17:20:17 tflink: https://fedorahosted.org/cloud/ticket/151 17:20:26 thanks 17:20:29 jberkus: from there I need to go to fesco, there's not nearly as much feedback thus far as I had hoped 17:21:03 I'm somewhat convinced that nobody wants to show up to do any of the work but they all want everything to be done months ago ... so, business as usual 17:21:26 maxamillion: open source is all about little red hens 17:21:52 maxamillion: do you want to wait for more feedback? 17:22:08 oh I know, I've been at it for a while... but normally when it's something that so many people seem so excited about, there are people willing to volunteer some time 17:22:40 it's "docker docker docker" all the time until work needs to be done around it ... but whatever, I'm just grumpy 17:22:40 maxamillion, that is problem in the workgroup recently :( 17:22:59 we can move on, I don't need to waste everyone's time complaining 17:23:21 maxamillion: ok. not putting an action item in, thougth, since you'll be out next week (so will I) 17:24:13 maxamillion, complains are also important to keep us in the correct path. 17:24:19 OK, I'm going to skip order because I dragged mattdm over here and go to making the download page clearer. Then I'll go back to FOSP and Test day 17:24:38 so, Fedora Atomic download page clearer 17:24:41 jberkus, Have you moved in to the tickets? 17:24:48 https://fedorahosted.org/cloud/ticket/154 17:24:53 kushal: eh, if you say so :) 17:25:09 no, going by the order of the action items. which is largely the tickets, only in a different order 17:25:28 * mattdm is here :) 17:25:47 * roshi lurks 17:25:53 #topic Action Items from last meeting 17:25:55 * jberkus to update ticket 115 with current status 17:25:55 * kushal to associate the items to owners in ticket 143 17:25:55 * kushal to work with tflink on smoke tests 17:25:56 * jzb write posts for Fedora Cloud Test day. 17:25:56 * scollier to follow up on misc email for FOSP 17:26:14 jberkus, go ahead please. 17:26:25 #topic make downloads page clearer https://fedorahosted.org/cloud/ticket/154 17:27:15 mattdm: you had some specific thoughts on changes to the current setup? 17:28:17 jberkus: yeah.... 17:28:40 So, I'm operating on the assumption that we are going to de-emphasize Fedora Cloud Base image 17:28:48 and promote Atomic Host to be a top-level edition 17:29:06 * rtnpro needed to report on fedora-motd 17:29:17 This means https://getfedora.org/atomic/ instead of https://getfedora.org/cloud/ 17:29:31 and currently, http://cloud.fedoraproject.org redirects to https://getfedora.org/cloud/ 17:29:52 but it could instead be a page like https://arm.fedoraproject.org/ 17:30:12 focused on private/public cloud images across spins and editions 17:30:26 ^ all of this is bascially from a discussion with mizmo a few months ago 17:31:06 makes sense, given that cloud deployments are like 80% of all new deployments these days ... 17:31:25 atomic.fedoraproject.org could redirect to https://getfedora.org/atomic/ 17:31:31 jberkus: based on what data? 17:32:22 _or_ it could be a landing page with links to getfedora, projectatomic.io, fedora docs, and maybe a related Hub 17:33:47 maxamillion: thought I had stats, but it's for apps, not OS. will need to look further 17:34:09 thoughts on matt's ideas, anyone? 17:34:17 jberkus: seems reasonable 17:34:34 jberkus: I'd be really interested in that information, I think it would be useful when making priorities on work we're doing 17:34:55 maxamillion: I'll make use of some of RH's analyst hours for better data 17:35:17 jberkus++++++ that'd be awesome 17:36:06 jberkus, ++ 17:36:08 #action jberkus to obtain stats about cloud vs hw deployments 17:36:54 mattdm: can you open a ticket laying out the two (three?) design proposals above so that we could get people to pick between them? 17:37:10 or at least give more concrete feedback ... 17:37:30 jberkus: in the cloud trac? 17:37:37 yah 17:37:42 yup 17:37:56 #action mattdm to create ticket giving download page redesign options 17:38:03 thanks. ok, next 17:38:20 (wait, was there a proposal _other_ than what I gave?) 17:38:30 Because it's really more like "one proposal, with variations" 17:38:38 #topic Fedora Cloud Test Day https://fedorahosted.org/cloud/ticket/152 17:38:57 mattdm: the original ticket just talked about making the text and arrangement of links clearer. it was much more modest 17:39:07 jberkus: kk 17:39:17 jberkus, I will have to update the wiki page, and then the ticket. 17:39:20 It went well. 17:39:21 so, someone want to do a test day report? Kushal? 17:39:32 jberkus, I will write that up. 17:39:41 kushal: well, it went well in terms of "we found lots of bugs" 17:39:48 :) 17:39:52 #action kushal to do test day writeup 17:40:11 But I hoped for more participation from cloud sig/wg 17:40:21 kushal: I did a non-standard test of F24. Is there anywhere to report that? There doesn't seem to be 17:40:33 jberkus, Add that in the wiki page 17:40:36 in the results section 17:41:20 kushal: is there a reason why there were no Atomic AMIs for AWS? that kept me from testing effectively 17:41:34 jberkus, Yes, we found that issue few hours back. 17:41:39 kushal: link? 17:42:01 jberkus, The image name changed, that was causing the missing the uploads. 17:42:06 * kushal is searching for the PR 17:42:10 https://github.com/fedora-infra/fedimg/pull/50 17:42:24 got it 17:42:30 https://github.com/fedora-infra/fedimg/pull/50 17:42:35 sayan, thanks. 17:43:49 kushal: so the next nightlies should generate images? 17:43:53 AMIs 17:44:17 dustymabe: so I am waiting for threebean to review the PR once 17:45:07 k 17:45:23 sayan, after that you will have to do a hotfix 17:45:32 kushal: yes 17:45:41 oh, really? 17:45:43 * threebean looks 17:45:49 ok, anything else on the test day? 17:46:15 one note that I heard about - some of the atomic test cases are a bit out of date 17:46:33 tflink, do you know which ones? 17:46:36 i think that coremodule is working on updating them 17:46:38 tflink: yeah. and there's no testing of kubernetes AFAICT 17:46:39 I can find links 17:47:08 kushal: the problem was mostly around testcloud installation instructions 17:47:20 Oh 17:47:20 IIRC, the test case itself (post-prep) was fine 17:47:35 I was just telling people to do "dnf install testcloud" 17:47:43 yeah, that's what it should say 17:47:59 but it tells folks to install from git and doesn't mention any of the deps, other setup bits etc. 17:48:21 fedoraproject.org/wiki/Local_Test_Cloud_Installation_Guide 17:48:43 tflink, oh, missed that then. 17:48:49 coremodule: do you have links to the test cases you found? 17:48:58 I think the biggest thing from the test day is this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1334588 17:49:10 https://github.com/fedora-infra/fedimg/pull/50 17:49:12 Yes, standby... 17:49:13 oops 17:49:16 https://bugzilla.redhat.com/show_bug.cgi?id=1334588 17:49:20 we have been kicking the can down the road on docker not working in Atomic 17:49:21 Just for record 17:49:27 tflink: I think that, for an AWS test, setting up a basic 3-node kubernetes cluster and deploying a pod could be a reasonable tst 17:49:30 oh, nice one 17:49:34 because we would test the latest version in fedora cloud base 17:49:44 latest one from updates-testing 17:49:48 and it would work 17:49:57 it would help to make the ansible-aws setup less complex, though 17:49:57 dustymabe, Ah, thanks for doing that. 17:50:02 so we would assume that once it reached stable docker would work in atomic 17:50:15 but I don't think that is the case 17:50:16 jberkus: that sounds reasonable to me, let us know if you need help on test case formatting etc. 17:50:27 * tflink assumes jberkus was talking about a manual test case 17:50:29 jberkus, we have a test for that ready in autocloud/tunir, waiting to deploy the new version to prod. 17:50:32 see comment #6 from that bu 17:50:34 bug 17:50:54 tflink: yeah 17:51:00 I'll open a ticket for myself 17:51:04 tflink, http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots 17:51:05 https://kushaldas.in/posts/testing-containers-using-kubernetes-on-tunir-version-0-15.html 17:51:06 and cc jbrooks on it 17:51:09 jberkus, ^^^^^ 17:51:37 jberkus, Problem is not everyone has an account in AWS. 17:51:42 tflink, That was the big one that'd throw you off, the rest assumed you had a working install. 17:51:45 The volunteers mostly not. 17:52:06 kushal: really? huh. 17:52:16 * jberkus thought everyone had an aws account these days 17:52:19 * jberkus has several 17:52:29 that's been an issue for any AWS testing for as long as I can remember 17:52:31 it would be good to doc other clouds too 17:53:24 jberkus, Volunteers don't have (mostly) :( 17:53:29 kushal: what about getting a budget for AWS-based testing? I mean, AWS is one of our big deployment targets, we ougth to test there (as well as on GCE, DO, etc.) 17:53:33 Not in any provider. 17:53:46 jberkus, That is coming, in future releases. 17:53:56 jberkus, We are getting to that part (slowly). 17:54:23 well, it's hurting us. you saw that Fedora currently has like 2.1% of cloud deployments. we're already behind the curve ... 17:54:37 tflink, The link in that guide has been updated to reflect the change. 17:54:38 anyway, not going to resove that here. anything else on test day? 17:54:39 where are we going to get this budget from? 17:55:01 mattdm: do we have money to spin up tests in all the major public IaaS providers? 17:55:07 #action jberkus to work on test for kubernetes cluster on AWS etc 17:55:33 maxamillion, OSAS is paying the official account, openshift team is donating our community account iirc (for AWS). 17:55:56 keep in mind that we're talking about something like $150 per test day 17:55:57 maxamillion: not allocated, since we've been blocked on legal. AWS we can do with the community cloud account. And I *think* Digital Ocean is likely to comp us some time if we ask nicely 17:56:22 (blocked on legal applies to Azure and GCE) 17:56:42 mattdm: yeah I think I can get a free account from DO 17:56:48 mattdm: that's a topic for another time 17:56:58 they just gave me a bunch of credits for doing testing 17:57:19 #topic FOSP https://fedorahosted.org/cloud/ticket/153 17:57:30 are scollier or jzb here? 17:57:56 jzb sent regrets 17:57:58 so, nothing on that 17:58:17 scollier was in training this week 17:58:49 2 minutes. 17:58:51 ok, I'm going to skip to other business 17:58:56 because something has come up 17:58:59 #topic other business 17:59:37 apparently we're responsible for part of this: https://fedoraproject.org/wiki/Workstation/Third_party_software_proposal 18:00:03 specifically: Rules for software packaged as Docker images 18:00:32 anyone already involved in that? 18:00:43 jberkus: I'm not 18:00:50 nope. 18:01:03 mattdm - i did a little blog writeup of the proposal - http://blog.linuxgrrl.com/2015/09/15/fedora-atomic-logo-idea/ 18:01:21 if I file a ticket, can someone stay on it to make sure it gets done? presumably someone other than maxamillion ? 18:01:37 mizmo++ 18:01:37 maxamillion: Karma for duffy changed to 21 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:01:39 mizmo++ 18:01:40 mizmo: love the logo! 18:01:45 mizmo: oh, I like it 18:01:53 mizmo, thanks :) 18:02:04 mizmo++ 18:02:04 kushal: Karma for duffy changed to 22 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:02:06 jberkus: I'm not but I probably should be, didn't know that was somehow falling on us 18:02:34 mizmo: Oh yeah! I rememberd that but forgot that your blog post covered ore than the logo 18:02:37 (actually didn't know that page existed) 18:02:39 well, we're not going to handle it here 18:02:45 but, I want a ticket owner 18:02:57 because if I create a ticket with no owner, nothing will happen ... 18:03:20 jberkus, what exactly we have to do as Cloud WG? 18:03:33 jberkus, I can take that ticket, but first I want to know what is required. 18:03:42 kushal: work with Fedora Server to create rules on third-party docker image software. that's all I know 18:03:52 beyond that ... mattdm ? 18:03:56 jberkus, Okay. 18:04:09 I'll join kushal on that adventure 18:04:11 We are already 3 minutes into extra time. 18:04:16 maxamillion, :) 18:04:29 jberkus, Add that ticket to start with. 18:04:40 ok 18:04:53 mattdm, oh hey theres a mockup https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/XAJQSUAGXJBXBG7LC3HKJEK4KBTNYTTP/ 18:05:01 #topic endmeeting 18:05:12 btw, we need a chair for next week 18:05:14 I can't do it 18:05:40 jberkus, it did not end :) 18:05:44 #endmeeting