atomic_wg
LOGS
17:01:22 <jbrooks> #startmeeting atomic_wg
17:01:22 <zodbot> Meeting started Wed Apr  5 17:01:22 2017 UTC.  The chair is jbrooks. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:22 <zodbot> The meeting name has been set to 'atomic_wg'
17:01:42 <jbrooks> #topic roll call
17:01:43 <bowlofeggs> .hello bowlofeggs
17:01:43 <roshi> .hello roshi
17:01:45 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
17:01:47 <yzhang> .hello yzhang
17:01:48 <zodbot> roshi: roshi 'Mike Ruckman' <mruckman@redhat.com>
17:01:49 <trishnag> .hello trishnag
17:01:51 <zodbot> yzhang: yzhang 'Yu Qi Zhang' <jzehrarnyg@gmail.com>
17:01:53 <dustymabe> .hello dustymabe
17:01:54 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
17:01:57 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
17:02:01 <jbrooks> .fas jasonbrooks
17:02:01 <zodbot> jbrooks: jasonbrooks 'Jason Brooks' <JBROOKS@REDHAT.COM>
17:02:13 <miabbott> .hello miabbot
17:02:15 <zodbot> miabbott: Sorry, but you don't exist
17:02:15 <miabbott> .hello miabbott
17:02:18 <zodbot> miabbott: miabbott 'Micah Abbott' <miabbott@redhat.com>
17:02:39 <yzhang> dustymabe no longer using the .hellomynameis anymore
17:02:43 <yzhang> he too has converted to short-hand
17:02:53 <jbrooks> #chair  bowlofeggs roshi  yzhang trishnag dustymabe miabbott
17:02:53 <zodbot> Current chairs: bowlofeggs dustymabe jbrooks miabbott roshi trishnag yzhang
17:02:56 <dustymabe> haha :)
17:03:00 <jbrooks> did I get everyone?
17:03:16 <dustymabe> looks like it
17:03:17 <jbrooks> #topic previous meeting action items
17:03:42 <jbrooks> yzhang and I were to talk about containerized kube
17:03:44 <jbrooks> And we did
17:04:01 <yzhang> yessir
17:04:03 <jbrooks> I'm going to try out a couple of the things we discussed, and get his and giuseppe's feedback
17:04:27 <jbrooks> Bascially around making the system container config a bit easier
17:04:54 <yzhang> just curious jbrooks, I forgot to ask, have you ever though about making the entirety of kube in system containers?
17:05:31 <jbrooks> yzhang, Yeah, for sure, I was waiting on a howto, but now you've provided that, I'm going to look into converting them
17:05:51 <dustymabe> jbrooks: yzhang: but they can still be run as non-system containers, right?
17:05:53 <jbrooks> It'll be nicer, because we can reuse the base image that's in ostree
17:05:55 <yzhang> jbrooks: nice, also giuseppe has made some system containers for openshift
17:05:56 <jbrooks> Yes
17:05:57 <yzhang> https://github.com/giuseppe/atomic-openshift-system-containers
17:05:58 <yzhang> here
17:06:06 <jbrooks> Cool
17:06:07 <yzhang> and yes dustymabe, they can
17:06:10 <dustymabe> cool
17:06:24 <jbrooks> Yeah, I really like them -- the systemd integration is awesome
17:07:00 <jbrooks> OK, tickets
17:07:09 <sayan> .hello sayanchowdhury
17:07:10 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
17:07:23 <jbrooks> #chair sayan
17:07:23 <zodbot> Current chairs: bowlofeggs dustymabe jbrooks miabbott roshi sayan trishnag yzhang
17:07:57 <jbrooks> #topic meeting tickets
17:08:05 <jbrooks> #link https://pagure.io/atomic-wg/issues?status=Open&tags=meeting
17:08:37 <jbrooks> #topic 264 2WK Atomic Release Criteria
17:08:54 <jbrooks> roshi, want to talk about it?
17:09:06 <roshi> can we come back to that in a minute?
17:09:09 <roshi> I just got a phone call
17:09:16 <jbrooks> Yeah, np
17:09:38 <jbrooks> #topic 254 Label/comment for primary RPM?
17:09:43 <dustymabe> i just pinged adam to see if he can join us
17:10:01 <dustymabe> #link https://pagure.io/atomic-wg/issue/254
17:10:08 <jbrooks> Cool, do we need him for this one?
17:10:14 <maxamillion> .hello maxamillion
17:10:15 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
17:10:18 <maxamillion> sorry I'm late
17:10:21 <dustymabe> maxamillion: np
17:10:27 <jbrooks> #chair maxamillion
17:10:27 <zodbot> Current chairs: bowlofeggs dustymabe jbrooks maxamillion miabbott roshi sayan trishnag yzhang
17:10:36 <dustymabe> topic is 254 Label/comment for primary RPM?
17:10:40 <dustymabe> https://pagure.io/atomic-wg/issue/254
17:11:04 <jberkus> sorry, for some reason it didn't signal me
17:11:07 <jberkus> .hello jberkus
17:11:08 <maxamillion> now that we're in time change, this overlaps with a weekly video call I'm on ... so ... :(
17:11:08 <zodbot> jberkus: jberkus 'Josh Berkus' <josh@agliodbs.com>
17:11:23 <jbrooks> #chair jberkus
17:11:23 <zodbot> Current chairs: bowlofeggs dustymabe jberkus jbrooks maxamillion miabbott roshi sayan trishnag yzhang
17:11:52 <jbrooks> So it looks like we're waiting on #249 for this one
17:12:09 <jbrooks> Maybe we remove the meeting label and make a note in #249 to re-add it once that's settled
17:12:11 <dustymabe> yep, remove the meeting tag?
17:12:16 <maxamillion> yeah
17:12:33 <jbrooks> cool
17:12:39 <maxamillion> that's going to be a while, we did a priority backlog planning yesterday and this work is at minimum 4-6 weeks away from getting started
17:12:47 <maxamillion> unless someone else wants to pick it up
17:12:47 <jbrooks> OK
17:13:12 <jbrooks> #topic 253 lower case vs Initial Cap in Labels
17:13:22 <jbrooks> #link https://pagure.io/atomic-wg/issue/253
17:14:28 <yzhang> so I think this is just boiling down to: do we want com.redhat.component or something else like org.fedoraproject.component
17:14:30 <dustymabe> i put my comment in there
17:14:42 <dustymabe> my biggest thing is "don't block"
17:14:58 <jbrooks> +1
17:15:12 <yzhang> +1 to dustymabe
17:15:36 <kushal> back
17:15:41 <trishnag> +1
17:15:45 <kushal> was having another meeting
17:15:47 <maxamillion> +1 to dustymabe
17:15:52 <jbrooks> Ok, assuming we're in agreement, who takes the action?
17:16:04 <dustymabe> and what is the action?
17:16:09 <jbrooks> heh
17:16:09 <maxamillion> is the action just to update the docs?
17:16:11 <jbrooks> totally
17:16:13 <yzhang> I think the koji support is already there right maxamillion
17:16:18 <yzhang> so just docs I guess
17:16:18 <maxamillion> yzhang: correct
17:16:21 <jbrooks> #chair kushal
17:16:21 <zodbot> Current chairs: bowlofeggs dustymabe jberkus jbrooks kushal maxamillion miabbott roshi sayan trishnag yzhang
17:16:23 <jberkus> two: (1) updating the guidelines, and (2) search-and-replace in existing images
17:16:55 <maxamillion> well ... search-and-replace takes special permissions, that's not something we normally allow
17:17:03 <jbrooks> We can ping ppl to change their own
17:17:12 <jbrooks> I can change mine
17:17:13 <maxamillion> package maintainers can't just drive by commit to other people's packages
17:17:36 <dustymabe> if they don't change their files, what breaks?
17:17:43 <maxamillion> dustymabe: nothing
17:17:44 <yzhang> yeah I think theres like me jbrooks and maxamillion's containers, as well as someone's python classroom?
17:17:48 <maxamillion> dustymabe: there's backwards compat
17:17:49 <yzhang> nothing breaks
17:17:57 <dustymabe> ok then, we send a message to existing maintainers and ask them to update
17:18:01 <yzhang> just not up-to-guidelines
17:18:03 <maxamillion> +1
17:18:09 <dustymabe> so action items
17:18:13 <jbrooks> And who'll update the guidelines?
17:18:15 <dustymabe> (1) update guidelines
17:18:21 <yzhang> I'll update the guidelines
17:18:25 <yzhang> so I can remember to do them
17:18:26 <dustymabe> (2) send email to existing maintainers + cc cloud list
17:18:30 <yzhang> for system containers too
17:18:47 <jbrooks> #action yzhang to update guidelines RE #253
17:19:00 <jbrooks> I can send an email to ppl
17:19:18 <maxamillion> +1
17:19:20 <jbrooks> #action jbrooks to notify container maintainers of guideline change
17:19:30 <dustymabe> thanks :)
17:19:35 <dustymabe> hashtag progress
17:19:38 <jberkus> if we're going to notify all maintianers, I'd like to get through with *all* the changes
17:19:46 <jbrooks> jberkus, good point
17:19:46 <jberkus> or at least all the ones we're currently discussing
17:20:02 <dustymabe> jberkus: wants to only notify maintainers once of all changes they need to make
17:20:13 <yzhang> does the previously raised point of versioning count
17:20:31 <dustymabe> yzhang: i think we can notify them that they need to use version 0 ?
17:20:43 <yzhang> sure
17:20:59 <jbrooks> OK, I'll keep an eye on it and prepare a mini running list of things to notify about -- I'll start an issue for that, I guess? To make sure we get them all
17:21:10 <dustymabe> they might rebel against that a bit? was that just guidance or required?
17:21:37 <jberkus> dustymabe: well, if we're going to replace it with automatic, then yeah, we'll need them to do it
17:21:45 <jberkus> however, there will be exceptions
17:21:54 <jbrooks> We can say, these are the revised guidelines, here's what's backward compat and what is not
17:22:05 <dustymabe> sounds good to me
17:22:13 <dustymabe> what is left to resolve on the "container" front?
17:22:27 * dustymabe would really like to have that out of the way
17:22:37 <jbrooks> #topic 248 Container Guidelines: Layered Images used as a base for other Layered Builds
17:22:43 <jbrooks> that's another, dustymabe
17:23:04 <dustymabe> #link https://pagure.io/atomic-wg/issue/248
17:23:25 <dustymabe> i think this one is done right?
17:23:29 <jbrooks> We haven't heard back from the issue submitter yet
17:23:43 <jbrooks> We're just agreeing that the way mine is done is right?
17:24:04 <jbrooks> Do we reference this in the guidelines?
17:24:07 <jbrooks> Layered images
17:24:08 <dustymabe> yeah - i think the issue submitter wants a section in the guidelines about it?
17:24:09 <jberkus> we should
17:24:29 <dustymabe> yzhang: mind adding a section on it?
17:24:40 <dustymabe> basically 1 - only use base images that were built in fedora
17:24:47 <dustymabe> 2 - here is an example of how to do it
17:24:57 <jbrooks> I can do it -- I'll take his suggested section and make it look like mine
17:25:05 <dustymabe> jbrooks++
17:25:09 <yzhang> jbrooks++
17:25:20 <jbrooks> #action jbrooks to add layered image section to guidelines
17:25:34 <dustymabe> jbrooks: can you add the ticket number to that
17:25:44 <dustymabe> roshi: can we use undo? to undo the action?
17:25:52 <jbrooks> #undo
17:25:53 <zodbot> Removing item from minutes: ACTION by jbrooks at 17:25:20 : jbrooks to add layered image section to guidelines
17:26:03 <jbrooks> #action jbrooks to add layered image section to guidelines RE 248
17:26:05 <roshi> yep, #undo is what you want
17:26:08 <dustymabe> yay
17:26:08 * roshi is off the phone
17:26:10 <roshi> sorry about that
17:26:32 <jbrooks> #topic 264 2WK Atomic Release Criteria
17:26:38 <miabbott> dustymabe: regarding about the base images, should we be encouraging using fully-qualified image names?
17:27:14 <jberkus> miabbott: oh, good point
17:27:27 <dustymabe> miabbott: like, to include the tag?
17:27:36 <jbrooks> miabbott, like what? how does this look: https://pagure.io/atomic-wg/issue/248#comment-432837
17:27:49 <miabbott> i mean the FROM line should be like 'FROM: registry.fedoraproject.org/fedora:25'
17:27:56 <miabbott> not just 'FROM: fedora:25'
17:28:09 <jbrooks> Oh, the base
17:28:10 <yzhang> I think miabbott means in general and not just the layered images
17:28:11 <miabbott> jbrooks: yeah!
17:28:18 <yzhang> well
17:28:19 <dustymabe> yeah - basically it has to come "from fedora" which in my mind means you have to have registry.fp.o in there
17:28:23 <miabbott> yzhang: yes, in general
17:28:57 <miabbott> i'm just advocating for being very explicit
17:29:08 <jbrooks> The official builder will get it from the right place, but if someone built it themselves, it'd come from docker hub, probably, right?
17:29:22 <jbrooks> So it would make sense to be explicit, I think
17:29:29 <miabbott> since you can get just about any base image from docker.io if the registry is not mentioned in the FROM
17:29:49 <miabbott> heck, you can even get RHEL base images from docker.io
17:30:07 <dustymabe> right, basically when I said: 1 - only use base images that were built in fedora
17:30:17 <dustymabe> i meant that they had to use ones that come from registry.fp.o
17:30:24 <dustymabe> which requires you to use a fully qualified name
17:30:38 <dustymabe> so....
17:30:45 <jbrooks> So we should put that in the example
17:30:51 <dustymabe> jbrooks: sure
17:30:53 <jbrooks> And in our existing dockerfiles
17:30:57 <dustymabe> yep
17:31:12 <jbrooks> OK, I can add that to the list of things we'll want to mention to the maintainers
17:31:18 <miabbott> yes to all that
17:31:38 <dustymabe> :)
17:31:42 <jbrooks> miabbott, You want to make that add to the container guidelines?
17:31:51 <miabbott> can do
17:32:23 <jbrooks> #action miabbott to add example of explicit registry inclusion to container guidelines
17:32:32 <miabbott> :thumbsup:
17:32:58 <jbrooks> ok, roshi ready to talk release criteria?
17:33:02 <roshi> yup
17:33:40 <roshi> so Atomic has lacked a lot of the typical documentation that something in Fedora has
17:33:47 <roshi> like a PRD and Release Criteria
17:34:19 <roshi> while we're not a release blocking image, because of 2 week release, it'd still be good to be explicit about base functionality thathas to work for a 2wk release
17:34:30 <roshi> these are an attempt at codifying these expectations
17:34:31 <roshi> https://fedoraproject.org/wiki/User:Roshi/QA/Atomic_Release_Criteria
17:34:38 <roshi> take a look at those, and see if I missed something
17:34:53 <maxamillion> +1
17:34:57 <roshi> but I think that basically covers what we want to work as a bare minimum for each release
17:35:05 <roshi> and it something we can reference in test cases
17:35:25 <kushal> I think we should make all the gating tests into release criteria.
17:35:27 <roshi> it's modeled after the regular Fedora Release Criteria that we tracking blocker bugs against
17:35:39 <maxamillion> a decent amount about Fedora Atomic breaks tradition with how things in Fedora habe been done for basically forever
17:35:50 <roshi> the goal is for us to have tests that cover all the criteria
17:36:01 <roshi> right
17:36:04 <maxamillion> which is fine, but I think we should aim to statisfy the areas that make sense
17:36:10 <jberkus> roshi++
17:36:17 <roshi> and has resulted in confusion when other WGs/Groups look at what's being done
17:36:24 <maxamillion> roshi++
17:36:44 <roshi> this is like a communication wrapper so other groups can see what we're aiming for and know what our targets are
17:36:44 <miabbott> good start roshi  +1
17:36:59 <dustymabe> roshi: that looks great
17:37:02 <roshi> since for the last few cycles, Atomic is only really known by members of the WG
17:37:04 <dustymabe> just read through it
17:37:04 <jbrooks> +1
17:37:05 <roshi> and we need to fix that
17:37:19 <dustymabe> roshi: yeah, we've been getting a lot more involvement though
17:37:20 <roshi> there's a great list of things I see as us needing, and this is just the first step
17:37:30 <kushal> roshi, That is correct.
17:37:30 <dustymabe> i anticipate awareness to rise
17:37:33 <roshi> right, but we still haven't really leveled out the confusion
17:37:47 <roshi> and awareness needs to be written down, not learned all tribally, is my point
17:37:54 <dustymabe> roshi: ideas for improving confusion level?
17:37:55 <kushal> But, we already have particular use-cases which we marked as gating tests for release.
17:38:17 <kushal> That is why I am suggesting to have those also in the release criteria.
17:38:21 <roshi> the next question that will require greater involvement from other WGs and releng, is how to treat atomic during pre-release
17:38:34 <kushal> May be this will make more tests for release than other WG(s).
17:38:39 <dustymabe> roshi: yes, that is something we are going to work on for f27
17:38:41 <roshi> kushal: I'll handle that later, these already cover most of the gating tests
17:38:50 <roshi> dustymabe: I do have ideas to lower the confusion
17:39:00 <dustymabe> we have had discussions with dennis and adam w about it
17:39:17 <roshi> mostly, writing docs and more visibility with other WGs about what the goals are
17:39:20 <dustymabe> we are going to create requirements for releng so we can have a better relationship
17:39:22 <roshi> and why those goals are good for fedora
17:39:26 <roshi> right
17:39:26 <kushal> roshi, but this means we are breaking away from our current criteria.
17:39:35 <roshi> kushal: what current criteria?
17:39:36 <dustymabe> roshi: I should create a ticket for the requirements doc
17:39:43 <kushal> roshi, Release criteria.
17:39:46 <roshi> which ones?
17:39:51 <roshi> there are no Atomic criteria
17:39:55 <kushal> For Fedora Atomic based on Gating tests.
17:39:57 <roshi> because it's never been release blocking
17:40:03 <roshi> tests arent' criteria
17:40:11 <dustymabe> hold up one second guys
17:40:23 <dustymabe> roshi's "criteria" is different than kushal
17:40:30 <roshi> kushal, tests vs criteria can be discussed at a later point
17:40:31 <roshi> right
17:40:42 <dustymabe> roshi's "criteria" is criteria that is defined like the rest of fedora
17:40:49 <kushal> dustymabe I understand.
17:40:51 <dustymabe> like what is done to  block alpha beta GA
17:41:03 <kushal> That is where we started our points (from Cloud days).
17:41:08 <dustymabe> i know we have our own tests that we rely on to block release
17:41:36 <dustymabe> but i think what roshi is saying is that because we don't have things like this explicitly written down, it makes it hard for the rest of the fedora community to understand us
17:41:44 <dustymabe> including roshi himself
17:41:49 <roshi> right, this is bringing atomic more in line with the rest of fedora, so it doesn't feel like two projects quite as much
17:41:56 <roshi> exactly
17:41:57 <dustymabe> i am all for that
17:42:03 <dustymabe> kushal: does that make sense?
17:42:13 <roshi> in the beginning, atomic just kinda came out of no where for those of us who weren't already working on it
17:42:51 <maxamillion> +1
17:43:19 <trishnag> roshi: dustymabe We can have the doc written down in https://github.com/projectatomic/atomic-host-docs on *fedora* branch which is going to be hosted on docs.projectatomic.io/fedora_atomic/
17:43:48 <jbrooks> All right, what's our next action?
17:43:54 <roshi> trishnag: the doc should probably live in the wiki with the rest of the criteria
17:44:05 <dustymabe> trishnag: yeah, i'm with roshi on that one
17:44:12 * roshi dreams of the Fedora wiki being as good as the Arch wiki
17:44:19 <maxamillion> roshi: OMG so much that
17:44:23 <maxamillion> Arch Wiki ++
17:44:25 <gholms> Heh
17:44:25 <dustymabe> maxamillion: yeah me 2
17:44:31 <jberkus> trishnag I think docs.projectatomc.io is for user docs, not releng docs
17:44:34 * dustymabe wishes we could get the arch folks to write docs for us
17:44:36 <maxamillion> credit where credit is due, they do great work
17:44:38 <trishnag> roshi: dustymabe Ack. just like Release Criteria we have for Fedora.
17:44:39 <roshi> but people neglect the wiki and if we'd put some time into it, I think we can start to get there
17:44:42 <roshi> at least for atomic
17:44:44 <roshi> right
17:44:49 <trishnag> jberkus: Understood.
17:44:54 <maxamillion> roshi: +1
17:45:03 <roshi> but that's what I had for this ticket
17:45:03 <dustymabe> roshi: i'm the biggest offender of neglecting the wiki
17:45:06 <roshi> more issues to come
17:45:08 <jberkus> trishnag: thanks for continuing to work on that while I was gone
17:45:10 <roshi> dustymabe: that you are :p
17:45:11 <dustymabe> please poke me if you want me to update a page
17:45:16 <roshi> always trying to not use it :p
17:45:19 <trishnag> jberkus: Certainly! :)
17:45:26 <dustymabe> roshi: i actually voted for wiki this time :)
17:45:38 <roshi> I noticed, now I need to check that you're OK :p
17:45:53 <maxamillion> actually ... we could probably write some kind of updater service script that updated the wiki pages from Markdown, ASCIIdoc, or reStructuredText files in the atomic-wg pagure repo using pandoc
17:46:02 <maxamillion> that could be an interesting thing
17:46:08 <trishnag> maxamillion: +1
17:46:15 <roshi> maxamillion: QA has a ton of ways to automate working on the wiki
17:46:18 <roshi> so we can do that
17:46:20 <dustymabe> maxamillion: yeah - that would be nice
17:46:33 <roshi> but that's where we're at now, take a look, see if anything is missing
17:46:57 <roshi> as far as plain english "this and this must work for an Atomic release to be good for public consumption"
17:47:08 <jbrooks> OK, so, people need to check out https://fedoraproject.org/wiki/User:Roshi/QA/Atomic_Release_Criteria
17:47:25 <roshi> you can edit the wiki, and I'll work with QA to find out where exactly those should live officially
17:47:34 <roshi> and not under User:Roshi/QA/
17:47:39 <kushal> dustymabe, Okay[
17:47:50 <jbrooks> OK, and we'll leave the meeting tag on here, and revisit next week?
17:48:01 <roshi> sure, should be quick if people take a look and sign off
17:48:10 <roshi> if it looks good, leave a +1 in the pagure ticket
17:48:15 <roshi> that work?
17:48:26 <jbrooks> sounds good
17:48:43 <maxamillion> roshi: +1
17:48:52 <jbrooks> do we record "everyone" actions like this?
17:49:08 <maxamillion> sure, why not
17:49:08 <jberkus> sure
17:49:09 <kushal> jbrooks, originally the WG is supposed to vote for these items.
17:49:11 <roshi> I'd do an #info noting that people should look
17:49:12 <maxamillion> just for posterity
17:49:22 <roshi> kushal: what do you mean?
17:49:29 <dustymabe> i voted in the ticket
17:49:43 <jbrooks> #info check out https://fedoraproject.org/wiki/User:Roshi/QA/Atomic_Release_Criteria and comment in issue #264
17:50:01 <jbrooks> kushal, Yeah, I don't think I'm a voting member
17:50:26 <dustymabe> jbrooks: we need to get that updated
17:50:40 * roshi doesn't even remember the list of members, tbh
17:50:44 <yzhang> can I also apply to become a member somehow
17:50:47 <yzhang> :D
17:51:07 <jbrooks> If nothing else, it needs an update for our atomic wg refresh
17:51:19 <dustymabe> yzhang: indeed - send an email to the list and we'll review members and add new ones in a future meeting
17:51:27 <dustymabe> miabbott: jlebon might also be interested
17:51:30 <trishnag> Does that mean member of atomic_wg? Then I am :).
17:51:47 <jbrooks> Ah, yes, there's a fas thing
17:51:48 * miabbott is cool with being a member
17:51:57 <trishnag> jbrooks: Right.
17:52:17 <jbrooks> miabbott, there are various blood oaths and initiation rites
17:52:40 <dustymabe> haha
17:52:43 <jbrooks> OK, we have two other items
17:52:45 <kushal> roshi, just for official records we vote on the tickets.
17:52:46 <miabbott> i haven't done one of those in a while.  will have to dig out my ceremonial daggers
17:52:54 <jberkus> jbrooks: we might have to put that off.  I'm completely out of mashmellow fluff, and so is costco
17:52:55 <trishnag> jbrooks: I also have an item for open ticket.
17:52:56 <jbrooks> dustymabe, the clarify older versions ticket
17:53:06 <roshi> kushal: I just wasn't sure what you meant, because that's exactly what we're doing :)
17:53:13 <jbrooks> and the FOSP, which... I don't know if there's anything new
17:53:22 <jbrooks> I'll swtich to
17:53:26 <jberkus> jbrooks: hardware is not installed
17:53:28 <jbrooks> #topic open floor
17:53:31 <dustymabe> older revisions?
17:53:40 <jbrooks> https://pagure.io/atomic-wg/issue/228
17:53:42 <jbrooks> N-1
17:53:48 <dustymabe> ahh ok
17:53:51 <yzhang> I have a quick question, not sure if its the correct place to bring up
17:53:56 <dustymabe> yzhang: shoot
17:54:01 <x3mboy> !
17:54:03 <dustymabe> trishnag: open floor time
17:54:05 <yzhang> is it possible to get runc 1.0.0 rc-3 into f26
17:54:16 <yzhang> # rpm -qa|grep runc
17:54:16 <yzhang> runc-1.0.0-5.rc2.gitc91b5be.fc26.1.x86_64
17:54:19 <yzhang> this is the current
17:54:20 <trishnag> We need to decide which blog posts we would like to have in our upcoming documentation from http://projectatomic.io/blog .
17:54:23 <trishnag> Here is the ticket to track so https://github.com/projectatomic/atomic-host-docs/issues/21 .
17:54:32 <dustymabe> yzhang: talk to container team?
17:54:41 <trishnag> We should open tickets for the blog posts that need to be considered as Doc content item. I will include those tickets in the above ticket.
17:54:45 <maxamillion> .whoowns runc
17:54:45 <zodbot> maxamillion: jchaloup
17:54:55 <trishnag> miabbott: jberkus or anyone can help with the same ^ ?
17:54:56 <x3mboy> I really want to thank you for the answer about https://pagure.io/atomic-wg/issue/262
17:55:03 <jberkus> trishnag: sure
17:55:03 <maxamillion> yzhang: ping the maintainer and find out, I don't see a reason why not
17:55:05 <yzhang> sure
17:55:07 <dustymabe> yzhang: we should be able to if we can get it in and make sure it doesn't hose everything first
17:55:10 <jbrooks> yzhang, probably ping lsm5
17:55:12 <trishnag> jberkus++ Thanks!
17:55:13 <zodbot> trishnag: Karma for jberkus changed to 6 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:55:19 <x3mboy> And I'm willing to know If there is a way to do what mattdm says, and how to do that
17:55:22 <x3mboy> ?
17:55:24 <yzhang> I will ask jan and lsm5
17:55:36 <jberkus> trishnag: I'll go through the backlog, shouldn't take that long
17:55:38 <miabbott> trishnag: i'll have a look as well
17:55:45 <dustymabe> x3mboy: let's chat in #fedora-cloud when this meeting is over
17:55:52 <sayan> My PR to apache libcloud to modify snapshots attribute got merged. Now we can directly integrate the feature to fedimg to fix the copy ami issue that was reported
17:55:56 <trishnag> miabbott++ Awesome. Thank you :)
17:55:56 <zodbot> trishnag: Karma for miabbott changed to 4 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:56:05 <x3mboy> dustymabe, ok cool
17:56:08 <x3mboy> ;)
17:56:18 <x3mboy> jberkus++
17:56:18 <zodbot> x3mboy: Karma for jberkus changed to 7 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:56:21 <x3mboy> dustymabe++
17:56:21 <zodbot> x3mboy: Karma for dustymabe changed to 16 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:56:29 <dustymabe> sayan: that's good news
17:56:30 <trishnag> jberkus: Sure.
17:56:35 <dustymabe> can we actually get it done now?
17:56:46 <dustymabe> and close this ticket: https://pagure.io/atomic-wg/issue/263
17:57:01 <sayan> dustymabe: yes
17:57:24 <dustymabe> please give status in the ticket and close the ticket when all amis have perms set right
17:57:26 <sayan> I'll fix and do a release after the freeze is over
17:57:39 <dustymabe> is freeze not over yet?
17:57:40 <sayan> The freeze is planned to be over today afaik
17:57:44 <dustymabe> ok
17:57:59 <sayan> I'm yet to check my mails
17:58:02 <dustymabe> is everyones open item taken care of?
17:58:26 <dustymabe> wow that was a heck of a free for all open floor
17:58:28 <dustymabe> :)
17:58:29 <trishnag> dustymabe: One more I have
17:58:34 * miabbott has to go
17:58:44 * yzhang waves to miabbott
17:58:47 <trishnag> Not sure I should say that here on #atomic.
17:58:52 <trishnag> s/on/or
17:58:59 <dustymabe> trishnag: both maybe
17:59:06 <dustymabe> just say it :)
17:59:09 <jbrooks> .
17:59:22 <trishnag> I need folks to test https://github.com/ansible/ansible/pull/23209 :)
17:59:28 <maxamillion> I ahve a hard stop, have to run
17:59:30 <maxamillion> laters all
17:59:55 * trishnag is done with items
18:00:02 <dustymabe> trishnag: i saw that come through - haven't had time to review
18:00:09 <jberkus> trishnag: I think you filed that issue on the wrong project
18:00:10 <dustymabe> trishnag: can you open a ticket in the atomic-wg issue tracker about it
18:00:27 <dustymabe> and we can get a few of us
18:00:36 <trishnag> jberkus: ansible modules has merged with ansible now.
18:00:40 <trishnag> dustymabe: Sure I will do.
18:00:45 <jberkus> trishnag: oh!
18:00:46 <jberkus> ok
18:01:19 <dustymabe> jbrooks: set the fuse
18:01:26 <jbrooks> .
18:01:29 <jbrooks> .
18:01:32 <jbrooks> .
18:01:39 <jbrooks> #endmeeting