17:04:09 #startmeeting fedora_atomic_wg 17:04:09 Meeting started Wed Mar 8 17:04:09 2017 UTC. The chair is jberkus. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:04:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:04:09 The meeting name has been set to 'fedora_atomic_wg' 17:04:19 #topic roll call 17:04:21 .hello maxamillion 17:04:22 maxamillion: maxamillion 'Adam Miller' 17:04:26 .hello jberkus 17:04:27 jberkus: jberkus 'Josh Berkus' 17:04:27 .hello trishnag 17:04:28 .hello sayanchowdhury 17:04:30 trishnag: trishnag 'Trishna Guha' 17:04:33 sayan: sayanchowdhury 'Sayan Chowdhury' 17:04:42 .hello roshi 17:04:43 roshi: roshi 'Mike Ruckman' 17:05:20 hey, logs for last week's meeting appear to be missing 17:05:36 https://meetbot.fedoraproject.org/sresults/?group_id=atomic_wg&type=team 17:05:57 * roshi has always wondered why we send them to the list when they're on meetbot... 17:06:01 aha 17:06:17 so we've been using the names "fedora_atomic_wg" and "atomic_wg" alternately 17:06:22 whcih breaks meetbot 17:06:55 #chair jberkus roshi trishnag sayan maxamillion jbrooks 17:06:55 Current chairs: jberkus jbrooks maxamillion roshi sayan trishnag 17:07:33 #topic Container Policy VFAD 17:07:47 so first thing is that we have a VFAD to hammer out some container policy things this Friday 17:08:13 all of these issues are explained here: https://pagure.io/atomic-wg/issues?status=Open&tags=VFAD 17:08:40 schedule for VFAD and goals are here: https://pagure.io/atomic-wg/issue/238 17:08:52 current schedule is 17:09:03 EST UTC 17:09:03 10:00-12:00 15:00-17:00 Part I 17:09:03 12:00-13:00 17:00-18:00 Break 17:09:04 13:00-15:00 18:00-20:00 Part II 17:09:43 don't forget atomic-wg 17:09:43 +1 17:10:00 * roshi plans to be there 17:10:03 I'll be setting the specific schedule after this meeting, so you have 1 hour to (a) add additional container policy issues if you have them, or 17:10:16 (b) comment on any of those issues that you need to be present and have time constraints 17:10:34 for example, kushal, you will probably only be ther efor the first half, so please mark which issues you care about most 17:10:52 * jbrooks will be there 17:11:10 VFAD questions/comments? 17:11:20 I will try to. late here..timezone. 17:11:21 * bowlofeggs waves wildly 17:11:50 May be the first half :) 17:11:53 trishnag: yeah, same with you. please *comment* on the issues you care the most about, and I'll put them first on the agenda 17:12:06 jberkus: OK 17:12:24 trishnag: sorry to have it so late, but Globe Is Round 17:12:31 also I need to be awake to run it 17:13:04 next 17:13:09 #topic Action Items 17:13:24 1. Dusty to create page for future VFAD topics 17:13:52 I did this actually: https://fedoraproject.org/wiki/Atomic/VFAD_ideas 17:14:04 if there is a VFAD you think we should have or you want to have, please add it to that wiki page 17:14:12 +1 17:14:23 even if it's a kinda sorta half VFAD, we'll combine it with something else 17:15:16 2. sayan to create ticket on moving fedimg 17:15:19 sayan: ? 17:15:30 jberkus: yes, I created the ticket 17:15:39 link? 17:15:47 for the minutes 17:15:57 yes, digging up the link 17:16:12 jberkus: https://pagure.io/atomic-wg/issue/237 17:16:20 thanks 17:16:42 #link https://pagure.io/atomic-wg/issue/237 17:16:52 ok, next up, issues 17:16:58 #topic issues 17:17:46 before I go through meeting tags, there's one outstanding in Web 17:17:51 right now we have NO AMI links 17:18:11 that's probably not great 17:18:26 no, and we haven't had them for 2+ weeks 17:18:48 https://pagure.io/fedora-websites/issue/641 17:18:56 this appears to be because of a permissions issue on the AMIs 17:19:13 https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/VJH4HG2N5NO3LT6MDVR63GIDNS3OXSIX/ 17:19:29 however, there has been no progress in resolving this in the last week AFAICT 17:20:53 jberkus: I wrote the script that fixes that issue 17:21:04 yah. so any idea what happened from there? 17:21:24 dgilmore need to run the script as I don't have the access to the main account 17:21:40 ah 17:21:45 who all has access? 17:21:51 jberkus, I will update accordingly (I am on leave today). 17:21:53 is that anyone in Infra? or is that RelEng? 17:21:58 maxamillion: afaik, dgilmore and mattdm 17:22:02 we should probably spread it out so we can fix issues like this 17:22:03 sayan: ah ok 17:22:04 maxamillion, only dennis and mattdm 17:22:09 noted 17:22:33 roshi: well, it has implications about a line of credit also so there might be some legal paperwork that has to be signed and such 17:22:33 ok, I think someone needs to nag those two until either it gets fixed or they grant access 17:22:35 roshi, dgilmore said that he does not want that primary account access to be shared across. 17:22:49 roshi: I definitely agree, but it might be a little more than just adding someone to the account 17:22:49 yeah, I remember when the change was made 17:23:00 it used to be open to the whole group 17:23:09 roshi: which I now realize you didn't actually infer ... so ignore me 17:23:21 I can't brain ... need more coffee 17:23:36 maxamillion: can you follow up on this? or should someone else? 17:24:13 I sense that it won't happen without follow-up 17:24:56 jberkus, yup. May be we can add acarter to the discussion. 17:25:03 That can help to speed things up. 17:25:25 kushal: you want to do the follow-up? 17:25:41 we need someone who will stay on this issue until it's resolved 17:26:05 jberkus: yeah, I can 17:26:06 don't all step forwards at once 17:26:07 I did ping dgilmore on IRC, he told he need to look how to generate the access tokens 17:26:09 ok 17:26:11 jberkus: sorry, multitasking 17:26:12 :) 17:26:23 or trying to anyways 17:26:31 #action maxamillion to follow-up on fixing ami permissions, links with dgilmore 17:26:53 maxamillion: lemme know if it'll help to have me send an email as well 17:26:58 ok, other issues 17:27:41 https://pagure.io/atomic-wg/issues?status=Open&tags=meeting 17:27:52 #228: I don't feel that we're any closer to setting release policy 17:28:45 this pretty much calls for a meeting 17:29:01 watch issues/email for one to be scheduled 17:29:08 +1 17:29:12 +1 17:29:17 jberkus: not that I can think of, but thanks 17:29:21 #action jberkus to schedule a meeting about support policy, rolling upgrades 17:29:39 +1 17:29:46 the other two issues have external dependencies which as far as I know haven't budged 17:29:57 rtnpro: any update on motd? 17:30:45 jberkus, nothing this week, I was away on PTO, I just resumed working today 17:30:57 ok, should it stay on the agenda for next week? 17:30:59 rtnpro, welcome back :) 17:31:14 IIRC, I was waiting for some reviews 17:31:24 jberkus, yes 17:31:33 #topic open floor 17:31:39 so, other stuff? 17:31:55 oh ... I have one thing 17:32:27 I have one thing. 17:32:40 trishnag: go, it's late for you 17:32:45 trishnag: that is, go ahead 17:33:00 at some point I'd like to put together a really nice Atomic Host + OpenShift on Fedora demo that's done in Ansible and would be easy for someone to deploy on a spare machine or in a VM for use at conferences when manning the booth in order to show off the tech ... anyone have any thoughts on that? 17:33:03 I just checked we have Documentation migration VFAD. We should also focus to have all documents in *one* place. 17:33:25 FWIW: the Container Review component now has a fedora-review flag on it. 17:33:25 maxamillion, dusty's blog post from a bit ago is pretty good on this 17:33:31 jbrooks: +1 17:33:57 We need to decide the place for the same. We have http://fedoracloud.readthedocs.io . Not sure if this is active. 17:34:22 I didn't even know we had that 17:34:23 trishnag: so, we already decided to move to ASCIIdoc 17:34:30 or maybe we could just make a fedora powered version of minishift? ... I wonder how much work that would be to maintain 17:34:44 mainly because if we do, we can get a bunch of doc content from Red Hat Doc Team 17:34:58 which takes us off of RTD 17:35:25 btw, I have the doc source from downstream docs already 17:35:35 jberkus: ACK. 17:35:36 maxamillion, I bet it wouldn't be too tough to do, not sure about maintenance -- they're actually having some problems right now that'd be made easier w/ overlay2 17:35:44 trishnag: we have a docs.projectatomic.io project 17:35:52 although I'd like to keep that for doc build tools 17:36:40 however, I think that the Atomic Host docs should live in somewhere under projectatomic.io because that way we can combine Fedora and CentOS docs whcih will be 95% the same 17:36:44 jberkus: we can have *fedoraatomic* something? 17:36:57 jberkus: rgr 17:37:20 one of the reasons to go with ASCIIDoc/ASCIIBinder is that it supports building "editions" of the docs 17:37:33 so for *output* we can have one for Fedora and one for CentOS from the same source 17:37:47 jberkus: sounds good 17:37:56 trishnag: I take it you want to work on this? 17:38:05 jberkus: Yes count me in. 17:38:10 I'm +1 to centering docs on projectatomic 17:38:30 ok 17:38:46 #action jberkus to set up github repo for atomichost ASCIIDoc source 17:38:56 Sounds good, we need actual working does, does not matter where it stays 17:39:16 +1 17:39:20 kushal: +1 17:39:21 ASCIIDoc is a nice toolchain 17:39:37 we're going to need to merge (a) downstream docs (b) our docs in .md format (c) RTD docs source and (d) blog content 17:40:05 which means we could get help even from people who don't know atomic that well, as long as they can copy, paste, and re-write markup 17:40:14 this was why I suggested a VFAD 17:40:25 Sounds good 17:40:26 trishnag: let's follow up on getting the infrastructure set up 17:40:33 jberkus: +1 17:40:54 trishnag: I'll ping you, we'll set up a schedule. we could even chat in the morning your time instead of late at night ;-) 17:41:29 jberkus: Sounds perfect :-). 17:42:23 #action jberkus, trishnag to kick off documentation re-org project 17:42:45 earliest I could do a Doc VFAD would be mid-April 17:42:48 too many conferences 17:43:20 ok, any other business? 17:44:15 * roshi has nothing 17:44:25 nothing here 17:44:31 * trishnag has nothing 17:44:36 ok, see people at the VFAD on friday 17:44:44 aside from that tests for atomic and cloud base should be running in taskotron rsn 17:44:50 look for agenda by Email later today/early tommorrow depending on your TZ 17:44:54 polishing up my patch to get through review 17:45:00 roshi: that's really good news 17:45:13 :D 17:45:41 trishnag took a look at the playbooks where the tests live 17:46:04 #endmeeting