Tuesday, 2017-12-05

*** yamamoto has quit IRC00:36
*** yamamoto has joined #openstack-meeting-500:38
*** yamamoto has quit IRC00:44
*** felipemonteiro has quit IRC00:51
*** yamamoto has joined #openstack-meeting-501:41
*** yamamoto has quit IRC01:46
*** felipemonteiro has joined #openstack-meeting-501:58
*** felipemonteiro_ has joined #openstack-meeting-502:17
*** felipemonteiro has quit IRC02:20
*** felipemonteiro_ has quit IRC02:20
*** felipemonteiro_ has joined #openstack-meeting-502:21
*** kei-ichi has quit IRC02:25
*** felipemonteiro_ has quit IRC02:25
*** kei-ichi has joined #openstack-meeting-502:26
*** kei-ichi has quit IRC03:00
*** kei-ichi has joined #openstack-meeting-503:01
*** lukepatrick has quit IRC03:14
*** lukepatrick has joined #openstack-meeting-503:18
*** kei-ichi has quit IRC03:23
*** kei-ichi has joined #openstack-meeting-503:23
*** yamamoto has joined #openstack-meeting-503:49
*** ricolin has joined #openstack-meeting-504:12
*** kei-ichi has quit IRC04:18
*** kei-ichi has joined #openstack-meeting-504:18
*** lukepatrick has quit IRC04:27
*** lukepatrick has joined #openstack-meeting-504:35
*** lukepatrick has quit IRC05:35
*** kei-ichi has quit IRC08:30
*** kei-ichi has joined #openstack-meeting-508:30
*** makowals has quit IRC09:25
*** makowals has joined #openstack-meeting-509:25
*** derekh has joined #openstack-meeting-509:39
*** makowals_ has joined #openstack-meeting-509:57
*** makowals has quit IRC09:58
*** makowals_ has quit IRC11:01
*** yamamoto has quit IRC11:28
*** yamamoto has joined #openstack-meeting-512:28
*** yamamoto has quit IRC12:31
*** yamamoto has joined #openstack-meeting-512:31
*** yamamoto has quit IRC12:38
*** yamamoto has joined #openstack-meeting-512:40
*** ricolin_ has joined #openstack-meeting-512:50
*** ricolin has quit IRC12:53
*** ricolin has joined #openstack-meeting-513:18
*** ricolin_ has quit IRC13:20
*** makowals has joined #openstack-meeting-513:26
*** annp has joined #openstack-meeting-513:45
*** ricolin_ has joined #openstack-meeting-513:46
*** yamamoto has quit IRC13:47
*** ricolin has quit IRC13:48
*** yamamoto has joined #openstack-meeting-514:11
*** ricolin_ has quit IRC14:17
*** ricolin has joined #openstack-meeting-514:17
*** kiennt26 has joined #openstack-meeting-514:49
*** MarkBaker has joined #openstack-meeting-514:56
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Dec  5 15:00:24 2017 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
mattmceuenGM all!15:00
mattmceuenAgenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2017-12-0515:00
*** annp has quit IRC15:00
srwilkerso/15:01
alanmeadowso/15:02
portdirecto/15:02
*** gagehugo has joined #openstack-meeting-515:02
mattmceuenGiving another min or so for agenda edits to complete15:03
MarkBakero/15:03
icolwello/15:03
srwilkersa wild alanmeadows appears15:03
alanmeadowsstraight from the bush15:03
mattmceuendon't spook him!15:04
portdirectI'm in transit, so may be less verbose than usual. (You can all sigh with relief now)15:04
* srwilkers uses flash -- it's not very effective15:04
mattmceuen#topic When to use a spec in OSH15:04
*** openstack changes topic to "When to use a spec in OSH (Meeting topic: openstack-helm)"15:04
mattmceuenOk -- I thought it would be a good time to refresh our local practice of spec authoring15:04
mattmceuenBoth as FYI to new team members, as well as a refresher for the rest of us :)15:04
mattmceuenAt this point in the OSH lifetime, we don't expect specs for every code change15:05
mattmceuenWhen we do expect specs are:15:05
v1k0d3no/15:05
mattmceuen1. when a change impacts multiple charts15:05
mattmceuen2. when a change needs design feedback from the larger team prior to implementation15:06
mattmceuen3. when a change does something substantially new that'll be modeled in other charts later15:06
mattmceuenThe gist being:  write specs as a means to drive common understanding (think: useful documentation) and common direction (think: everyone's aligned)15:07
mattmceuenthoughts/questions?15:07
v1k0d3nsounds good to me.15:07
v1k0d3ngood recap15:07
portdirectSounds good mattmceuen15:07
mattmceuencool beans.  thanks guys I'll get off the process soapbox.15:08
mattmceuenNext:15:08
mattmceuen#topic Carryover CICD topics from last week15:08
*** openstack changes topic to "Carryover CICD topics from last week (Meeting topic: openstack-helm)"15:08
mattmceuenGreat focus-meeting on CICD last week -- we couldn't fit everything in :)  good problem to have.15:08
mattmceuenportdirect:  want to speak to helm test and friends?15:09
v1k0d3nwas really sad to miss last week, but couldn't make it. was there some docs/notes (i'm assuming the same etherpad format)?15:09
mattmceuenYep!  notes and transcript: http://eavesdrop.openstack.org/meetings/openstack_helm/2017/15:09
v1k0d3nawesome. thanks mattmceuen15:10
portdirectSo I'm thinking we need a spec for what we have in helm test15:10
mattmceuenSounds pretty cross-chart to me.  What do you want to get out of said spec?15:11
portdirectAs currently we have been pretty good with what I hope we decide as the core rationale for what we want from this functionality but as more contributors come in we should formalize a bit.15:11
portdirectSo from my perspective we should be able to run 'helm test' at any point in a charts life, without lasting impact on the environment15:12
portdirectThis means that by definition the tests should be non impacting, or destructive15:12
v1k0d3n++15:12
mattmceuenagree.15:13
portdirectThough we are limited by what helm currently provides us with15:13
v1k0d3nare they impacting or destructive currently? we've just recently started testing with custom rally yaml.15:13
portdirectI'd like to export developing a pattern for running a test on each node in the cluster15:14
portdirectv1k0d3n: no, but this is not formalised at present15:14
v1k0d3nok. sounds good.15:14
mattmceuenCan we document the pattern for testing openstack vs. non-openstack charts in that spec as well?15:15
portdirectIs there also appetite for adding a 'really hammer this thing' flag? That would enable destructive testing?15:15
portdirectmattmceuen: yes def the pattern we write up in the spec should be application agnostic15:16
srwilkersportdirect: yep.  `helm test` is generally meant as a smoke test for verifying a chart just deploys something functional.  i've been toying around with the idea of having a chart for running helm tests against specific chart groups in openstack-helm-infra.  dont know if that makes sense the way i worded it, but without something like rally for services outside of openstack, it's been difficult verifying15:16
srwilkerseverythings working the way it should15:16
srwilkersas using `helm test` the way i have been with those charts, it's really introducing dependencies on the other services when it really shouldnt if we're treating each chart as its own entity15:17
srwilkersportdirect: i've got an appetite for such a flag15:18
portdirectThis needs to be encapsulated in the spec for sure, I'm assuming that you are r3fering to things like the mysql exporter?15:18
mattmceuenthat speaks more to my thought portdirect -- I agree the spec should be agnostic, but am thinking of advice like "if you're testing an OS service, you can use rally; otherwise, here are some guidelines"15:18
srwilkersreferring to fluentd/elasticsearch/prometheus and friends15:18
portdirectsrwilkers: yeah, and here I think we need to specify a 'minimum' set of infra that we have running, so we don't end up with a ceilometer type situation15:19
srwilkers++15:19
portdirectWhere tests were passing but nothing useful was being collected....15:20
srwilkersyep15:20
mattmceuenportdirect:  are you looking for a volunteer for the spec, or are you volunteering for it?15:20
srwilkerssounds like he's volunteering, and i'd be happy to throw some input on it as well15:20
portdirectI'm volunteering to do it, unless there is someone who really wants it.15:20
mattmceuenSounds good - thanks portdirect.  Excellent idea.15:21
srwilkersi dont really want it, but willing to contribute/do it if there's nobody else15:21
mattmceuen#action portdirect to work on a spec formalizing our `helm test` approach15:21
mattmceuennext:  do we have lamt in the house?15:21
mattmceuenWe'll table his item till next time.15:22
mattmceuen#topic  LMA updates15:22
*** openstack changes topic to "LMA updates (Meeting topic: openstack-helm)"15:22
mattmceuenswilkers what's goin on!15:22
srwilkersONAP and coffee mostly :)15:23
srwilkersbut15:23
*** lrensing has joined #openstack-meeting-515:23
srwilkerswe got prometheus merged in (finally).  osh-infra currently has charts for:  prometheus, kube-state-metrics, node-exporter, and alertmanager15:23
mattmceuenWOOO15:23
srwilkersthis gives us a solid base for monitoring the underlying infrastructure, along with rbac rules that match those in the kubernetes/charts/stable repo15:24
srwilkersalong with that (tied in to the previous topic), we now have support for executing helm tests on charts in osh-infra15:24
portdirectCan we get these exporting logs in the gate as a priority, or did I miss that getting added?15:24
srwilkersand prometheus currently passes some basic smoke tests, so huzzah15:24
jayahnhi15:25
srwilkersportdirect: that'll be fluent-loggings job15:25
srwilkersim currently adding support for doing that as we speak15:25
srwilkersexpect a patchset in the next hour or so15:25
srwilkersthe idea is that we can use a deployed fluentbit instance to export logs from the pods running in the osh-infra gates15:25
srwilkersand we can also use prometheus to export the metrics gathered during the gate run to give an idea of the services' performance in the gate jobs15:26
srwilkersthat will also be added today15:26
portdirectNice, we really need that and the supporting docs for how to use/ingest them asap15:27
srwilkersalso big shoutout to jayahn and sungil for the work they did on fluent-logging15:27
srwilkersportdirect: yep15:27
srwilkersjust took a few tweaks to get it to the finish line, but im really happy with how its working right now15:27
jayahnwe found out that version matching between fluent-bit and fluentd is somewhat sensitive.15:27
srwilkersjayahn: yeah, ive noticed the same15:28
jayahnif we want more simple stuff, we can only run fluent-bit.15:28
jayahnwe have a plan to add that "selection" possible through fluent-logging chart.15:28
srwilkersonce the log and metrics exporting is done in the osh-infra gates, the next step is to get the prometheus chart running prometheus 2.015:28
srwilkersprometheus 2.0 makes me happy.  the rework to the underlying storage layer is really solid, and the overall resource consumption has been reduced significantly15:29
portdirectW00t15:29
portdirectAny loss of features that hit us, e.g. openstack exporter?15:30
portdirectOr they all sweet?15:30
srwilkersnope, they're all sweet15:30
portdirectNice15:30
mattmceuenlove backwards compatibility.15:30
jayahnnice!15:30
srwilkersim chatting with some of the prometheans wednesday here at kubecon, and going to ask them about the maturity of the openstack service discovery mechanisms they're adding to prometheus15:31
srwilkersas that will actually reduce the necessity of some of the openstack-exporter's responsibility15:31
srwilkersanyway, thats it for me15:32
mattmceuenawesome - thanks srwilkers15:32
mattmceuen#topic Review Needed15:32
*** openstack changes topic to "Review Needed (Meeting topic: openstack-helm)"15:32
* jayahn portdirect really being less verbose? 15:32
jayahnneed to rebase, i guess. but again for adding lbaas to neutron15:33
* srwilkers thinks portdirect needs a built-in -vvv flag15:33
mattmceuen    add lbaas to nuetron: https://review.openstack.org/#/c/522162/15:33
jayahnbut it requires kolla neutron version 4.0.0 since 3.x does not have that15:33
* portdirect fingers on fire, this phone is being worked..15:33
jayahnwill it be any problem for the current upstream?15:34
portdirectjayahn: for current upstream yes15:34
portdirectBut we could turn it off by default, which I think would be ok?15:34
jayahnsure15:34
portdirectWhat is the status of lbaas in neutron currently?15:35
mattmceuenAny other PS we need some extra eyes on, all?15:35
jayahnnot sure. we only used lbaas in neutron, not octavia15:35
portdirectIs it being supported moving forward? Or is everyone all in on ocavia?15:35
jayahnour use case is integrating with vendor appliance, such as a10, f5, etc15:36
portdirectmattmceuen: I'd love some feedback on the dev guide I've been working on15:36
jayahnso does not really need octativa15:36
portdirectjayahn: roger, that kinda fits with what I'd seen, in that vendors are still using it15:37
jayahnyeah. they have lbaas v2 support as long as I know.15:37
mattmceuenupdated dev guide: https://review.openstack.org/#/c/523173/15:37
jayahni only sereiously did integration work with a10 though.15:38
mattmceuen#topic things to share15:39
*** openstack changes topic to "things to share (Meeting topic: openstack-helm)"15:39
mattmceuenHey jayahn you had an item here, go for it15:39
jayahnhttps://github.com/sktelecom-oslab/taco-scripts  >> skt's version of osh aio installation15:39
portdirectNice15:40
mattmceuenoh awesome15:40
jayahnfully inspired by portdirect's scripts on sydney15:40
portdirectIt would be great to see if we could get elements of this merged into the dev docs ps above15:40
mattmceuenwill give that a spin, jayahn!15:40
jayahnthanks. :) btw, this is ocata. :)15:41
portdirectHaving examples of deploying with kubespray and co is awesome15:41
* srwilkers has a sudden urge to find tacos15:41
* mattmceuen I know right15:41
* jayahn luck you srwilkers. you are in austin15:42
mattmceuenJay, you keep the floor:15:42
mattmceuen#topic destructive testing tool comparison15:42
*** openstack changes topic to "destructive testing tool comparison (Meeting topic: openstack-helm)"15:42
* portdirect is about to leave new Orleans:D15:42
jayahnas requested, we did a quick comparison15:42
* mattmceuen full disclosure: I just got distracted and will have to catch up on these deets from the chat logs15:42
jayahncookiemonster has more flexibility comparng to other tools. can define more types to kill, have REST API call to start and stop15:43
jayahnbut, all of three are doing similar things.15:44
jayahnwe will add more documentations and use cases.15:44
jayahnhappy to get any questions on how we use this cookiemonster in our ci, and for some demo15:45
mattmceuenAlso - there are some good details jayahn added as comparision in the agenda (bottom): https://etherpad.openstack.org/p/openstack-helm-meeting-2017-12-0515:45
jayahnthat is all from me15:46
mattmceuenany questions on the comparison at this point?15:46
mattmceuenThanks jayahn - :)  eeiden is out at the OPNFV conference digging to get their thoughts on destructive testing too15:47
portdirectCan we drive it from so.thong other than the api?15:47
portdirectLol something15:47
jayahnso.thong.. it exactly sounded like bull poo. (in korean word)15:48
*** StaceyF has joined #openstack-meeting-515:48
v1k0d3nlol15:48
jayahnportdirect: could you explain a bit more?15:49
jayahnsomething like?15:49
portdirectA configmap/file15:49
jayahnnot at the current version. but open to any feature suggestion15:50
portdirectHaving an extra endpoint to manage, (auth etc) always makes me sad15:50
portdirectBut for dev this is great15:50
jayahni will note your question, and will talk to my developer15:51
mattmceuenThanks guys.15:52
jayahnportdirect: could you tell me more about "It would be great to see if we could get elements of this merged into the dev docs ps above"15:52
jayahnyour comments on installation scripts.15:52
jayahnwe can add "how to" guide with tools we are using. but need to know what you exactly want to have.15:53
jayahnping me anytime. I will happy to listen and follow. :)15:54
mattmceuenT-minus five15:55
mattmceuen#topic roundtable15:55
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:55
mattmceuenAny other topics for today?15:55
v1k0d3nlooking forward to seeing any folks who are doming to kubecon :)15:56
mattmceuensame!15:56
mattmceuenAlrighty -- thanks guys, see you in the chat room15:56
mattmceuen#endmeeting15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:56
openstackMeeting ended Tue Dec  5 15:56:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-12-05-15.00.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-12-05-15.00.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-12-05-15.00.log.html15:56
*** lrensing_ has joined #openstack-meeting-515:58
*** lrensing_ has quit IRC15:59
*** lrensing has quit IRC16:00
*** gagehugo has left #openstack-meeting-516:00
*** roman_g has joined #openstack-meeting-516:04
*** kiennt26 has quit IRC16:27
*** lukepatrick has joined #openstack-meeting-516:39
*** gmmaha has joined #openstack-meeting-516:41
*** ricolin has quit IRC16:49
*** ricolin has joined #openstack-meeting-516:53
*** gmmaha has left #openstack-meeting-517:02
*** derekh has quit IRC17:03
*** makowals has quit IRC18:11
*** makowals has joined #openstack-meeting-518:12
*** makowals has quit IRC18:12
*** makowals has joined #openstack-meeting-518:12
*** makowals has quit IRC18:13
*** makowals has joined #openstack-meeting-518:13
*** makowals has quit IRC18:13
*** makowals has joined #openstack-meeting-518:14
*** makowals has quit IRC18:14
*** makowals has joined #openstack-meeting-518:15
*** makowals has quit IRC18:15
*** ricolin has quit IRC18:40
*** roman_g has quit IRC19:00
*** yamamoto has quit IRC19:27
*** lukepatrick has quit IRC19:33
*** lukepatrick has joined #openstack-meeting-519:51
*** jrist has quit IRC20:05
*** StaceyF has quit IRC20:21
*** yamamoto has joined #openstack-meeting-520:28
*** yamamoto has quit IRC20:35
*** roman_g has joined #openstack-meeting-520:39
*** jrist has joined #openstack-meeting-521:46
*** lrensing has joined #openstack-meeting-521:50
*** sshank has joined #openstack-meeting-521:54
*** makowals has joined #openstack-meeting-522:17
*** yamahata has joined #openstack-meeting-522:19
*** MarkBaker has quit IRC22:29
*** MarkBaker has joined #openstack-meeting-522:31
*** MarkBaker has quit IRC22:31
*** makowals has quit IRC22:40
*** sshank has quit IRC22:44
*** yamahata has quit IRC22:49
*** sshank has joined #openstack-meeting-522:59
*** roman_g has quit IRC23:01
*** roman_g has joined #openstack-meeting-523:02
*** roman_g has quit IRC23:02
*** yamahata has joined #openstack-meeting-523:04
*** yamahata has quit IRC23:13
*** lrensing has quit IRC23:16
*** lrensing has joined #openstack-meeting-523:40
*** yamahata has joined #openstack-meeting-523:43
*** lukepatrick has quit IRC23:47
*** sshank has quit IRC23:51
*** sshank has joined #openstack-meeting-523:53

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