15:00:03 <portdirect> #startmeeting openstack-helm
15:00:04 <openstack> Meeting started Tue Nov 27 15:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:07 <openstack> The meeting name has been set to 'openstack_helm'
15:00:16 <portdirect> lets give it a few mins for people to roll up
15:00:23 <portdirect> #topic rollcall
15:00:28 <srwilkers> o/
15:01:05 <evrardjp> o/
15:01:16 <mattmceuen> \o/
15:01:39 <portdirect> calm down mattmceuen, we need to save those precious calories
15:01:57 <mattmceuen> I've been in efrardjp's native land for a week, I have calories to spare
15:02:07 <srwilkers> nah, if you burn more, you can just replace them with liquid calories of the alcoholic variety
15:02:25 <mattmceuen> evrardjp how does everyone in France stay so thin when two out of every three storefronts is a restaurant.
15:02:28 <alanmeadows> o/
15:02:31 <evrardjp> mattmceuen: oh great :) (I suppose that was my country, and due to beer's vertures my nickname was wrongly spelled :p )
15:02:32 <mattmceuen> ^based on my several blocks of paris
15:02:51 <evrardjp> mattmceuen: I am not living in France :p
15:03:01 <mattmceuen> Native land thought, right?
15:03:07 <evrardjp> nope :p
15:03:13 <mattmceuen> well never mind then!
15:03:17 <portdirect> shall we begin?
15:03:20 <evrardjp> But yeah same thing in Belgium :)
15:03:25 <evrardjp> portdirect: yes!
15:03:32 <portdirect> #topic new repos (docs, images) status
15:03:39 <portdirect> i think this is yours evrardjp
15:03:47 <evrardjp> yeah
15:03:51 <evrardjp> well
15:04:02 <evrardjp> there are reviews pending in those two repos
15:04:32 <evrardjp> I would be super thrilled if we could get consensus and get the ball rolling
15:05:01 <portdirect> both the seed commits from you and lamt look good to me
15:05:22 <portdirect> soon as fungi adds me to the cores list for them, I'll +2 and add all the other cores
15:05:32 <evrardjp> https://review.openstack.org/#/c/619262/ and https://review.openstack.org/#/c/614425/ for example
15:05:41 <evrardjp> perfect.
15:06:09 <evrardjp> If you have access to more people for documentation, it might be interesting to put them core to that specific group too. But that's up to you :)
15:06:19 <portdirect> that was the plan
15:06:31 <evrardjp> Can I go on the next topic (with different order than agenda?)
15:06:33 <portdirect> jayahn, ianychoi_ were also going to go into docs
15:06:42 <portdirect> sure - what you want to do next?
15:06:55 <evrardjp> usage of reno
15:06:56 <ianychoi> Thank u for pinging me :)
15:07:14 <portdirect> #topic reno
15:07:21 <evrardjp> I consider those repos should have release notes from the start
15:07:25 <evrardjp> those new repos*
15:07:49 <portdirect> sure - its on the 1.0 criteria - lets start that ball rolling
15:07:53 <evrardjp> I also believe that existing repos should be adapted to support release notes. I can add this, if you want.
15:07:59 <evrardjp> great.
15:08:04 <ianychoi> Great :)
15:08:19 <evrardjp> I guess if you're all okay with that, I can patch this in the remaining repos.
15:08:30 <evrardjp> Last question on that topic, where will this be published?
15:08:36 <mattmceuen> ooooooold patch to add Reno - https://review.openstack.org/#/c/563481/
15:08:46 <mattmceuen> If you want to used that evrardjp feel free, or I can abandon
15:08:48 <portdirect> ah - flippy :)
15:08:55 <mattmceuen> good ol' flippy
15:09:14 <evrardjp> mattmceuen: that's exactly the files I'd change, so I will take that forward indeed.
15:09:32 <portdirect> sweet - thanks mattmceuen and evrardjp :)
15:09:41 <evrardjp> I probably will compare to my other patch in osh-images for comparison, and match with cookiecutter's current code.
15:10:08 <evrardjp> so on the publication location...
15:10:25 <evrardjp> Do we want to put all the docs/release notes into osh-docs ?
15:10:36 <evrardjp> and consider that all our official documentation is in that repository?
15:11:22 <evrardjp> if reno go into that repository, we'll just need to create convenience script for syncing release notes.
15:11:45 <evrardjp> if all repositories have docs + release notes, there is no need for syncing.
15:11:55 <mattmceuen> good point
15:12:11 <portdirect> i'd prefer for now to keep release notes in their own repos
15:12:25 <evrardjp> I have built OSH-images to be completely independant: its own docs + renos.
15:12:51 <evrardjp> portdirect: ok so we keep things separate. Great, thanks for clarifications!
15:12:58 <evrardjp> that's all I had on this topic.
15:13:38 <portdirect> thx evrardjp
15:13:54 <portdirect> i think your up next :)
15:13:57 <portdirect> #topic priorities
15:14:34 <evrardjp> ok, this is a tricky topic, let me gather my words there
15:14:41 <srwilkers> hehe
15:15:33 <evrardjp> I just wanted to raise the fact it's very hard to track, for an external eye, how to help, and on what to help. I know the specs are something we can work on, but it doesn't 'feel' like everybody is pointing its energy towards that
15:16:30 <evrardjp> so I am sometimes confused about whether my energy is correctly used. I don't want to push towards a direction that's not a priority.
15:17:00 <portdirect> i think in general the 1.0 spec shows where we should be putting energy
15:17:08 <alanmeadows> evrardjp - just to help clarify whats the context of help - toward 1.0 or toward something else?
15:17:36 <evrardjp> alanmeadows: Good question.
15:18:30 <evrardjp> I will just give my experience here: I thought separation and clarity of repositories and their usage was a priority, because I saw the 'idea' of clean cut repositories in the spec.
15:19:15 <evrardjp> So for me, I wanted to reduce technical debt to allow this move to happen. Yet, I understand that 1.0 is many goals, and some could be orthogonal to the changes I want to propose
15:20:06 <evrardjp> My point is I don't have a clear view of 'the focus of the week/month'
15:21:26 <evrardjp> Let me restructure my words with the content of the spec: Is "Charts in the appropriate project" scheduled before or after "Split Ceph chart" ?
15:22:00 <portdirect> both of those activities are done, we 1st moved the ceph chart, and then split it
15:22:37 <evrardjp> sorry to have asked a stupid question then :p
15:23:04 <portdirect> no - it raises a good point, at least we should have a way of indicating this
15:23:09 <srwilkers> https://storyboard.openstack.org/#!/worklist/341
15:23:17 <alanmeadows> perhaps back to the release note wish
15:23:53 <portdirect> i think that links great srwilkers, it shows how for these things storyboard can be a pain :)
15:23:57 <evrardjp> srwilkers: interesting I was on story board: https://storyboard.openstack.org/#!/project/openstack/openstack-helm
15:24:46 <portdirect> but to alans point, i think releasenotes would help a lot here as we burn down the list
15:24:49 <evrardjp> portdirect: great, so now I know that everything in there has focus, everything else is optional. Thanks srwilkers for the link.
15:25:11 <portdirect> i'm also kinda on the fence re a 'theme for the week/month'
15:25:15 <fungi> i've added portdirect to those core reviewer groups now
15:25:19 <srwilkers> thanks fungi
15:25:22 <fungi> np
15:25:29 <portdirect> fungi: \o/
15:25:36 <evrardjp> thanks fungi
15:26:48 <evrardjp> ok now that I have a tool to focus on the priorities, I think we can go onto next topic :)
15:27:27 <alanmeadows> @srwilkers/@portdirect is it safe to say that if https://storyboard.openstack.org/#!/worklist/341 is the canonical 1.0 worklist, it may need some filling in of the edges?
15:27:38 <srwilkers> alanmeadows: yep
15:27:49 <alanmeadows> Like for instance, it addresses the need for helm test coverage across all charts, but not the activation of said helm tests in the gate to validate upgrade viability
15:27:53 <alanmeadows> just as a random example
15:27:56 <portdirect> certainly
15:28:07 <evrardjp> it doesn't cover release notes either
15:28:35 <portdirect> its def the point we should be adding those aspects
15:28:38 <alanmeadows> it would be great to fill in all the missing pieces so we have something we can say covers it all
15:28:38 <evrardjp> I'd love if we could just have that board as a reference.
15:29:01 <portdirect> lets try and get that in shape for the next meeting, so we can review it
15:29:04 <srwilkers> evrardjp: that was the point initially.  it just needs some love to update it
15:29:27 <srwilkers> as there are some work items in flight that address some of those items, but the open changes don't reference them to reflect that
15:29:56 <alanmeadows> mattmceuen also has the etherpad likely from dublin
15:30:01 <alanmeadows> that we can overlay to this
15:30:09 <alanmeadows> if anyone needs a refresher
15:31:37 <mattmceuen> https://etherpad.openstack.org/p/openstack-helm-ptg-rocky
15:32:22 <portdirect> awesome, thanks mattmceuen
15:35:11 * srwilkers whistles
15:36:25 <portdirect> ok - i think we done here for now, lets get that list updated for next week.
15:36:31 <portdirect> #topic roundtable
15:36:40 <srwilkers> what about the helm v3 chat?
15:37:04 <portdirect> whoops - sorry multitasking :)
15:37:33 <portdirect> as we discussed at the summit, and denver ptg it would be great to see a prototype of a lua based chart
15:37:53 <portdirect> this should not have direct impact on the 1.0 release work for osh
15:38:09 <evrardjp> is this because of the 'fun factor' , or because it will actively help in tech debt reduction?
15:38:15 <evrardjp> (just curious)
15:38:17 <alanmeadows> I do not personally know the level of functionality available in `dev-v3`
15:38:22 <alanmeadows> this is far from a fun factor
15:38:29 <srwilkers> evrardjp: helm v3 brings significant changes
15:38:38 <portdirect> yeah - this is critical evaluation
15:38:48 <portdirect> helm v3 is less important
15:38:53 <evrardjp> alanmeadows: I suppose I should read this as -- we have to do this anyway, as no retrocompat will be provided- ?
15:39:22 <portdirect> what is, is evaluating LUA scripting over GO templating to articulating openstack in kubernetes
15:39:44 <portdirect> and we need to know what that looks like.
15:39:52 <alanmeadows> we know gotpl will still be supported
15:40:02 <alanmeadows> the value add here is more what we've discussed a few times over
15:40:12 <evrardjp> ok
15:40:22 <alanmeadows> that there is a significant onramp burden to jumping into OSH charts
15:40:36 <alanmeadows> and that LUA may be a way for us to simplify them to the point where we can attract more developers
15:40:55 <srwilkers> getting rid of some gnarly helper templates would be a welcome addition
15:40:56 <evrardjp> that sounds like a great point for the future indeed.
15:40:57 <alanmeadows> there is a lot of macro/helm-toolkit experise required today
15:41:09 <alanmeadows> expertise, rather
15:41:39 <alanmeadows> srwilkers, exactly
15:42:01 <alanmeadows> we've always said this was a desired goal - even pre v3
15:42:11 <alanmeadows> and with LUA, it seems like it may be the most opportune option
15:42:28 <srwilkers> yup
15:42:38 <evrardjp> Maybe this can be added to another story board for version 1.1/2.0 ?
15:42:39 <portdirect> but just to (for once) be the voice of restraint, we need to actually get something together to see if it offer us what we are looking for
15:42:49 <portdirect> we all feel it will, but we need to prove this out
15:43:00 <portdirect> evrardjp: this would be a 2.0
15:43:04 <evrardjp> investigation can be part of it.
15:43:08 <alanmeadows> yes and the timing is somewhat important I think
15:43:18 <alanmeadows> the earlier we do it, the earlier we can provide feedback to the helm v3 community
15:43:26 <alanmeadows> otherwise, helm v3 is released, and we just need to work with it
15:43:27 <portdirect> exactly
15:44:27 <portdirect> this week i can get a v3 dev env up and running, and push a ps for it
15:44:36 <srwilkers> sweet
15:44:49 <portdirect> which will at least allow us to track how v3 is shaping up.
15:46:48 <alanmeadows> cool
15:47:46 <srwilkers> anything else here?
15:48:08 <portdirect> i think we are done?
15:48:25 <portdirect> thanks for coming everyone
15:48:33 <portdirect> #endmeeting