Tuesday, 2018-03-13

*** yamahata_ has quit IRC00:37
*** yamahata_ has joined #openstack-meeting-501:51
*** tuanla____ has joined #openstack-meeting-502:00
*** ricolin has joined #openstack-meeting-503:15
*** radeks has joined #openstack-meeting-507:42
*** derekh has joined #openstack-meeting-509:26
*** yamahata_ has quit IRC09:56
*** yamamoto has quit IRC11:46
*** yamamoto has joined #openstack-meeting-511:50
*** yamamoto has quit IRC12:01
*** yamamoto has joined #openstack-meeting-512:01
*** yamamoto has quit IRC12:06
*** tuanla____ has quit IRC12:11
*** MarkBaker has joined #openstack-meeting-512:21
*** hoangcx_ has joined #openstack-meeting-512:53
*** MarkBaker has quit IRC12:56
*** hoangcx_ has left #openstack-meeting-513:10
*** mjturek has joined #openstack-meeting-513:23
*** yamamoto has joined #openstack-meeting-513:34
*** yamamoto has quit IRC13:39
*** yamamoto has joined #openstack-meeting-513:53
*** MarkBaker has joined #openstack-meeting-513:53
*** yamamoto has quit IRC13:55
*** mjturek has quit IRC13:59
*** d|k has joined #openstack-meeting-513:59
*** seungkyua has joined #openstack-meeting-514:07
*** annp has joined #openstack-meeting-514:23
*** annp has quit IRC14:29
*** felipemonteiro has joined #openstack-meeting-514:29
*** annp has joined #openstack-meeting-514:30
*** pcarver has joined #openstack-meeting-514:48
*** wxy| has joined #openstack-meeting-514:54
*** wxy| has quit IRC14:55
*** wxy| has joined #openstack-meeting-514:56
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Mar 13 15:00:53 2018 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. 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
mattmceuen#topic rollcall15:01
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:01
jayahno/15:01
pcarverhi15:01
seungkyuahi15:01
*** annp has quit IRC15:01
jayahnseungkyua: you made it. :)15:01
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-ptg-rocky15:01
mattmceuenThat's not the agenda15:01
portdirecto/15:02
seungkyuayes. ha15:02
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-meeting-2018-03-1315:02
mattmceuenThis is the agenda :)15:02
mattmceuenthanks for joining guys!15:02
jayahnsince we have "review PTG highlights" on the agenda, the first link can also be agenda15:02
mattmceuenFeel free to add anything to the agenda15:02
jayahnlol15:02
mattmceuengood save jayahn :D15:02
mattmceuenI am just back from vacation and trying to catch up / get in the swing of things so please bear with me15:03
mattmceuen#topic PTG Highlights15:03
*** openstack changes topic to "PTG Highlights (Meeting topic: openstack-helm)"15:03
mattmceuenA big thanks to everyone who participated in the PTG15:03
jayahnfighting with blizzard15:04
mattmceuenWe had some really valuable discussion, and was good to meet some more of the team face to face too15:04
mattmceuenaaaaaaaaand blizzard.  that was fun! :)15:04
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-ptg-rocky15:04
mattmceuen^ here are our notes from the sessions15:04
mattmceuenThere is much in there that we will be driving over the next 6 months and the rocky cycle15:04
mattmceuenPlease everyone take a look at your leasure and inwardly digest.  For folks who attended it will be a good refresher and for folks who did not a good learning15:05
mattmceuenFor now, I want to just touch on a small group of takeaways to make sure they're communicated well with the team15:05
mattmceuenPlease interrupt me if you'd like to briefly discuss; in depth discussion should probably become agenda items of their own.15:06
jayahnsure thing15:06
mattmceuenFirst:  we refined our general versioning approach.  The  general direction is documented in the etherpad.15:06
jayahnsqure sugar presentation was great :)15:07
mattmceuenWe hope to get our 1.x gated version support all the way to master (non-voting).  We will not branch OSH to 2.0 till we need to, likely for e.g. kubernetes upgrades (not OpenStack upgrades unless we find a real reason)15:07
mattmceuenWe came up with a list of criteria for OSH v.1.0.  I will author a spec for this and socialize it with y'all for feedback.15:08
mattmceuenDestructive testing:  we would liek to add cookiemonster testing as a 3rd party gate, and would also like to explore powerfulseal15:09
mattmceuenDocs: we need ops and troubleshooting guide that describes how to handle the sharper edges of OSH ops15:09
mattmceuenDocs: we need sane defaults for the LMA stack, or a well-documented way to inject operator-specific things (I added an agenda item for this one)15:09
mattmceuenDocs:  Helm-Toolkit and chart authoring should be documented15:10
mattmceuenDocs:  all our executable documentation should be gated, following the pattern established already15:10
mattmceuen(notice the trend?  we have a lot of documentation needs!  that's not the full list either - would love folks to volunteer for these)15:10
mattmceuenStoryboard:  we want to follow the community goal for this assuming it's established, and will plan to follow the critical mass of folks migrating to storyboard rather than blazing the trail15:11
jayahnone after-feedback: tagging with major openstack version caused some confusion with few people when I explain to team.  we might want to document that tagging policy well.15:12
mattmceuen+115:12
mattmceuenMailing List:  I will begin leveraging it to call out any big items from the team meetings that should be mailed out (and then potentially discussed).  Anyone else can feel free to do the same of course, not exclusively me :)15:12
jayahnwe will !15:13
mattmceuenMailing list:  will be leveraged in situations where the discussion participants prefer it, likewise with IRC.  There is no wrong way to start or continue a conversation, and different folks prefer different means - we will try to meet in the middle and all be flexible.15:14
jayahnwho is blue one on etherpad? Roy?  hi roy :)15:15
jayahnsorry matt, i did not mean any interruption.15:15
mattmceuennope this one's just long :-D15:16
mattmceuenReviewers:  we need more reviewers and more core reviewers.  We need more substantive reviews given the volume of patchsets that are coming through, not just +1's w/o comments.    We will be watching for folks to prove their value as reviewers over time with an eager eye toward adding cores, and truing up our current core list to accurately reflect reality.15:16
srwilkerso/15:17
jayahn+115:17
jayahnyou are great summarizer... matt.15:17
mattmceuenCores should probably also in general be announcing the direction for the project ,with input from the entire team of course.  W.r.t. the item above about announcing big outcomes from our meetings.  This wasn't something we discussed in the PTG but is something I'm connecting the dots on as I type.  We can discuss more later if desired.15:18
mattmceuenYAML ordering:  Jay & team will author a spec for this, defining an ordering for top-level values keys, and having an alphabetical ordering under that15:19
mattmceuenwhew15:19
mattmceuenThat's not the full list, not even all the big hitters, but are some of the important bits to make sure we're all clear on.  Please see the etherpad for more.15:19
mattmceuenAny discussion / comments?15:19
portdirectwe should mention the upgrade gate15:20
portdirectas its kinda the big-hitter for any 1.0.x release15:20
mattmceuenalso please add in anything I missed you'd like to communicate -- just like ^ portdirect thanks :)15:20
srwilkerssorry, reading scrollback as i lost track of time15:20
portdirectstory of your life srwilkers ?15:21
srwilkersportdirect: so it seems15:21
mattmceuenYep we need to gate our upgrades as part of 1.0, and "supporting an  OS version" is synonymous with "a gated upgrade path"15:21
portdirect++15:21
portdirectmattmceuen: "the summarizer" :D15:21
mattmceuenanything else?15:21
mattmceuenmy fingers are so tired15:21
jayahnyou need AI to write down for you.15:22
mattmceuenone more thing on our list of features needed :D15:22
*** mjturek has joined #openstack-meeting-515:23
mattmceuen#topic YAML Values Ordering15:24
*** openstack changes topic to "YAML Values Ordering (Meeting topic: openstack-helm)"15:24
mattmceuenSpeak of the devil - there's already a spec in progress! https://review.openstack.org/#/c/552485/15:24
mattmceuen(did I mention I'm still catching up :) )15:24
jayahnThis is just starting, pls put your opinion on the reviews, and let's get dicussion going15:24
mattmceuenthat's outstanding15:24
mattmceuenyes let's please get eyes on this.15:24
jayahnI was yelling this morning to put this spec on line. :)15:24
mattmceuenhaha just in time!15:25
portdirectis powerds0111 here?15:25
portdirectlooks like a great start :)15:25
jayahnhm.. good question.15:25
mattmceuenthat was also something we brought up at the PTG - potentially moving the time of the meeting to something that works better for the majority of team members15:26
jayahnhe was 7am armada weekly this morning (daylight saving mistake), probably sleeping.15:26
mattmceuenah daylight savings time, america's gift to the world15:27
mattmceuendon't worry, we don't like it either15:27
mattmceuen(speaking for all americans)15:27
mattmceuen#topic [openstack-dev] [release] Relaxed rules for cycle-trailing projects15:27
*** openstack changes topic to "[openstack-dev] [release] Relaxed rules for cycle-trailing projects (Meeting topic: openstack-helm)"15:27
srwilkerscan confirm: hate DST15:28
mattmceuenjayahn I have not read this one yet, can you please give us the gist15:28
*** yamamoto has joined #openstack-meeting-515:28
jayahnwe just found this with openstack-helm filter on mailing list.15:29
jayahnI think Roy(?) seems knows better15:29
jayahnlong stroy short, it was after-two-week" requirements for any packaging/deployment project to be included in coordinated release15:30
jayahnnow they relaxed that to any time in 3 month.15:30
jayahnaccording to this specific mail from Thierry Carrez15:30
*** gmmaha has joined #openstack-meeting-515:30
jayahnjust FYI15:31
srwilkersthe tl;dr being that we could still be considered part of the Queens release if we release before the end of rc2 this cycle i think?15:31
jayahnyeap15:31
jayahnexactly15:31
mattmceuenWe are technically release-independent, this appears to be part of the confusion.15:32
srwilkersrc2 might be unrelated, seems that's the cutoff for any deliverables that arent packaging15:32
portdirect^^15:32
portdirectWe are release independent15:32
mattmceuenThe idea is that we are starting with Newton, and working our way to Master as quickly as is feasible :)15:32
jayahnyeap. that was our goal15:32
jayahnwe are release independent. but it seems like there is rule to be included in so called "coordinated openstack release"15:33
jayahnanyhow, i think we can go to the next one15:34
mattmceuenagree.  I think our discussion at the PTG helped crystallize in our own minds how the OSH versioning/releasing should work, and we'll just need to get that documented to clear up any confusion for others15:34
mattmceuen#topic LMA stack defaults15:35
*** openstack changes topic to "LMA stack defaults (Meeting topic: openstack-helm)"15:35
mattmceuensrwilkers we missed you~15:35
mattmceuenSo it was brought up that we should have one or both of a couple things w.r.t. LMA in OSH15:35
srwilkersi was there in spirit15:35
srwilkersi was that snow ruining everyones day15:35
mattmceuenthere was plenty of irish spirit there, I think I saw you15:36
mattmceuenFirst:  a meaningful out-of-box configuration for all the LMA components; usable dashboards that operators can use without knowing too much about LMA configuration15:36
mattmceuenSecond:  a documented way for operators to inject their configurations in15:37
mattmceuenWhat are your thoughts srwilkers on these, current state & future state?15:37
* mattmceuen has never configured the lma stack except by pushing some buttons15:37
*** eeiden has joined #openstack-meeting-515:38
*** yamamoto has quit IRC15:38
srwilkersFirst point -- yes, that'd be great.  I think we'll find more meaningful out of box configurations as more end users start kicking the tires and seeing what makes sense15:38
portdirectI think this ties in with the rework of the gate - to follow the same format as other osh components (ie kill armansible)15:38
srwilkersyep15:38
mattmceuen+1 and also +1 for armansible15:39
jayahn pls explain me armansible15:39
jayahnㅠ. ㅠ15:39
mattmceuenarmada + ansible :)  clever!15:40
pcarversorry to interrupt, but what is LMA?15:40
jayahnlogging, monitoring, alarm15:40
mattmceuenno interruption, o/ pcarver!15:40
mattmceuenanything else on this topic before we move onwards?15:41
srwilkerscurrent state for first point is that it's mostly followed upstream references for the services charted out, but future state needs to be targeting more real things.  examples that come to mind:  multiline configured in fluentbit to successfully capture python stack traces, more targeteted log filtering perhaps15:41
jayahn+1 on that15:42
srwilkerssecond:  there's a patchset in flight in osh that's a bit stale now that tries to outline some of the configuration entities in the charts, but would also benefit from some feedback with anyone with more ops experience than i have currently.  particularly whether it makes sense  to serve as a foundation to build on15:42
srwilkersas i think writing an ops guide for the LMA stuff would benefit from collective input, as opposed to just my own15:43
mattmceuenthere's probably an 80/20 rule at play here -- 80% of the things that an OSH operator might want to tune could be tuned via 20% of the configuration, so if we document (e.g. gates) that 20% and point folks toward the projects' own documentation, that might be valuable?15:44
mattmceuen(maybe even 90/10)15:44
srwilkersyep. the patchset i have in flight makes a point of directing users to the projects' documentation for clarification on what the exposed configurations target15:45
mattmceuenI think a place to start in any case is to gate with the tunables that we most expect to be tweaked, and build from there15:45
mattmceuenperfect15:45
srwilkersyep15:45
mattmceuencool beans15:46
srwilkersthats it from me15:46
jayahni will put it in my todo list15:46
mattmceuenawesome, thanks for volunteering jayahn!15:46
d|ksrwilkers: because i'm lazy, could you give a link to the patch you're talking about?15:46
jayahnmore yelling for me. :)15:46
jayahnyeap, link would be great15:46
srwilkersi too am lazy d|k15:47
srwilkersbut here you go15:47
srwilkershttps://review.openstack.org/#/c/528488/15:47
d|kSLOTHS UNITE!15:47
d|kthx!15:47
*** yamahata_ has joined #openstack-meeting-515:47
mattmceuenHA15:48
mattmceuen#topic can we modify kolla-build15:48
*** openstack changes topic to "can we modify kolla-build (Meeting topic: openstack-helm)"15:48
mattmceuenjayahn can you elaborate on that one?15:48
jayahni might know the answer but15:48
jayahnsince we are getting kolla image not from kolla, but from our own15:48
jayahnwill it be possible to modify official kolla build?15:49
jayahnfor instance, adding lbaas stuff on newton kolla.15:49
jayahni remember portdirect said kolla did not want us to have our own version of kolla image.15:49
jayahnit is just question to clarify what we can do here. :)15:50
mattmceuensrwilkers portdirect what are your thoughts - anyone can surely propose a PS to kolla, so I guess it's a question of liklihood of acceptance :)15:50
jayahnsince newton is end of life, we cannot propose ps to kolla. it is all done deal.15:51
jayahnotherwise, we will do ps on kolla side.15:51
jayahnfor sure15:52
mattmceuencool - if anyone has addn'l input on that it would be great, and we can continue in the chat room if so!15:52
mattmceuen#topic SKT work planning15:52
*** openstack changes topic to "SKT work planning (Meeting topic: openstack-helm)"15:52
jayahnthat was our way of sharing15:53
mattmceuenjayahn shared some work his team at SKT as a group are planning to focus on this month -- https://etherpad.openstack.org/p/openstack-helm-meeting-2018-03-1315:53
jayahnI will share at least once a month about our plan for the month.15:53
jayahnanyone can give us feedback on priority or suggest  things to do15:53
mattmceuenthank you for sharing jayahn, that's very valuable and is probably something that we need to do more of overall15:53
jayahnor do question on the topic15:53
jayahnregard this as a sort of backlog for us.15:54
jayahnyou can influence it. :)15:54
mattmceuenteam, please take a look at what jayahn has in that backlog and discuss feedback in irc/mailing list/etc15:54
mattmceuenreally appreciate you taking the initiative there15:54
mattmceuenthis dovetails into another topic :)15:55
mattmceuen#topic specs for big changes15:55
*** openstack changes topic to "specs for big changes (Meeting topic: openstack-helm)"15:55
jayahnthis is just our quick opinion.15:55
mattmceuenJay notes a couple of PS in the agenda that could have benefitted from discussion via a spec or otherwise first15:55
mattmceuenI agree15:55
mattmceuenFull disclosure:  some of us got a fire lit under our butts with one of those15:56
jayahnunderstood. just say it then. :)15:56
mattmceuen:)15:57
jayahnwe will support15:57
mattmceuenwe'll strive for good communication as well15:57
mattmceuen#topic roundtable15:57
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:57
ttxre: rc2 above -- actually that would be before rocky-2 milestone15:57
mattmceuensorry for rushing thru this, 2.5 mins left :)15:57
ttxthe new wording says "3 months after the coordinated release"15:57
ttxso you'd have until May basically. The sooner the better though15:58
jayahnokay. :)15:58
jayahnthanks for clarification15:58
ttxnp!15:58
portdirectttx: we are going to remain release independent15:58
portdirecthow does this impact that?15:58
mattmceuenYep that is the part that's confusing me too15:58
mattmceuencan we continue the convo in #openstack-helm?  I want to make sure we're on the same page but we're outta time!15:59
mattmceuen#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Mar 13 16:00:03 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-03-13-15.00.html16:00
mattmceuenthanks ttx16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-13-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-13-15.00.log.html16:00
*** d|k has left #openstack-meeting-516:00
*** gmmaha has left #openstack-meeting-516:00
ttxportdirect: oh, if you are release-independent then you don't do per-cycle releases at all16:01
ttxso you don't do a "queens release"16:01
* ttx jumps on the right channel16:01
*** seungkyua has quit IRC16:07
*** seungkyua has joined #openstack-meeting-516:07
*** seungkyua has quit IRC16:11
*** radeks has quit IRC16:27
*** wxy|_ has joined #openstack-meeting-516:33
*** wxy| has quit IRC16:34
*** ricolin has quit IRC17:11
*** wxy|_ has quit IRC17:19
*** felipemonteiro_ has joined #openstack-meeting-517:29
*** felipemonteiro has quit IRC17:31
*** derekh has quit IRC18:01
*** felipemonteiro_ has quit IRC18:05
*** yamahata_ has quit IRC18:19
*** felipemonteiro has joined #openstack-meeting-518:51
*** yamahata_ has joined #openstack-meeting-518:54
*** felipemonteiro_ has joined #openstack-meeting-518:55
*** felipemonteiro has quit IRC18:59
*** radeks has joined #openstack-meeting-520:06
*** radeks has quit IRC21:19
*** eeiden has quit IRC21:26
*** seungkyua has joined #openstack-meeting-521:32
*** seungkyua has quit IRC21:36
*** yamamoto has joined #openstack-meeting-523:08
*** felipemonteiro_ has quit IRC23:16
*** skazi has quit IRC23:20
*** skazi has joined #openstack-meeting-523:34
*** mjturek has quit IRC23:59

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