17:00:53 #startmeeting Fedora Cloud WG 17:00:53 Meeting started Wed Feb 3 17:00:53 2016 UTC. The chair is kushal. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:53 The meeting name has been set to 'fedora_cloud_wg' 17:00:59 #topic Roll Call 17:01:05 .hellomynameis kushal 17:01:06 kushal: kushal 'Kushal Das' 17:01:07 .fas jasonbrooks 17:01:09 jbrooks: jasonbrooks 'Jason Brooks' 17:01:09 .hello smdeep 17:01:12 smdeep: smdeep 'Sudeep Mukherjee' 17:01:19 .hello trishnag 17:01:21 trishnag: trishnag 'Trishna Guha' 17:01:23 .hello scollier 17:01:24 scollier: scollier 'Scott Collier' 17:01:28 .hello mmicene 17:01:29 nzwulfin: mmicene 'Matt Micene' 17:01:46 Anyone else? 17:01:59 #chair jbrooks smdeep trishnag scollier nzwulfin 17:01:59 Current chairs: jbrooks kushal nzwulfin scollier smdeep trishnag 17:02:06 #chair maxamillion 17:02:06 Current chairs: jbrooks kushal maxamillion nzwulfin scollier smdeep trishnag 17:02:07 .hello maxamillion 17:02:08 maxamillion: maxamillion 'Adam Miller' 17:02:33 Anyone else? 17:03:45 Okay, last week we had very low attendance 17:03:55 This week is better 17:04:08 So action items from the old meeting 17:04:51 #topic Action items from last meeting 17:04:52 * jzb actually update ticket 135 17:04:52 * jzb will update and close 135 17:04:52 * kushal to find test results and then create the ticket to release 17:04:52 https://dl.fedoraproject.org/pub/alt/atomic/testing/23-20160116/Cloud-Images/ 17:04:52 * jzb open ticket with Websites about listing current AMIs 17:05:00 jzb, is not here today. 17:05:27 I decided to wait for a new build to mark it release ready, but then from 29th all builds are failing :( 17:06:16 So, want to know if everyone here is okay about releasing https://dl.fedoraproject.org/pub/alt/atomic/testing/23-20160116/Cloud-Images/ as the updated image? 17:06:29 I will still have to file the rel-eng ticket anyway. 17:06:31 .fas subho 17:06:32 subho: subhodip 'Subhodip Biswas' <440volt.tux@gmail.com> - subho '' 17:06:49 kushal, any known issues? 17:06:50 subho, type .hellomynameis sucho 17:06:59 scollier, Nope iirc 17:07:09 but there must be tons of new packages :) 17:07:13 including a new kernel 17:07:23 Not sure if that matters :) 17:07:30 .hellomynameis subho 17:07:31 subho: subho 'None' 17:07:42 kushal, what kind of QA doe the images get before marked as ready for release? 17:07:43 .fas sayanchowdhury 17:07:43 sayan: sayanchowdhury 'Sayan Chowdhury' 17:08:03 yeah, there were some issues with the builds prior to the last two-week release ... appears we have new ones 17:08:22 scollier, currently we only had automatic autocloud one, but today I am going to ask our manual testers to test this one once. 17:08:37 smdeep, fhackdroid trishnag are part of that team 17:08:39 kushal: wait, releasing what now? .. is this the two-week atomic or something else? 17:08:49 maxamillion, updated base image :) 17:08:56 maxamillion, not two week atomic :) 17:09:01 kushal: ah, cool cool 17:09:11 http://koji.fedoraproject.org/koji/tasks?start=0&state=all&view=flat&method=createImage&order=-id 17:09:22 ^^ this link shows the states of all cloud builds 17:09:32 ok 17:09:40 kushal, okay 17:09:44 kushal, sorry, but what's the diff between a base image and a two week? i should prob know this. 17:10:09 scollier, base image is the regular cloud image, two week atomic is the Atomic host image :) 17:10:16 kushal, oh, ok. 17:10:46 scollier, So two week atomic goes out regularly thanks to help from maxamillion and rest of the rel-eng team. 17:11:05 kushal, +1 from me if your team runs it through the ringer 17:11:05 But we have to test this base image to release it as an updated image. 17:11:12 kushal, ack 17:11:14 scollier, Noted, thanks :) 17:11:33 smdeep, trishnag pryanka fhackdroid you have work :) 17:11:35 kushal, do you have a test plan you can link to? 17:11:51 Sure 17:12:07 scollier, we have the formal QA tests, and then one can run the formal autocloud tests too using tunir. 17:12:26 scollier, wait, giving the link 17:12:48 * kushal searches his worknotes. 17:12:59 the Cloud Base image is an official deliverable for a normal Fedora Release isn't it? ... if so, do we have any kind of sign off from QA for the release criteria being met? (do we need to modify that criteria?) 17:13:06 https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test 17:13:06 kushal, can send later. that's ok. 17:13:11 kushal, excellent, thanks. 17:13:25 maxamillion, ^^ those are the formal tests we have to run 17:13:45 kushal: awesome +1 17:14:02 maxamillion, I will create a copy of that page so that people can update. 17:14:28 kushal: sounds good 17:14:30 https://github.com/kushaldas/tunirtests/wiki 17:14:46 ^^ this contains details of current tests on autocloud. 17:14:55 * scollier looks 17:15:09 * smdeep bookmarks 17:15:32 That reminds me to update the file test (it is a non-gating test), and the package is not there in the base image anymore :) 17:15:49 Not sure if we count that as a bug or not. 17:16:50 For the rest of open tickets, do anyone wants to discuss any from https://fedorahosted.org/cloud/report/9 ? 17:16:51 kushal, on the wiki page, in the "how to test" section, I don't see the cloud image listed for download 17:17:02 in teh table 17:17:15 scollier, yeah, we have to fill those for our nightly. 17:17:45 kushal, i don't understand what that means 17:18:27 scollier, Means that wiki page for the latest rawhide, but we need to make one for our release (and the latest rawhide builds are broken). 17:19:03 scollier, We are thinking about marking our nightly 23-20160116 as the updated release. 17:19:10 s/thinking/talking 17:19:38 kushal, ok, so it would be added to the table for everyone to test? got it. 17:19:48 yes. 17:19:51 scollier, manual work :) 17:19:57 kushal, ack. got it, thanks. 17:20:15 Do we want any owners to discuss any of https://fedorahosted.org/cloud/report/9 ? 17:20:43 * scollier looks 17:21:23 yeah, I want to discuss https://fedorahosted.org/cloud/ticket/148 ... we had talked about it previously and people said they would comment on the ticket but haven't 17:21:39 kushal, there's not really a ticket for it, but i got the fedora-dockerfiles from 15 open PRs down to 4, now back up to 7. still cleaning up the merge from f22,23 branches back to master. 17:21:43 maxamillion, guilty as changed . 17:21:50 scollier++ 17:21:50 kushal: Karma for scollier changed to 1 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:22:00 if I don't get anything back, I'm just going to move forward with things as-is and submit to FESCo 17:22:08 maxamillion, reading 17:22:12 maxamillion, Will put this priority for this week. 17:22:35 scollier, btw, I was wondering about having more real usable apps there as Fedora docker files 17:22:45 kushal: much appreciated 17:22:47 and then some good documentation about how to use them. 17:22:48 kushal, such as? 17:23:24 scollier, say a normal user want to run ghost (blogging platform) or wordpress on their atomic image. 17:23:55 got it, so multi-container configurations that comprise an application 17:23:58 scollier, if we can provide them something (may be nulecule spec based) which will be super easy to install/run 17:24:01 kushal, i've wanted that forever 17:24:07 scollier, Yes sir. 17:24:11 scollier, /me too 17:24:40 maxamillion, this is in progress too: https://github.com/projectatomic/container-best-practices 17:24:51 scollier, that can be really useful for atomic users. 17:24:56 maxamillion, providing guidelines for Dockerfiles, etc... 17:25:04 scollier, and we can get more people to use our two week releases 17:25:11 https://github.com/projectatomic/container-best-practices 17:25:18 Just putting up for link :) 17:25:19 maxamillion, i think one of the things we are thinking about is providing a "Dockerfile Template" which would container required labels, etc... 17:25:31 scollier: ah, I didn't know that existed ... nice 17:25:32 kushal, ack. 17:25:51 maxamillion, it's meant to be an upstream effort. 17:25:56 scollier: rocking 17:26:18 maxamillion, to create the doc, just clone and "make" it'll create an index.html that you can view the content with 17:26:27 scollier, is there any place to read the html? 17:26:32 like readthedocs 17:26:48 kushal, they are working on getting it integrated into projectatomic.io 17:26:53 scollier, Okay 17:26:57 so that nightly builds would be published automagically 17:27:17 maxamillion, IMO though, what you've raised is a complicated topic :) 17:27:22 scollier, this is why I like readthedocs and sphix personally, every git push goes in nicely 17:27:36 kushal, ok, will pass that along. 17:27:55 who is working on integrating it on projectatomic ? 17:28:05 scollier: it is 17:28:05 misc, hello there :) 17:28:11 #chair misc 17:28:11 Current chairs: jbrooks kushal maxamillion misc nzwulfin scollier smdeep trishnag 17:28:23 misc, baude 17:28:25 (cause I guess I could help as I did the builder for the website, and it can support pulling from more than 1 git) 17:28:33 misc, excellent 17:28:36 scollier: it needs to be project-wide but it's so far just been me writing down whatever the hell I thought made sense, this is my attempt to get more folks involved so we can really drive it 17:28:38 mind if i connect you tow? 17:28:50 maxamillion, totally understand 17:28:59 scollier: no problem. but I am traveling for the time being and in pto for a while after :) 17:29:06 misc, ack 17:29:22 Any thing else? 17:29:26 maxamillion, i think it might be helpful 17:29:36 We are like almost "Open Floor" anyway. 17:29:38 if you held a "review workshop"? of sorts 17:29:40 (and I am also in brno tomorow evening, so we can also discuss over beverage, it usually help to raise priority to make sure I am not thirsty) 17:29:50 misc, :) 17:30:03 Is it open floor now? 17:30:11 scollier: connect what? 17:31:04 #topic Open Floor 17:31:05 maxamillion, i was asking misc if i could connect him and baude for integrating the best practices guide into projectatomic.io 17:31:07 smdeep, Now :) 17:31:17 kushal, so I will test 23-20160116 manually right? 17:31:19 Is Kung Fu Panda 3 alright for an 8 year old 17:31:19 scollier: ohhh ok 17:31:22 :) 17:31:30 maxamillion, i was mentioning to you that i think it would be good if you held a reviewer workshop 17:31:34 and covered the toolchain 17:31:37 trishnag, yes, just download that image on our infra cloud. 17:31:45 kushal, okay :) 17:31:57 smdeep, :) 17:32:02 :) 17:32:13 scollier: absolutely, I'd be really interested in that 17:32:21 scollier: I haven't the first clue how to go about that though 17:32:28 So this week people are busy+ traveling for devconf 17:33:02 kushal: +1 17:33:14 maxamillion, happy to brainstorm over an etherpad if you like 17:33:53 trishnag, read your blog very insipiring 17:34:04 Anyway if there is nothing else we can end the meeting. 17:34:17 scollier: yup, I'm in 17:34:17 maxamillion: a question, is there a good resource to start learning to write tests 17:34:27 nzwulfin: that'd be a question for kushal 17:34:34 smdeep, thank you :) :) 17:34:47 trishnag, welcome! 17:34:51 sorry i meant for taskotron .. re your email to the list 17:34:52 nzwulfin, I guess you saw your github wiki page. 17:34:56 nzwulfin, ah :) 17:35:22 i've got some bad tunirtests already submitted ;) 17:35:48 nzwulfin, hehe :) 17:35:56 i found running / installing / managing taskotron, but not how to actually write a YAML test 17:36:10 nzwulfin: oh, a lot of that is up in the air right now ... the implementation of the mechanism by which we will write the tests is still in flight, but to the best of my knowledge one of the goals will be that we could run the tunir tests via taskotron (or something similar) 17:36:35 ah ok .. then i'll stay tuned to that discussion 17:37:56 Okay, then closing this meeting. 17:38:06 5 17:38:08 4 17:38:08 3 17:38:09 2 17:38:10 1 17:38:11 #endmeeting