15:01:14 <portdirect> #startmeeting openstack-helm
15:01:14 <openstack> Meeting started Tue Feb  5 15:01:14 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:17 <openstack> The meeting name has been set to 'openstack_helm'
15:01:25 <portdirect> #topic rollcall
15:01:34 <howell> o/
15:01:36 <portdirect> lets give it 5 mins for people to arrive
15:01:40 <georgk> hello
15:02:06 <portdirect> Agenda is here, add away: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-02-05
15:02:21 <srwilkers> o/
15:06:05 <portdirect> ok - lets go
15:06:11 <portdirect> #topic how to deliver and deploy kernel modules needed by a container?
15:06:16 <portdirect> srwilkers: this is yours
15:06:22 <srwilkers> nope, that's not me
15:06:33 <georgk> it was my question
15:06:39 <portdirect> oh - sorry!
15:06:47 <georgk> it comes up in the contesxt of running DPDK
15:07:28 <portdirect> so in the etherpad i mentioned how we are doing this today
15:07:30 <georgk> I saw the init container but misunderstood that the module needs to reside on  the host, not the container
15:07:42 <portdirect> yeah - thats a gap in this approach for sure
15:07:59 <portdirect> in that we dont attempt to install modules - just load them
15:08:03 * mattmceuen o/ sorry I'm late
15:08:05 <georgk> makes, sense. Now I need to figure out how to get the kernel modules on the host OS.
15:08:14 <georgk> DPDK delivered with 16.04 is quite old
15:08:26 <portdirect> this is where having mattmceuen about helps :)
15:08:28 <georgk> and I´d like to make use of a newer version
15:08:46 <portdirect> as i assume your q is in the context of airship?
15:08:55 <georgk> might be more an Airship question, not openstack-helm
15:09:04 <portdirect> its both for sure
15:09:06 <georgk> right, I can take this to the airship channel
15:09:23 <mattmceuen> ty georgk, I'm catching up :)  let's discuss there
15:09:29 <portdirect> in osh - we say you can load modules, but getting them there is out of scope (up to a point)
15:09:43 <portdirect> but things like minimirror should help cloase that gap quickly
15:09:56 <georgk> ok
15:10:16 <portdirect> mattmceuen: not sure if you have any info to hand about loading custom repos etc?
15:11:51 <mattmceuen> absolutely - there is some airship scope on the cusp to help with this!
15:12:24 <georgk> I ´ll catch mattmceuen in the airship channel after this meeting
15:12:48 <portdirect> nice  - thanks guys - though rememebr mini-mirror can be use outside of airship as well :)
15:12:59 <portdirect> I'm looking forward to seeing rpm support for sure.
15:13:14 <portdirect> ok lets move on
15:13:23 <portdirect> #topic Docs TOC draft
15:13:58 <portdirect> so as we discussed last week - I've boshed together a very rough draft for an, ahem, idealised set of docs for osh
15:14:07 <portdirect> https://review.openstack.org/#/c/634944/1/doc/source/index.rst
15:14:36 <portdirect> lets get some eyes on this - at this stage, lets concentrate on the content, rather than rst formatting etc
15:14:57 <portdirect> and once its developed a bit we can start to flesh out the supporting structure behind it
15:15:20 <srwilkers> sounds good
15:15:24 <portdirect> in particular it would be great to get the eyes of people new to OSH on these
15:15:50 <portdirect> so we can try to get a structure in place that helps people enagage both in the project, but also use its deliverables.
15:16:38 <georgk> +1
15:18:17 <portdirect> i know its a quite meeting this week - so lets move on, but I'll also bring this up in irc etc for those that are not here today
15:18:33 <portdirect> #topic K8S slack #openstack-helm channel
15:19:08 <portdirect> so for a long time we have been in the wonderful position of having a dedicated slack channel given to use by the CNCF in their k8s slack
15:19:43 <portdirect> we have been as custodians, and to put it bluntly, bad citizens there
15:19:57 <portdirect> the channel has over 500 active memebers
15:20:13 <portdirect> who have done a wonderful job of self organising and supporting each other
15:20:22 <srwilkers> that's really unfortunate
15:20:23 <portdirect> sorry to lay down the hammer like this
15:20:45 <portdirect> but I think at a minimum, all cores in OSH should be present in that channel
15:20:50 <srwilkers> is there no longer the possibility of syncing both chats anymore?
15:20:58 <portdirect> and we need to provide some support to its memebers
15:21:20 <portdirect> not that im aware of atm - though I'm gonna try to find some infra to set up a bridge
15:21:47 <mattmceuen> will do portdirect, sad to say I didn't realize the need was there
15:22:13 <srwilkers> also genuinely curious -- why not try and direct them here? i feel supporting two distinct chats is going to not only be difficult to do, but will result in potential missed messages between users who only use one
15:22:30 <srwilkers> which of course, a bridge solves that
15:22:47 <portdirect> honestly - the numbers suggest if a shift were to occur that it would make sense to move our primary channel from irc to slack
15:23:15 <portdirect> but as thats got its own challenges - i think a bridge is the long term solution
15:23:34 <srwilkers> it is
15:23:50 <portdirect> in simple terms - we have 66 people in IRC and 567 in slack at this point in time
15:24:02 <srwilkers> is there any way to at least post a channel message that informs them of our weekly meetings at a minimum?  i think getting them engaged in that alone adds immense value
15:24:15 <portdirect> im working with the slack admins atm
15:24:17 <srwilkers> okay
15:24:23 <portdirect> i expect that in place by EOD :)
15:24:30 <srwilkers> cool
15:25:35 <portdirect> ok - lets move on
15:25:51 <portdirect> #topic Parkinglot
15:26:03 <portdirect> anything else people want to discuss this week?
15:27:16 <arunkant> Hi, new to this channel. I was wondering where to enter topics for this meeting. Upstream agenda link shows old meetings only..
15:27:17 <arunkant> https://etherpad.openstack.org/p/openstack-helm-meeting-agenda
15:28:44 <srwilkers> arunkant: typically they'll be posted in the #openstack-helm channel at some point before the meeting begins
15:29:19 <portdirect> arunkant: we use the format: https://etherpad.openstack.org/p/openstack-helm-meeting-YYYY-MM-DD
15:29:36 <portdirect> we should update that doc to reflect this
15:31:04 <arunkant> okay. So should I add the topics to that etherpad or just somehow specify to IRC openstack-helm channel ?
15:31:26 <portdirect> arunkant: feel free to add to it
15:31:38 <srwilkers> Might be valuable to just start creating the etherpad for the following weeks meeting at the end of each weekly meeting
15:31:48 <portdirect> anything you want to bring up this week? we have another 30 mins
15:31:52 <portdirect> good point srwilkers
15:31:57 <arunkant> portdirect: okay.
15:33:11 <arunkant> portdirect: Yes, I have review around adding changes related to another distro support in keystone service, specifically around opensuse based image.
15:33:26 <arunkant> https://review.openstack.org/#/c/633847/
15:33:43 <portdirect> ah yes!
15:33:51 <portdirect> really cool to see this work
15:34:05 <portdirect> are there opensuse images avalible?
15:34:20 <arunkant> I want to see how to approach this common problem which we will see when we need to support distros other than default ubuntu ..
15:34:34 <portdirect> i think we should look to adress this properly so we can make thinks like opensuse a 1st class citizen in osh
15:34:41 <portdirect> yup
15:34:57 <portdirect> to me it seems this should come in phases
15:35:07 <srwilkers> Agreed - this will be pretty exciting to flesh out
15:35:07 <portdirect> we should get a spec up for multiple-distro support
15:35:12 <srwilkers> ++
15:35:21 <arunkant> portdirect: yes, there are loci images available
15:35:27 <portdirect> and then get some images to use (and build them in zuul)
15:36:17 <portdirect> arunkant: we need to get this pushing dockerhub: https://github.com/openstack/openstack-helm-images/blob/master/openstack/loci/build.sh
15:36:50 <portdirect> the most important thing i think - is that we are able to gate on non-ubuntu images
15:37:02 <portdirect> but this should  be articulated in the spec
15:37:11 <portdirect> would you be able to take on writing it?
15:37:16 <arunkant> portdirect: yes, I think evrardjp is working on it.
15:37:51 <portdirect> great - look forward to seeing a ps for it
15:38:42 <portdirect> looking at the ps you have - i think if we own the apache config a bit more - then the only diff required will be to specify the apache config we want to use
15:39:10 <portdirect> which means we wont need to toggle on params to use the default config locations between distros
15:39:14 <arunkant> portdirect: Okay..will circle back on spec aspect of this. Just curious, what are thoughts on how support for multiple distros need to be handled.
15:39:46 <portdirect> 1) spec, 2) images, 3) gates
15:40:20 <arunkant> portdirect: okay :) .. then I should get that spec working..
15:40:24 <portdirect> the only things i think we will see distro specific issues with are services that use apache
15:40:42 <portdirect> up until late last year i was mostly using centos personally
15:40:57 <portdirect> with the exeption of keystone and nova-placement
15:43:14 <arunkant> portdirect: I can see cinder may have some issues as well as expected storage binaries location might be different.
15:43:51 <portdirect> roger
15:44:09 <portdirect> though that should be just a case of rootwrap and cinder.conf over-rides?
15:45:03 <arunkant> portdirect: yes, might be. I recall seeing cinder error with suse image locally..need to investigate further.
15:45:19 <portdirect> nice
15:45:29 <portdirect> would be great to see the work suse is doing here
15:45:49 <arunkant> protdirect: thanks. Will work on getting spec out. That's it from me about this topic.
15:48:03 <portdirect> ok - any other topics?
15:48:28 <srwilkers> nothing from me -- been a quiet week for me
15:49:21 <portdirect> ok - lets wrap up - thanks everybody :D
15:49:26 <portdirect> #endmeeting