Tuesday, 2017-11-14

*** sshank has quit IRC00:24
*** TuanLA has joined #openstack-meeting-500:59
*** ricolin_ has joined #openstack-meeting-501:15
*** iyamahat_ has quit IRC02:30
*** yamahata has quit IRC02:30
*** yamamoto has joined #openstack-meeting-503:52
*** kei-ichi has quit IRC03:53
*** kei-ichi has joined #openstack-meeting-503:53
*** TuanLA has quit IRC04:43
*** TuanLA has joined #openstack-meeting-504:44
*** TuanLA has quit IRC04:47
*** yamahata has joined #openstack-meeting-505:31
*** 3NAABTTL6 has quit IRC05:32
*** benj_ has joined #openstack-meeting-505:33
*** makowals has joined #openstack-meeting-507:29
*** ralonsoh has joined #openstack-meeting-508:09
*** yamamoto has quit IRC08:09
*** yamamoto has joined #openstack-meeting-508:12
*** yamamoto has quit IRC08:12
*** kei-ichi has quit IRC08:14
*** kei-ichi has joined #openstack-meeting-508:15
*** iyamahat has joined #openstack-meeting-508:40
*** yamamoto has joined #openstack-meeting-508:41
*** yamahata has quit IRC08:44
*** yamamoto has quit IRC08:50
*** iyamahat has quit IRC08:51
*** haint has joined #openstack-meeting-508:59
*** nguyentrihai has quit IRC09:01
*** markvoelker has quit IRC09:21
*** derekh has joined #openstack-meeting-509:39
*** zaneb has quit IRC09:54
*** yamamoto has joined #openstack-meeting-510:01
*** makowals has quit IRC10:01
*** makowals has joined #openstack-meeting-510:03
*** felipemonteiro has joined #openstack-meeting-510:16
*** markvoelker has joined #openstack-meeting-510:21
*** yamamoto has quit IRC10:36
*** yamamoto has joined #openstack-meeting-510:36
*** xek_ is now known as xek11:00
*** felipemonteiro has quit IRC11:38
*** ralonsoh has quit IRC13:32
*** ralonsoh has joined #openstack-meeting-514:24
*** markvoelker has quit IRC14:43
*** markvoelker has joined #openstack-meeting-514:43
*** yamahata has joined #openstack-meeting-514:53
*** iyamahat has joined #openstack-meeting-514:55
*** zaneb has joined #openstack-meeting-514:58
*** mateuszb has joined #openstack-meeting-514:59
*** korzen_ has joined #openstack-meeting-514:59
srwilkers#startmeeting openstack-helm15:00
openstackMeeting started Tue Nov 14 15:00:49 2017 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:01
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:01
korzen_hello15:01
srwilkerso/15:01
jayahno/15:01
mateuszbo/15:02
srwilkershere's the agenda:  https://etherpad.openstack.org/p/openstack-helm-meeting-2017-11-1415:02
srwilkerswe'll give it a few minutes to see if anyone else comes along or wants to add to it15:02
*** Quack has joined #openstack-meeting-515:02
v1k0d3nhey all! o/\o15:03
srwilkershey v1k0d3n \o/15:03
v1k0d3no/*\o15:03
srwilkersalright, seems we've got a good list to start with15:04
srwilkers#topic: graph drawing in documentation15:05
*** openstack changes topic to ": graph drawing in documentation (Meeting topic: openstack-helm)"15:05
srwilkersall you jayahn15:05
*** seungkyua has joined #openstack-meeting-515:05
jayahnI just wanted to have a graph drawing capability in doc. :)15:05
jayahni did my best to copy the example configuration.15:05
srwilkersi agree -- pictures are a great way to share things15:06
jayahnnot sure if i did all the necessary stuff to setup "sphinxcontrib-blockdig". if anyone can give more feedback. please. :)15:06
srwilkersadmittedly i dont know enough about getting it enabled to tell if that's the right way or not15:06
srwilkerslamt is really good at that sort of stuff15:07
lamto/15:07
jayahnah. lamt is here. :)15:07
jayahnhttps://review.openstack.org/#/c/519653/15:07
*** iyamahat has quit IRC15:08
jayahnpls leave any feedback on ps. :)15:08
srwilkersill poke lamt and make sure he gives some feedback there15:08
srwilkersanything else on this jayahn?15:08
jayahnnope15:08
srwilkerssweet15:09
srwilkers#topic fluent-logging15:09
*** openstack changes topic to "fluent-logging (Meeting topic: openstack-helm)"15:09
srwilkersi like this one -- take it away jayahn15:09
jayahnwe are almost done with putting flunt-based logging.15:09
jayahnthis is be the first one, it will be followed by next steps.15:10
jayahnhowever, is openstack-helm-infra gate is working properly?15:10
srwilkersyeah, it's working -- i can work with you and provide feedback to do what we need to run it properly15:10
jayahnokay. that would be great.15:11
srwilkersonce things are tidied up, ill make sure everythings documented appropriately so adding new services is easy15:11
jayahncan you do through review? or will it be better to setup  a serate time?15:11
srwilkersid be happy to do it through review15:11
srwilkersif that's okay15:11
jayahnokay. great!15:11
srwilkersalso, wanted to get everyones and yours thoughts on something with the fluent-logging stuff15:12
jayahnfyi, we have checked new version of fluent-bit support kubernetes plugin and some experimental kafka output. that will be our very next thing to do after this is merged.15:12
jayahnokay. srwilkers shoot it. :)15:13
srwilkerswould it be worth considering handling the parsers and fluentbit configurations via values.yaml?  reason i ask is because while it works out of the box, its very opinionated in that it's expecting you'll only ever use the json logging driver for docker15:13
srwilkersie, it only gets log events via tailing /var/log/whatever and /var/lib/docker/containers/whatever15:14
srwilkersit's not something i want us to spin the wheels on with the current patchset, because some of your work and mateuszb's work really depends on the fluent-logging stuff being finished15:14
srwilkersbut might be worth considering as an enhancement down the road15:14
jayahnokay. we will surely consider your idea into our enhancement task.15:15
jayahni will talk to sungil about this.15:15
srwilkersawesome :) i can draw up some pictures and throw some roughed up ideas your way too if that helps15:15
seungkyuaright all docker container logs are json type. We need to change that.15:16
seungkyuaand kubernetes logs in /var/log/xxx15:16
srwilkersbut really jayahn -- it's great work. :)15:16
jayahnas you said, the current ps will be just the first of all the waves coming after. let's make this base thing work, then continuosly enhance it15:16
srwilkersi agree15:16
srwilkersthats all i had15:17
jayahnseungkyua is our senior developer. he agrees with you, srwilkers.15:17
jayahn:)15:17
srwilkersnice -- pleasure to meet you seungkyua o/15:17
seungkyuanice to meet you.15:18
jayahnif he says yes.. it means yes for us :)15:18
srwilkers#topic default alert list spec15:18
*** openstack changes topic to "default alert list spec (Meeting topic: openstack-helm)"15:18
srwilkersawesome :)15:18
seungkyuathis is the first time online chat. :)15:18
jayahnah. this is very very early draft.15:18
jayahnjust want to get everyone's opinion on "what is the best way to write it".15:19
mateuszbI'll take a look at it tomorrow jayahn :)15:19
jayahnI think we first define "alert/alarm definition" things like we would like to alert on cpu idle, cpu percent, etc.15:20
jayahnbut not defining actual trigger threshold in this spec.15:20
srwilkersyeah, i was going to say your input would be awesome mateuszb since this touches what you've been working against15:20
v1k0d3njayahn: wrt to the fluent work, i can take a look at it too...we've been doing a lot of this recently too for some internal demos. would be nice to get this into upstream.15:20
srwilkersjayahn: yeah i agree15:20
srwilkersv1k0d3n: thatd be awesome :)15:20
jayahnv1k0d3n, awesome :)15:20
jayahnthanks mateuszb. i will add more alert definition in this week. your feedback would be really helpful15:21
*** zaneb has quit IRC15:21
srwilkersanything else on this one?15:22
jayahni think korzen_ only has the firs half of meeting time. let's turn it to him now. :)15:22
srwilkerssounds good15:23
korzen_yes15:23
srwilkers#topic multi namespace support for entrypoint15:23
*** openstack changes topic to "multi namespace support for entrypoint (Meeting topic: openstack-helm)"15:23
korzen_so I would like to highlight that multiple namespace support is done in the PS15:23
srwilkersi just workflowed it :)15:23
korzen_#link https://review.openstack.org/#/c/510810 Support services in different namespaces15:23
korzen_#link https://review.openstack.org/#/c/511515/  Add jobs and daemonsets namespace support15:24
korzen_after it being merged, the full solution is enabled15:24
korzen_so we can add cross namespace dependencies for services via enpoints, and for jobs and daemonsets in dependencies section15:24
korzen_I am testing it in use-case where every service have its own infra15:25
v1k0d3nnice work over there korzen_ ! :) great to see this added.15:25
srwilkersnice korzen_ :)15:25
korzen_like keystone namespace would have its own mariadb, rabbimq ingress etc15:25
korzen_ceph would be common15:25
v1k0d3nyeah that's awesome. always been the goal...15:26
korzen_thx ;)15:26
v1k0d3nyou guys made it reality. :)15:26
korzen_glad to see that it is appreciated ;)15:26
korzen_I guess that multiple namespace it is all15:27
korzen_for RBAC15:27
srwilkers#topic RBAC support15:27
*** openstack changes topic to "RBAC support (Meeting topic: openstack-helm)"15:27
korzen_#link https://review.openstack.org/#/c/464630  RBAC authorization support15:28
korzen_this one i huge but it contains all RBAC rules that are needed to be run15:28
korzen_I wanted to get portdirect review on that one15:28
korzen_all necessary details are included in agenda15:29
korzen_I would also test in for multiple namespace use-case in following days15:29
korzen_but example with ceph and ceph-config made this PS ready for multiple namespace15:30
jayahnkorzen_ we will try to review this RBAC one as well15:30
srwilkersill get portdirect to look at it today and provide his feedback15:30
korzen_ok, I need to run15:31
korzen_it is all from my side15:31
srwilkerslater korzen_ :)15:31
srwilkers#topic log based alerting approaches15:31
jayahnthanks korzen_15:31
*** openstack changes topic to "log based alerting approaches (Meeting topic: openstack-helm)"15:31
korzen_bye15:31
srwilkerstake it away mateuszb15:31
mateuszbI've got a couple of patchsets in review regarding log-based alarms15:31
mateuszbI've grouped them into 2 categories depending on the approach:15:31
mateuszb1. Based on ElastAlert:15:32
mateuszbElastAlert chart: https://review.openstack.org/#/c/516629/15:32
mateuszbNagios: passive check for DB errors: https://review.openstack.org/#/c/518543/15:32
mateuszbPushing notifications from ElastAlert to Nagios: https://review.openstack.org/#/c/518711/15:32
mateuszband 2. Based on fluent-plugin-prometheus:15:32
mateuszbGathering DB errors count using fluent-plugin-prometheus: https://review.openstack.org/#/c/514938/15:32
mateuszbExample log-based alert in Prometheus: https://review.openstack.org/#/c/515061/15:32
mateuszbNagios: Prometheus check for DB errors in logs: https://review.openstack.org/#/c/519318/15:32
mateuszbSo I've verified that both of the solutions are ready to be integrated with Nagios (I wasn't so sure about ElastAlert+Nagios, but it works well)15:33
jayahnthese are really beautifully categorized examples. :)15:33
mateuszbI'm leaving it as it is until the decision is made which of the two approaches we choose (I'd vote for ElastAlert as it's precisely designed for log-based alerting - with a lot of configuration capabilities in place)15:34
mateuszbSo any comments and votes are welcome :)15:34
*** korzen_ has quit IRC15:36
mateuszbthat's all from me15:36
jayahnElastAlert seems great tool to use. +1 on that.15:37
jayahnhowever, since we are probably use prometheus alert manager for metric-based alert, it would be good to use single solution for all the alert. so +1 on fluent-plugin-prometheus. :)15:37
jayahni will do some discussion with my team members, and will leave our feedback.15:37
mateuszbYou're not helping ;)15:37
mateuszbOk that would be great15:37
jayahnyeap. i know. :(15:37
srwilkersyeah, im a bit torn on this.  i feel like ive introduced some confusion with nagios, as it was meant to be pitched as a deadmans switch for things like backing prometheus with ceph15:37
srwilkersbut elastalert is able to fire off alerts independently right?  it doesnt need nagios or alertmanager?15:38
mateuszbNo, it doesn't need nagios and alertmanager15:38
srwilkersokay, that makes me feel better.15:38
mateuszbIt fires off alerts independently - but there is a possibility to execute a script, which in turns executes the passive chech to Nagios15:39
mateuszbcheck *15:39
srwilkerscool :)15:39
jayahnI would like to compare alert template on both solution, i mean how flexible it is to set some alert patterns.15:40
srwilkersyeah, that's something to consider for sure15:40
srwilkersbut great work all around on this stuff mateuszb15:40
mateuszbWell, I may prepare a list of what's needed to add additional alert in both cases15:41
mateuszbto make things faster, I'll write it on slack tomorrow15:41
srwilkerssounds good :)15:42
mateuszbin order not to wait until the next meeting :)15:42
jayahngreat!15:42
*** zaneb has joined #openstack-meeting-515:43
srwilkersanything else?15:43
mateuszbno, that's all. Thanks15:44
srwilkers#topic reviews needed15:44
*** openstack changes topic to "reviews needed (Meeting topic: openstack-helm)"15:44
srwilkersCell service:  https://review.openstack.org/#/c/516810/15:45
jayahncell service and nova placement is two essential stuff to do ocata. these are almost ready. pls do final review on this. :)15:45
srwilkers:)15:45
jayahnFYI, as portdirect's request, we will do separate upstream "value override to make ocata work". probably make a new mvp values.15:46
jayahnNeutron: Correct section name for linuxbridge bridge_mappings config: https://review.openstack.org/#/c/518503/15:46
srwilkersjayahn: that'd be awesome.15:46
jayahnwe have been testing vlan-based provider-network w/ linuxbridge15:47
jayahnto support some of legacy openstack env.15:47
jayahnthis is one of few thing we are fixing while doing that.15:47
jayahni think it is rather straight-forward. pls review. :)15:47
srwilkersjust workflowed it15:48
jayahnthanks15:48
jayahnthat is all15:49
srwilkersawesome :)15:49
srwilkersany other last minute items?15:49
srwilkersotherwise we can take the open discussion to the openstack-helm channel -- im getting rushed out of my conference room :)15:50
jayahnbye15:50
srwilkers:)15:50
mateuszbbye15:50
srwilkersthanks for coming everyone15:50
srwilkers#endmeeting15:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:50
openstackMeeting ended Tue Nov 14 15:50:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-11-14-15.00.html15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-11-14-15.00.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-11-14-15.00.log.html15:51
*** ricolin_ has quit IRC15:56
*** mateuszb has quit IRC16:09
*** seungkyua has quit IRC16:23
*** zaneb has quit IRC16:25
*** zaneb has joined #openstack-meeting-516:25
*** yamamoto has quit IRC17:15
*** yamahata has quit IRC17:15
*** yamamoto has joined #openstack-meeting-517:21
*** yamamoto has quit IRC17:26
*** yamamoto has joined #openstack-meeting-517:36
*** yamamoto_ has joined #openstack-meeting-517:40
*** yamamoto has quit IRC17:41
*** seungkyua has joined #openstack-meeting-517:42
*** yamamoto_ has quit IRC17:45
*** seungkyua has quit IRC17:46
*** iyamahat has joined #openstack-meeting-517:49
*** yamamoto has joined #openstack-meeting-517:52
*** derekh has quit IRC17:54
*** yamahata has joined #openstack-meeting-517:59
*** yamamoto has quit IRC18:03
*** sshank has joined #openstack-meeting-518:19
*** sshank has quit IRC18:25
*** sshank has joined #openstack-meeting-518:29
*** yamamoto has joined #openstack-meeting-518:29
*** yamamoto has quit IRC18:35
*** yamamoto has joined #openstack-meeting-518:36
*** iyamahat_ has joined #openstack-meeting-519:03
*** iyamahat has quit IRC19:03
*** yamamoto has quit IRC19:11
*** ralonsoh has quit IRC19:46
*** sshank has quit IRC20:01
*** yamamoto has joined #openstack-meeting-520:12
*** yamamoto has quit IRC20:23
*** seungkyua has joined #openstack-meeting-521:12
*** seungkyua has quit IRC21:16
*** sshank has joined #openstack-meeting-521:33
*** felipemonteiro has joined #openstack-meeting-521:35
*** sshank has quit IRC21:40
*** sshank has joined #openstack-meeting-521:42
*** makowals_ has joined #openstack-meeting-521:56
*** zigo has quit IRC21:59
*** makowals has quit IRC22:00
*** zigo has joined #openstack-meeting-522:01
*** kei-ichi has quit IRC22:02
*** kei-ichi has joined #openstack-meeting-522:02
*** sshank has quit IRC22:18
*** sshank has joined #openstack-meeting-522:27
*** sshank has quit IRC22:30
*** felipemonteiro has quit IRC23:34

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