17:01:42 <jberkus> #startmeeting fedora_atomic_wg
17:01:42 <zodbot> Meeting started Wed May 17 17:01:42 2017 UTC.  The chair is jberkus. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:42 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:42 <zodbot> The meeting name has been set to 'fedora_atomic_wg'
17:01:49 <jberkus> #topic roll call
17:01:53 <jberkus> .hello jberkus
17:01:54 <zodbot> jberkus: jberkus 'Josh Berkus' <josh@agliodbs.com>
17:02:26 <yzhang> .hello yzhang
17:02:27 <zodbot> yzhang: yzhang 'Yu Qi Zhang' <jzehrarnyg@gmail.com>
17:02:48 <dustymabe> .hello dustymabe
17:02:49 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
17:02:53 <dustymabe> hi fatherlinux
17:03:07 <miabbott> .hello miabbott
17:03:07 <zodbot> miabbott: miabbott 'Micah Abbott' <miabbott@redhat.com>
17:03:41 <jbrooks> .hello jasonbrooks
17:03:42 <zodbot> jbrooks: jasonbrooks 'Jason Brooks' <JBROOKS@REDHAT.COM>
17:04:34 <walters> .hello walters
17:04:35 <zodbot> walters: walters 'Colin Walters' <walters@redhat.com>
17:05:36 <jberkus> #chair dustymabe miabbott jbrooks walters yzhang
17:05:36 <zodbot> Current chairs: dustymabe jberkus jbrooks miabbott walters yzhang
17:05:55 <jberkus> sayan was supposed to dial in, but he's volunteering at PyCon today, so who knows
17:06:03 <maxamillion> .hello maxamillion
17:06:05 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
17:06:08 <dustymabe> maxamillion: \o
17:06:16 <jberkus> #chair dustymabe miabbott jbrooks walters yzhang maxamillion
17:06:16 <zodbot> Current chairs: dustymabe jberkus jbrooks maxamillion miabbott walters yzhang
17:06:46 <jberkus> #topic meeting minutes
17:07:06 <jberkus> before we start, I wanted to make sure that people knew that the meeting id for this meeting is fedora_atomic_wg
17:07:17 <jberkus> NOT atomic_wg, not fedora_atomic, and not atomic-wg
17:07:34 <jberkus> this is per the wiki page: https://fedoraproject.org/wiki/Cloud#Meetings
17:07:42 <maxamillion> +1
17:07:57 <yzhang> aye aye
17:08:03 <dustymabe> jberkus: +1
17:08:10 <jberkus> this is important because our minutes are now completely fragmented in meetbot, making it almost impossible for any new member of the WG to get background
17:09:02 <jberkus> does anyone know if there's a way to fix meetbot archives retroactively?
17:09:41 <maxamillion> if it can be done, we'd probably have to ask the infra team
17:10:04 <jberkus> maxamillion: who/where would that be specifically?
17:10:12 <dustymabe> jberkus: probably not worth it - we'll just fix it going forward
17:10:19 <maxamillion> jberkus: https://pagure.io/fedora-infrastructure
17:10:23 <jberkus> ok, thanks
17:10:30 <jberkus> #topic action items from last meeting
17:10:55 <jberkus> dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker
17:11:00 <jberkus> dustymabe: ?
17:11:48 <dustymabe> jberkus: re-action please. i just learned how to migrate issues from one repo to another
17:11:56 <dustymabe> takes some manual work
17:12:03 <jberkus> action: dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker
17:12:10 <jberkus> #action: dustymabe to migrate some cloud-base tickets to the cloud-sig tracker from the atomic-wg tracker
17:12:14 <dustymabe> planning on finishing that up today and i'll ping jdoss and the other guy
17:12:18 <jberkus> ok
17:12:33 <jberkus> x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points
17:12:39 <jberkus> so, x3mboy didn't show up at the meeting
17:12:51 <jberkus> and I've been trying to reach him since then with no luck
17:13:00 <x3mboy> Yes, sorry for that
17:13:04 <jberkus> since I don't have a current example of the talking points ...
17:13:04 <jberkus> ahah
17:13:15 <x3mboy> I answer the in the ticket, I was sick that day
17:13:17 <dustymabe> jberkus: he did respond
17:13:17 <x3mboy> :'(
17:13:20 <dustymabe> https://pagure.io/atomic-wg/issue/262#comment-441102
17:13:38 <x3mboy> jberkus, sorry if I made you lost time
17:13:44 <x3mboy> It wasn't intentional
17:13:52 <jberkus> no, I just don't want to miss the deadline for the talking points
17:13:59 <jberkus> can you do this afternoon?
17:14:59 <jberkus> #action: x3mboy and jberkus to hold meeting tomorrow to discuss marketing talking points
17:15:24 <jberkus> that's it for actions, now on to issues
17:15:25 <x3mboy> jberkus, yes, please. Tell me the time...
17:15:33 <jberkus> #topic issues flagged as meeting
17:15:37 <dustymabe> jberkus x3mboy ++
17:15:50 <jberkus> x3mboy: 4pm EDT?
17:15:55 <x3mboy> Ok
17:16:05 <x3mboy> Today right?
17:16:23 <jberkus> yes
17:16:44 <jberkus> #269 fedimg: don't use 'builder' instance for uploading AMIs
17:16:56 <jberkus> dustymabe: you need sayan to answer this?
17:17:26 <dustymabe> jberkus: punt, we got an update from him last week but i think he is not here today
17:17:34 <dustymabe> because of pycon
17:17:44 <jberkus> dustymabe: yah, he was supposed to dial in from the convention center but I bet he lost track
17:18:04 <dustymabe> jberkus: he is also in a different time zone than he is normally used to
17:18:16 <jberkus> I know, he's staying at my house
17:18:29 <dustymabe> so probably easy to lost track of when the meeting should start
17:18:33 <dustymabe> jberkus: :)
17:18:38 * roshi is here
17:18:43 <dustymabe> roshi: \o
17:18:45 <jberkus> ok, next
17:18:47 <roshi> sorry I'm late
17:19:02 <jberkus> #228 clarify policy on atomic host support for older Fedora "number" releases
17:19:11 <jberkus> is there anything left to DO for this issue?
17:19:18 <jberkus> do we need to document it somewhere we haven't?
17:19:40 <roshi> we can gather up the logs from all the meetings with the wrong name, and re-run them through meetbot manually
17:19:45 <roshi> sorry, reading backscroll
17:19:58 <jbrooks> jberkus, I was thinking a blog post?
17:20:00 <dustymabe> jberkus: we were going to do a blog post, right?
17:20:08 <jbrooks> I'll send a PR for that
17:20:09 <jberkus> ah, ok
17:20:15 <dustymabe> also - would be great to have a page where we document this policy
17:20:23 <jberkus> dustymabe: should be on the atomic PRD, no?
17:20:24 <jbrooks> I can put it on the wiki
17:20:39 <dustymabe> jberkus: sounds like as good a place as any
17:21:45 <jbrooks> #action jbrooks to write project atomic blog post re #228, and add info to fedora PRD
17:21:47 <jberkus> speaking of which, we really need the council to officially approve the PRD
17:21:59 <jberkus> I have no idea how to proceed with that
17:22:17 <jberkus> #action jberkus to ask mattdm about how to get PRD approved
17:22:19 <dustymabe> roshi: maxamillion ^^ is that something we are lacking?
17:22:49 <roshi> tbh, I thought it was already approved and ready to go
17:22:52 <maxamillion> dustymabe: "that" ?
17:22:56 <roshi> as in, we're done with it
17:23:03 <dustymabe> that == PRD
17:23:03 <maxamillion> dustymabe: that == PRD?
17:23:04 <roshi> I thought the WGs approved those
17:23:18 <maxamillion> dustymabe: I thought that was already done a few meetings ago
17:23:22 * roshi could be wrong though
17:23:25 <maxamillion> so ... not that I know of?
17:23:28 <roshi> sure, ask mattdm
17:23:34 <jberkus> roshi: maybe I just need to agenda it at a council meeting
17:23:44 <dustymabe> so we have a PRD, the question is, does it have to be approved by someone other than us?
17:23:46 <jberkus> but I'm pretty sure the council needs to know we have one
17:24:03 <roshi> that makes sense
17:24:33 <jberkus> ok
17:24:37 <jberkus> #topic open floor
17:24:43 <jberkus> who's first?
17:25:00 <dustymabe> FYI we had an AH release on Monday
17:25:06 <dustymabe> so that is a +
17:25:08 <roshi> who's on second
17:25:34 <jberkus> yay
17:25:50 <dustymabe> open floor topic: containers
17:25:57 <dustymabe> how are we doing on container reviews?
17:26:01 <dustymabe> any blockers at this point
17:26:03 <dustymabe> ?
17:26:15 <maxamillion> on that note, I owe everyone a container relase
17:26:34 <maxamillion> I was out at jury duty yesterday, otherwise it would have gone out yesterday
17:27:27 <maxamillion> also, I need to track down a good f26 base image because the one in the registry is super old and I'm not sure why
17:27:50 <dustymabe> maxamillion: you'll have to wait til tomorrow
17:28:04 <dustymabe> dracut bug has all of the f26 stuff busted
17:28:16 <maxamillion> dustymabe: ooooooof course it does
17:28:25 <dustymabe> it hit stable this morning so tomorrow's images should have a 'path to success'
17:28:32 <jberkus> dustymabe: I've been held up on owncloud because of needing to set up DB environment + travel
17:28:51 <dustymabe> jberkus: you need that in order to test it?
17:29:00 <jberkus> yah, it's a dependency
17:29:24 <dustymabe> so there is another container review that owncloud depends on ?
17:29:27 <jberkus> and since we don't yet have a clear way to handle dependencies ...
17:29:36 <jberkus> dustymabe: no, we published some DB contianers already
17:29:50 <jberkus> they're just not configured in a way which works with owncloud, which really needs Kube/OpenShift
17:29:58 <dustymabe> hmm. ok
17:30:03 <jberkus> I got sidetracked into the issues around how to run DBs inside OpenShift, which is complicated
17:30:29 <dustymabe> k
17:32:09 <jberkus> is there a list of contianers pending review somewhere?
17:32:14 <jberkus> like, all of them?
17:32:40 <dustymabe> one sec
17:33:06 * dustymabe had a bz query for it at one point
17:33:37 <yzhang> something like: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&classification=Fedora&list_id=7379197&product=Fedora%20Container%20Images&query_format=advanced
17:33:39 <yzhang> maybe?
17:33:50 <jberkus> #action: dustymabe to put bz query for containers pending review on wiki
17:34:30 <jberkus> ok, I already know that's missing some
17:34:55 <dustymabe> how do we make sure we don't 'drop' things
17:35:13 <jberkus> well, that's a problem.  if we have no comprehensive way to get a list of containers pending review, then we will drop them
17:35:15 <jberkus> maxamillion: ?
17:35:34 <dustymabe> maxamillion: has given me a query to use in the past
17:35:38 <dustymabe> it might even already be on the wiki
17:35:40 * dustymabe looks
17:36:15 <maxamillion> yeah, there's a query somewhere
17:36:56 <jberkus> I'd like to add a check on contiainer review to these meetings
17:37:04 <jberkus> so if we can have a query, that would be great
17:37:11 * jberkus is sad we have to use bugzilla for this
17:37:39 <dustymabe> there is this page for viewing review status
17:37:48 <dustymabe> http://fedoraproject.org/PackageReviewStatus/
17:38:01 <dustymabe> don't know if we can use it for just viewing container reviews
17:38:36 <yzhang> maxamillion: on another note the "request for review in bugzilla" link in the review process still directs to docker images
17:38:50 <jberkus> would be good, could you or maxamillion look into getting a line added to that for contianer review?
17:39:42 <dustymabe> jberkus: i don't know what all would be required there - we can add a ticket for this, but most likely won't be able to work on it until after f26 is out the door
17:39:46 <dustymabe> pretty slammed until then
17:39:57 <dustymabe> acceptable?
17:40:04 <jberkus> sure, can you add a ticket?
17:40:19 <dustymabe> yeah - i'll add one to our tracker and we can dissemenate from there
17:40:20 <jberkus> #action dustymabe to add a ticket to look into getting an easy-to-use container review link after F26
17:40:39 <dustymabe> s/dissemenate/dissemenate
17:40:45 <dustymabe> gifhr
17:40:59 <jberkus> ok, anything else?
17:41:07 <dustymabe> s/dissemenate/disseminate
17:42:21 <jberkus> any other topics for open floor?
17:42:23 <jberkus> walters: ?
17:42:37 * sayan has an update
17:42:40 <walters> i don't have anything atm
17:42:43 <dustymabe> sayan: hiya :)
17:42:50 <sayan> dustymabe: hey :)
17:43:00 <jberkus> sayan: go ahead
17:43:20 <maxamillion> jberkus: where?
17:43:36 <jberkus> maxamillion: TBD.  ideally, several places
17:43:54 * roshi has nothing for open floor
17:44:01 <maxamillion> yzhang: it does?
17:44:06 <jberkus> maxamillion: oh, I was talking about the PackageReviewStatus page
17:44:10 <maxamillion> jberkus: rgr
17:44:12 <sayan> I did not get much time last week, due to preparing for the event. But I did setup the autocloudreporter, but strangely it's not receiving any of the autocloud messages
17:44:19 <yzhang> maxamillion: https://bugzilla.redhat.com/enter_bug.cgi?alias=&assigned_to=nobody@fedoraproject.org&attach_text=&blocked=&bug_file_loc=http://&bug_severity=unspecified&bug_status=NEW&cf_build_id=&cf_category=---&cf_clone_of=&cf_cloudforms_team=---&cf_crm=&cf_cust_facing=---&cf_devel_whiteboard=&cf_docs_score=&cf_documentation_action=---&cf_environment=&cf_internal_whiteboard=&cf_mount_type=---&cf_ovirt_team=---&cf_pm_score=&cf_qa_whiteboard=&cf_re
17:44:19 <yzhang> gression_status=---&cf_story_points=---&cf_type=Bug&comment=Container%20Build%20Info%20URL:%20%3CURL%20of%20diectory%20containing%20Dockerfile%20here%3E%0D%0ADescription:%20%3Cdescription%20here%3E%0D%0AFedora%20Account%20System%20Username:&component=Container%20Review&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text/plain&data=&deadline=&defined_cf_layered_products=&defined_cf_partner=&defined_groups=1&defined_rh_sub_comp
17:44:20 <yzhang> onent=0&dependson=&description=&docs_contact=&estimated_time=&external_bug_id_1=&external_id_1=0&flag_type-155=X&flag_type-16=X&flag_type-415=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=unspecified&product=Fedora%20Docker%20Images&qa_contact=extras-qa@fedoraproject.org&rep_platform=Unspecified&requestee_type-155=&requestee_type-16=&short_desc=Container%20Review%20Reques
17:44:25 <yzhang> t%20-%20%3Cmain%20component%20name%20here%3E%20-%20%3Cshort%20summary%20here%3E&status_whiteboard=&target_milestone=---&target_release=---&version=rawhide
17:44:28 <yzhang> oh god
17:44:30 <yzhang> sorry
17:44:32 <yzhang> I did not
17:44:33 <roshi> lol
17:44:40 <jbrooks> heh
17:44:40 * yzhang should check the link first
17:44:42 * jberkus bursts out laughing
17:44:46 <roshi> that's a long URL
17:45:04 <yzhang> mayhaps that was the original URL that maxamillion used to query
17:45:11 <dustymabe> sayan: what does autocloudreporter supposed to do?
17:45:22 <roshi> report results to resultsdb
17:45:42 <yzhang> maxamillion: its the link in the second bullet of https://fedoraproject.org/wiki/Container:Review_Process#Dockerfiles
17:45:50 <sayan> so, fedimg should not directly tieup with autocloud
17:46:25 <sayan> because it needs to tieup with taskotron later, so fedimg will listen to resultsdb
17:46:38 <dustymabe> sayan, makes sense
17:46:48 <dustymabe> so we want to have autocloud report results to resultsdb?
17:46:56 <roshi> it already does
17:47:03 <sayan> dustymabe: yes, it does via autocloudreporter
17:47:13 <sayan> as roshi said it already does
17:47:22 <dustymabe> but that's not working?
17:48:08 <sayan> dustymabe: right now, in production it listens to the compose test messages
17:48:38 <sayan> I added code to listen for the ami testing, which is not working
17:49:02 <maxamillion> yzhang: well crap, I swear I fixed that
17:49:09 <maxamillion> yzhang: alright, I'll fix it
17:49:11 <sayan> not working = the fedmsg consumer is not listening to the messages autocloud is emitting
17:49:22 <yzhang> maxamillion: thanks!
17:49:32 <dustymabe> sayan: ok. will check back with you - hopefully that doesn't give you too much more trouble than it already has
17:49:52 <maxamillion> yzhang: sorry about that, I really thought that was handed already ... I must have missed one
17:50:13 <maxamillion> handled*
17:50:22 <sayan> sure
17:50:23 <yzhang> maxamillion: no problem, I was just scouring through the wiki looking for a url to query pending reviews
17:50:34 <yzhang> doesn't affect me really, I already know the process :D
17:50:54 <miabbott> yzhang humblebrag
17:52:44 <yzhang> anyways I gotta run to another meeting
17:52:49 <yzhang> gl friends
17:52:51 <jberkus> ok, any other items for open floor?
17:52:57 <jberkus> 3
17:53:02 <maxamillion> yzhang: +1
17:53:07 <roshi> thanks jberkus :)
17:53:12 <jberkus> 2
17:53:36 <jberkus> 1
17:53:46 <jberkus> #endmeeting