Tuesday, 2018-11-27

*** lemko has quit IRC00:08
*** slaweq has joined #openstack-meeting-500:16
*** slaweq has quit IRC00:24
*** slaweq has joined #openstack-meeting-501:16
*** slaweq has quit IRC01:24
*** slaweq has joined #openstack-meeting-502:13
*** slaweq has quit IRC02:24
*** yamahata has quit IRC02:41
*** iyamahat_ has quit IRC02:41
*** slaweq has joined #openstack-meeting-503:16
*** slaweq has quit IRC03:24
*** iyamahat has joined #openstack-meeting-504:09
*** slaweq has joined #openstack-meeting-504:11
*** slaweq has quit IRC04:24
*** yamahata has joined #openstack-meeting-504:27
*** skazi has quit IRC05:46
*** slaweq has joined #openstack-meeting-506:11
*** slaweq has quit IRC06:24
*** skazi has joined #openstack-meeting-506:48
*** slaweq has joined #openstack-meeting-507:42
*** ralonsoh has joined #openstack-meeting-508:29
*** irclogbot_1 has quit IRC08:44
*** irclogbot_1 has joined #openstack-meeting-508:47
*** irclogbot_1 has quit IRC08:53
*** irclogbot_1 has joined #openstack-meeting-508:57
*** skazi has quit IRC08:59
*** skazi has joined #openstack-meeting-509:06
*** skazi has quit IRC09:06
*** derekh has joined #openstack-meeting-509:40
*** roman_g has quit IRC09:58
*** roman_g has joined #openstack-meeting-510:00
*** jlvillal has joined #openstack-meeting-510:58
*** roman_g has quit IRC11:18
*** roman_g has joined #openstack-meeting-511:26
*** roman_g has quit IRC11:26
*** roman_g has joined #openstack-meeting-511:26
*** sgrasley has joined #openstack-meeting-514:05
*** hongbin has joined #openstack-meeting-514:41
*** skazi has joined #openstack-meeting-514:45
portdirecto/14:59
evrardjpo/14:59
portdirect#startmeeting openstack-helm15:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
portdirectlets give it a few mins for people to roll up15:00
portdirect#topic rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
srwilkerso/15:00
*** mattmceuen has joined #openstack-meeting-515:00
evrardjpo/15:01
mattmceuen\o/15:01
portdirectcalm down mattmceuen, we need to save those precious calories15:01
mattmceuenI've been in efrardjp's native land for a week, I have calories to spare15:01
srwilkersnah, if you burn more, you can just replace them with liquid calories of the alcoholic variety15:02
mattmceuenevrardjp how does everyone in France stay so thin when two out of every three storefronts is a restaurant.15:02
alanmeadowso/15:02
evrardjpmattmceuen: oh great :) (I suppose that was my country, and due to beer's vertures my nickname was wrongly spelled :p )15:02
mattmceuen^based on my several blocks of paris15:02
evrardjpmattmceuen: I am not living in France :p15:02
mattmceuenNative land thought, right?15:03
evrardjpnope :p15:03
mattmceuenwell never mind then!15:03
portdirectshall we begin?15:03
evrardjpBut yeah same thing in Belgium :)15:03
evrardjpportdirect: yes!15:03
portdirect#topic new repos (docs, images) status15:03
*** openstack changes topic to "new repos (docs, images) status (Meeting topic: openstack-helm)"15:03
portdirecti think this is yours evrardjp15:03
evrardjpyeah15:03
evrardjpwell15:03
evrardjpthere are reviews pending in those two repos15:04
evrardjpI would be super thrilled if we could get consensus and get the ball rolling15:04
portdirectboth the seed commits from you and lamt look good to me15:05
portdirectsoon as fungi adds me to the cores list for them, I'll +2 and add all the other cores15:05
evrardjphttps://review.openstack.org/#/c/619262/ and https://review.openstack.org/#/c/614425/ for example15:05
evrardjpperfect.15:05
evrardjpIf 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
portdirectthat was the plan15:06
evrardjpCan I go on the next topic (with different order than agenda?)15:06
portdirectjayahn, ianychoi_ were also going to go into docs15:06
portdirectsure - what you want to do next?15:06
*** ianychoi_ is now known as ianychoi15:06
evrardjpusage of reno15:06
ianychoiThank u for pinging me :)15:06
portdirect#topic reno15:07
*** openstack changes topic to "reno (Meeting topic: openstack-helm)"15:07
evrardjpI consider those repos should have release notes from the start15:07
evrardjpthose new repos*15:07
portdirectsure - its on the 1.0 criteria - lets start that ball rolling15:07
evrardjpI also believe that existing repos should be adapted to support release notes. I can add this, if you want.15:07
evrardjpgreat.15:07
ianychoiGreat :)15:08
evrardjpI guess if you're all okay with that, I can patch this in the remaining repos.15:08
evrardjpLast question on that topic, where will this be published?15:08
mattmceuenooooooold patch to add Reno - https://review.openstack.org/#/c/563481/15:08
mattmceuenIf you want to used that evrardjp feel free, or I can abandon15:08
portdirectah - flippy :)15:08
mattmceuengood ol' flippy15:08
evrardjpmattmceuen: that's exactly the files I'd change, so I will take that forward indeed.15:09
portdirectsweet - thanks mattmceuen and evrardjp :)15:09
evrardjpI probably will compare to my other patch in osh-images for comparison, and match with cookiecutter's current code.15:09
*** jamesgu_ has joined #openstack-meeting-515:10
evrardjpso on the publication location...15:10
evrardjpDo we want to put all the docs/release notes into osh-docs ?15:10
evrardjpand consider that all our official documentation is in that repository?15:10
evrardjpif reno go into that repository, we'll just need to create convenience script for syncing release notes.15:11
evrardjpif all repositories have docs + release notes, there is no need for syncing.15:11
mattmceuengood point15:11
portdirecti'd prefer for now to keep release notes in their own repos15:12
evrardjpI have built OSH-images to be completely independant: its own docs + renos.15:12
evrardjpportdirect: ok so we keep things separate. Great, thanks for clarifications!15:12
evrardjpthat's all I had on this topic.15:12
portdirectthx evrardjp15:13
portdirecti think your up next :)15:13
portdirect#topic priorities15:13
*** openstack changes topic to "priorities (Meeting topic: openstack-helm)"15:13
evrardjpok, this is a tricky topic, let me gather my words there15:14
srwilkershehe15:14
*** roman_g has quit IRC15:15
evrardjpI 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 that15:15
evrardjpso 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:16
portdirecti think in general the 1.0 spec shows where we should be putting energy15:17
alanmeadowsevrardjp - just to help clarify whats the context of help - toward 1.0 or toward something else?15:17
evrardjpalanmeadows: Good question.15:17
evrardjpI 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:18
evrardjpSo 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 propose15:19
evrardjpMy point is I don't have a clear view of 'the focus of the week/month'15:20
evrardjpLet me restructure my words with the content of the spec: Is "Charts in the appropriate project" scheduled before or after "Split Ceph chart" ?15:21
portdirectboth of those activities are done, we 1st moved the ceph chart, and then split it15:22
evrardjpsorry to have asked a stupid question then :p15:22
portdirectno - it raises a good point, at least we should have a way of indicating this15:23
srwilkershttps://storyboard.openstack.org/#!/worklist/34115:23
alanmeadowsperhaps back to the release note wish15:23
portdirecti think that links great srwilkers, it shows how for these things storyboard can be a pain :)15:23
evrardjpsrwilkers: interesting I was on story board: https://storyboard.openstack.org/#!/project/openstack/openstack-helm15:23
portdirectbut to alans point, i think releasenotes would help a lot here as we burn down the list15:24
evrardjpportdirect: great, so now I know that everything in there has focus, everything else is optional. Thanks srwilkers for the link.15:24
portdirecti'm also kinda on the fence re a 'theme for the week/month'15:25
fungii've added portdirect to those core reviewer groups now15:25
srwilkersthanks fungi15:25
funginp15:25
portdirectfungi: \o/15:25
evrardjpthanks fungi15:25
evrardjpok now that I have a tool to focus on the priorities, I think we can go onto next topic :)15:26
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
srwilkersalanmeadows: yep15:27
alanmeadowsLike 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 viability15:27
alanmeadowsjust as a random example15:27
portdirectcertainly15:27
evrardjpit doesn't cover release notes either15:28
portdirectits def the point we should be adding those aspects15:28
alanmeadowsit would be great to fill in all the missing pieces so we have something we can say covers it all15:28
evrardjpI'd love if we could just have that board as a reference.15:28
portdirectlets try and get that in shape for the next meeting, so we can review it15:29
srwilkersevrardjp: that was the point initially.  it just needs some love to update it15:29
srwilkersas there are some work items in flight that address some of those items, but the open changes don't reference them to reflect that15:29
alanmeadowsmattmceuen also has the etherpad likely from dublin15:29
alanmeadowsthat we can overlay to this15:30
alanmeadowsif anyone needs a refresher15:30
*** mjturek has joined #openstack-meeting-515:30
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-ptg-rocky15:31
portdirectawesome, thanks mattmceuen15:32
* srwilkers whistles15:35
portdirectok - i think we done here for now, lets get that list updated for next week.15:36
portdirect#topic roundtable15:36
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:36
srwilkerswhat about the helm v3 chat?15:36
portdirectwhoops - sorry multitasking :)15:37
portdirectas we discussed at the summit, and denver ptg it would be great to see a prototype of a lua based chart15:37
portdirectthis should not have direct impact on the 1.0 release work for osh15:37
evrardjpis this because of the 'fun factor' , or because it will actively help in tech debt reduction?15:38
evrardjp(just curious)15:38
alanmeadowsI do not personally know the level of functionality available in `dev-v3`15:38
alanmeadowsthis is far from a fun factor15:38
srwilkersevrardjp: helm v3 brings significant changes15:38
portdirectyeah - this is critical evaluation15:38
*** Brutus333 has joined #openstack-meeting-515:38
portdirecthelm v3 is less important15:38
evrardjpalanmeadows: I suppose I should read this as -- we have to do this anyway, as no retrocompat will be provided- ?15:38
portdirectwhat is, is evaluating LUA scripting over GO templating to articulating openstack in kubernetes15:39
portdirectand we need to know what that looks like.15:39
alanmeadowswe know gotpl will still be supported15:39
alanmeadowsthe value add here is more what we've discussed a few times over15:40
evrardjpok15:40
alanmeadowsthat there is a significant onramp burden to jumping into OSH charts15:40
alanmeadowsand that LUA may be a way for us to simplify them to the point where we can attract more developers15:40
srwilkersgetting rid of some gnarly helper templates would be a welcome addition15:40
evrardjpthat sounds like a great point for the future indeed.15:40
alanmeadowsthere is a lot of macro/helm-toolkit experise required today15:40
alanmeadowsexpertise, rather15:41
alanmeadowssrwilkers, exactly15:41
alanmeadowswe've always said this was a desired goal - even pre v315:42
alanmeadowsand with LUA, it seems like it may be the most opportune option15:42
srwilkersyup15:42
evrardjpMaybe this can be added to another story board for version 1.1/2.0 ?15:42
portdirectbut 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 for15:42
portdirectwe all feel it will, but we need to prove this out15:42
portdirectevrardjp: this would be a 2.015:43
evrardjpinvestigation can be part of it.15:43
alanmeadowsyes and the timing is somewhat important I think15:43
alanmeadowsthe earlier we do it, the earlier we can provide feedback to the helm v3 community15:43
alanmeadowsotherwise, helm v3 is released, and we just need to work with it15:43
portdirectexactly15:43
portdirectthis week i can get a v3 dev env up and running, and push a ps for it15:44
srwilkerssweet15:44
portdirectwhich will at least allow us to track how v3 is shaping up.15:44
alanmeadowscool15:46
srwilkersanything else here?15:47
portdirecti think we are done?15:48
portdirectthanks for coming everyone15:48
portdirect#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:48
openstackMeeting ended Tue Nov 27 15:48:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-11-27-15.00.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-11-27-15.00.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-11-27-15.00.log.html15:48
*** Brutus333 has quit IRC15:50
*** Brutus333 has joined #openstack-meeting-515:53
*** Brutus333 has quit IRC16:02
*** john_W has joined #openstack-meeting-516:03
*** cliffparsons has joined #openstack-meeting-516:15
*** john_W has quit IRC16:36
*** roman_g has joined #openstack-meeting-516:37
*** roman_g has quit IRC17:21
*** derekh has quit IRC17:23
*** roman_g has joined #openstack-meeting-517:23
*** yamahata has quit IRC17:58
*** iyamahat has quit IRC17:58
*** iyamahat has joined #openstack-meeting-518:18
*** yamahata has joined #openstack-meeting-518:37
*** ralonsoh has quit IRC19:07
*** jlvillal has left #openstack-meeting-519:11
*** roman_g has quit IRC19:12
*** slaweq_ has joined #openstack-meeting-520:44
*** skazi has quit IRC20:57
*** slaweq_ has quit IRC21:03
*** slaweq has quit IRC22:03
*** cliffparsons has left #openstack-meeting-522:17
*** slaweq has joined #openstack-meeting-522:19
*** slaweq has quit IRC22:24
*** iyamahat_ has joined #openstack-meeting-522:53
*** iyamahat has quit IRC22:56
*** radeks has quit IRC22:57
*** iyamahat_ has quit IRC22:58
*** iyamahat has joined #openstack-meeting-522:58
*** mjturek has quit IRC23:16
*** slaweq has joined #openstack-meeting-523:29
*** slaweq has quit IRC23:33
*** iyamahat has quit IRC23:54
*** hongbin has quit IRC23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!