17:00:56 <scollier> #startmeeting fedora_cloud_wg
17:00:56 <zodbot> Meeting started Wed Aug 10 17:00:56 2016 UTC.  The chair is scollier. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:56 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:56 <zodbot> The meeting name has been set to 'fedora_cloud_wg'
17:01:02 <scollier> #topic Roll Call
17:01:05 <sayan> .hello sayanchowdhury
17:01:06 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
17:01:09 <scollier> .hello scollier
17:01:11 <zodbot> scollier: scollier 'Scott Collier' <emailscottcollier@gmail.com>
17:01:13 <trishnag> .hello trishnag
17:01:15 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
17:01:18 <rtnpro> .fas rtnpro
17:01:19 <zodbot> rtnpro: rtnpro 'Ratnadeep Debnath' <rtnpro@gmail.com>
17:01:27 <dustymabe> .hellomynameis dustymabe
17:01:28 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
17:01:32 <kushal> .fasinfo kushal
17:01:33 <zodbot> kushal: User: kushal, Name: Kushal Das, email: mail@kushaldas.in, Creation: 2006-02-17, IRC Nick: kushal, Timezone: Asia/Kolkata, Locale: en, GPG key ID: 9DD5346D, Status: active
17:01:36 <zodbot> kushal: Approved Groups: @summer-coding magazine commops +sysadmin-darkserver sysadmin-datanommer +sysadmin-fedimg marketing @gitpym @gitpathagar cla_fedora cla_done fedorabugs packager docs cvsl10n gitliveusb-creator web gitfedora-web @gittranslation-filter sysadmin art gitfedoratv @gitgach @gitlekhonee @gitpony @git-boog @gitsparcy cla_fpca +python-sig +ambassadors gitspin-kickstarts nuancier-mentor
17:01:39 <jbrooks_> .hello jasonbrooks
17:01:42 <zodbot> jbrooks_: jasonbrooks 'Jason Brooks' <JBROOKS@REDHAT.COM>
17:01:44 <maxamillion> .hello maxamillion
17:01:46 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
17:01:48 <kushal> oops
17:01:50 <kushal> .hellomynameis kushal
17:01:51 <zodbot> kushal: kushal 'Kushal Das' <mail@kushaldas.in>
17:02:16 <scollier> #chair kushal scollier maxamillion jbrooks trishnag rtnpro
17:02:16 <zodbot> Current chairs: jbrooks kushal maxamillion rtnpro scollier trishnag
17:02:34 <scollier> #chair kushal scollier maxamillion jbrooks trishnag rtnpro sayan
17:02:34 <zodbot> Current chairs: jbrooks kushal maxamillion rtnpro sayan scollier trishnag
17:02:40 <dustymabe> no chair for me
17:02:42 <dustymabe> :)
17:02:44 <scollier> #chair kushal scollier maxamillion jbrooks trishnag rtnpro sayan dustymabe
17:02:44 <zodbot> Current chairs: dustymabe jbrooks kushal maxamillion rtnpro sayan scollier trishnag
17:02:46 <dustymabe> i'll stand
17:02:49 <scollier> heh.
17:02:58 <maxamillion> it's over rated
17:02:58 <scollier> welcome back from Flock for all who went.
17:03:01 <scollier> what a great conference.
17:03:12 <maxamillion> +1
17:03:13 <dustymabe> scollier: my favorite of the year
17:03:24 <maxamillion> it's tied with Summit for me :)
17:03:24 <scollier> I finally met kushal in person!
17:03:59 <kushal> :)
17:03:59 <scollier> cool, so let's get started, there are no action items from the last meeting.
17:04:11 <scollier> we can kick around some tickets and then open floor it.
17:04:41 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/125
17:05:07 <scollier> Looks like jberkus isn't here today, moving on.
17:05:18 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/136
17:05:44 <scollier> No Ian. whew.  moving on.
17:05:46 <bowlofeggs> .hello bowlofeggs
17:05:49 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
17:05:55 <dustymabe> bowlofeggs: \o/
17:05:57 <scollier> #chair kushal scollier maxamillion jbrooks trishnag rtnpro sayan dustymabe bowlofeggs
17:05:57 <zodbot> Current chairs: bowlofeggs dustymabe jbrooks kushal maxamillion rtnpro sayan scollier trishnag
17:06:02 <scollier> hi bowlofeggs
17:06:17 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/147
17:06:26 <scollier> ok, i think we have jbrooks here
17:06:45 <jbrooks_> Hi, yes
17:06:59 <bowlofeggs> hey scollier!
17:07:07 <scollier> hiya
17:07:14 <jbrooks_> Basically, that one is pending some big rewrite of everything, but I think in the short term we can solve dusty's reported problem
17:07:17 <scollier> and dustymabe, any feedback on ^
17:07:39 <scollier> jbrooks who owns that rewrite?
17:07:40 <jbrooks_> Dusty needs living links for vagrant, I showed him where he can get those
17:07:50 <jbrooks_> maxamillion, I think
17:08:08 <dustymabe> scollier: jbrooks_. yeah I see where those links are- not great that they are in the testing location
17:08:13 <dustymabe> but better than nothing i guess
17:08:18 <jbrooks_> dustymabe, they're the same content
17:08:24 <jbrooks_> but I know what you mean
17:08:34 <dustymabe> indded. but we still have no guarantee those won't change either
17:08:35 <jbrooks_> the shas check out and everything
17:08:39 <maxamillion> jbrooks_: ?
17:09:08 <maxamillion> oh yeah
17:09:16 <jbrooks_> yeah
17:09:36 <maxamillion> so, I'm going to try and resolve that this week actually ... the rewrite just isn't going to happen in a reasonable timeline because of other things going on
17:09:53 <maxamillion> it's going to be a kludge, but we'll get something in place
17:09:55 <jbrooks_> In any case, this is one we can probably stop revisiting every mtg, there should be some sort of cold storage classification
17:10:26 <scollier> jbrooks_ a note on the ticket would suite just fine, me thinks
17:11:16 <scollier> i think we have enough on that one, let's move to next.
17:11:22 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/151
17:11:59 <scollier> kushal, you touched this last, maxamillion, it has you as owner.  updates?
17:12:39 <maxamillion> I've said before that I thought this could be closed because the QA team is happy with where we last level set things unless I'm mistaken
17:12:55 <kushal> yes, we can close this one.
17:12:59 <scollier> maxamillion, kushal +1
17:13:29 <scollier> kushal, want to do that?
17:13:40 <kushal> I will go ahead and do that
17:13:47 <scollier> kushal, thanks
17:13:51 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/153
17:14:06 <scollier> so this one is owned by jberkus.
17:14:09 <scollier> however
17:14:18 <scollier> i did get a chance to chat with misc last week at flock
17:14:27 <scollier> i think we are going to kick the tires on an internal instance
17:14:37 <scollier> to get him familiar with deploying origin on Fedora
17:14:46 <dustymabe> scollier: +1
17:14:49 <scollier> and start some documentation on this.  I'll update the ticket.
17:15:21 <maxamillion> scollier++
17:15:21 <zodbot> maxamillion: Karma for scollier changed to 1 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:15:37 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/155
17:16:01 <scollier> i see jbrooks_ just updated
17:16:06 <scollier> i think it's good to go.
17:16:32 <scollier> there are some open questions in the last comment.
17:16:42 <scollier> if folks would like to chime in for jbrooks_
17:16:47 <jbrooks_> +1
17:16:59 <dustymabe> jbrooks_: looks good to me
17:17:08 <dustymabe> who can do make the change?
17:17:25 <dustymabe> s/do//
17:17:52 <jbrooks_> I can take a crack at a PR
17:17:53 <maxamillion> I wanted to make sure that's something we as a group actually want because I've heard a lot of mixed feedback on the topic, if it is something we want then I'll do it this week
17:17:59 <jbrooks_> Ah, sweet
17:18:05 <maxamillion> I'm going to try and use this week to clean up some of the atomic mess
17:18:14 <jbrooks_> So, I'm +1 and dusty is, who else?
17:18:15 <maxamillion> before diving face first back into OSBS insanity
17:18:26 <maxamillion> I'm +0, I don't care
17:19:21 <jbrooks_> Lazy consensus wins?
17:19:22 <kushal> I also +0
17:19:26 <jbrooks_> Has anyone been -1?
17:19:26 <kushal> jbrooks, hehe :)
17:20:17 <scollier> jbrooks_ in summary, the change is to add new content so people can atomic host upgrade every two weeks?
17:20:42 <maxamillion> scollier: we would turn off the nightly ostree builds and only do them every two weeks
17:20:43 <jbrooks_> scollier, The change is to compose a tree at the same time as the images, so the tree and images line up
17:20:57 <jbrooks_> versus the current, which is continuous, based on bodhi
17:21:16 <scollier> jbrooks_ ok
17:21:27 <maxamillion> do note that there's nothing currently in place to handle one-off releases for critical CVEs
17:21:35 <jbrooks_> Right
17:21:38 <scollier> hmm.
17:21:39 <maxamillion> I mean, we cold just fire off the script and do one
17:22:00 <dustymabe> maxamillion: hmm - i didn't think we were going to stop doing nightly builds
17:22:00 <scollier> is this to reduce some overhead for someone?
17:22:12 <scollier> removing nightlys?
17:22:49 <maxamillion> scollier: no idea
17:22:51 <jbrooks_> Colin would like it to work this way
17:23:01 <maxamillion> dustymabe: colin wants the nightly builds stopped
17:23:06 <jbrooks_> There's some benefit w/ static deltas, making updates faster
17:23:12 <maxamillion> dustymabe: at least that's what I understood
17:23:15 <jbrooks_> There's a desire to say, I'm on X deploy
17:23:23 <dustymabe> ok let's just make sure we are all on the same page
17:23:23 <scollier> jbrooks_ you have a note in there about a process for dealing with crit sec issues, if we can get there, I'm +1
17:23:38 <dustymabe> there are a couple of things we could be talking about
17:23:45 <dustymabe> there is nightly build of fedora atomic host image
17:23:55 <dustymabe> there is compose of the ostrees
17:24:08 <maxamillion> the nightly build is part of the compose
17:24:25 <jbrooks_> The continuous trees from bodhi would still exist
17:24:30 <jbrooks_> One could rebase to them
17:24:35 <dustymabe> I thought what colin wanted was simply thatthere be a two week 'ref' people could follow
17:24:35 <maxamillion> there's another updates-ostree (for lack of a better term) that happens daily as part of a bodhi process, the updates-ostree will stop
17:24:36 <jbrooks_> If that's what you wanted
17:24:46 <maxamillion> wait, what?
17:25:09 <dustymabe> and the images we release every two weeks are programmed to follow that ref by default
17:26:14 <maxamillion> I think one of the problems with me implementing this is that I'm a little ignorant to the finer points of ostree management and creation (not because of lack of interest, just lack of time and the fact that OSBS derailed the last 9 months of my life) ... so I'm largely going to be learning as I go
17:26:31 <jbrooks_> maxamillion, I can help
17:26:41 <jbrooks_> I maintain the centos scripts
17:26:46 <maxamillion> jbrooks_: +1 thanks
17:27:04 <scollier> dustymabe, we all on same page now?
17:27:13 <dustymabe> jbrooks_: how do you understand what colin was asking for?
17:27:30 <maxamillion> scollier: I don't think so
17:27:32 <jbrooks_> dustymabe, It's all in the filed issues, and I've also talked to him
17:27:39 <jbrooks_> But we can talk to him again
17:27:55 <dustymabe> ok - well from everything i read there is nothing that says we should stop building nightly cloud images
17:28:09 <dustymabe> just that they should be programmed to follow the 2 week 'ref' by default
17:28:13 <jbrooks_> Yeah, did I say that?
17:28:21 <dustymabe> no maxamillion did
17:28:47 <dustymabe> I believe
17:29:04 <jbrooks_> My understanding is we do a compose alongside the image build, and use that by default, and bodhi continues doing its thing
17:29:22 <maxamillion> yes, I did the ticket referenced here mentions it https://fedorahosted.org/rel-eng/ticket/6313
17:29:35 <maxamillion> or maybe something mentioned in there does ... I can't remember now
17:29:51 <maxamillion> doesn't matter, if that's not included in this then just ignore me
17:30:30 <dustymabe> maxamillion: no worries
17:30:35 <jbrooks_> maxamillion, I'll follow up w/ you
17:30:41 <dustymabe> i just still think there is value in the nightllies
17:30:49 <scollier> dustymabe, i tend to agree
17:30:50 <dustymabe> jbrooks_: thanks for following up
17:30:55 <scollier> cool.
17:30:57 <scollier> alright.
17:30:58 <dustymabe> jbrooks_: feel free to pull me in  to that
17:31:03 <jbrooks_> ok
17:31:07 <maxamillion> jbrooks_: alright
17:31:17 <scollier> next ticket is kickstart docs, will wait on that since jberkus is out
17:31:33 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/160
17:31:35 <scollier> rtnpro, all you
17:32:10 <rtnpro> so, we have the package for fedora-motd tested and available in F24 repo
17:33:14 <rtnpro> I had ping'd jan to know about the workflow to include fedora-motd in F25 release, and it was said that if it's in the repo, nothing special needs to be done
17:33:37 <rtnpro> I believe, all we need is to include the package in the cloud base image and atomic image
17:33:45 <dustymabe> rtnpro: there is no reason we can't do it in Fedora 24
17:34:01 <rtnpro> the sooner, the better :)
17:34:02 <dustymabe> just would need proper testing up front and then tests added to tunirtests
17:34:24 <rtnpro> I can come up with the test cases
17:34:27 <dustymabe> you'll need to get some volunteers to test it and kushal / trishnag to verify your tunir tests
17:34:40 <rtnpro> I can get folks to test it
17:34:42 <dustymabe> most importantly we don't want to break things :)
17:34:48 <trishnag> I can do that :)
17:34:50 <rtnpro> dustymabe, +
17:34:52 <rtnpro> +1
17:34:57 <rtnpro> trishnag, +1
17:35:05 <dustymabe> i think that's really the big thing right now
17:35:20 <kushal> sounds good to me.
17:35:22 <dustymabe> did you rename the package ? I thought you wanted to make it more generic than fedora-motd
17:35:23 <maxamillion> everything's always broken anyways ... why change now?
17:35:30 <scollier> heh
17:35:30 <gholms> Heh
17:35:35 <rtnpro> so, how do I get the package included for the next build and testing
17:35:36 <rtnpro> ?
17:36:01 <rtnpro> IIRC, there was a PR/patch for the fedora cloud base image kickstart file
17:36:04 <dustymabe> rtnpro: I think the best thing to do is to have people install it by "unlocking" the ostree
17:36:09 <dustymabe> and installing the rpm
17:36:18 <dustymabe> so you don't need an image build for that
17:36:28 <rtnpro> ok
17:36:46 <dustymabe> have them test it that way and then we can include it in the kickstart for cloud base and then the manifest for ostree
17:37:03 <dustymabe> then we'll make sure to test the nightlies before a two week release comes out
17:37:29 <rtnpro> I will create a test workflow for manual testing and add it to Fedora Wiki or the ticket #160, and then later translate the workflow to test cases
17:37:57 <scollier> thanks rtnpro, good to go?
17:38:04 <trishnag> rtnpro: +1
17:38:09 <rtnpro> yes :)
17:38:27 <scollier> excellent.
17:38:31 <scollier> #topic Ticket https://fedorahosted.org/cloud/ticket/167
17:38:34 <scollier> kushal, ^
17:39:05 <rtnpro> #action rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image
17:39:20 <kushal> Sometimes our images fail to pass a blocking test.
17:39:39 <kushal> Like in the example user log file. It can be anything.
17:39:57 <kushal> The question is: should we keep the release blocking till it gets fixed?
17:40:16 <kushal> also for few things (like the same example), we found it failing time to time.
17:40:24 <scollier> kushal, that makes sense to me.
17:40:38 <kushal> We don't know the exact cause why it comes back.
17:40:49 <scollier> if it's a blocking test, something has to be fixed
17:41:07 <kushal> trishnag, has replied to the list with the bug number.
17:41:12 <kushal> trishnag, do you have it handy?
17:41:36 <trishnag> kushal: yes
17:41:42 <trishnag> https://bugzilla.redhat.com/show_bug.cgi?id=1353688
17:41:54 <kushal> Thanks.
17:42:06 <kushal> scollier, just want to hear what others think :)
17:43:05 <kushal> Anyone?
17:43:19 <dustymabe> so I don't think this particular issue is release blocking
17:43:34 <dustymabe> we want a test there to make sure that it doesn't come back after it does get fixed
17:43:53 <kushal> dustymabe, so we can move that test to a nonblocking one.
17:44:05 <dustymabe> kushal: i think that depends on how you look at it
17:44:14 <dustymabe> who is working on atomic host bugs in fedora
17:44:16 <dustymabe> ?
17:44:34 <dustymabe> no one is picking them up unless they have implications downstream somewhere
17:44:54 <dustymabe> so if we want to wait forever to do this release then we make this bug a release blocking one
17:45:06 <maxamillion> I think the answer to that is "nobody"
17:45:17 <dustymabe> if we want to accept it the way it is for now until someone cares enough to spend time to fix it
17:45:26 <dustymabe> then we make it non-blocking for now
17:45:29 <maxamillion> I don't think anyone is specifically working on Fedora Atomic Host from a development perspective
17:45:42 <dustymabe> yeah - there is part of the problem
17:45:57 * dustymabe included
17:46:02 * dustymabe is part of the problem
17:46:02 <maxamillion> does anyone in this group realistically have the time to take that on?
17:46:10 <kushal> dustymabe, yes (that no one is working).
17:46:34 <dustymabe> i would love to - i just have too much other stuff going on
17:46:46 <dustymabe> dayjob - and then i'm moving so that takes away my free tinme
17:46:58 <maxamillion> dustymabe: exactly, I think that a similar problem with everyone else ... and it's not so much a placement of blame as it is a reality of our situations
17:47:06 <maxamillion> dustymabe: myself included
17:47:16 <kushal> maxamillion, well said.
17:47:21 <dustymabe> right
17:47:21 <kushal> same with everyone else.
17:47:27 <dustymabe> i'm hoping things change soon
17:47:39 <dustymabe> change and hope - two words for the gutter
17:47:55 <maxamillion> dustymabe: hey now, those words won two presidential elections ;)
17:48:01 <dustymabe> :)
17:48:40 <maxamillion> anyhoo ... we should likely find a way to resolve that, either by clearing up cycles within our group or finding someone who can take that on ... I'll ask around a little and see if there's anyone who can join the effort
17:48:54 <scollier> thanks maxamillion
17:49:14 <kushal> maxamillion, thanks.
17:49:16 <maxamillion> scollier: can't promise much but I'll try :)
17:49:18 <scollier> kushal, looks like it may take a bit to resolve this.  anything else?
17:49:20 * kushal has two items for open floor.
17:49:23 <kushal> scollier, nope
17:49:24 <scollier> excellent.
17:49:26 <dustymabe> either way we should go ahead and release
17:49:35 <dustymabe> this has been a bug for a while
17:49:37 <scollier> dustymabe, agreed, on that issue.
17:49:40 <maxamillion> dustymabe: the release went out actually :)
17:49:45 <scollier> #topic Open Floor
17:49:45 <dustymabe> really?
17:49:48 <maxamillion> dustymabe: it just wasn't supposed to ... which was the bug
17:49:57 <scollier> ah
17:49:58 <maxamillion> dustymabe: https://getfedora.org/en/cloud/download/atomic.html
17:50:06 <dustymabe> hmm
17:50:07 <kushal> Two points.
17:50:21 <dustymabe> when I went to the page yesterday it said that the tests had failed
17:50:29 <dustymabe> and the latest release was over two weeks old
17:50:38 <kushal> 1. Trisha has started her internship in Fedora Engineering team from this Monday. She will work with our WG.
17:50:43 <kushal> oops
17:50:45 <dustymabe> trishnag++
17:50:46 <kushal> trishnag,
17:50:49 <scollier> yea
17:50:55 <kushal> trishnag, sorry for the typo.
17:51:00 * kushal needs rest
17:51:13 <trishnag> kushal: heh :)
17:51:20 <kushal> 2. We need to update the autocloud test cases in between any freeze on infra.
17:51:30 * trishnag is excited :)
17:51:33 <kushal> No code update, but a data point for the autocloud project.
17:51:56 <kushal> So, I will open a discussion in the infra list for that permission.
17:52:06 <kushal> because we keep adding new tests
17:52:12 <kushal> and changing things as required.
17:52:45 <kushal> Any comments?
17:53:30 <dustymabe> none here
17:53:36 <maxamillion> dustymabe: yeah, the website is updated on a 30 minute cronjob interval so there's a period of inconsistency :/
17:53:52 <scollier> we have ~ 7 minutes left
17:53:56 <dustymabe> oh - i thought that it really didn't update because of the failed test
17:54:10 <scollier> while they are discussing that, jbrooks_ do you have a link to the openshift container builds for centos?
17:54:12 <sayan> kushal: nope
17:54:38 <kushal> #action kushal to write to infra for permission to update Autocloud tests while in freeze
17:54:46 <jbrooks_> scollier, I can look, I'm not sure where they are
17:54:53 * gholms has a thing for open floor
17:54:58 <scollier> jbrooks_ kk.  thank you
17:55:01 <dustymabe> gholms: \o/
17:55:14 <kushal> gholms, hi there :)
17:55:20 <gholms> o/
17:55:27 <jbrooks_> scollier, there are some here https://wiki.centos.org/ContainerPipeline
17:55:29 <maxamillion> dustymabe: it sadly released but shouldn't have ... there is definitely a bug
17:55:48 <dustymabe> well glad we didn't block on that test this time
17:55:53 <dustymabe> but yeah, def a bug :)
17:56:04 <dustymabe> gholms: you going ?
17:56:40 <scollier> jbrooks_ perfect.  thank you
17:56:46 <gholms> Shall I?  Sure.
17:56:50 <dustymabe> googog
17:57:06 <gholms> I'm having trouble figuring out how to handle a cloud-init bug.
17:57:10 <gholms> .bug 1344735
17:57:10 <zodbot> gholms: Bug 1344735 – /var/log/cloud-init.log empty - https://bugzilla.redhat.com/1344735
17:57:29 <gholms> syslogd is in charge of writing cloud-init.log, but we turned that off.
17:57:44 <scollier> while they are discussing that, maxamillion, any objections to me creating a ticket to containerize origin on fedora?
17:57:54 <gholms> journald also stored everything that cloud-init sent to syslog, but we turned off journal persistence as well.
17:58:30 <gholms> How are people supposed to debug cloud-init failures on instances when they can't log into them or turn them off?
17:58:37 <kushal> gholms, I thought we have that between reboots.
17:58:37 <dustymabe> 'turned off journal persistence'
17:58:41 <dustymabe> what does that mean?
17:58:57 <maxamillion> scollier: none at all, that'd be great
17:59:01 <gholms> That means we don't create /var/log/journal
17:59:11 <gholms> (Or at least we didn't the last time I checked)
17:59:28 <trishnag> Oh
17:59:45 <dustymabe> gholms: you mean the plain text version?
17:59:56 <gholms> Yes
18:00:12 <gholms> Do we create /var/log/journal again?  We didn't used to.
18:00:18 <scollier> dustymabe, we have 1 minute left here, y'all can keep the conversation going, but I need to hard stop for another meeting.
18:00:27 <dustymabe> gholms: does this help?
18:00:28 <dustymabe> http://dustymabe.com/2014/09/08/capture-elusive-cloud-init-debug-output-with-journalctl/
18:00:31 <scollier> dustymabe, mind ending meeting when ready?
18:00:36 <kushal> gholms, I am not sure then, I will have to dig.
18:00:39 <dustymabe> scollier: go ahead and end meeting
18:00:40 <gholms> If so then inspecting a dead instance should be possible, assuming journalctl bothers to maintain some level of compatibility.
18:00:46 <dustymabe> we'll continue in #fedora-cloud
18:00:52 <gholms> Ok
18:00:53 <scollier> cool
18:00:55 <scollier> thanks everyone.
18:00:56 <maxamillion> +1
18:00:57 <kushal> Thank you everyone :)
18:01:02 <scollier> #endmeeting