Tuesday, 2018-06-05

*** ricolin has joined #openstack-meeting-500:47
*** seungkyua has joined #openstack-meeting-501:43
*** seungkyua has quit IRC01:47
*** yamamoto has joined #openstack-meeting-502:15
*** yamahata has quit IRC03:41
*** yamamoto_ has joined #openstack-meeting-506:57
*** slaweq has joined #openstack-meeting-506:59
*** stokvis has joined #openstack-meeting-507:00
*** yamamoto has quit IRC07:00
*** radek__ has joined #openstack-meeting-508:14
*** roman_g has joined #openstack-meeting-508:28
*** derekh has joined #openstack-meeting-508:46
*** ricolin has quit IRC11:02
*** yamamoto_ has quit IRC11:29
*** yamamoto has joined #openstack-meeting-511:35
*** yamamoto has quit IRC11:58
*** roman_g has quit IRC12:30
*** roman_g has joined #openstack-meeting-512:31
*** yamamoto has joined #openstack-meeting-512:44
*** yamamoto has quit IRC13:44
*** radeks has joined #openstack-meeting-513:49
*** lajoskatona_ has joined #openstack-meeting-514:00
*** lajoskatona_ has quit IRC14:00
*** stokvis has quit IRC14:18
*** hongbin has joined #openstack-meeting-514:21
*** derekh has quit IRC14:44
*** yamamoto has joined #openstack-meeting-514:45
*** tdoc has joined #openstack-meeting-514:51
*** yamamoto has quit IRC14:51
*** jgu_ has joined #openstack-meeting-514:56
*** yamamoto has joined #openstack-meeting-514:56
*** slaweq_ has joined #openstack-meeting-514:58
*** slaweq has quit IRC14:58
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Jun  5 15:00:19 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:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
srwilkerso/15:00
*** gmmaha has joined #openstack-meeting-515:00
mattmceuenGM srwilkers!15:00
gmmahao/15:00
srwilkershey mattmceuen :D15:00
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-meeting-2018-06-0515:00
alanmeadowso/15:01
roman_go/15:01
mattmceuenHere's our agenda - please add all the burning talking points that have been keeping you up at night15:01
lamto/15:01
*** yamamoto has quit IRC15:01
srwilkersthats a long list15:01
mattmceuenplease prioritize them to talk about the OSH things first15:01
mattmceuenif we move fast we can work our way down to spicy mexican food15:02
mattmceuenFirst thing:15:02
mattmceuen#topic Storyboard Friday15:02
*** openstack changes topic to "Storyboard Friday (Meeting topic: openstack-helm)"15:02
mattmceuenStoryboard Friday.15:03
mattmceuenNot sure of the exact time  but we'll keep the migration communicated in the channel15:03
mattmceuenI suggest to be safe, let's just stay out of Launchpad on Friday15:03
rwellumHopefully smooth sailing... o/15:03
srwilkershey rwellum o/15:04
rwellumhi srwilkers15:04
*** gagehugo has joined #openstack-meeting-515:04
mattmceuenAs far as our daily lives post-storyboard15:04
mattmceuen1) use Storyboard for all new scope and bugs and specs going forward15:05
mattmceuenthere are no more blueprints, no more bugs15:05
mattmceuenEverything is a Story (hence the name)15:05
portdirectspecs?15:05
mattmceuenYep specs should be captured as stories15:05
portdirectI need to read up - but would we no longer be doing them in gerrit?15:05
mattmceuenWe should find an example of a story spec15:06
mattmceuenSpecs in gerrit15:06
mattmceuenJust no blueprint in launchpad any more - a story in storyboard instead15:06
alanmeadowsare folks generally creating a story linking to the gerrit spec for full storyboard awareness?15:06
alanmeadowsI am unaware of the sb customs15:07
mattmceuen2)  For linking PS to Stories (in general) here is a quick example from Kendall15:07
mattmceuenAs for instructions on git commit headers its pretty simple. You link both the task and the story in the commit. You should know this from Upstream Institute :wink: It ends up looking like this:15:07
mattmceuen-----------------15:07
mattmceuenCommit message summary line stuff15:07
mattmceuenCommit message body info. All the details. Blah blah blah.15:07
mattmceuenStory: 88288215:07
mattmceuenTask: 222115:07
mattmceuenChange-Id: djk3kj24jk2kj21kj1kj25009sdfk15:07
mattmceuen----------------15:07
mattmceuenrwellum - have you seen any good example / prior art for spect-storyboard linking?15:08
rwellumLooking at ironic right now to pull one out15:09
mattmceuenAwesome thanks15:09
pcarver_I haven't been following storyboard development. Did they standardize on a way of showing release content?15:09
mattmceuenAlso thanks to rwellum for leading this effort15:09
jayahno/15:10
*** pcarver_ is now known as pcarver15:10
mattmceuenRelease content in what sense - like release notes?15:10
mattmceuenhey jayahn!15:10
jayahnhey15:10
pcarverI mean the equivalent to Launchpad's "Series and milestones" pages15:10
roman_gq: would we change URL in #openstack-helm topic from Launchpad to Storyboard?15:11
srwilkersroman_g: i would imagine so15:11
pcarverWhere you can see what bugs and blueprints are planned for any future milestone or were contained in any past milestone15:11
rwellumBTW airship is already using storyboard: https://storyboard.openstack.org/#!/project_group/8515:12
mattmceuenLucky them, they started there so don't have to do a migration :)15:12
mattmceuenNote I'm planning to shamelessly model after the links on the ironic wiki15:13
mattmceuenhttps://wiki.openstack.org/wiki/Ironic15:13
mattmceuenre: bug tracker / feature tracker15:13
alanmeadowsairship is already hoving over storyboard15:13
mattmceuenspecifying the release is not jumping out to me pcarver15:13
mattmceuenalanmeadows is here all day, folks15:13
pcarverHmm, looking at OSH's Launchpad it doesn't look like you've been tracking any releases yet anyway15:14
portdirectnope15:14
portdirectas we dont yet have one15:14
portdirectthough probably should have bee tracking toward it15:14
portdirect*been15:14
*** wxy| has joined #openstack-meeting-515:15
mattmceuenYeah, we just have a spec for 1.0, and I'm going to translate remaining work items into stories.  I'll release teg them in the right way if we can figure out what that looks like.15:15
pcarverNeutron is what I usually look at as the ideal example https://launchpad.net/neutron/+series15:15
portdirectpcarver: you know that launchpad is going away?15:16
pcarverYou can see every milestone all the way back to the Diablo series and click on any one to see what was in it15:16
rwellumGood example of ironic, plus tags: https://storyboard.openstack.org/#!/story/200206415:16
pcarverportdirect: I'm aware of it, but when I asked the Storyboard folks about this functionality  8-12 months ago it wasn't even on their radar15:16
portdirectroger15:17
mattmceuenaha15:17
mattmceuendoes subject-prefixing stories-for-specs with "[RFE]" sound good to y'all?15:17
pcarverI'm not sure if it's because they didn't/don't care about recording history or if they just weren't familiar with Launchpad's interface15:17
rwellumThis amongst other reasons is why the transition hasn't happened for all. But we reasoned that being fairly new, for OSH it's better now than later.15:18
pcarverThey kind of suggested that every project would just invent its own practices15:18
rwellumpcarver: yeah same message I got at the summit.15:18
pcarverWhich sounded like an awful idea to me15:18
portdirectwe work with what we have :)15:18
mattmceuen+1 :)15:18
mattmceuenaka "do what Ironic does till we see something we don't like"15:19
mattmceuenAlright - any other Storyboard items before we tie this one up and breathlessly wait till friday15:19
portdirectshouldn't be to physically painful15:19
pcarverBut if everybody is on their own to establish and follow practices, then it would be at least a good idea to figure out what those are15:19
rwellumpcarver: think it's worthwhile firing off an email to openstack-dev?15:19
pcarverrwellum: Possibly. I haven't been following storyboard migrations, so maybe some teams have already figured out standard practices.15:20
mattmceuenwould be helpful for teams to have all best practices summarized in one place, even if it has the caveat to "do whatever you want"15:20
mattmceuenAlright we'd better keep rolling.  Let's stay in sync on this in the #openstack-helm channel15:22
mattmceuen#topic Review OSH troubleshooting brainstorming15:22
*** openstack changes topic to "Review OSH troubleshooting brainstorming (Meeting topic: openstack-helm)"15:22
pcarverThe main question for any give team to answer (e.g. OSH), is whether the team sees value in maintaining a history of what the series and milestones were and what was in each15:22
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-troubleshooting15:22
jayahni do think there is value in maintinaing history15:23
portdirectI really see value in release notes15:23
mattmceuenAgree - we should start off on the right foot15:23
portdirectas meeting part of that requirements15:23
mattmceuen+115:23
mattmceuenWe have a reno PS ready to merge in, but we're waiting on having our own release notes best practices documented before pushing that out15:24
rwellumFor the trouble shooting, I filled out of a lot of this, which is 'ironic' because I have little osh experience to date - most of this was from my notes on kolla-k8s15:24
portdirecthow much is osh specific?15:24
portdirectand how much is general k8s?15:24
rwellumSo no hurt feelings if we cut stuff.15:24
rwellum99% kubernetes15:25
*** radeks has quit IRC15:25
rwellumBut  added a section: what to do if something goes wrong, that I would expect to be more osh related of course.15:25
mattmceuen+100015:25
*** radek__ has quit IRC15:25
mattmceuenI really like that section at the end15:26
alanmeadowsI would take this opportunity to say long-term whats needed is a crowsnest OSH chart15:26
alanmeadowssomething to look at data from k8s, cni, prometheus, OS sevices, and so on15:26
mattmceuenBecause it will save us a lot of grief :D even if that is k8s specific, it's a quick list of what info to gather15:26
jayahncrownset?15:26
alanmeadowsand provide simple checklists for end users15:26
alanmeadowsmost of this checking can be mechanized15:26
alanmeadows"You have the following pods in a CrashLoop: ..."15:27
alanmeadows@jayahn: having fun with nautical words.. a simple dashboard15:27
mattmceuenhttps://goo.gl/images/fZFwuG15:27
jayahnah..15:27
rwellum+1 alanmeadows - that's what I was getting at. because you can filter out so many questions this way.15:27
tdocBeing a new user, I think most of the stuff in there is useful, by now most of it I had figured out, but it would surely have helped to have from the start.15:27
alanmeadowsthis would be the first non-helm development effort of OSH, but it would be tremendous15:28
mattmceuenSince we're in brainstorming mode, it's better to err toward putting stuff in that etherpad now15:28
mattmceuenThe trick will be curating that down to OSH documentation without getting too far into the business of hosting k8s-general docs15:28
mattmceuenMaybe some really key concepts, and then link out to k8s docs for more15:29
*** slaweq has joined #openstack-meeting-515:29
*** nguyenhai93 has joined #openstack-meeting-515:29
rwellum+115:29
mattmceuenI think we should let the troubleshooting guide material keep maturing for another week or two - just wanted to remind people it's out there and to please review / add to it15:30
jayahn+115:30
tdoc+115:30
mattmceuenIf alanmeadows wants to turn it into a design doc for a new crowsnest, well that's one of those four opens :)15:30
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-troubleshooting15:30
mattmceuenthanks to rwellum, roman_g, and anyone else who's contributed so far (can't see everyone's names)15:31
alanmeadowsWe threw around the idea of simply extending cockpit, I can look into it15:31
alanmeadowsfull 360 view15:31
mattmceuenpete has an item on the agenda, but he's in a side convo so we'll come back to him15:31
mattmceuen#topic Elasticsearch S3 snapshot repos via radosgw s3 api15:31
*** openstack changes topic to "Elasticsearch S3 snapshot repos via radosgw s3 api (Meeting topic: openstack-helm)"15:31
mattmceuen@srwilkers take it away15:31
rwellumportdirect: can you take a look (or recomend another experienced user) at the 'what to do when something goes wrong' section, with a strong OSH bias please?15:32
srwilkersso this is something we talked about quite some time ago, when i first introduced curator to the elasticsearch chart15:32
*** nguyenhai_ has quit IRC15:32
srwilkersoriginally there was a PVC in the chart that relied on a readwritemany provisioner, that could be used to create filesystem snapshot repositories for elasticsearch15:32
*** slaweq_ has quit IRC15:33
srwilkersi think we all agreed it wasnt the best mechanism for providing this functionality, and wanted to use the s3 api for radosgw instead, since elasticsearch includes s3 snapshot repository functionality15:33
srwilkershttps://review.openstack.org/55941715:33
srwilkersthere's a few things im working on adding to bring this to the finish line, but i've got it to a point that it's functional15:34
srwilkersim hoping to get the loose ends tied up before the end of the week15:34
mattmceuenthat's awesome15:35
* portdirect is back15:35
srwilkersthe last bit im working on adding is the ability to create an arbitrary number of snapshot repositories, which can be useful for when curator needs to manage multiple indexes15:35
mattmceuenOnce we have the Swift chart in, that will be a secondary s3 mechanism for backups15:35
mattmceuen*snapshots15:35
portdirectdoes swift support s3?15:35
srwilkersso we can have a repository for standard log snapshots, a repository for things we may want to keep for extended periods of time, or whatever else your heart desires15:36
mattmceuenI haven't tried it, but read that it does15:36
srwilkersanyway, that's all ive got here.  can expect some updated docs highlighting the current state of the lma union along with this when its ready15:37
mattmceuenmy heart desires lots of logs15:37
mattmceuenExcellent - thanks for the update srwilkers15:37
mattmceuenportdirect:  you're up15:37
rwellumI think you mean 'your heart will go on'..15:37
mattmceuen#topic Helm-Toolkit (portdirect)15:37
*** openstack changes topic to "Helm-Toolkit (portdirect) (Meeting topic: openstack-helm)"15:37
mattmceuendon't make me start singing rwellum, I'll do it15:38
* srwilkers grabs the pennywhistle15:38
* rwellum covers ears15:38
* jayahn think he needs to do something as well15:39
mattmceuenWe will come back to portdirect again :)15:40
mattmceuen#topic Production vs Bare Bones values.yaml15:40
*** openstack changes topic to "Production vs Bare Bones values.yaml (Meeting topic: openstack-helm)"15:40
mattmceuenalanmeadows!15:40
jayahndon't understand exactly what it means15:41
alanmeadowssorry dragged into a call15:41
mattmceuenwant to hold off on this topic?15:41
alanmeadowssure, its been discussed before but I want to bring it to a wider audience15:41
alanmeadowswe can revisit next chat15:42
mattmceuenok - we will table for now.  jayahn a teaser of the topic (bullet points) is in the agenda15:42
mattmceuensrwilkers:15:42
mattmceuen#topic OpenStack Exporter15:42
*** openstack changes topic to "OpenStack Exporter (Meeting topic: openstack-helm)"15:42
srwilkerswell, this one couldve used some input from alanmeadows and portdirect but i'll throw it out regardless.  it was pretty clear to me in vancouver that there's a real need for a solution for monitoring an openstack control plane via prometheus15:43
srwilkersmonasca even goes as far as to mimic prometheus's functionality by providing mechanisms for scraping exporter endpoints15:44
portdirectand AT&T has a nice one in att-comdev?15:44
srwilkersbingo bango15:44
portdirectso - lets move it into -infra15:44
srwilkersportdirect: i think that's a great idea15:44
mattmceuen+115:44
portdirectsrwilkers: its only great as it was yours15:45
portdirecti just stole your punchline15:45
srwilkersportdirect: youre making me blush15:45
mattmceuensrwilkers can you please collaborate w/ the author to get it into OS infra?15:45
srwilkersmattmceuen: sure can15:46
mattmceuengreat15:46
mattmceuenalright we have portdirect --15:46
mattmceuen#topic Moving of charts to their correct locations15:46
*** openstack changes topic to "Moving of charts to their correct locations (Meeting topic: openstack-helm)"15:46
portdirectso - we really need to get the charts in the right place15:47
portdirectit would be nice to use this an a 1st try at storybarding things?15:48
*** wxy| has quit IRC15:48
portdirectand also for newer devs to get used to the gates etc?15:48
*** wxy| has joined #openstack-meeting-515:49
mattmceuenAgree.  The work is mentioned in the 1.0 spec and should be a good way to get involved15:49
mattmceuenin the code proper15:49
portdirectit would be fairly simple for me to do a mega ps that moved them all - but think this would be a great opportinity to get some more people working on the gates :D15:49
portdirectrwellum: could you help me with the storyboard side of things15:49
portdirectI'll have a stab at it, but expect I'll need some help15:50
rwellumSure portdirect15:50
portdirectthen once we have that people could grab to story for each chart?15:50
mattmceuenYeah - let's create per-chart stories for this that account for gating, and then divide & conquer15:50
mattmceuen+115:50
portdirectnice15:50
pcarverportdirect: storybarding sounds like a nice variation. Matt can sing along with the stories.15:51
mattmceuenThey will be ballads15:51
portdirectits the typo that keeps on giving15:51
mattmceuenwe are a heroic team are we not15:51
portdirectmy ambition is for us to become the plumbers of openstack15:51
mattmceuenWe have 9mins and three items on agenda to go -- portdirect want to tackle helm-tk?15:52
portdirectok15:52
mattmceuen#Topic Helm Toolkit15:52
*** openstack changes topic to "Helm Toolkit (Meeting topic: openstack-helm)"15:52
portdirectso I'm gonna try and get most of the functions in helm toolkit using maps(dicts) as inputs15:52
portdirectrather than the tuples we have today15:52
portdirectas this will help with a couple of things:15:53
portdirect1) documentation15:53
portdirect2) allowing greater flexibilitiy15:53
portdirect3) wait for it15:53
portdirect... proper unit tests15:53
portdirectso - as we do this i think its essential we start unit testing the helm-toolkit lib15:54
mattmceuenThat would be a much nicer interface to htk and also UNIT TESTS!  Are you thinking we should refactoring the dependent chart code as we go, or adapt the old interface htk interface around the new?15:54
rwellumfor item in dict.iteritems(): .....15:54
portdirectrefactor as we go15:54
portdirectas we now have the gates for it :D15:54
rwellumThere did it for you portdirect ;) jk obviously.15:54
portdirectI'll also work on airship and and other projects (ceph/tungsten fabric) to help them with the shift15:55
portdirectbut overall this will put us in a much stronger place15:55
srwilkers+115:55
portdirectthats all i got there15:55
mattmceuenAwesome.   Let's look for ways to spread this work out as well, since there will be a lot of it, and with some proper examples it shouldn't be too bad15:56
mattmceuen#topic     multi-node deployer feedback15:56
*** openstack changes topic to "multi-node deployer feedback (Meeting topic: openstack-helm)"15:56
mattmceuen#rwellum go for it!15:56
rwellumAt the summit I spoke to 2 people about OSH, who like me, they had all successfully deployed a single OSH node, but got stuck with multiple-nodes. They were following the guide - but with some confusion over the fact - is it a guide or is it a bunch of gate script(s). I recall this was a somewhat fatal error we made in kolla-k8s - whenever someone claimed is didn't work we'd point to a green Gate run and say 'it15:56
rwellummust be your fault'. Problem was the gate scripts were so utterly tweaked for that specific environment it wasn't always obvious how to apply it to your own. So my question is: should this work in other environments to the gate environment? And has someone experienced tried running through this from scratch lately? (And hopefully - the debugging guide will help too.)15:56
rwellumHopefully answer a lot shorter than my qn.15:57
*** yamamoto has joined #openstack-meeting-515:58
mattmceuenrwellum can we chew on this one a bit and discuss next week?15:58
rwellumFor sure...15:58
srwilkersor we can take it to the channel after the meeting too15:58
mattmceuenI think the answer is probably in the middle.  And I also want to go thru the install guide fresh with the latest myself.15:59
mattmceuenIt's been a couple months15:59
mattmceuen#topic Vitrage Chart15:59
*** openstack changes topic to "Vitrage Chart (Meeting topic: openstack-helm)"15:59
mattmceuen1 min left :)15:59
rwellumI know we're tight on time...15:59
mattmceuenprobably can't do this justice but trying...15:59
rwellumBasically my Mothership did Vitrage and it would be a good way of getting some developers into OSH by producign the chart.16:00
rwellumWas going to have a crack at it16:00
mattmceuenThat will be really awesome.16:00
portdirectnice16:00
rwellumSo it's a good candidate then?16:00
srwilkersrwellum: thats awesome. we'd be happy to provide any feedback along the way16:00
rwellumCool beans then16:00
portdirectrwellum: if a dev wants to work on it16:00
mattmceuenEagerly looking fw to helping with reviews on that - let us know if there is anything we can help with getting that going16:00
portdirectits a good candidate :D16:00
mattmceuenalright we're over time, great meeting all!16:01
mattmceuen#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
openstackMeeting ended Tue Jun  5 16:01:13 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-06-05-15.00.log.html16:01
*** gmmaha has left #openstack-meeting-516:01
*** yamamoto has quit IRC16:03
*** gagehugo has left #openstack-meeting-516:03
*** slaweq_ has joined #openstack-meeting-516:05
*** slaweq has quit IRC16:09
*** slaweq_ is now known as slaweq16:09
*** tdoc has left #openstack-meeting-516:09
*** sshank has joined #openstack-meeting-516:44
*** yamamoto has joined #openstack-meeting-516:50
*** yamamoto has quit IRC17:00
*** slaweq has quit IRC17:04
*** slaweq has joined #openstack-meeting-517:04
*** radeks has joined #openstack-meeting-517:04
*** wxy| has quit IRC17:11
*** sshank has quit IRC17:13
*** radeks has quit IRC17:15
*** spiette has quit IRC17:17
*** sshank has joined #openstack-meeting-517:19
*** spiette has joined #openstack-meeting-517:27
*** yamahata has joined #openstack-meeting-517:27
*** jamesgu has joined #openstack-meeting-517:42
*** jgu_ has quit IRC17:44
*** yamamoto has joined #openstack-meeting-517:56
*** yamamoto has quit IRC18:02
*** radeks has joined #openstack-meeting-518:38
*** sshank has quit IRC18:55
*** yamamoto has joined #openstack-meeting-518:58
*** yamamoto has quit IRC19:03
*** radeks has quit IRC19:11
*** radeks has joined #openstack-meeting-519:19
*** radeks has quit IRC19:25
*** mjturek has quit IRC19:38
*** yamamoto has joined #openstack-meeting-519:59
*** yamamoto has quit IRC20:05
*** joe_w has joined #openstack-meeting-520:44
*** mjturek has joined #openstack-meeting-520:48
*** yamamoto has joined #openstack-meeting-521:01
*** yamamoto has quit IRC21:05
*** slaweq has quit IRC21:10
*** yamamoto has joined #openstack-meeting-522:02
*** yamamoto has quit IRC22:06
*** mjturek has quit IRC22:55
*** yamamoto has joined #openstack-meeting-523:03
*** yamamoto has quit IRC23:07
*** hongbin has quit IRC23:27
*** jamesgu has quit IRC23:45
*** ricolin has joined #openstack-meeting-523:52

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