Tuesday, 2017-09-26

*** yamamoto has quit IRC00:16
*** yamamoto has joined #openstack-meeting-500:21
*** yamamoto has quit IRC01:50
*** yamamoto has joined #openstack-meeting-501:50
*** yamamoto_ has joined #openstack-meeting-501:51
*** zenirc369 has joined #openstack-meeting-501:54
*** yamamoto has quit IRC01:55
*** zenirc369 has quit IRC02:33
*** zenirc369 has joined #openstack-meeting-504:39
*** felipemonteiro has joined #openstack-meeting-505:35
*** yamamoto_ has quit IRC05:37
*** yamamoto has joined #openstack-meeting-505:37
*** felipemonteiro has quit IRC06:00
*** iyamahat has joined #openstack-meeting-506:23
*** iyamahat has quit IRC06:24
*** iyamahat has joined #openstack-meeting-506:24
*** makowals has joined #openstack-meeting-506:33
*** iyamahat has quit IRC07:07
*** makowals has quit IRC07:11
*** markvoelker has quit IRC08:06
*** iyamahat has joined #openstack-meeting-508:12
*** iyamahat_ has joined #openstack-meeting-508:14
*** iyamahat has quit IRC08:14
*** iyamahat_ has quit IRC08:20
*** ralonsoh has joined #openstack-meeting-508:31
*** yamamoto has quit IRC08:31
*** yamamoto has joined #openstack-meeting-508:34
*** TuanLA has joined #openstack-meeting-508:35
*** yamamoto has quit IRC08:39
*** mariusv has quit IRC08:46
*** yamamoto has joined #openstack-meeting-508:47
*** yamamoto has quit IRC08:47
*** mariusv has joined #openstack-meeting-508:48
*** derekh has joined #openstack-meeting-509:00
*** yamamoto has joined #openstack-meeting-509:10
*** yamamoto has quit IRC09:12
*** yamamoto has joined #openstack-meeting-509:14
*** yamamoto has quit IRC09:16
*** yamamoto has joined #openstack-meeting-509:16
*** yamamoto has quit IRC09:31
*** yamamoto has joined #openstack-meeting-509:35
*** markvoelker has joined #openstack-meeting-510:07
*** iyamahat has joined #openstack-meeting-510:35
*** iyamahat has quit IRC10:36
*** iyamahat has joined #openstack-meeting-510:37
*** markvoelker has quit IRC10:41
*** iyamahat has quit IRC10:43
*** iyamahat has joined #openstack-meeting-510:45
*** iyamahat has quit IRC10:46
*** iyamahat_ has joined #openstack-meeting-510:46
*** iyamahat_ has quit IRC10:54
*** ralonsoh_ has joined #openstack-meeting-511:21
*** ralonsoh has quit IRC11:24
*** iyamahat has joined #openstack-meeting-511:27
*** TuanLA has quit IRC11:29
*** iyamahat has quit IRC11:29
*** iyamahat has joined #openstack-meeting-511:31
*** markvoelker has joined #openstack-meeting-511:39
*** iyamahat has quit IRC11:48
*** markvoelker has quit IRC12:12
*** markvoelker has joined #openstack-meeting-512:32
*** yamamoto has quit IRC12:38
*** yamamoto has joined #openstack-meeting-512:55
*** zenirc369 has quit IRC13:02
*** yamamoto has quit IRC13:06
*** felipemonteiro has joined #openstack-meeting-513:32
*** felipemonteiro_ has joined #openstack-meeting-513:34
*** felipemonteiro has quit IRC13:38
*** annp_ has joined #openstack-meeting-513:53
*** yamamoto has joined #openstack-meeting-514:07
*** yamamoto has quit IRC14:14
*** felipemonteiro_ has quit IRC14:22
*** makowals has joined #openstack-meeting-514:34
*** zenirc369 has joined #openstack-meeting-514:38
*** ralonsoh_ is now known as ralonsoh14:52
srwilkers#startmeeting openstack-helm15:00
openstackMeeting started Tue Sep 26 15:00:35 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
portdirecto/15:00
srwilkers#topic roll-call15:00
*** openstack changes topic to "roll-call (Meeting topic: openstack-helm)"15:00
srwilkerso/15:00
srwilkers\o/15:00
srwilkers\o15:01
portdirectw00t for OSH ;)15:01
* srwilkers looks around15:02
srwilkerswhere's everyone else?15:02
alanmeadows\o15:03
jayahno/ was sleeping..... need to wake up :)15:03
srwilkershey jayahn :)15:04
srwilkerssorry we woke you, but glad you're here15:04
v1k0d3no/15:04
srwilkerslet's get started -- we've got a full agenda15:04
srwilkershere's the agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2017-09-2615:05
srwilkers#topic PTG Summary15:05
*** openstack changes topic to "PTG Summary (Meeting topic: openstack-helm)"15:05
srwilkersit was great seeing everyone at the PTG last week15:05
*** slarimore02 has joined #openstack-meeting-515:05
jayahnyeah. it was really good. :)15:06
srwilkersthink we made a lot of progress in terms of paths forward and for cleaning up some stale work15:06
*** Quack has joined #openstack-meeting-515:06
srwilkerssince we've got a full agenda -- it'd be awesome to get some feedback on this summary over the next few days and to provide any additions where necessary15:06
srwilkersand if there's anywhere you'd like to do some work, feel free to add your name to any sections, and we can revisit this summary next week15:07
srwilkers#action srwilkers follow up with summary etherpad action items next meeting15:07
*** lrensing has joined #openstack-meeting-515:08
lrensingo/15:08
srwilkers#topic kubernetes entrypoint namespace support15:08
*** openstack changes topic to "kubernetes entrypoint namespace support (Meeting topic: openstack-helm)"15:08
srwilkershey lrensing o.15:08
srwilkerso/15:08
srwilkersportdirect: you added this one15:08
*** gagehugo has joined #openstack-meeting-515:08
srwilkersseems the PR for adding support for namespaces in k8s entrypoint is here:  https://github.com/stackanetes/kubernetes-entrypoint/pull/2515:08
portdirectwould be great to get some eyes on this15:09
portdirectand see if we can help them get it merged quickly15:10
portdirectas this will really unblock a lot of things for us15:10
portdirectnot much more to say than that really :)15:10
srwilkersyeah, this would be great.  i'll take a look at it and provide some feedback15:11
srwilkersanything else on this topic?15:12
srwilkersmoving on then15:12
srwilkers#topic NFS in OSH15:12
*** openstack changes topic to "NFS in OSH (Meeting topic: openstack-helm)"15:12
portdirectso theres been some bit-rot in the nfs based deployment for dev15:13
portdirectI was wondering if we wanted to contunue support for it, and if so do it properly15:13
portdirectv1k0d3n: i think you have guys on this?15:13
v1k0d3nwe had it in terms of repairing it for the gate. :)15:14
v1k0d3nchart work is a bit of a new request albeit not hard.15:14
portdirectnice - we dont have a gate for nfs atm - so getting one would be great :)15:14
*** felipemonteiro has joined #openstack-meeting-515:15
portdirectI think that to do it properly it would need to be a chart rather than the static manifests we have atm15:15
v1k0d3nsorry misspoke nfs in general.15:15
v1k0d3nwould we be willing to accept the nfs cleanup before starting on the chart work?15:15
portdirectwfm15:15
v1k0d3nbecause if yes, than i think sean has this already.15:15
v1k0d3nsean?15:15
srwilkersv1k0d3n: yep.  im all for that15:15
v1k0d3nok, well that works. this morning i was thinking chart was being asked for instead of the repair work. this works perfectly for us then.15:16
srwilkersi'd really like to see an NFS chart for some of the services i've been playing with, as ceph backing things like elasticsearch makes me :(15:16
slarimore02yeah I have the fixes for a gate ready to go and will submit a PS today15:16
*** felipemonteiro_ has joined #openstack-meeting-515:16
portdirectnice - cheers slarimore0215:17
lrensingnfs chart sounds like a good idea15:17
srwilkersyeah, just a misunderstanding.  triaging any issues with the gates, NFS or otherwise, is always higher priority :)15:17
v1k0d3nperfect. then we can work with tyson to get the chart work completed.15:17
srwilkersawesome15:17
v1k0d3nok...great to know. thanks guys/gals. :)15:17
srwilkersanything else on this topic?15:17
v1k0d3nwe're good on our side.15:17
v1k0d3nthanks @portdirect15:18
srwilkers#topic oslo-genconfig hack removed15:18
*** openstack changes topic to "oslo-genconfig hack removed (Meeting topic: openstack-helm)"15:18
portdirectwanted to say thanks to everyone for getting reviews on this15:18
portdirectwas a big change, but went through very smooth15:18
v1k0d3n+115:19
portdirectonly one ps left and i think its all done15:19
portdirecthttps://review.openstack.org/#/c/507293/15:19
v1k0d3nthe ps from yesterday portdirect ? i had a good look yesterday, just needed to ++ it.15:19
srwilkersim personally glad to see it gone15:19
v1k0d3nyes, very creative way to remove it.15:19
portdirectyeah (to both of you ;) )15:19
*** felipemonteiro has quit IRC15:20
portdirectjust took the work dulek did, and added multstring support15:20
portdirectso credit to him15:20
srwilkersthe hero we need15:20
v1k0d3nthat dulek...sharp guy :)15:20
srwilkersanything else on this topic?15:21
portdirectnah - with the fix for the armada gate merged I'm good15:21
srwilkersnice15:21
v1k0d3ndone15:21
srwilkers#topic docker version support15:21
*** openstack changes topic to "docker version support (Meeting topic: openstack-helm)"15:21
*** felipemonteiro_ has quit IRC15:21
portdirectohh - I'm on a roll15:21
portdirectso as in the etherpad, k8s 1.7 does some dif things with docker 1.13 and above15:21
portdirectit shares the pid namespaces in a pod15:22
portdirectthis means that the pause container had pid 115:22
portdirect*has15:22
portdirectso systemd (other than centos afaik) is kinda broke15:22
portdirectand the rabbitmq liveliness probes as well15:22
portdirectthe rabbitmq stuff really needs fixed, as they are pretty cray15:23
portdirectbut the systemd support (for things like maas) is a bigger issue15:23
portdirectso what should we do?15:23
portdirectsay 1.13 is not supported on k8s 1.7? or work to make it work?15:23
v1k0d3nhttps://github.com/kubernetes/kubernetes/pull/45236 i believe.15:24
portdirectthats the one15:24
portdirectthey are rolling it back in 1.815:24
portdirectby making it optional15:24
v1k0d3nit's not optional at all in 1.7?15:24
srwilkershonestly, id rather say 1.13 isn't supported and wait for 1.8.  i think there's more pressing work that needs to be done right now15:25
portdirectnope15:25
srwilkersbut thats my opinion15:25
lrensingi’d vote for just saying 1.13 isnt supported also srwilkers15:25
*** lukepatrick has joined #openstack-meeting-515:25
v1k0d3n+1 definitely15:25
jayahn+115:25
portdirectthats my pref as well15:25
srwilkersthere's some work id like to see done with rabbitmq first before we touch anything else15:25
lamtportdirect : I tried to dnf install docker (not latest), and I think it is still pulling 1.1315:25
v1k0d3neasier. let's us continue with 1.715:26
portdirectI'll get the docs updates as part of this ps then: https://review.openstack.org/#/c/507305/15:26
srwilkersyep15:26
v1k0d3nthat works portdirect15:26
portdirectlamt: hmm for me on f26 it was 1.12 but we can pit it if needed :/15:26
portdirect*pin15:26
lamtif you can - that would be great15:27
srwilkersseems we have consensus here then.  anything else/15:27
lamtthat or my f26 is doing something weird15:27
portdirectI've seen a lot of crazyness in the infra mirrors on it as well15:27
portdirectso - TLS?15:28
srwilkers#topic TLS15:28
*** openstack changes topic to "TLS (Meeting topic: openstack-helm)"15:28
portdirectso this is a long pole - but would be good to  get some people thinking about it15:29
portdirectI'd really like to see internal tls supported ootb in osh15:29
portdirectthough this gets tricky - as though its very easy to provide support for a opinionated deployment15:30
portdirectturns out theres a lot of opinions about the best way to manage certs15:30
portdirectone thing i do see as being a requirement - is having something fronting the openstack apis15:30
portdirectto perform termination15:31
portdirectthis is done in kolla-k8s very well15:31
portdirectand I think it would make sense to follow their pattern of having a sidecar doing that function15:32
v1k0d3nman, i hate to say this for fear of getting flamed...but is this a good place for a spec proposal?15:32
*** StaceyF has joined #openstack-meeting-515:32
v1k0d3nthis is a touchy one15:32
portdirectthough this leavs the big issue of how certs get to pods15:32
portdirectits exectly what Im about to propose15:32
portdirect:)15:32
srwilkersv1k0d3n: yep.15:32
v1k0d3nawesome. good deal.15:32
portdirectbut would be great to get some initial ideas for the direction that i should go in15:33
portdirectso - any thoughts?15:33
portdirectin the etherpad I outlineed two approaches i see as viable (but I'm sure there are many more)15:33
portdirect1) an init container that reqests a cert15:34
portdirect2) just use secrets (wildcards) and make it the deployers problem to get/manage them15:34
srwilkersid prefer the spec lays out the options mentioned, and outlines the pros/cons/considerations for each15:35
srwilkersthen we can just iterate from there and remove what doesnt make sense as we go15:35
srwilkersbceause honestly15:35
srwilkersi dont know where to suggest to start15:35
portdirectcool - damn, hoped i was gonna get to kull some early15:35
srwilkersnope15:35
srwilkers#action portdirect to draft spec for handling TLS15:36
portdirect:P15:36
srwilkersanything else here?15:36
v1k0d3nany thought on providing certs via letsencrypt?15:36
portdirectI can put that in for sure15:36
portdirectthough it would be ahrd to get the required number of certs from them15:37
v1k0d3nyeah :(15:37
portdirectfor public (external) they would be great - though there is an upstream chart that does this quite well afaik15:37
v1k0d3nwould be interesting to hear how some big orgs do this today. some may have policies that all certs need to be signed by a known entity.15:37
jayahnsurely15:38
v1k0d3ni know AT&T used to be that way. not sure how things are done specifically for groups like AIC or SKT (even Charter for that matter...i'd have to find out).15:38
portdirectyeah - we ant doing any self signed and 0 validation hackery thats for sure15:38
v1k0d3ntotal pain :( like you said...the subject is deep.15:38
v1k0d3nyeah, that's what i figured.15:39
srwilkerssounds like considerations to include and discuss in the spec ;)15:40
srwilkersanything else on this topic?  i bet jayahn is excited to talk about SONA :)15:40
v1k0d3ni'm good. added the placeholder.15:41
srwilkers#topic SONA integration15:41
*** openstack changes topic to "SONA integration (Meeting topic: openstack-helm)"15:41
srwilkersjayahn: all you :)15:41
jayahnnot much :)  it is on-going work as described in the etherpad15:41
jayahnhad two questions which all resoved from the comment there. :)15:42
*** felipemonteiro has joined #openstack-meeting-515:42
jayahnespecially, with upcoming sona chart on openstack-helm-infra, we will work on providing 3rd party gating.15:42
jayahnand I needed to get an official approval on that. :)15:43
portdirectthats awesome jayahn15:43
portdirectthe ps you have in for neutron looks very close to ready15:43
jayahni got your comments, we will try to finish this ps asap.15:44
portdirectThe other thing I'll add - though tangental is that I;m reworking the kubeadm container at the moment15:44
portdirectI'm hoping that we can get to making all the gates voting within a month15:44
jayahni got your comments, we will try to finish this ps asap.15:45
jayahnah, great! lots of voting machines will come.15:45
jayahnwe can move on to the next topic.15:46
srwilkers#topic fluent-logging15:46
*** openstack changes topic to "fluent-logging (Meeting topic: openstack-helm)"15:46
jayahni submitted spec for fluent-bit & fluentd logging & chart for that.15:47
srwilkersspec looks good jayahn :)15:47
srwilkersalso been looking at the work in flight15:47
jayahnwe will remove WIP tag soon. pls provide your reviews on this.15:47
jayahnone question here, ps includes both fluent-bit and fluentd. for now, we think this is okay.15:48
jayahnhowever, since we also have fluentd standalone chart, want to know if we want to do further effort to combine fluentd chart into one15:49
srwilkersyour approach here makes the most sense.  i think this would make the current fluentd chart obsolete, and i think that's okay15:49
jayahnthe current one does not have capability to run "fluentd" as standalone daemonset w/o fluent-bit.15:50
jayahnthere are two use cases, 1) just use fluentd as agent 2) use fluent-bit as agent, and fluentd as server(aggregator)15:50
srwilkersi think option 2 is more sane to be honest15:51
srwilkersas that's the typical use ive seen the more ive dug into how others are using it15:51
srwilkersespecially as we look at larger deployments, the smaller footprint for fluent-bit makes me happy15:51
jayahnokay. :)15:51
srwilkersplus i like that fluent-bit includes the popular plugins by default15:52
srwilkersim good here.  anything else to add jayahn ? :)15:52
jayahnnope. i am also good15:52
srwilkers#topic cinder-backup15:53
*** openstack changes topic to "cinder-backup (Meeting topic: openstack-helm)"15:53
srwilkersnice, it's merged15:53
srwilkersglad it's working jayahn15:53
jayahnah, this is just simple question from me, since cinder-backup was brought up on ptg meeting15:53
jayahnlet us know if you find any issue on cinder-backup.15:54
srwilkerssounds good15:54
srwilkerswill do15:54
portdirectroger - we should also enable it in the horizon config15:54
*** kiennt26 has joined #openstack-meeting-515:54
srwilkers#topic OSH-infra/addons gates15:54
*** openstack changes topic to "OSH-infra/addons gates (Meeting topic: openstack-helm)"15:54
srwilkersso lamt is working on getting zuul cloner set up appropriately so we can start gating addons/infra better15:54
srwilkersas im starting to run into issues testing prometheus exporters, as the services they're monitoring live in OSH proper currently15:55
portdirectyeah - along with the updates to kubeadm-aio I'm hoping that we can get the gates running well across all three repos by the end of next week15:56
srwilkersbut right before the meeting, i've now got prometheus running with exporters for:  ceph, rabbitmq, mysql, and cadvisor15:56
srwilkersand they're functional :D15:56
portdirectnice :)15:56
jayahngreat!15:56
srwilkers#topic open discussion15:56
*** openstack changes topic to "open discussion (Meeting topic: openstack-helm)"15:56
srwilkersi'll make this one quick15:56
srwilkersi had a question regarding our weekly meeting -- it seems there was an email thread about teams being able to now host weekly meetings in the project channels15:57
srwilkersi think it'd be great to start hosting our meeting in #openstack-helm, so anyone who misses it can read the scrollback15:57
srwilkerswithout needing to be mindful of the scrollback of other teams15:57
srwilkersbut that's my opinion, and overall not that important15:57
srwilkersany opinions any other way?15:58
jayahnnot much. i am okay with either way15:58
portdirecthmm - I quite like the meeting channel as it logs the meetings: http://eavesdrop.openstack.org/meetings/openstack_helm/2017/15:58
portdirectwould we be able to keep this if we moved it into #openstack-helm15:58
jayahnas long as it leaves logs.. like portdirect mentioned15:59
srwilkersill look into what we need to do to ensure they're captured15:59
portdirectif we can then moving may make sense15:59
portdirectas it would make slack access easier15:59
srwilkersexactly what i was going to say15:59
srwilkers#topic srwilkers check into logging meetings in #openstack-helm16:00
*** openstack changes topic to "srwilkers check into logging meetings in #openstack-helm (Meeting topic: openstack-helm)"16:00
srwilkersoops16:00
srwilkers#topic open discussion16:00
*** openstack changes topic to "open discussion (Meeting topic: openstack-helm)"16:00
srwilkers#action srwilkers check into logging meetings in #openstack-helm16:00
portdirectso -1 if we loose the meeting logs, +1 if we can keep them :D16:00
srwilkersalright, thats it for today16:00
srwilkerssee you in #openstack-helm16:00
srwilkers#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Tue Sep 26 16:00:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-09-26-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-09-26-15.00.txt16:00
*** annp_ has quit IRC16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-09-26-15.00.log.html16:00
*** gagehugo has left #openstack-meeting-516:09
*** kiennt26 has quit IRC16:35
*** derekh has quit IRC16:54
*** rama_y has joined #openstack-meeting-517:11
*** sshank has joined #openstack-meeting-517:29
*** sshank has quit IRC17:34
*** sshank has joined #openstack-meeting-517:37
*** ralonsoh has quit IRC17:51
*** sshank has quit IRC18:56
*** lrensing has quit IRC19:56
*** sshank has joined #openstack-meeting-520:03
*** zenirc369 has quit IRC20:09
*** sshank has quit IRC20:13
*** sshank has joined #openstack-meeting-520:13
*** lrensing has joined #openstack-meeting-520:36
*** felipemonteiro has quit IRC20:36
*** StaceyF has quit IRC21:11
*** lrensing has quit IRC21:28
*** lrensing has joined #openstack-meeting-521:33
*** lukepatrick has quit IRC21:36
*** yamahata has joined #openstack-meeting-521:55
*** lukepatrick has joined #openstack-meeting-522:38
*** lukepatrick has quit IRC22:47
*** yamamoto has joined #openstack-meeting-523:05
*** lrensing has quit IRC23:09
*** sshank has quit IRC23:56

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