17:02:24 #startmeeting fedora_cloud_wg 17:02:24 Meeting started Wed May 4 17:02:24 2016 UTC. The chair is scollier. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:24 The meeting name has been set to 'fedora_cloud_wg' 17:02:33 Hello everyone. 17:02:41 [GNU]: if you stopped chaning your name maybe you would 17:02:45 .hello jasonbrooks 17:02:46 jbrooks: jasonbrooks 'Jason Brooks' 17:02:46 changing :) 17:02:50 .hello scollier 17:02:52 scollier: scollier 'Scott Collier' 17:02:56 <[GNU]> .hello goern 17:02:57 .hellomynameis dustymabe 17:02:57 [GNU]: goern 'Christoph Görn' 17:03:00 dustymabe: dustymabe 'Dusty Mabe' 17:03:04 .hello jberkus 17:03:05 jberkus: jberkus 'Josh Berkus' 17:03:07 .hello trishnag 17:03:08 trishnag: trishnag 'Trishna Guha' 17:03:13 .hello tflink 17:03:14 tflink: tflink 'Tim Flink' 17:03:14 trishnag: \o/ 17:03:17 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink 17:03:17 Current chairs: dustymabe goern jberkus jbrooks kushal scollier tflink trishnag 17:03:19 <[GNU]> dustymabe, if zodbot the emperor is good with my nick-fas_account mapping you should be too :P 17:03:26 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink [GNU] 17:03:26 Current chairs: [GNU] dustymabe goern jberkus jbrooks kushal scollier tflink trishnag 17:03:29 .hello chandankumar 17:03:30 chandankumar: chandankumar 'Chandan Kumar' 17:03:36 dustymabe, o/ 17:03:39 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink [GNU] chandankumar 17:03:39 Current chairs: [GNU] chandankumar dustymabe goern jberkus jbrooks kushal scollier tflink trishnag 17:03:43 anyone else/ 17:04:12 chandankumar: hi! 17:04:23 ok, let's get started by reviewing the open tickets, then we'll look at last weeks action items, then we'll roundtable. 17:04:38 scollier: I like your style already 17:04:42 dustymabe, Hello 17:04:44 ticket report is listed here: https://fedorahosted.org/cloud/report/9 17:04:59 let's run through them, starting with https://fedorahosted.org/cloud/ticket/115 17:05:08 dustymabe, any updates? 17:05:23 scollier: the FAD has been submitted and is awaiting approval 17:05:32 jberkus, from? 17:05:37 Council 17:05:56 lemme update the ticket with a link to the council ticket, momemnt 17:05:58 jberkus: thanks so much 17:06:07 jberkus, excellent 17:06:18 #action jberkus to update ticket 115 with current status 17:06:27 everyone please show appreciation to jberkus for this the next time you see him in person or virtually 17:06:59 yes, thanks jberkus. 17:07:02 scollier: done 17:07:06 next on the list is: https://fedorahosted.org/cloud/ticket/125 17:07:12 jberkus, back to you sir. 17:07:55 still pending, nothing to report. likely getting done as part of my summit demos, so a realistic deadline is mid-June. 17:08:21 jberkus, ack, curious, how do you plan on organizing these? 17:08:33 scollier: probably just a list of examples 17:08:44 in a repo, unless someone as a better idea? 17:09:09 They could live in Fedora-Dockerfiles 17:09:10 jberkus, i like that. think it's worth collecting a list and prioritizing? 17:09:21 jberkus, from the larger group 17:09:39 .hello sayanchowdhury 17:09:39 i think one obvious one people understand, that exercises a bit of functionality is wordpress... 17:09:40 sayan: sayanchowdhury 'Sayan Chowdhury' 17:09:44 scollier: only if people are willing to write them 17:09:48 Was disconnected :( 17:09:57 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink [GNU] sayan 17:09:57 Current chairs: [GNU] chandankumar dustymabe goern jberkus jbrooks kushal sayan scollier tflink trishnag 17:10:00 .hellomynameis kushal 17:10:01 kushal: kushal 'Kushal Das' 17:10:04 There's overlap w/ already-done work by the nulecule folks 17:10:09 scollier: I'm not into having other folks tell me what to create, becuase I already hsve stuff I'm working on 17:10:17 like wordpress 17:10:20 jberkus, understood. 17:10:21 jbrooks: yeah, I was gonna port some the nulecule examples ... 17:10:36 <[GNU]> so we put a kubernetes directory in each of the https://github.com/fedora-cloud/Fedora-Dockerfiles/ directories? 17:10:36 jberkus, at any rate, happy to review them once you make some progress. 17:10:59 <[GNU]> jberkus, there is a wordpress in Fedora-Dockerfiles :) why not extend that one? 17:11:12 * kushal is going to update how to run meeting section of the wiki page. 17:11:19 jberkus, might make sense even to do this via nulecule 17:11:26 scollier: so, question: is there a reason to NOT use nulecule/atomicapp for this? that is, a reason why we want pure-Kubernetes? 17:11:28 kushal, what are you saying man ;) 17:11:28 atomicapp is part of fedora, after all 17:11:28 Hopefully that will be helpful. 17:11:42 would help me to know what it is 17:11:48 jberkus, there's use cases for both, i think nulecule creates a portable format. 17:12:00 <[GNU]> jberkus, pure kube is on the development path to nuleculization 17:12:12 jbrooks, We have asked for a nulecule example before. 17:12:28 jbrooks, rtnpro tried to have, but he said it will be duplicate of work. 17:12:36 https://github.com/projectatomic/nulecule-library/tree/master/wordpress-centos7-atomicapp/artifacts/kubernetes 17:13:15 so i'm here.. just thinking 17:13:43 I think in any form having kube files will help us down the road. whether they are in nulecules or just plain raw 17:13:47 so either way works for now 17:13:53 just getting content is useful 17:14:00 ack 17:14:05 <[GNU]> true 17:14:54 lets add comments / thoughts to the ticket for jberkus 17:15:07 apologies, just got back from lunch 17:15:07 moving to next ticket: https://fedorahosted.org/cloud/ticket/136 17:15:15 jzb: \o/ 17:15:22 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink [GNU] sayan jzb 17:15:22 Current chairs: [GNU] chandankumar dustymabe goern jberkus jbrooks jzb kushal sayan scollier tflink trishnag 17:15:25 hiya jzb 17:15:46 Ian isn't around for 136 17:15:57 any thoughts dustymabe? 17:16:07 scollier: I can ask Ian about this tomorrow maybe 17:16:12 he is here with us in India 17:16:14 scollier, He must be enjoying the Indian heat 17:16:21 either way probably won't make f24 17:16:22 dustymabe, :) 17:16:26 dustymabe, where are those vagrantfiles? 17:16:41 .hello maxamillion 17:16:42 maxamillion: maxamillion 'Adam Miller' 17:16:51 sorry, I've been semi-here but am double booked right now 17:16:52 #chair scollier jbrooks goern dustymabe kushal jberkus trishnag tflink [GNU] sayan jzb maxamillion 17:16:52 Current chairs: [GNU] chandankumar dustymabe goern jberkus jbrooks jzb kushal maxamillion sayan scollier tflink trishnag 17:17:26 scollier, inside the code of imagefactory iirc 17:17:43 kushal, what does that mean? we don't distribute them? 17:17:50 scollier: what Vagrantfiles? 17:18:02 ahh yes 17:18:06 inside of imagefactory 17:18:08 dustymabe, the vagrantfiles referenced in 136 17:18:37 scollier, they get automagically added into the image as a reference iirc. 17:18:39 there is an open ticket for being able to specify a vagrantfile as input to magefactory 17:18:53 that will replace the embedded vagrantfile 17:19:03 dustymabe, ok. 17:19:17 dustymabe, so, we can wait until ian is back for update on that. 17:19:20 next ticket: https://fedorahosted.org/cloud/ticket/143 17:19:25 kushal ^ 17:19:52 scollier, Are we discussing the tickets from trac? 17:19:58 kushal, yup 17:20:15 kushal: so rtpro's package had some issues 17:20:24 dustymabe, Yes, he told me today. 17:20:30 I opened issues upstream 17:20:36 dustymabe, Thanks. 17:20:40 we probably won't make f24 :( 17:20:52 but the good news is that if we start releasing monthly it won't matter much 17:21:10 dustymabe, and atomic is 2 weeks anyway 17:21:25 right, but motd is for more than just atomic 17:21:40 dustymabe, Yes. 17:22:38 scollier, So, no other update on that ticket. 17:22:41 kushal, can we go in and mark those items off the list that are completed? 17:22:47 kushal, and ones that are blocked? 17:23:05 scollier, I think we can just update the ticket with those details. 17:23:24 ok, and there's two lists, comment 4 and 7 17:23:49 kushal, thanks 17:23:56 next ticket: https://fedorahosted.org/cloud/ticket/147 17:24:15 don't overwrite download location 17:24:16 yeah we should get status from people on the other items 17:24:40 dustymabe, agree. maybe list owner by item 17:24:52 item by owner? 17:25:04 i think so dustymabe 17:25:10 kushal: can you do that? ^^ 17:25:18 scollier, feel free to update the topic for each ticket. 17:25:21 I think I know them all but I'm not sure 17:25:22 dustymabe, Okay, I will do that. 17:25:35 nzwulfin was one of them I think 17:25:43 maxamillion was one. etc.. 17:25:50 scollier, dustymabe One issue, not everyone replied to my mail when I asked about changes in the list. 17:26:01 #action kushal to associate the items to owners in ticket 143 17:26:03 scollier, so the wiki page only have 3 items listed. 17:26:08 kushal: did you ask about the status of changes? 17:26:18 dustymabe, I know only for those 3 17:26:37 and the atomic developer mode 17:26:49 anyway I will ask around 17:26:54 matt mincene was one of them 17:26:54 Please go ahead to the next ticket. 17:26:56 right? 17:27:02 dustymabe, Yes. 17:27:03 gluster, etc.. 17:27:07 kushal, ack, thanks. 17:27:14 next ticket is https://fedorahosted.org/cloud/ticket/147 17:27:23 maxamillion, any thoughts on that one? 17:27:44 #topic Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 17:27:50 scollier: I think he has said in the past we'll punt that one til after f24 17:27:57 so move to next ticket 17:28:08 dustymabe, ok. we should update that ticket ;) 17:28:23 next ticket: https://fedorahosted.org/cloud/ticket/148 17:28:37 Container "Packager" Guildelines and Naming Conventions 17:28:56 #topic Container "Packager" Guildelines and Naming Conventions https://fedorahosted.org/cloud/ticket/148 17:29:05 maxamillion: ^^ 17:29:12 There is an active discussion in the fedora-devel list 17:29:13 kushal, ok, i'll do that, was wondering how you were calling that. 17:29:23 scollier, check the pm :) 17:29:43 kushal, yup, looks like it's waiting on fesco 17:29:51 ok, moving on. 17:29:57 it's not waiting on fesco 17:30:01 scollier, I think FESCo asked to get feedback from everyone on devel list. 17:30:05 there's a discussion on devel list 17:30:07 +1 17:30:13 I'll update the ticket 17:30:25 ah, ok maxamillion, thanks. 17:31:02 #topic Need owner to define basic container smoke testing requirements https://fedorahosted.org/cloud/ticket/151 17:31:27 jberkus, ^ 17:31:34 We have the initial tests related to docker from maxamillion 17:31:55 kushal, where is that listed? 17:31:57 kushal: so is this ticket about testing *docker* or abotu testing *images*? it's been completely unclear 17:32:05 Still question is: Do we want to run some common tests in every image? 17:32:29 scollier: it's in the wiki ... but we're also going to be adding other things based on feedback from QA 17:32:30 kushal, well, IMO, it would help to have a jenkins job that tests every image automagically once it's built. 17:32:42 scollier: https://fedoraproject.org/wiki/QA/Draft/Docker 17:32:47 i thought the consensus was that there are no common tests we could run on all images 17:32:48 * scollier reads 17:32:53 jberkus, It is about testing images, but we have to make sure that docker also gets tested for our usecases. 17:33:00 so we will need to have a custom test script or at least run parameters for each image 17:33:04 scollier: the current plan is to run all tasks written for a given image when it's produced 17:33:06 kushal, i would keep those separate 17:33:07 is there a way within the testing framework to do that? 17:33:10 tflink, Just wanted to ask once more loudly :) 17:33:15 scollier: there's going to be a taskotron task that automatically tests an image when the build goes in, guidelines for those tests are what the improvements to the Draft is about 17:33:24 tflink, who creates teh task? 17:33:27 jberkus: under development, still working out some of the details 17:33:47 scollier: the creator of the layered image, I think. nobody else makes sense to me 17:33:54 scollier: the tasks are created automatically, the image owner will be responsible for providing tests 17:34:06 maxamillion, tflink, ok 17:34:10 maxamillion, tflink, are there templates for tests? 17:34:19 to make it easier on the owner? 17:34:31 scollier: templates, no. examples, yes 17:34:47 scollier: not currently, there will be guidelines but creating templates for testing things in docker containers is like providing a testing template for shell scripts ... I'm not sure the methodology applies 17:34:53 we can look into templates once we have some better definition of "what is being tested and what is needed" 17:35:03 tflink: + 17:35:05 +1 17:35:07 ack 17:35:08 I can't type :/ 17:35:23 i think a pattern applies: run image, check port, check app... 17:35:27 the functionality needed in Taskotron is almost done, waiting on a few reviews and library to be packaged 17:35:35 tflink, excellent. 17:35:44 so, jberkus are you good here? 17:35:44 er, a library to be packaged 17:36:24 tflink: if you need package reviews, feel free to ping me and I'll gladly help there 17:36:25 the current plan is to initially provide 2 types of examples: one that uses a bash script to poke at the image and the other using py.test or unittest to build a more formalized test case/suite 17:36:27 scollier: yes, seems like tflink and maxamillion are on it 17:36:32 tflink, maxamillion would you mind braindumping some of this into the ticket? 17:36:36 maxamillion: thanks, will do 17:36:53 once we have a structure for this, we need to doc how to write the tests 17:36:55 scollier: can do, was waiting for some input from kushal before i wrote much more down 17:37:03 agreed 17:37:03 tflink: +1 17:37:09 excellent 17:37:27 #action kushal to work with tflink on smoke tests 17:37:29 #topic Fedora Coud Test Day for F24 https://fedorahosted.org/cloud/ticket/152 17:37:45 I just added the wiki page for the same 17:37:47 everything is still pretty vague but I think we're getting closer to being able to do some testing :) 17:37:48 looks like kushal has updated the ticket, got hte wiki updated 17:38:08 tflink, i've been struggling with testing images for fedora-dockerfiles.. forever. 17:38:22 Can someone please update the right components in bugzilla in https://fedoraproject.org/wiki/Test_Day:2016_05_10_Cloud ? 17:38:35 scollier: yeah, from what I can tell, pretty much everyone is struggling with that to a certain extent :-/ 17:38:56 Tomorrow I will work with the community members to write down some more tests, which we can then add into http://testdays.fedorainfracloud.org/events/7 17:38:57 dustymabe: did we ever get the needed Karma for Docker? 17:39:00 kushal: can you find the old test day info create a template from that 17:39:05 kushal, who would do that? 17:39:10 jzb: we need one more +1 :) 17:39:14 dustymabe: OK 17:39:28 dustymabe: I just put F24 beta on my new laptop 17:39:30 scollier, anyone who wants to update :) Otherwise I will do that edit later tomorrow 17:39:31 well, pre-beta 17:39:40 Btw, 2016-05-10 is the test day :) 17:39:55 #info 2016-05-10 is the Fedora Cloud Test day 17:40:04 dustymabe, Okay, thanks. 17:40:12 great. all good here kushal? 17:40:18 we need to publish the heck out of that. 17:40:27 #action jzb write posts for Fedora Cloud Test day. 17:40:35 thanks jzb 17:40:40 jzb, I will ping you tomorrow evening, I should be having everything set for that. 17:40:52 scollier, yes, go ahead to next ticket 17:40:58 #topic design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 17:41:13 [GNU], ^ puiterwijk ^ 17:41:24 <[GNU]> ja, thats just a tracker for what jzb and maxamillion are doing 17:41:46 I think misc sent a mail to the list on the same. 17:41:57 scollier: misc sent an email to the infra list asking which binaries to pick 17:41:57 Or may be I am wrong and just dreamed about it. 17:42:09 But I think he had a thorough plan of what to do and got some parts setup 17:42:13 kushal, yes, do we know if there's a ticket on the fed-infra side for this? puiterwijk 17:42:20 puiterwijk, i will reply to that email today 17:42:27 [GNU]: I'm not a part of that 17:42:37 #action scollier to follow up on misc email for FOSP 17:42:58 everytime that comes up, I'm brought into it ... I have nothing to do with it, I don't know what's going one, please everyone stop pinging me about it 17:43:07 on* 17:43:11 maxamillion, ;/ 17:43:18 maxamillion, :) 17:43:18 like every other day I get a ping about it 17:43:32 I don't know!! :( 17:43:34 <3 17:43:56 scollier: I was calling it FOOT 17:43:59 maxamillion: sorry. I think we associate you with openshift too much 17:44:12 jzb, for? 17:44:31 <[GNU]> jzb, followup on other ticket? 17:44:56 puiterwijk, misc, is there fedora infrastructure ticket? if so, we can link to that from our side. 17:45:02 scollier: Fedora OpenShift Origin Testbed 17:45:12 dustymabe: which is totally fine, <3 me some openshift ... I'm just very ignorant as to what's going on with that specific project 17:45:13 jzb, ah. 17:45:28 scollier: I don't think so yet. 17:45:36 https://fedoraproject.org/wiki/Cloud/OpenShift_Origin_Testbed 17:45:50 jzb, nice! 17:45:54 I have not filled much out on that. And we can change it if FOSP is preferred. 17:46:00 I think we decided to have just one ticket so all discussions go to a single place, and since there's nothing directly needed from infra other than me and misc 17:46:03 * jbrooks likes FOOT 17:46:10 jzb, i'll add that to the ticket, maybe we can fill it out a bit. 17:46:20 We can talk about how it doesn't smell right, etc 17:46:35 +1 17:46:37 puiterwijk, fine here. so we can just use the ticket referenced here. 17:46:38 FOOT/FOSP - both are catchy. FOOT is fine 17:46:46 ok, no more feet. 17:46:48 scollier: fine with me 17:46:49 #topic make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 17:46:49 also, we can discuss arches 17:47:02 Testbed sounds a little more like its for automated testing 17:47:11 playground sounds more for experimentation :) 17:47:12 this is jberkus and kushal 17:47:16 FOOP? 17:47:19 haha 17:47:22 there's a lot of stuff with "OSP" in it and it's possibly ambiguous with OpenStack Platform, FOOT is probably better 17:47:31 FOOT++ 17:47:39 jberkus, I think now you have find someone from the website team to update the pages. 17:47:43 jzb: POOF ! 17:47:55 maxamillion, just like data 17:47:55 Playground for OpenShift Origin on Fedora .... somethimg something 17:48:03 kushal: so I don't know anything about how the fedora web infra works 17:48:04 I like 17:48:19 just paint the bikeshed so we can move on ;) 17:48:39 kushal: if it doesn't involve really complex stuffs we can just clone the repo and submit patches to the Website team. 17:48:41 jberkus, ask for help in #fedora-websites 17:48:48 they're super-happy (I think) when we just send a patch. 17:48:54 ok 17:48:59 jzb: what's the platform? 17:49:00 jzb, we can do that too, I prefer to stay away from HTML+CSS 17:49:06 pagure 17:49:20 https://pagure.io/fedora-websites 17:49:27 I believe that has the pages we are looking for. 17:50:03 time to create a fedora-website atomic app ;-) 17:50:36 ok 17:50:45 tow more tickets, 10 minutes 17:51:06 go go go 17:51:09 #topic Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 17:51:24 this one was created by maxamillion 17:51:29 o hai 17:51:54 list of deliverables: https://fedoraproject.org/wiki/Fedora_Program_Management/Updating_deliverables/Fedora24#updating_deliverables 17:52:19 maxamillion, these are guidelines, no? 17:52:34 maxamillion, like the docker base image has exceptions for security reasons? 17:52:43 or does the user have to update a running image? 17:52:52 scollier: yes, but we need at least a target "normal" cadence of releases 17:52:53 Looks good to me. 17:52:58 ack 17:53:00 there are some question marks 17:53:13 scollier: currently we're planning ad-hoc based on high sev security but details are still being sorted 17:53:26 maxamillion, ack. that's good 17:53:47 basically Atomic Repos and Atomic Installer Image are the only '?' left (refresh the page, I just updated) 17:53:47 maxamillion, for the atomic images, are those not on 2 week cycles? 17:53:48 should the atomic ISO and the atomic cloud image say 2 weeks? 17:53:54 scollier: they are 17:53:57 dustymabe, yes I think 17:54:03 the Atomic ISO currently gets no testing 17:54:06 well, that's not true 17:54:11 it gets no post-install testing 17:54:15 maxamillion, it does in OpenQA 17:54:20 maxamillion, True 17:54:50 maxamillion, I will ping you about it later. 17:54:53 and there have been issues in the past with anaconda where the install passed but the storage config was messed up but it wasn't noticeable until post-install reboot 17:54:57 kushal: alright 17:55:03 excelelnt 17:55:04 one more 17:55:05 maxamillion: yeah, that has been fixed, I believe. 17:55:13 lmacken: it has 17:55:15 because it wasn't installing to a volume < 40G or something 17:55:26 >40G, rather 17:55:27 lmacken: but we have no automated testing in place that would have caught that 17:55:30 caught* 17:55:34 right. 17:55:46 * lmacken caught it :P 17:55:54 lmacken++ 17:55:54 kushal: Karma for lmacken changed to 10 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:56:00 maxamillion, do we have a list of things we want to test, and the tests need to be written by someone? 17:56:12 scollier, should be the same of normal atomic images. 17:56:15 Atomic Repos ... do we want those to be constantly updated daily just like the RPM repos or do we want that to follow the two-week release? (The Atomic team has said they'd like to see an option stream of 2 week cadence but I'm open to suggestion here) 17:56:19 kushal, oh 17:56:46 maxamillion, I say update only in 2 weeks. 17:56:49 kushal: true but I think the method of running them is a bit different, no? 17:57:04 maxamillion, Unless there is a security update. 17:57:05 ie, installing with anaconda and then running vs. starting an image 17:57:12 maxamillion: is there a problem with doing it like we do today? 17:57:13 tflink: +1 17:57:22 dustymabe: not that I know of, no 17:57:33 tflink, I was talking about the tests after the installation is done. 17:57:39 dustymabe: but there's been requests for something different in the past so it was brought up from a scheduling standpoint 17:57:57 right. I think I saw walters request something like this in the past 17:57:57 tflink, maxamillion That user experience should be the same of any other atomic user. 17:57:59 3 minutes. 17:58:04 I can't remember the reasons 17:58:12 kushal: yeah, just trying to add detail - the tests may be the same from a high level but there are pretty big differences in the details of how they need to be run 17:58:34 tflink, yes, I was not saying anything about that part. 17:58:35 kushal: +1 17:58:38 dustymabe: I can't either 17:58:48 dustymabe: I think there's a releng ticket about it, I'd have to go looking for it 17:58:58 we can table this if needed though, it's not urgent 17:59:08 I'll get more information on the atomic repos and add to the ticket 17:59:14 1 minute :) 17:59:14 maxamillion, thanks. 17:59:18 maxamillion: maybe the idea is to have more testing on the tree before we release it 17:59:21 or something 17:59:31 ok, 1 minutes round table. :( 17:59:39 sorry about that folks. 17:59:49 open floor? 17:59:51 yup 17:59:59 anyone have anything? 18:00:10 From 25th to 12th i will be in US for PyCon+Cloud FAD 18:00:10 dustymabe: but there won't be any more testing, it all gets the same testing nightly 18:00:12 * tflink has one quick thing 18:00:22 We need chairs to help on those days. 18:00:31 I want to bring up that the cloud base and cloud base vagrant images are now using extlinux 18:00:36 maxamillion, we have to book hotel :) 18:00:41 dustymabe, yay :) 18:00:49 alright folks. we are at time. 18:00:57 let's move back to fedora-cloud 18:00:57 this could be a good or a bad thing depending on how you look at it 18:01:01 http://209.132.184.119/compose 18:01:02 i've heard little bits about a setup to do automated testing on docker in fedora - if anyone knows about it, could you let me know so I know where to direct people when i get questions about it 18:01:08 thanks everyone, we'll pick up next week. 18:01:10 ^^ new web ui for compose based autocloud 18:01:17 #endmeeting