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