16:30:23 <dustymabe> #startmeeting fedora_coreos_meeting
16:30:23 <zodbot> Meeting started Wed Jan 29 16:30:23 2020 UTC.
16:30:23 <zodbot> This meeting is logged and archived in a public location.
16:30:23 <zodbot> The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:30:23 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:30:23 <zodbot> The meeting name has been set to 'fedora_coreos_meeting'
16:30:35 <dustymabe> #topic roll call
16:30:36 <bgilbert> .hello2
16:30:37 <zodbot> bgilbert: bgilbert 'Benjamin Gilbert' <bgilbert@backtick.net>
16:30:39 <dustymabe> .hello2
16:30:39 <kaeso[m]> .hello lucab
16:30:41 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dusty@dustymabe.com>
16:30:42 <miabbott> .hello miabbott
16:30:44 <zodbot> kaeso[m]: lucab 'Luca Bruno' <lucab@redhat.com>
16:30:46 <zodbot> miabbott: miabbott 'Micah Abbott' <miabbott@redhat.com>
16:30:55 <ksinny> .hello sinnykumari
16:30:56 <zodbot> ksinny: sinnykumari 'Sinny Kumari' <ksinny@gmail.com>
16:30:57 <jlebon> .hello2
16:30:58 <ksinny> o/
16:31:00 <zodbot> jlebon: jlebon 'None' <jonathan@jlebon.com>
16:31:17 <mnguyen_> .hello mnguyen
16:31:20 <zodbot> mnguyen_: mnguyen 'Michael Nguyen' <mnguyen@redhat.com>
16:31:56 <dustymabe> #chair bgilbert kaeso[m] miabbott ksinny jlebon mnguyen_
16:31:56 <zodbot> Current chairs: bgilbert dustymabe jlebon kaeso[m] ksinny miabbott mnguyen_
16:32:14 <dustymabe> nice to be back for a meeting this week! sorry I missed last week
16:33:36 <dustymabe> #topic Action items from last meeting
16:33:50 <dustymabe> * bgilbert to work with x3mboy on FCOS infographic
16:33:50 <dustymabe> * slowrie to help us get the azure image upload/boot tested
16:34:13 <dustymabe> I will pick up working with marketing on an infographic
16:34:39 <dustymabe> to let bgilbert focus on some of the tooling we want to get some polish on
16:34:46 <dustymabe> #action dustymabe to work with x3mboy on FCOS infographic
16:34:51 <bgilbert> dustymabe: +1, thanks!
16:34:55 <dustymabe> np
16:35:16 <dustymabe> looks like slowrie isn't around today
16:35:20 <miabbott> slowrie did some initial testing in Azure; ran into DNS problems
16:35:31 <miabbott> https://github.com/coreos/fedora-coreos-tracker/issues/356
16:35:38 <dustymabe> miabbott: so are those issues with  our image or issues with his account or issues with azure?
16:35:52 <dustymabe> ahh thanks for the link
16:36:04 <dustymabe> #info slowrie did some initial testing in Azure; ran into DNS problems https://github.com/coreos/fedora-coreos-tracker/issues/356
16:36:36 <red_beard> .hello red_beard
16:36:37 <zodbot> red_beard: Sorry, but you don't exist
16:36:40 <red_beard> .hello redbeard
16:36:41 <zodbot> red_beard: redbeard 'Brian 'redbeard' Harrington' <bharring@redhat.com>
16:36:59 <dustymabe> ok that seems it for action items
16:37:28 <dustymabe> there are no meeting tickets I see so I'll run through a few topics and then open it up for open floor - if you want a main topic send me a DM and I'll bring it up
16:38:09 <dustymabe> #topic devconf.cz fedora coreos lab
16:38:26 <dustymabe> #link https://dustymabe.com/2020/01/23/devconf.cz-2020-fedora-coreos-lab/
16:38:40 <dustymabe> we had a great turnout at the hands on lab we did at devconf.cz this past weekend
16:38:54 <dustymabe> there was not an empty seat in the room and some people were standing
16:39:35 <dustymabe> So this is great news - as it at least shows from a small sample size that we have interest in FCOS
16:39:49 <jlebon> dustymabe++
16:39:50 <bgilbert> \o/
16:39:53 <jlebon> that's awesome
16:39:57 <ksinny> nice!
16:40:12 <dustymabe> If you are interested in running the lab yourself the link above can be used to run it at home so give it a spin if you want to learn more about FCOS
16:40:35 <abai> dustymabe++
16:40:35 <zodbot> abai: Karma for dustymabe changed to 5 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:40:56 <dustymabe> thanks darkmuggle ashcrow walters miabbott for coming and helping out with the lab
16:40:57 <ksinny> Also, I like the way lab content has been prepared, prerhaps people can follow that later on who didn't get chance to attend in person
16:41:02 <ksinny> dustymabe++
16:41:26 <dustymabe> ok that was a quick FYI
16:41:47 <dustymabe> #topic FCOS "out of preview" retrospective
16:42:14 <dustymabe> I'm throwing this topic in here to see if there's anything we learned from the out of preview release
16:42:29 <dustymabe> obviously there is a lot we know we have to improve on (automation, etc)
16:42:40 <dustymabe> but anything in particular that is new that we learned that we need to do?
16:43:22 <kaeso[m]> I'm doing a double stable+testing release, and it turns out the process doesn't parallelize a lot
16:43:58 <dustymabe> kaeso[m]: which parts? the jenkins pipeline runs themselves?
16:44:11 <kaeso[m]> (I think this the first double we do)
16:44:19 <jlebon> kaeso[m]: yes, now that we're doing double releases each time, i think we need to prioritize https://github.com/coreos/fedora-coreos-pipeline/issues/68
16:44:53 <kaeso[m]> dustymabe: yes, so far the jenkins builds
16:44:53 <dustymabe> yep, I think that should help a lot
16:45:17 <jlebon> i can tackle it soon
16:45:42 <dustymabe> jlebon: I added a label to sync over to internal JIRA tracking
16:45:45 <dustymabe> thanks!
16:45:57 <jlebon> +1
16:46:11 <dustymabe> so with an uptick in user interest, did we learn anything about our users and how they are trying to use FCOS that maybe we didn't expect?
16:47:33 <dustymabe> we definitely get the users asking questions about how to install packages, but we've been doing a good job of trying to push them towards containers I think
16:47:46 <kaeso[m]> Personally I wasn't expecting this one https://github.com/coreos/fedora-coreos-tracker/issues/352#issuecomment-577733058
16:48:27 <dustymabe> kaeso[m]: yeah I half expected that
16:48:59 <dustymabe> that's definitely an interesting one for us to try to solve a bit down the road I think
16:49:14 <jlebon> kaeso[m]: heh, RHEL AH cloud kickstarts actually do this too -- pull down system containers and install them
16:49:50 <kaeso[m]> the whole offline install and customize pet node, I mean
16:51:17 <jlebon> ahh gotcha
16:51:32 <dustymabe> anything else we want to say about the preview release before moving on to another topic
16:52:22 <dustymabe> #topic open floor
16:52:32 <dustymabe> anyone with anything for open floor?
16:53:18 <dustymabe> #info we are in the process of doing a new release for the testing and stable streams (thanks kaeso[m])
16:53:39 <kaeso[m]> https://github.com/coreos/fedora-coreos-tracker/issues/355
16:53:58 <kaeso[m]> this one showed up yesterday
16:54:07 <jlebon> #info we now have some basic upgrade testing: https://github.com/coreos/fedora-coreos-pipeline/pull/190
16:54:57 <dustymabe> kaeso[m]: interesting
16:55:00 <miabbott> #info there is interest from Exoscale (EU cloud provider) to make FCOS available in their cloud
16:55:17 <kaeso[m]> I didn't know Vultr, but as a platform looks quite sane. Does Fedora have accounts there?
16:55:53 <dustymabe> kaeso[m]: I don't think so. vultr themselves reached out to us a few years ago but we didn't have the resources to look at them
16:56:06 <dustymabe> i think they are probably willing to give us accounts if we have time to work on it
16:56:25 <jlebon> starting with just providing the platform-id stamped images should be straightforward
16:56:46 <kaeso[m]> that would be nice, they seem to even support arbitrary PXE
16:57:38 <jlebon> miabbott: do you have a contact?
16:57:52 <dustymabe> jlebon: yep, they're going to open an issue in our tracker too
16:57:57 <miabbott> jlebon: sanja just provided an introduction via email today
16:58:08 <jlebon> +1
16:58:08 <miabbott> and what dustymabe said  :)
16:59:56 <dustymabe> anything else for open floor?
17:00:36 <dustymabe> Now that we are out of preview and also got this conference out of the way I'm looking forward to steady progress through bi-weekly releases
17:00:43 <dustymabe> and settling into some cadence there
17:00:46 <dustymabe> :)
17:01:04 <red_beard> dustymabe: based on questions i've seen raised (even internally) i think a push will need to be done walking folks through use cases
17:01:35 <dustymabe> red_beard: i.e. educating people on the philosophy behind FCOS and also when not to use it?
17:01:40 <red_beard> last night the most recent question was: "how to monitor system performance on RHCOS? In RHEL there are tools like sar, vmstat, iostat, etc. Similarly, do we have any tools or ways to monitor system performance"
17:01:58 <red_beard> and if folks are asking about RHCOS, they need to know about FCOS.
17:03:04 <dustymabe> red_beard: so the use case it "how to monitor system performance on FCOS?" and we'd provide some docs there?
17:03:12 <dustymabe> docs/guidance
17:03:20 <kaeso[m]> red_beard: that's an interesting one, are people running manual interactive tools to monitor clusters of RHEL nodes?
17:03:32 <red_beard> i think (for now) a fedora magazine article is sufficient
17:03:54 <red_beard> kaeso[m]: abso-lutely
17:04:30 <kaeso[m]> red_beard: my understanding is that there is an higher level direction of getting those out of the node as metrics in a continuous way, and then do performance monitoring in an aggregated way
17:05:36 <red_beard> i'm merely pointing out that i'm directly seeing users who are confused and think that *COS is dark witchery and needs all new tools
17:06:01 <red_beard> kaeso[m]: you and i spent lots of time educating folks about that, now there is a whole new crew of folks who can share that message ;)
17:06:33 <kaeso[m]> fair
17:06:58 <dustymabe> anything else for open floor?
17:07:51 <dustymabe> will close out meeting in a few minutes if nothing else comes up
17:09:23 <dustymabe> #endmeeting