Tuesday, 2018-09-18

*** slaweq has joined #openstack-meeting-500:11
*** slaweq has quit IRC00:16
*** markvoelker has quit IRC00:44
*** yamahata has quit IRC01:25
*** iyamahat has quit IRC01:25
*** slaweq has joined #openstack-meeting-502:11
*** slaweq has quit IRC02:16
*** roman_g has quit IRC02:46
*** slaweq has joined #openstack-meeting-504:11
*** slaweq has quit IRC04:16
*** slaweq has joined #openstack-meeting-505:02
*** skazi has quit IRC05:03
*** slaweq has quit IRC05:06
*** slaweq has joined #openstack-meeting-506:19
*** skazi has joined #openstack-meeting-506:45
*** persia has quit IRC08:06
*** persia has joined #openstack-meeting-508:07
*** markvoelker has joined #openstack-meeting-508:36
*** derekh has joined #openstack-meeting-508:49
*** markvoelker has quit IRC09:11
*** markvoelker has joined #openstack-meeting-510:07
*** iyamahat has joined #openstack-meeting-510:29
*** iyamahat has quit IRC10:35
*** roman_g has joined #openstack-meeting-510:37
*** markvoelker has quit IRC10:41
*** markvoelker has joined #openstack-meeting-512:04
*** mjturek has joined #openstack-meeting-513:15
*** sgrasley has joined #openstack-meeting-513:47
*** mjturek has quit IRC13:57
*** radeks_ has joined #openstack-meeting-513:58
*** mjturek has joined #openstack-meeting-514:06
*** radeks_ has quit IRC14:14
*** gagehugo has joined #openstack-meeting-514:28
*** mjturek has quit IRC14:43
*** hongbin has joined #openstack-meeting-514:46
*** mjturek has joined #openstack-meeting-514:47
*** iyamahat has joined #openstack-meeting-514:52
*** lemko has joined #openstack-meeting-514:56
*** happyhemant has joined #openstack-meeting-514:57
*** john_W has joined #openstack-meeting-514:59
srwilkers#startmeeting openstack-helm15:00
openstackMeeting started Tue Sep 18 15:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is srwilkers. 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
srwilkers#topic rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
srwilkerso/15:00
mattmceueno/15:00
*** Lnic has joined #openstack-meeting-515:01
*** jamesgu__ has joined #openstack-meeting-515:01
lamto/15:01
jayahno/15:01
jamesgu__o/15:01
srwilkerslet's take a few minutes and add any last minute items to the agenda15:01
jayahnthis switching in hurry is confusing me.. :)15:01
srwilkers#startmeeting15:01
openstacksrwilkers: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:01
srwilkersoops15:02
srwilkershttps://etherpad.openstack.org/p/openstack-helm-meeting-2018-09-1815:02
srwilkersthere we go15:02
john_Wo/15:02
srwilkerslets get started at 5 after -- gives us a few minutes to add things here15:02
ianychoio/15:02
jayahnhey ianychoi15:03
ianychoijayahn, hello :)15:04
srwilkers#topic PTG recap15:05
*** openstack changes topic to "PTG recap (Meeting topic: openstack-helm)"15:05
portdirecto/15:05
srwilkershere's the etherpad we used at the PTG https://etherpad.openstack.org/p/openstack-helm-ptg-stein15:05
evrardjpo/15:05
srwilkersi was really happy with what we were able to chat through, and was especially happy to see some new faces as well as the usual suspects (like jayahn ;) )15:05
portdirectyeah - over the three days we had some really productive sessions15:06
srwilkersportdirect: ill let you lead this topic and the others until you get your new smile ;)15:06
portdirectand its always great to both find out what else is going on in openstack - and put faces to irc names15:06
ianychoiSo nice - although I couldn't stay during Wed-Fri at PTG15:07
portdirectfor me the real highlights were the work that we will kick off this week on docs15:07
portdirectthanks so much ianychoi and jayahn for helping with this15:07
evrardjpirc nickname/face resolution service is so underrated15:08
mattmceuen+115:08
portdirectand also getting some much needed thinking about our gating, and im really looking forward to evrardjp 's help here!15:08
jayahnoh. no. it is co-working, not helping. :) thanks to you.15:08
jayahn+1 on evrardjp!15:08
ianychoiportdirect, it was so great pleasure to see u, and thanks a lot all :)15:08
ianychoievrardjp, so glad that you were also deeply involved with openstack-helm team :)15:09
evrardjp:)15:09
evrardjpgating is on my pipeline, 5th currently15:09
portdirectit was also great to see some new faces appear and hear about use cases we had not imagined for osh15:09
evrardjpsorry if I can't land that today :p15:09
portdirectin particular, the turnout for airship was great, so i hope to see some tighter colab there15:10
portdirectand also people wanting to use ironic and senlin for k8s cluster management15:10
portdirectso it seems like whatever olstion the edge working group comes up with for hardware and k8s provisioning, osh has a home for now in the mix :D15:11
portdirect*solution15:11
portdirectI'll try to get a proper write up for the next meeting15:11
portdirectanything anyone else want to add?15:11
srwilkersalso, looking at exploring getting monasca's helm charts working with openstack-helm to show it as a potential option15:12
evrardjpportdirect: nope, nice to have met you all!15:13
jayahnditto15:13
srwilkersgood to move on portdirect?15:13
portdirectyeah15:13
srwilkers#topic Docs Repo15:13
*** openstack changes topic to "Docs Repo (Meeting topic: openstack-helm)"15:13
srwilkersportdirect: take it away15:14
portdirectI'll bea ble to start this, prob not finish15:14
srwilkersroger15:14
portdirectwhich in many ways sounds like the docs themselves15:14
portdirect:)15:14
* mattmceuen ba-dum-ching15:14
portdirectat the ptg we discussed creating a new repo15:14
portdirectopenstack-helm-docs15:14
portdirectwhich we will use to home all the documentation for osh(-infra/-addons) etc15:15
portdirectthis week we plan to seed this repo with some cores spanning multiple languages15:15
portdirectand then once we have a outline of the desired docs in place15:16
portdirectuse the great work that our korean speaking contributors have done to seed this repo15:16
jayahnhttps://etherpad.openstack.org/p/openstack-helm-docs-outline15:16
portdirect^^15:16
jayahnthis was the etherpad link we created for gathering idea on outline15:17
portdirectyeah - we still need to finish hashing that out15:17
jayahnyeap15:17
portdirectI think looking at other projects for inspriation, eg OSA/Kolla/TripleO/K8s/Istio would really pay dividends here15:17
* portdirect has to leave15:18
portdirectbut I think we really have a good path forward15:18
srwilkersportdirect: i agree15:18
portdirectyou ok to take it from here jayahn ?15:18
jayahnwell, portdirect said most of it.15:19
jayahnwe just need to get inspriation, and put it into our own osh docs outline.15:19
srwilkersyep, i think we should make it a point to try and have an idea of what things look like before next week's meeting15:20
srwilkersthat way we can get started :)15:20
ianychoiI am not sure other project cases which repo only has docs but IMO it is good direction forward15:20
jayahnfyi, next week is korean-thanksgiving holiday week in korea15:21
srwilkersjayahn: oh, let's shoot for the week after next then, so as not to disrupt the holiday :)15:21
jayahnI will try to put some thought into outline etherpad though15:21
srwilkerssounds good to me15:22
srwilkersany other points on this topic?15:22
evrardjpnone15:22
jayahnnot really, ianychoi will help us go through this path as well.15:22
jayahnthanks in advance.15:22
evrardjpthanks jayahn and ianychoi15:22
srwilkers:)15:22
ianychoijayahn, definitely :) evrardjp also thanks!15:23
srwilkers#topic Gates15:23
*** openstack changes topic to "Gates (Meeting topic: openstack-helm)"15:23
srwilkersthis one will cover a few things15:23
evrardjp:)15:23
srwilkersfirst, wanted to just call general awareness to the fact the checks in openstack-helm are all very unhappy.  the glance bootstrap job is failing, and we need to find the root cause15:24
evrardjpif someone asks why it's broken: I didn't do it15:24
evrardjp(yet)15:24
srwilkersi've got a few changes in flight to help us achieve that.  first, ive proposed disabling all check/gate jobs except for the single node nfs gates to help ease the load on openstack-infra15:24
srwilkershttps://review.openstack.org/#/c/603368/15:25
srwilkersso we're not constantly launching multinode checks we know are going to fail, while we sort things out.  once we can fix the issue, we'll add the jobs we disabled15:25
*** Lnic has quit IRC15:25
mattmceuensigh, of course the single node nfs gate failed on that PS...15:26
evrardjpyeah but let's try to fix it earlier rather than later. Merging things with reduced test coverage is risky15:26
evrardjpmattmceuen: yeah :(15:26
srwilkersyeah, we'll need to disable the rest of them mattmceuen15:26
srwilkersevrardjp: agreed.  this is my highest priority right now15:27
evrardjpsrwilkers: when I will have a little time to clean up the gates, I will also make sure the log files gathering is not so verbose15:27
srwilkersor make them nonvoting for the moment, to get the change to disable them in15:28
srwilkersevrardjp: that's been one of the nice-to-have's on my list for awhile15:28
evrardjpsrwilkers: I will ping you for reviews when I will be on it15:28
srwilkersas the number of things we gathered originally made sense, but now accounts for a significant portion of the post run job's time15:28
evrardjpthanks for the work on gates srwilkers15:28
srwilkersevrardjp: awesome, will be happy to review whatever you need.  i secretly like working on the gates -- it's like a puzzle15:29
evrardjpsrwilkers: I know the feeling :)15:29
srwilkersbut since you brought it up, the other portion of this topic was to announce/discuss some of the ideas you had for making our gates more efficient15:30
evrardjpfor those who weren't there in the gating conversation about the PTG ...15:30
srwilkersevrardjp: take it away ;)15:30
evrardjphaha15:30
evrardjpnice thanks15:30
evrardjpyeah so, I have seen quite a series of duplicate jobs, some redundant and missing coverage15:30
evrardjpfor example jamesgu__ would love to see opensuse support I guess :)15:31
jamesgu__ah yes15:31
evrardjpso the plan is to slowly simplify what we can, making everything more modular.15:31
evrardjpI will first combine playbooks, then make sure each of those are enough modular to trigger parts of them depending on the jobs15:31
evrardjpone base job will be tested on multiple distros15:32
evrardjpfurther (longer) jobs will be moved to periodics15:32
evrardjpWhich means two things:15:32
evrardjp1) help will be needed for those reviews, so that we can have shared ownership of gating15:32
evrardjp2) attention will be requested on periodic logs, so that we have shared knowledge of failures, and focus on those before merging new things (that's the hardest part)15:33
evrardjpWell that's my opinion :)15:33
evrardjpofc people can/will disagree :D15:34
evrardjphahaha15:34
evrardjpdoes that plan look okay?15:34
jayahnunderstood. especially, i totally agreed on "hardest part".. will need everyone's attention and support15:34
srwilkersevrardjp: i think that's a good plan15:34
mattmceuenThat's awesome evrardjp - thanks for taking this on15:35
evrardjpI guess another point we might add, is that periodics are cheaper than check+gates15:35
srwilkersthe shared ownership for gating will be awesome15:35
mattmceuenHow will the "periodic" part be managed?15:35
evrardjpso if some specific case should arise, it could become an experimental check, and then, if we have more people interested by it, go periodic15:35
evrardjpmattmceuen: well that's up to us to decide15:35
evrardjpI would like to discuss this in another meeting, to be better prepared15:36
evrardjpI have a few ideas and experience around that15:36
mattmceuenawesome.15:36
srwilkersevrardjp: yeah, sorry.  i ambushed you on this one, although i didnt expect us to get this detailed :)15:36
evrardjpbut it will take a certain amount of time in the discussion, and I don't want to monopolize the conversation15:36
srwilkersi agree we should discuss this more formally once you've had some more time to get your thoughts down :)15:37
evrardjpsrwilkers: yeah didn't get the chance to work on it yet, sorry :(15:37
srwilkersevrardjp: that's okay :)15:37
*** jamesgu has joined #openstack-meeting-515:38
srwilkersany other comments before moving on?15:38
evrardjpnone15:38
srwilkers#topic Move to uWSGI15:38
*** openstack changes topic to "Move to uWSGI (Meeting topic: openstack-helm)"15:38
srwilkersportdirect set this on the agenda, but since he's unavailable at the moment do we want to move this topic to the next meeting or discuss this in the openstack-helm channel when hes back around?15:39
srwilkersbecause thankfully, i cant read his mind15:39
srwilkers:)15:40
mattmceuenone of those - I don't have a preference15:40
srwilkerslet's try to get his attention later in the channel15:40
srwilkers#topic Values ordering spec15:41
*** openstack changes topic to "Values ordering spec (Meeting topic: openstack-helm)"15:41
*** jamesgu__ has quit IRC15:41
srwilkersthis was something we talked about at the PTG.  jayahn and his team started the spec here and did most of the work15:41
srwilkersi've just simply worked to move it the last little bit: https://review.openstack.org/#/c/552485/15:41
srwilkersone of the items we mentioned at the PTG was having some sort of mechanism to enforce this ordering, so as to avoid the overhead of relying on just reviews to prevent divergence15:42
srwilkersevrardjp suggested yamllint to achieve that, and i threw together a quick change to include it in the linting job in osh-infra at the moment: https://review.openstack.org/#/c/603222/15:43
evrardjpyeah it's kinda ugly -- and yamllint is not so flexible in terms of custom rules -- sorry for that15:43
evrardjpbut I guess it's better than the jungle?15:43
srwilkersthe only grievance i have is that to prevent the key-ordering rule from analyzing top level keys, we have to disable/reenable the key-ordering rule via comments around each top level key15:43
srwilkersevrardjp: yeah, it's better than nothing at the moment.  also saved us from having to hand-cook some bash to do it, at least in the interim15:44
evrardjpI have briefly checked on jsonschema15:44
evrardjpbut I guess when I will have more time I will write a proper linter15:44
evrardjpthat's just far down on my list, I am not sure we'll ever see it : p15:45
portdirectjsonschema may be a fut here?15:45
portdirectfit15:45
srwilkersyeah, it would be nice to have a future state to work towards15:45
mattmceuenevrardjp, just looking at the yamllint PS real quick just now, I must have missed it - where is the key ordering actually defined?15:45
evrardjpmattmceuen: I can check the patchset, but generally yamllint take a default configuration, and you extend it based on your needs with small modifications15:45
evrardjpI think the config key for that is keyordering15:45
evrardjpiirc15:45
evrardjpportdirect: it might, but it doesn't have some of the linting features (and json is unordered)15:46
evrardjpI have to check all of that. In the meantime, I appreciate the consitency, as it helps not forgetting anything and brings consistency15:47
evrardjpand brings ease of reviewing*15:47
mattmceuenSo evrardjap you're saying we're relying on the default key ordrering now, but can extend that to define our own?  If so sounds good to me :)15:48
srwilkersmattmceuen: the key-ordering rule uses unicode point to determine alphabetic ordering of the keys.  if we disable it for top level keys, it ensures all our sub-level keys are ordered correctly15:48
evrardjpmattmceuen: exactly what srwilkers just said15:48
srwilkerswhile allowing us to, in a hacky fashion, ensure our top level keys are ordered in the way we define in our spec15:48
evrardjpit's not possible to extend the configuration or rules for this yet.15:48
mattmceuenOh, so the "yamllint disables" would need to be long lived across all charts15:48
evrardjpit's just a boolean: care or not care15:48
srwilkersmattmceuen: yeah, until we determine a more thorough way to do it15:49
evrardjpmattmceuen: yes, that's why it's ugly :p15:49
mattmceuengotcha15:49
mattmceuen:D15:49
srwilkersits not ideal, but neither is having sprawl across the charts15:49
srwilkersive got some other ideas, but we can save those for the openstack-helm channel15:49
srwilkerswe've got one more item i'd like to tackle in the time we have left15:49
evrardjpsounds nice15:49
srwilkers#topic Dropping newton support15:50
*** openstack changes topic to "Dropping newton support (Meeting topic: openstack-helm)"15:50
srwilkersat the ptg, we discussed whether it was time to move on from newton as the default as it's a bit long in the tooth15:50
jamesgu+115:51
srwilkersthe general thought was "yes", but we didnt have a quorum in attendance so i wanted to discuss this here and vote now15:51
mattmceuen+115:51
jayahn+115:51
srwilkers+!15:51
jamesguwhat will be the new default?15:51
lamt+115:51
srwilkers(yes, im that excited)15:51
evrardjp+115:51
evrardjpjamesgu: let's ask for rocky15:51
evrardjp:D15:51
evrardjpor master15:52
jamesguyou know what exactly I was thinking!15:52
srwilkersmaster or bust!15:52
srwilkersjust kidding (maybe)15:52
evrardjpsrwilkers: haha15:52
evrardjpjamesgu: ;)15:52
jayahni am good with that. ;)15:52
ianychoiI don't know the details on openstack-helm but also +1 for same direction :)15:52
srwilkersso it seems we have quorum for moving on from newton -- i'll follow up with portdirect on discussing next steps here15:53
mattmceuenNote we only have overrides defined in the repo for Newton, Ocata, and Pike:  https://github.com/openstack/openstack-helm/tree/master/tools/overrides/releases/pike15:53
evrardjpit's simpler and in alignment with upstream expectations to be tracking master, but I understand it's a delicate game, and the latest stable is an "easier to track" and understandable goal for deploy projects15:53
evrardjpmattmceuen: good point15:53
srwilkers#action srwilkers to follow up with portdirect on moving on from newton as default15:53
mattmceuenFirst step is we need to get overrides defined, then gating established, then we can pick good defaults from among the battle-hardened gated versions15:53
srwilkersmattmceuen: that's true, but think portdirect also had work to support queens awhile back15:53
evrardjpsrwilkers: there were people that weren't at the ptg, could you explain the plan?15:53
srwilkersevrardjp: sure15:54
jayahnqueens will not be that hard.15:54
portdirectjayahn: queens is done, just not merged15:54
jayahni know. :)15:54
jayahnthat is what i mean by not be that hard15:54
srwilkersportdirect: you care to elaborate on the plan here, if you're afoot?15:54
portdirecti may be missibng context15:55
portdirectbut we intend to move to ocata by default for now15:55
mattmceuensounds like the anesthetic hasn't worn off15:55
evrardjphaha15:55
mattmceuen++ ocata for now15:55
portdirectand then also add upgrade gating as a periodical (thx evrardjp !)15:55
portdirectonce thats in place, too the moon! or rocky...15:55
jamesgucould I ask why not even Pike for example?15:56
evrardjpjamesgu: I guess the intent is to slowly move towards latest15:56
srwilkersevrardjp: jamesgu: yep15:56
evrardjpby having a path to upgrade that's periodically tested15:56
portdirect^ this, though i hope slow becomes very quick15:56
jamesgugot it15:56
portdirectas i (and alanmeadows ) have tested upgrades a few times15:56
evrardjpportdirect: I also have dreams :)15:57
srwilkerslol15:57
srwilkersdont let your dreams be dreams evrardjp15:57
evrardjphaha good point!15:57
srwilkersalright, one last thing before we adjourn15:57
srwilkers#topic reviews15:57
*** openstack changes topic to "reviews (Meeting topic: openstack-helm)"15:57
srwilkersi've listed some things that would be nice to get some reviews on15:57
srwilkersS3 manifests, snippets, scripts for HTK: https://review.openstack.org/#/c/588066/15:58
srwilkersElasticsearch S3 repository support: https://review.openstack.org/#/c/559417/5615:58
srwilkersTrim OSH-Infra dev deploy gates: https://review.openstack.org/#/c/602833/15:58
srwilkersUpdate fluentbit version, config template: https://review.openstack.org/#/c/602784/15:58
srwilkersAdd kernel, dockerd, kubelet logs: https://review.openstack.org/#/c/602786/15:58
srwilkersRFC: Add htk snippet for tolerations https://review.openstack.org/#/c/595021/515:58
srwilkersoh, i just noticed the gnocchi and ceilometer item on the etherpad -- im sorry whoever put that down there15:58
srwilkerslet's discuss that in openstack-helm once portdirect is back around, as he's the last one to work on those i think15:58
srwilkersthat puts us at time -- let's carry over anything we want to discuss in openstack-helm15:59
srwilkersthanks everyone16:00
srwilkers#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Sep 18 16:00:04 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-09-18-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-09-18-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-09-18-15.00.log.html16:00
portdirectthx steve - i know mattmceuen did not have time to dicuss his item, lets get that 1st next time16:00
portdirectas review quaility is somthing we really need to get attention on.16:00
evrardjpthanks everyone16:00
ianychoiThanks all16:01
*** john_W has quit IRC16:02
*** mjturek has quit IRC16:10
*** mjturek has joined #openstack-meeting-516:12
*** mjturek has quit IRC16:22
*** mjturek has joined #openstack-meeting-516:40
*** mjturek has quit IRC16:45
*** yamahata has joined #openstack-meeting-516:50
*** derekh has quit IRC17:02
*** gagehugo has left #openstack-meeting-517:11
*** skazi has quit IRC17:26
*** mjturek has joined #openstack-meeting-518:16
*** iyamahat has quit IRC18:17
*** yamahata has quit IRC18:17
*** iyamahat has joined #openstack-meeting-518:27
*** iyamahat_ has joined #openstack-meeting-518:30
*** iyamahat has quit IRC18:34
*** yamahata has joined #openstack-meeting-518:48
*** mjturek has quit IRC19:34
*** mjturek has joined #openstack-meeting-519:49
*** mjturek has quit IRC20:47
*** lemko has quit IRC21:27
*** slaweq has quit IRC22:26
*** hongbin has quit IRC23:03
*** slaweq has joined #openstack-meeting-523:11
*** slaweq has quit IRC23:16

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