17:03:57 #startmeeting Fedora Atomic Working Group 17:03:57 Meeting started Wed Nov 23 17:03:57 2016 UTC. The chair is kushal. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:03:57 The meeting name has been set to 'fedora_atomic_working_group' 17:04:05 #topic Roll Call 17:04:08 .hello scollier 17:04:09 .fas jasonbrooks 17:04:09 scollier: scollier 'Scott Collier' 17:04:12 jbrooks: jasonbrooks 'Jason Brooks' 17:04:12 trishnag, you can take over now :) 17:04:19 .hello rmartinelli 17:04:19 .hello dustymabe 17:04:19 rmartinelli: Sorry, but you don't exist 17:04:21 .hellomynameis kushal 17:04:23 dustymabe: dustymabe 'Dusty Mabe' 17:04:24 .hello maxamillion 17:04:25 .hello rimolive 17:04:26 kushal: kushal 'Kushal Das' 17:04:27 .hello trishnag 17:04:29 .hello sayanchowdhury 17:04:29 maxamillion: maxamillion 'Adam Miller' 17:04:30 .hello misc 17:04:32 rmartinelli: rimolive 'None' 17:04:35 trishnag: trishnag 'Trishna Guha' 17:04:38 sayan: sayanchowdhury 'Sayan Chowdhury' 17:04:42 misc: misc 'None' 17:04:48 .hello bowlofeggs 17:04:49 bowlofeggs: bowlofeggs 'Randy Barlow' 17:04:59 #chair scollier jbrooks rmartinelli dustymabe maxamillion trishnag sayan misc bowlofeggs 17:04:59 Current chairs: bowlofeggs dustymabe jbrooks kushal maxamillion misc rmartinelli sayan scollier trishnag 17:05:07 trishnag, take over please 17:05:13 * trishnag was going to chair only 17:05:58 trishnag, I am not stealing the chair, no worries :) 17:06:12 #topic Action items from last meeting 17:06:35 I'm very sorry but I have to step afk for a couple minutes, I will catch up on backscroll asap 17:06:47 maxamillion: that's fine 17:07:03 * kushal will write to list for the agenda of the features meeting for Atomic group 17:07:09 * trishnag will create an issue on tunirtests for https://pagure.io/atomic-wg/issue/173 17:07:12 maxamillion: sure 17:07:30 and I missed it thanks to my sick leaves + allergies 17:07:37 I will send it out tomorrow morning my time. 17:07:48 trishnag, readd that please :) 17:07:56 kushal: sure. thanks for the update 17:08:01 I just created the ticket on tuniritests https://github.com/kushaldas/tunirtests/issues/57 17:08:53 moving to the meeting items 17:08:57 #topic Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 17:09:12 #action kushal will write to list for the agenda of the features meeting for Atomic group 17:09:24 sayan: Thanks 17:09:36 scollier: hey. here comes the future of dockerfiles :) 17:09:45 scollier: should we revisit this when maxamillion comes back to keyboard? 17:09:51 dustymabe, sure 17:09:55 dustymabe, i have some questions 17:09:56 dustymabe: cool 17:09:57 trishnag: let's push this to last? 17:10:02 yes 17:10:08 okay 17:10:33 scollier: please go ahead :). or do you want to wait for maxamillion to come back? 17:10:41 trishnag, wait 17:10:50 okay 17:11:11 #topic Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users https://pagure.io/atomic-wg/issue/173 17:11:45 trishnag: this should be an easy fix - assign to me and untag from meeting 17:11:55 dustymabe: okay 17:12:26 dustymabe: done 17:12:49 #topic Finish new Fedora Cloud PRD https://pagure.io/atomic-wg/issue/170 17:13:04 jberkus is missing today 17:13:17 jberkus is not around. Does anybody want to say something for this ticket? 17:13:46 kushal: I don't have anything for that today 17:14:17 It seems I can take that as no. moving to next item. 17:14:23 #topic Spec for IRC bot to notify about blockers https://pagure.io/atomic-wg/issue/169 17:14:57 I hope we will notice the channel topic 17:15:03 Who all actually read the topics? 17:15:12 kushal: I don't 17:15:17 or rarely.. 17:15:47 same here. I don't. 17:15:53 nope 17:16:23 rarely too 17:16:26 So, somehow I am feeling that we are trying to solve a human issue with technology 17:16:34 But ... 17:16:37 * maxamillion is back 17:16:54 apologies 17:16:54 maxamillion, welcome back :) 17:16:59 kushal: I think emails to the list are a better answer 17:17:04 dustymabe: +1 17:17:19 and probably easier to implement 17:18:21 Why not push the fedmsg messages to the channel? 17:18:35 dustymabe, yes, we can just enable any failure bugs to pagure into a mail to the list 17:18:46 dustymabe, Sayan has bugyou for filing bugs 17:19:20 But he had problem about image names iirc 17:19:20 now we do need to be careful about too many notifications 17:19:30 sayan, do you want to talk about that? 17:19:44 hopefully we don't have too many "blocker" bugfs 17:19:45 dustymabe, I would love to see people complaining about too many notifications :) 17:20:50 yes, the issue was that since the image name has dates, bugyou was creating new issues everyday 17:20:52 we do have to realize that 99% of people on the cloud list are casual users/contributors and too many notifications will turn them off 17:20:59 or with every autocloud failure 17:21:11 I fixed the issue with regex 17:22:17 dustymabe: yeah 17:22:19 ok so can we decide on something? 17:22:25 IRC->email 17:22:45 and the frequency of emails is something we can tweak as we go 17:23:02 who has an action item out of this? 17:23:26 we can throw every notification to IRC and tweak the number of emails that goes 17:23:33 to the list 17:23:44 sayan: ok 17:23:49 sayan, email will go out for every update (that is every failure on autocloud) from pagure 17:23:58 would you like to update the ticket ? 17:24:21 dustymabe, I will 17:24:44 dustymabe, not just in current condition (bad state with allergy attacks), will do that tomoor 17:24:47 tomorrow 17:24:53 kushal: sure. 17:24:55 I look into this and update on my findings 17:24:58 #action kushal to update #169 17:25:29 ok let's move to the next ticket. 17:25:34 #topic Ship fedora-motd in F24 atomic image https://pagure.io/atomic-wg/issue/160 17:25:46 is rtnpro around? 17:25:51 F24 atomic is dead 17:25:56 rtnpro: kushal any update for the ticket? 17:26:00 maxamillion: RIP 17:26:02 maxamillion, has to update to F25 17:26:04 dustymabe, haha 17:26:05 maxamillion: yeah 17:26:14 kushal: +1 17:27:08 looks like rtnpro is not around. 17:27:22 #topic Proposed website changes for Cloud Base → Atomic Host switch https://pagure.io/atomic-wg/issue/158 17:27:28 I don't think he would be around for next few weeks 17:27:44 I guess we can close this as we are in F25 lifetime now 17:27:46 sayan, :) 17:28:17 We now have it https://getfedora.org/atomic \o/ :) 17:28:38 i'll update the ticket and close it 17:28:40 we can close the ticket https://pagure.io/atomic-wg/issue/158 ? 17:28:48 dustymabe: cool thanks. 17:29:23 #topic make Fedora Atomic download page clearer https://pagure.io/atomic-wg/issue/154 17:29:43 trishnag: will ping jberkus for an update on this 17:29:49 go to next 17:29:51 dustymabe: okay 17:30:12 #topic design, deploy and document Fedora OpenShift Playground (FOSP) https://pagure.io/atomic-wg/issue/153 17:30:32 jberkus isn't around. 17:30:37 mhh ? 17:30:52 misc: hey :) 17:31:15 so, for fosp, we have a domain name : fosp.fedorainfracloud.org, and I did reinstall all on Fedora 25 17:31:34 and now the status is "console work, but the reigistry wasn't deployed", and I am fixing it 17:31:36 misc: f25 atomic host? 17:31:41 dustymabe: nope, cloud 17:31:54 misc: ok 17:32:00 how much hardware do we have there? 17:32:08 still running in fedora cloud 17:32:17 misc, tell me if we can test and help :) 17:32:21 misc: i.e. the openstack thing? 17:32:27 dustymabe: yup 17:32:41 so around 20 cores I think, in 8 VM 17:32:45 ok 17:33:09 kushal: oh, I was about to send something, but when i tested, i found that there was no registry 17:33:10 misc: can we have a meeting sometime with "everyone interested in FOSP" to kind of get a briefing on that project? 17:33:16 so console is functional 17:33:31 but you can't build anything and t took me a while to understand why 17:33:56 dustymabe: briefing on the progress ? 17:34:05 I'm getting Connection Reset in this domain. Is it already available? 17:34:11 dustymabe, +1 to that idea 17:34:15 misc: not exactly. basically a 0 to 60 of everything FOSP 17:34:25 dustymabe: sure 17:34:35 on friday ? 17:34:36 what it is, what hardware do we have, where it lives, who controls it, what are the plans, what is the current status 17:34:48 misc: maybe schedule for two weeks from now 17:34:55 dustymabe: +1 17:35:07 holidays in the US this week 17:35:17 1) a openshift instance deployed for the WG to test openshift 2) none 3) in openstack instance of Fedora 4) not panicking 5) waiting on ansible 17:35:53 oh wait, i fogot who control, so far, me, but others gave me their ssh keys. As this is not working yet, I have yet to write more docs 17:36:05 would still be good to havea meeting with a short preso if possible 17:36:13 to get more people up to speed 17:36:16 sure, even a long preso :) 17:36:16 EOM :) 17:37:34 [Frost gathers on the windows] 17:37:49 FGOTW? 17:37:51 :) 17:38:09 hehe 17:38:28 okay we can now probably move to the next ticket. 17:38:35 #topic vagrant boxes fixups https://pagure.io/atomic-wg/issue/136 17:39:11 jbrooks has already created PR for the ticket. 17:39:43 yep. now we just need someone to give imagefactory some love :) 17:39:58 The PR needs to be reviewed though https://github.com/redhat-imaging/imagefactory/pull/392 17:40:28 dustymabe, do you know who is maintaining it? 17:40:51 kushal: ian wrote it, i don't know who is maintaining it now 17:40:58 dustymabe, same here 17:41:25 looks like mostly Iam 17:41:29 Looks like ian. 17:41:36 Ian, but I know he would love for someone to take it on 17:41:41 yeah, he merges PRs 17:42:52 ok, next 17:43:05 Moving back to first ticket. 17:43:13 #topic Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 17:43:20 scollier: there you go. 17:43:25 ok, sec 17:44:31 so i had several good comments on the ticket over the past week 17:44:40 none of them advocating that we continue fedora-dockerfiles 17:44:43 so 17:45:14 what i need is, a link to a procedure that I can add to the github repo, which points potential contributors to fedora-dockerfiles, to the new dist-git process 17:45:24 I'm aiming to have "New (scaled-out) Docker Layered Image Build Service" available in about two weeks which will allow for all of the fedora-dockerfiles to be migrated to Fedora's DistGit and be distributed directly from Fedora (and mirrored to Docker Hub on a two-week release cadence) 17:45:38 maxamillion, that's great 17:45:46 i'd like to capture that process and point people to it 17:46:05 in the mean time, I am going to add a note, that we are not taking any new PRs 17:46:14 I have docs in the wiki that are still in draft form, I'm going to clean them up next week and get them out the door but the procedures and guidelines have all passed FESCo approval (FPC passed them along to FESCo for review/approval) 17:46:50 maxamillion, i believe i have that link. 17:46:54 cool 17:46:55 trishnag, so, that's pretty much it 17:47:01 anything from anyone else on the topic? 17:47:41 scollier: ack. Thanks for the update. 17:48:15 Moving to open floor 17:48:18 trishnag, i'll leave the ticket open until maxamillion and I are closed out 17:48:29 scollier: Sure thing. 17:48:45 scollier: I would propose that we move the Fedora Dockerfiles repo to something like Fedora-Dockerfiles-Examples 17:48:53 the old links will still redirect 17:49:08 dustymabe, and leave it running? 17:49:11 and make the readme very clear about the status of the dockerfiles in that repo 17:49:31 scollier: sure, i.e. you can just have people that submit PRs and merge them without feeling bad 17:49:35 dustymabe, we need a maintainer for that. 17:49:39 But do we have maintainer for the repo? like scollier asked 17:49:43 or we could just freeze the repo 17:49:58 dustymabe, that's what i was thinking, freeze, and move people over. 17:50:11 i dont have cycles to maintain a fedora-dockerfiles-* repo 17:50:27 scollier: k 17:50:42 can you guys update the ticket with the status? 17:50:48 dustymabe, yes 17:50:51 scollier: Do you need volunteers to maintain? I can help. 17:51:12 rmartinelli, i would like to go in and address the existing open PRs, if you can help, that would be great 17:52:08 scollier: ok, I'm in. 17:52:26 rmartinelli, thanks 17:53:18 #topic Open Floor 17:53:33 Is it just me or does the web site have no links to regular cloud images at all now? 17:53:51 A couple people have asked me where to find them, and the best I could point them to was dl.fp.o. 17:53:52 gholms: that is right. we are making a new page 17:53:59 They aren't even on alt.fp.o yet. 17:54:00 gholms: It has 17:54:16 gholms: https://alt.fedoraproject.org/ 17:54:27 https://pagure.io/fedora-websites/issue/57 17:54:30 Alternative Downloads on https://getfedora.org/ 17:54:50 trishnag: Can you point me to what part of that page points to cloud base images? 17:54:54 gholms: I'll send an email to the cloud list that you can point people to 17:55:12 * misc also add people asking 17:55:14 Okay, so it's still a work in progress, then. 17:55:23 gholms: we have to create https://cloud.fedoraproject.org 17:55:25 s/add/had/ 17:55:26 it is not there 17:55:43 gholms: yes. in short. this working group has been really bad at making any changes 17:55:54 mattdm opened his ticket a long time ago 17:56:07 Oh interesting. It was there today morning :) 17:56:07 not anymore now. 17:56:08 and we never followed up with the websites team to let them know they needed to do work 17:56:16 Hehe. The constant struggle of being stretched too thin. ;) 17:56:22 trishnag: It was not there yesterday either. 17:56:28 gholms: yes, hopefully it will be better now 17:56:28 gholms: Cloud images are not anymore here https://alt.fedoraproject.org :). 17:56:30 You might be thinking of the aarch64/ppc page. 17:56:37 I have some more cycles to "close the loop" on some issues 17:56:52 ...which would be great if I was one of the five people running a cloud on one of those architectures. ;) 17:56:59 gholms: I have seen today :)(India morning). and pointed the link to someone :( 17:57:18 The link you posted was to dl.fedoraproject.org, IIRC. 17:57:36 trishnag: it's possible the web team has been making progress and that is what you saw 17:57:42 So anyhoo, yeah, it's still a known issue, so I can stop worrying about it now. 17:57:42 this is an open ticket they are working on btw 17:57:51 gholms: I will send a mail to the list and link you to it 17:57:53 dustymabe: might be. 17:57:54 :) 17:57:58 so we need to wait for https://cloud.fedoraproject.org 17:58:05 and summarize the issue as well as provide links for all deliverables 17:58:10 Thanks 18:00:17 We are almost at the end of the meeting. 18:00:19 going 18:00:20 5 18:00:21 4 18:00:21 3 18:00:22 2 18:00:24 1 18:00:25 #endmeeting