15:00:54 <portdirect> #startmeeting openstack-helm
15:00:55 <openstack> Meeting started Tue Jan  8 15:00:54 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:56 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:58 <openstack> The meeting name has been set to 'openstack_helm'
15:01:00 <portdirect> #topic rollcall
15:01:02 <srwilkers> o/
15:01:27 <jayahn> o/
15:02:47 <alanmeadows> o/
15:03:12 <mattmceuen> o/
15:03:12 <evrardjp> o/
15:03:16 <howell> o/
15:03:18 <georgk> o/
15:03:26 <nick_kar> o/
15:03:33 <dimitris_> o/
15:03:43 <evgenyl> o/
15:04:32 <portdirect> ok - lets begin
15:05:08 <portdirect> 1stly Happy New year everyone, I hope you all had a great break and have a fantastic year.
15:05:20 <portdirect> #topic meeting-location
15:05:52 <portdirect> more of an announcement really, but the venue of this meeting will change to openstack-meeting-4 at some point: https://review.openstack.org/#/c/626182/2/meetings/openstack-helm-team-meeting.yaml
15:06:22 <srwilkers> sounds good
15:06:29 <evrardjp> shouldn't the startdate have changed in that patchset? :p
15:06:40 <evrardjp> to express when the change happens?
15:06:43 <evrardjp> just saying ... : p
15:07:05 <srwilkers> :p
15:07:15 <srwilkers> might as well change that, and change the chair as well since that's outdated too
15:07:15 <jayahn> +1 on evrardjp
15:07:16 <evrardjp> so when do we change, next week?
15:07:26 <portdirect> evrardjp: i trust ttx to do the right thing ;)
15:07:37 <evrardjp> he is french
15:07:45 <evrardjp> :D
15:07:51 <srwilkers> unless the start date is meant to reflect the project's start date for meetings overall
15:07:52 <mattmceuen> lol
15:07:53 <srwilkers> oh wow
15:07:57 <portdirect> evrardjp: i believe once the ps merges, we will shift in sync
15:08:15 <portdirect> so would expect to move next week, unless its nit picked to death..
15:08:24 <mattmceuen> sounds good to me
15:08:35 <evrardjp> srwilkers: the chair change should happen in a different patchset
15:08:44 <evrardjp> but yeah, we all agree then :)
15:08:49 <mattmceuen> what all do we need to update - the wiki, the PS, anything else?
15:08:50 <evrardjp> cool thanks for the notice!
15:08:59 <portdirect> I'll get that done at some point, though i dont mind leaving mattmceuen on the hook ;P
15:09:10 <srwilkers> evrardjp: that's fine.  i just think it needs to change in general, regardless of which changeset it's a part of
15:09:23 <srwilkers> portdirect: dirty
15:09:28 <mattmceuen> happy to help, I'll do the wiki :p
15:09:29 <portdirect> the wiki certainly needs some love, though i *still* cannot log into it to make edits
15:09:38 <portdirect> that would be great mattmceuen
15:09:51 <portdirect> can you also remove the refeence to biweekly meetings in the wiki
15:10:03 <mattmceuen> oh wow is that still there :)  willdo
15:10:08 <portdirect> thx dude
15:10:23 <portdirect> ok to move on?
15:10:50 <srwilkers> yup
15:11:01 <portdirect> #topic "denver openstackpalloza"
15:11:55 <portdirect> so - with the combined ptg and summit (almost like the good old days eh?) I'm hopeing we can have a much more lively/productive set of sessions in denver
15:12:22 <portdirect> are people in here planning on attending all (or part) of the events there?
15:12:45 <georgk> I am planning to be there
15:12:45 <srwilkers> i'm anticipating being there for part of it
15:13:12 <jayahn> worst time ever to have openstackpalloza. May 1 (holiday), May 6 (Holiday), between May 1~May3 my kid's short vacation
15:13:55 <jayahn> either i cannot go or i go with family. :)
15:14:03 <portdirect> bring them!
15:14:22 <portdirect> I've put an etherpad up here: https://etherpad.openstack.org/p/openstack-helm-denver-2019
15:14:42 <portdirect> please use it to add topics that you'd like to dicsuss at the event
15:15:02 <portdirect> I'll also see if we can get telepresence set up for those that cannot attend
15:15:06 <evrardjp> srwilkers: woot
15:15:37 <srwilkers> :)
15:15:51 <portdirect> I've also added a section for `summit events`
15:16:33 <evrardjp> I am curious , isn't it palooza, instead of palloza?
15:16:35 <portdirect> I expect that I'll be submitting another workshop (or two) for the summit itself
15:16:43 <evrardjp> <- english is not my native language
15:16:54 <portdirect> evrardjp: being dyslexic i feel i can make my own rules.
15:17:13 <evrardjp> portdirect: like for the workshop, prepare for failure!
15:17:16 <evrardjp> :p
15:17:36 <evrardjp> workshops are a great idea
15:17:43 <evrardjp> though
15:17:45 <portdirect> evrardjp: hopefully not, though spinning up 100 clouds is always fun.
15:18:17 <portdirect> anyway - thats all I have on this
15:19:34 <portdirect> #topic OVS-DPDK
15:19:41 <georgk> yeah
15:19:52 <portdirect> georgk: do you want to continue the convo from the airship meeting?
15:20:07 <georgk> so, noob trying to wrap his head around this and happy for reviews and advices
15:20:13 <georgk> yes, please
15:20:30 <georgk> BTW: please ignore that the list is on an Akraino wiki
15:20:30 <portdirect> for those that were not in the airship meeting
15:20:38 <portdirect> :)
15:21:15 <portdirect> georgk has done some great work outlineing the steps required for ovs-dpdk support in an openstack-helm cloud deployed with airship here: https://wiki.akraino.org/display/AK/Support+of+OVS-DPDK+in+Airship
15:21:20 <portdirect> georgk: over to you
15:21:20 <hogepodge> (hi, late arrival)
15:21:32 <georgk> so, there was a comment that many of these things can be done by Airship today already, which is great
15:21:34 <srwilkers> hey hogepodge
15:22:07 <georgk> so, if you can point me to how to get the configuration (e.g. for hugepages) done, that would be very appreciated
15:22:26 <georgk> moreover, I have pushed an initial patch with an ovs-dpdk helm chart
15:22:33 <georgk> #link https://review.openstack.org/#/c/626894/
15:23:02 <portdirect> georgk: re that ps - is there a reason that dpdk support cannot be added to the existing ovs chart?
15:23:28 <alanmeadows> beat me to that one
15:23:32 <alanmeadows> just scanning i only see image deltas
15:23:36 <alanmeadows> but i must be missing something
15:23:56 <georgk> mhh, probably not - we just need to parameterize the attributes related to hugepages
15:24:22 <portdirect> extra mounts in here: https://review.openstack.org/#/c/626894/1/ovs-dpdk/templates/daemonset-ovs-vswitchd.yaml
15:24:33 <georgk> right
15:25:05 <portdirect> i think if you wrapped those in {{ if .conf.dpdk.enabled }} or similar
15:25:05 <georgk> yeah, ok, parameterizing this might make more sense, given the amount of common code
15:25:14 <georgk> I agree
15:25:15 <portdirect> then you shoudl be able to reuse the exising chart
15:25:18 <portdirect> nice
15:25:55 <evrardjp> +1 on parametrization
15:26:29 <georgk> ok, ok.
15:27:00 <georgk> then I was wondering on which tools to use to get  the hugepage configuration done on the host
15:27:02 <portdirect> on the hugepage work - I'd recommend looking at libvirt for pointers
15:27:27 <portdirect> re getting them on the host - thats where i think airships drydock comes into play
15:28:03 <georgk> yes, that´s my understanding (again sanity check)
15:29:03 <georgk> ok, so I´ll update the chart as suggested and look into drydock
15:29:06 <portdirect> nice - i think if you get the changes to ovs into the exising chart, then we can really start to help here
15:29:29 <georgk> I am lacking a good dev environment at the moment, though
15:29:35 <portdirect> it would also be great if you took the items you have in the akrano wiki and got them into launchpad
15:29:47 <georgk> will do
15:29:49 <portdirect> that we cant help with georgk :(
15:30:10 <mattmceuen> I can :)
15:30:18 <mattmceuen> georgek let's take that one back to #airship
15:30:35 <mattmceuen> catching up - can't help with dev env necessarily
15:30:36 <georgk> mattmceuen: ok, great
15:30:41 <mattmceuen> but can help with with the drydock
15:30:48 <mattmceuen> ;-)
15:31:06 <georgk> sure ;-)
15:31:19 <georgk> ok, I think that´s it from my side for now
15:31:23 <georgk> thanks
15:31:28 <portdirect> nice - thanks georgk
15:31:47 <portdirect> really nice to see this start to come together, you've really championed it dude
15:32:13 <georgk> :-)
15:32:56 <jayahn> evrardjp: just quick check. are you suggesting this requires spec? https://review.openstack.org/#/c/603971/
15:33:35 <jayahn> and frankly speaking, i don't know how to put it in release note. can somebody help me on that?
15:33:45 <portdirect> pefect segway
15:33:49 <evrardjp> nope, not a spec
15:33:50 <portdirect> #topic reviews
15:34:32 <jayahn> then, cloud you be a bit more specific on documentation?
15:34:44 <jayahn> want to followup :)
15:34:47 <portdirect> jayahn: I think the intent of that ps is pretty clear, and definatly solves a issue for many people
15:35:14 <evrardjp> jayahn: IMO, now that we have release notes available in all the repos, we should give insights about what's changing in the repositories. Here you're bringing a new feature in, which IMO, deserves a few words in a release notes. A longer explanation can be given in a documentation page
15:35:18 <portdirect> i think a note in the documetation on how to use it to say use an external mysql or keystone would be great
15:35:20 <jayahn> portdirect: yeap, that we thought
15:35:56 <portdirect> evrardjp: can you help jayahn though the process of writing a reno note?
15:35:58 <evrardjp> the purpose is for future you or any other person, to be able to see that feature and enable it on its deployments
15:36:07 <evrardjp> portdirect: sure!
15:36:10 <jayahn> okay. i can work on putting few words or a note in documentation.
15:36:33 <portdirect> frankly the commit message itself is almost whats required for the reno work
15:37:04 <portdirect> jayahn: re https://review.openstack.org/#/c/625803/  (timezone work)
15:37:09 <evrardjp> portdirect: I don't mean it should be different -- the commit message and the release notes are, for me, destined to two different audiences.
15:37:25 <portdirect> again i really like this - its been on my mental to do list for ages
15:37:35 <portdirect> but i need to double check the implementation
15:37:48 <portdirect> kfox111 did some great work here ages ago
15:37:58 <evrardjp> the commit messages is for OSH developers, while the reno is meant for deployers which don't particularily need to git blame things
15:38:06 <portdirect> and i think his method was a bit cleaner (though my memory is fuzzy)
15:38:24 <portdirect> evrardjp: 'is almost' ;)
15:38:27 <jayahn> can someone teach me how to add things in reno? :)
15:39:08 <jayahn> okay, got that from osh irc channel
15:40:18 <evrardjp> (for the record in the OSH irc channel, we discussed how to create a release note using reno new <releasenotename>
15:40:20 <evrardjp> )
15:40:36 <portdirect> nice - thanks evrardjp
15:41:03 <portdirect> on the docs work: https://review.openstack.org/#/c/625853/ I must hold my hands up here, work, and vaction got the better of me
15:41:21 <portdirect> i also sent the cores email to the old ml addr :(
15:41:22 <evrardjp> jayahn: https://docs.openstack.org/reno/latest/
15:41:31 <portdirect> will resend right after the meeting
15:41:52 <jayahn> evrardjp: you are the best!
15:42:50 <evrardjp> I think what's important to remember, is the focus of the release notes. IMO, the release notes should be focused on exposing features/bugs/gotchas/upgrade tips to deployers, the ones which won't git blame the code.
15:43:18 <evrardjp> It's a good quick intermediary before writing a fully featured documentation.
15:43:41 <portdirect> ++
15:43:45 <jayahn> ++
15:43:50 <portdirect> evrardjp: while your here, could you pull the junk data out of the quay.io login for now in here: https://review.openstack.org/#/c/624713/
15:43:58 <portdirect> and then i think we can merge
15:44:17 <evrardjp> portdirect: still on my todolist, I wanted to do it yesterday/today, still didn't find the time yet.
15:44:23 <evrardjp> portdirect: probably tomorrow.
15:44:36 <evrardjp> latest
15:44:49 <evrardjp> thanks for the reviews btw :)
15:45:21 <portdirect> evrardjp: nah man, thanks for your work bootstrapping that repo, really helped lighten the load.
15:47:14 <portdirect> ok - lets open the floor
15:47:25 <portdirect> #topic any other business?
15:48:13 <evrardjp> I hope you had nice holidays everyone
15:48:20 <evrardjp> that's it :)
15:48:41 <jayahn> thanks!
15:49:47 <portdirect> ok - lets wrap up then
15:50:22 <portdirect> tune in next time, same osh time, probably different osh channel
15:50:28 <portdirect> #endmeeting