17:02:36 #startmeeting fedora_cloud_wg 17:02:36 Meeting started Wed May 25 17:02:36 2016 UTC. The chair is scollier. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:36 The meeting name has been set to 'fedora_cloud_wg' 17:02:41 hello everyone 17:02:49 .hello maxamillion 17:02:49 .hello scollier 17:02:50 .fas jasonbrooks 17:02:50 #topic roll call 17:02:52 maxamillion: maxamillion 'Adam Miller' 17:02:55 .hello trishnag 17:02:55 scollier: scollier 'Scott Collier' 17:02:58 jbrooks: jasonbrooks 'Jason Brooks' 17:03:01 trishnag: trishnag 'Trishna Guha' 17:03:09 .hellomynameis dustymabe 17:03:10 dustymabe: dustymabe 'Dusty Mabe' 17:03:19 #chair trishnag jbrooks dustymabe maxamillion sayan rtnpro 17:03:19 Current chairs: dustymabe jbrooks maxamillion rtnpro sayan scollier trishnag 17:03:28 did i miss anyone? 17:03:53 .hello sayanchowdhury 17:03:54 sayan: sayanchowdhury 'Sayan Chowdhury' 17:04:04 I have a couple of topics before we get into tickets. 17:04:17 #topic Chairing future meetings 17:04:45 need some folks to hit https://fedoraproject.org/wiki/Cloud 17:04:55 and please sign up for a spot to chair future meetings. 17:04:59 I added blank entries for june 17:05:02 dustymabe, thanks. 17:05:12 dustymabe, i'll sign up for a couple. 17:05:12 sayan: interested in chairing some meetings? 17:05:23 dustymabe: yes, sure 17:05:24 howdy 17:05:27 hi jzb 17:05:31 .hellomynameis jzb 17:05:32 jzb: jzb 'Joe Brockmeier' 17:05:33 #chair trishnag jbrooks dustymabe maxamillion sayan rtnpro jzb 17:05:33 Current chairs: dustymabe jbrooks jzb maxamillion rtnpro sayan scollier trishnag 17:05:47 no one should be afraid, it's not hard 17:05:57 and we'll all help you while the meeting goes on 17:06:00 it's not hard, it's fun! 17:06:11 dustymabe: I will update the wiki 17:06:13 I would argue the cloud meeting is a great place to learn 17:06:18 sayan: thanks! 17:06:26 so, i just wanted to put that out there. thanks for anyone that volunteers. 17:06:29 next topic 17:06:41 #topic migrated dockerhub to org 17:06:59 scollier: is that a ticket? 17:07:08 dustymabe, no, it should be. 17:07:19 #action scollier to create ticket for migrating docker hub to org 17:07:35 Hi jberkus 17:07:39 #chair trishnag jbrooks dustymabe maxamillion sayan rtnpro jzb jberkus 17:07:39 Current chairs: dustymabe jberkus jbrooks jzb maxamillion rtnpro sayan scollier trishnag 17:07:40 at conference, poor wifi 17:08:02 I went ahead and migrated the docker hub account from a user account, to an "Organization" 17:08:14 this gives us the flexibility to create "teams" and has some RBAC 17:08:33 so we can have more than just me going in and building images now, for the layered images. 17:08:33 scollier: +1 17:08:45 if anyone has any interest in participating in that, please ping me. 17:09:23 ok, not to much on that, i have one more. 17:09:33 #topic fedora images in AWS 17:09:54 #info jzb grabbed June 8 and June 22 to chair. 17:10:05 Can someone explain why the way to launch images into AWS is initiated from the fedora cloud page, and not searchable in AWS AMI list? 17:10:30 thanks jzb 17:11:05 scollier: I think they aren't searchable because we aren't a part of the "marketplace" 17:11:17 the centos images are 17:11:26 can you search and find the centos images that way? 17:11:35 dustymabe, looking 17:12:24 dustymabe, they are def part of marketplace: https://wiki.centos.org/Cloud/AWS 17:12:29 dustymabe, any reason why we are not? 17:12:38 jzb, ? 17:12:43 so there are positivies and negatives to being a part of the marketplace - positive: your images show up in search - negative: you have to confirm you want to use the image (click a check box) before you get to use them 17:13:08 without clicking the check box you can't use the images I don't think 17:13:11 scollier: so 17:13:22 and some users (in some companies) don't have aws web console access 17:13:25 if you go to Community AMIs 17:13:32 you can find what look like the Fedora standard AMIs 17:13:57 There's even an operating system link on the side that includes Fedora 17:13:58 dustymabe, jzb, i'd like to see them, not part of marketplace, but just "available" as a public image. 17:14:17 i'd like to reduce the barrier to entry for people trying this stuff. 17:14:21 scollier: what's a recent date? 17:14:25 scollier: er, for an image 17:14:36 jzb, what do you mean? 17:14:46 Fedora-Cloud-Base-24-20160519.n.0.x86_64-us-east-1-PV-standard-0 17:14:54 if I search under "Community AMIs" and "Fedora" 17:14:59 hmm 17:15:00 for "Fedora" and 2016" 17:15:06 I get recent Cloud Base images 17:15:07 that's technically "unreleased" 17:15:18 dustymabe: apparently not :-) 17:15:25 heh 17:15:30 well - it's just because we autoupload things to aws 17:15:33 also I can find Atomic things 17:15:40 sayan: ^^ 17:15:42 can you help with that 17:15:52 Fedora-Cloud-Atomic-23-20160421.x86_64-us-east-1-HVM-gp2-0 for example 17:16:03 scollier: does this fit the bill for "finding" images or no? 17:16:40 clearly we need to document this, though 17:16:53 so, my AWS-fu is slightly rusty 17:16:59 jzb, i thinks so, as long as dustymabe and sayan and others agree those are "fedora uploaded / released" images. 17:17:16 how hard would it be to write a Python script that people could just apply their AWS ID to in order to launch an image from the command line? 17:17:21 jzb, dustymabe, is there a interval that someone from here uploads images? 17:17:29 scollier: I'm not sure 17:17:51 I think what would be great, if we can do it, is a Python or Ansible script that looks to a .file for AWS creds and just launches something 17:17:53 maxamillion, can we include uploading to AWS as part of 2 week process? 17:18:23 jzb, for that matter, maybe not just AWS... 17:18:26 but gce, others? 17:18:41 i'm sure these conversations have happend and I'm just missing something. 17:19:02 scollier: we already upload images AFAIK 17:19:13 to AWS 17:19:23 scollier: I don't think we have images on those platforms yet though? 17:19:30 as for making it easy to start up our images in cloud providers 17:19:33 scollier: what do you mean? 17:19:37 jzb, i don't know, just wanted to chat about it. 17:19:38 the AWS images should be there 17:19:41 scollier: I don't suppose this is something the e2e team could help with? :-) 17:19:44 I'd say using vagrant plugins would be a good option 17:20:10 maxamillion, jzb, dustymabe, ok, so we have two ways to launch images, one through fedora cloud page, one from searching via AWS community AMIs 17:20:22 ok 17:20:28 scollier: yes 17:20:36 maxamillion, are they uploaded to any other providers? 17:20:56 scollier: not to azure 17:21:05 I don't think we have them in GCE either 17:21:07 scollier: no, I don't think fedimg has support for anything else 17:21:07 scollier: no they are not uploaded to any other providers 17:21:11 dustymabe, azurely we want to do that 17:21:17 sorry. 17:21:20 scollier: indeed 17:21:31 scollier: ouch 17:21:33 :-) 17:21:45 ok, is that something we want to do? 17:21:53 yes 17:22:00 scollier: this got hung up on legal last 17:22:05 i'm asking because, I think that would make installing and testing Origin easier, on multiple providers. 17:22:06 jzb: yep 17:22:21 scollier: basically the agreements for the providers require an indemnification we didn't want to sign 17:22:37 scollier: like, Fedora will be responsible if someone sues Google for patents on the Fedora image. 17:22:42 or whatever 17:22:43 jzb, sigh. 17:22:50 scollier: right? 17:22:52 But 17:23:03 jzb: oh, that's fun 17:23:05 I'll poke the bear again. Eventually the bear will either give in or eat me. 17:23:13 jzb, that would be nice, thanks. 17:23:29 #action jzb to follow up on getting fedora cloud images onto Azure and other providers 17:23:31 #action jzb take another run at legal 17:23:34 cool, thanks 17:23:43 does anyone have anything else before we move to tickets? 17:23:54 scollier: mattdm was following up with Azure on legal 17:24:00 here is the ticket - https://github.com/fedora-infra/fedimg/issues/10 17:24:23 sayan, updated last year 17:24:33 and before that june of 2014 17:24:47 jzb, maybe work out of that ticket? 17:25:06 scollier: The ticket was updated on last year in December I guess 17:25:18 looking 17:26:44 o 17:26:45 k 17:27:02 let's move to some tickets 17:27:19 #topic https://fedorahosted.org/cloud/ticket/115 17:27:35 this is Fedora Cloud FAD 17:27:37 dustymabe, ^ 17:27:53 oh, I guess jberkus as well. 17:28:32 FAD is scheduled - anything left for us to do other than the actual work related to the FAD? 17:28:37 any more administrivia? 17:28:37 I think Josh dropped, bad connection 17:28:40 dustymabe: book travel? 17:28:47 * maxamillion is all booked up on travel 17:28:49 Josh asked me about this 17:28:54 so for anybody wondering 17:28:54 yeah. if you are coming and haven't booked travel 17:28:56 * tflink is still looking for a roommate 17:29:08 since it looks like *everybody* is a RHT person 17:29:10 tflink: what day are you leaving 17:29:16 just book & expense travel normally 17:29:28 * dustymabe leaving on Wednesday night 17:29:31 and follow the guidelines for moving to our cost center if your travel is being covered by the Fedora budget. 17:29:42 dustymabe: thursday 17:30:25 ok, anything else on that? 17:30:36 tflink: if you want to stay with me you can 17:30:36 moving on 17:30:42 but I check out on wednesday 17:30:51 dustymabe: when do you arrive? 17:30:55 Monday 17:31:46 dustymabe: would it work better the other way around where I keep the room until thursday? 17:32:08 * tflink also arrives on monday 17:32:43 ok, skipping 125 as jberkus is out. 17:32:54 #topic vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 17:33:01 tflink: let's follow up after meeting 17:33:09 sounds like a plan 17:33:35 looks like Ian owns this 17:33:36 scollier: skip for now 17:33:40 dustymabe, ack. 17:34:06 #topic Proposals for F24 features https://fedorahosted.org/cloud/ticket/143 17:34:40 jzb, ^ 17:35:00 scollier: no updates today. :-/ 17:35:15 will make sure to follow up as we're getting close to release. Need to tie this in with the release announcement anyway. 17:35:34 jzb, oky 17:35:46 #topic Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 17:35:58 #action Follow up on ticket 143 17:36:01 #undo 17:36:01 Removing item from minutes: ACTION by jzb at 17:35:58 : Follow up on ticket 143 17:36:12 #action jzb Follow up on Ticket 143 before Cloud FAD. 17:36:17 this was maxamillion 17:36:25 maxamillion, anything we can help with on this ticket? 17:36:46 scollier: not right now - til post f24 17:36:53 ehhh 17:37:13 I'm hoping we can make movement on that at the FAD, I'm trying to get some ground work done between now and then, time permitting 17:37:35 the whole thing is a mess and needs a rewrite, which is planned 17:37:42 maxamillion, do you have a session on this at FAD? 17:37:44 should it? 17:37:56 dustymabe, ^ 17:38:30 I figured it fit under the Atomic Edition category ... if we're going to switch over to this entirely, it needs fixing 17:38:42 but if we need to explicitly call it out, then yes ... likely so 17:38:52 jzb, opinions? 17:39:31 just a sec. I thought I commented in ticket 17:40:33 scollier: I think we're agreed, it's a matter of implementation, yes? 17:40:46 to the best of my knowledge, yes 17:40:57 ok, that's cool. 17:41:28 we'll move on for now then, unless there's anything else. 17:41:39 if the docker layered image build system will *EVER* stop being the bane of my existence then I'll be able to actually get to this 17:41:48 maxamillion, :( 17:42:01 maxamillion, maybe we can get an update from you on that during open floor? 17:42:05 i'd like to hear the status. 17:42:48 * roshi lurks 17:42:55 maxamillion: I'm sure there are many things after that lined up to be the next bane of your existence. 17:43:07 next ticket (148) is also maxamillion, but it's currently in progress and being discussed on list, so I think we can skip. 17:43:35 jzb: oh no, this one is going to stick around until I either die, get fired, quit, or docker dies 17:43:44 #topic Need owner to define basic container smoke testing requirements https://fedorahosted.org/cloud/ticket/151 17:43:47 maxamillion, heh. 17:44:17 maxamillion: well, nobody's going to fire you, and you're not allowed to quit or die. 17:44:24 so... death of Docker it is. 17:44:28 The eternal ticket :P 17:44:42 jzb: either that or it will just be the bane of my existance forever 17:44:46 annnnnnnnnnnyyyyyyyyyyyyyyyyyyyhooooooo 17:44:50 I feel like we're the Night's Watch. 17:44:59 :-) 17:45:02 maxamillion, your actually the owner of that ticket too. ^ 17:45:03 jzb: basically, and I'm apparently John Snow 17:45:09 scollier: yes 17:45:40 scollier: there's an email thread with kushal, tflink and myself sorting that out ... it's kind of stalled so it might be something we should just knock out at the FAD 17:46:03 maxamillion: should we have a test container? 17:46:13 maxamillion, sounds good to me. anything causing the stall that we can help with? 17:46:15 sorry, i think that's my bad 17:46:19 jzb: how do you define what that means? 17:46:35 assuming you're talking about the thread I think you're talking about 17:46:52 jzb: the problem is trying to define a basic smoke test for all possible docker containers is basically like saying "let's write a single set of test cases that are valid against all possible shell scripts" 17:46:57 maxamillion: I mean, a Dockerfile and built container that expose as much functionality as possible. 17:47:05 fair 17:47:07 tflink: yeah, probably ... I honestly can't remember who it's stalled on 17:48:11 maxamillion, shouldn't the test cases be left up to the image owner? 17:48:18 +1 17:48:32 How do we think about / approach test cases for rpms? 17:48:45 does httpd work, etc 17:48:54 scollier: that's the plan, but we'd like to come up with *some* kind of sanity check baseline 17:49:06 maxamillion, maybe 3 categories: 17:49:10 1. does the image builde? 17:49:10 jbrooks: there's basical rpm sanity checking 17:49:21 2. Does the image run (with instructions on how to do so) 17:49:30 scollier: the image will already be built by the time it hits the testing 17:49:34 3. Does the image provide expected results? 17:49:45 tflink: ^ 17:49:54 let's sort by most popular images in the docker hub and just come up w/ some basic hello world tests 17:49:59 divvy it up 17:50:04 i'll do some 17:50:16 this is completely disjoint from the docker hub 17:50:32 As a source of popularity to choose where to start 17:51:16 yeah, the only thing that I can think of outside the checks done during build is an atomic security check 17:51:17 we already have piles of stuff to build initially from scollier's fedora-dockerfiles repo (or whatever it's called) 17:51:24 +1 17:51:25 outside of that, I think it's going to be per-image 17:51:54 Yeah, testing the image = testing the app inside 17:52:04 jbrooks, ^ that. 17:52:05 the only thing left on the taskotron side that I know of is figuring out how to get the built images onto the test client but that might just be pointing some docker tools @ the correct place 17:53:17 tflink, should that work be tracked in the ticket mentioned? 17:53:42 the smoke testing requirements ticket? 17:53:47 tflink, ya 17:54:15 tflink, or is the taskotron work tracked somewhere else? i dunno. 17:54:53 yeah, it's tracked elsewhere - in our phabricator instance. https://phab.qadevel.cloud.fedoraproject.org/ 17:55:01 tflink, excellent. 17:55:14 hadn't seen that. 17:55:19 ok, we have about 5 more minutes 17:55:22 and a few more tickets. 17:55:44 i'd like for everyone to just review remaining open tickets when they can? https://fedorahosted.org/cloud/report/9 17:55:49 and change topic to open floor. 17:56:06 #topic Open Floor 17:56:26 does anyone have anything to discuss in the remaining time? 17:56:46 ! 17:56:48 maxamillion: did we get everything set for ticket 155 17:57:09 post f24 release deliverables 17:57:11 cadence 17:57:24 trishnag: go ahead 17:57:40 no, still need to sort out the Atomic repos, cwalters I think wanted it every 2 weeks 17:57:54 scollier, dustymabe can anyone chair meeting? 17:58:03 If yes I would like to grab 29th of June :) 17:58:06 but most people in the cloud SIG wanted it constantly updating along with mainline fedora rpm content 17:58:12 I don't care in the slightest which 17:58:18 trishnag: yep! 17:58:20 anyone 17:58:27 trishnag, excellent. 17:58:36 trishnag: point of order 17:58:43 trishnag: that's during RHT summit 17:58:47 odds are most of us won't be around 17:58:50 oh. 17:59:02 jzb, oh 17:59:04 trishnag: that is true - we'll probably cancel that week 17:59:09 trishnag, steps to run meeting are listed here: https://fedoraproject.org/wiki/Cloud#Meetings 17:59:18 trishnag: add an entry for the following wednesday and add your name to it 17:59:21 trishnag: not to dissuade you from running one :-) 17:59:34 maxamillion: I say we have both 17:59:35 trishnag: just thought I'd point out that one probably won't happen 17:59:38 or you'd be very lonely. 17:59:39 :-) 17:59:54 Cool, welp, time is running out. 17:59:55 I will be able to chair meeting after 16th of June since my exams are going on 17:59:56 we can easily have a ref that only gets updated on two week releases 18:00:03 scollier, dustymabe jxb^ 18:00:11 jzb^ 18:00:12 and another ref which gets updated continuously 18:00:16 trishnag, ack. there will be plenty of opportunities. 18:00:21 that's a good option 18:00:32 going to go ahead and end the meeting. thanks for joining everyone. 18:00:35 dustymabe: that's a shit load easier said than done 18:00:47 #endmeeting