Tuesday, 2018-10-16

*** hongbin has quit IRC00:16
*** slaweq has joined #openstack-meeting-501:11
*** slaweq has quit IRC01:16
*** yamahata has quit IRC01:24
*** slaweq has joined #openstack-meeting-503:11
*** slaweq has quit IRC03:16
*** slaweq has joined #openstack-meeting-504:11
*** slaweq has quit IRC04:16
*** skazi has quit IRC05:03
*** slaweq has joined #openstack-meeting-505:11
*** slaweq has quit IRC05:15
*** slaweq has joined #openstack-meeting-506:11
*** slaweq has quit IRC06:16
*** slaweq has joined #openstack-meeting-506:55
*** spiette has quit IRC07:00
*** spiette has joined #openstack-meeting-507:03
*** markvoelker has quit IRC07:29
*** markvoelker has joined #openstack-meeting-507:29
*** ralonsoh has joined #openstack-meeting-507:29
*** markvoelker has quit IRC07:34
*** yamahata has joined #openstack-meeting-507:41
*** roman_g has joined #openstack-meeting-507:55
*** markvoelker has joined #openstack-meeting-508:30
*** derekh has joined #openstack-meeting-508:52
*** markvoelker has quit IRC09:03
*** yamahata has quit IRC09:06
*** persia has quit IRC09:27
*** persia has joined #openstack-meeting-509:28
*** markvoelker has joined #openstack-meeting-510:00
*** markvoelker has quit IRC10:34
*** roman_g has quit IRC11:21
*** roman_g has joined #openstack-meeting-511:22
*** markvoelker has joined #openstack-meeting-511:31
*** lemko has joined #openstack-meeting-511:54
*** markvoelker has quit IRC12:04
*** sgrasley has joined #openstack-meeting-513:37
*** mjturek has joined #openstack-meeting-513:42
*** yamahata has joined #openstack-meeting-514:01
*** hongbin has joined #openstack-meeting-514:05
*** munimeha1 has joined #openstack-meeting-514:20
*** jaesang has joined #openstack-meeting-514:48
*** gagehugo has joined #openstack-meeting-514:55
*** john_W has joined #openstack-meeting-515:00
*** mattmceuen has joined #openstack-meeting-515:00
evrardjpo/15:00
mattmceueno/15:00
jayahno/15:00
lamt\o15:00
evrardjpI have to run, enjoy the meeting15:00
mattmceuensee you evrardjp15:00
srwilkerso/15:00
john_Wo/15:02
portdirect#startmeeting openstack-helm15:02
openstackMeeting started Tue Oct 16 15:02:21 2018 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:02
openstackThe meeting name has been set to 'openstack_helm'15:02
portdirectsorry I'm late o/15:02
portdirect#topic rollcall15:02
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:02
lamt\o15:02
*** DanCrank has joined #openstack-meeting-515:02
srwilkerso/15:03
jaesango/15:03
portdirectalso - heres the agenda https://etherpad.openstack.org/p/openstack-helm-meeting-2018-10-1615:03
mattmceuenno worries portdirect o/ \o (<- high five?)15:03
portdirectshall we begin?15:04
portdirect#topic Armada job in openstack-helm15:04
*** openstack changes topic to "Armada job in openstack-helm (Meeting topic: openstack-helm)"15:04
portdirectsrwilkers: the floor is yours :D15:04
srwilkersmorning!15:04
srwilkersso the past few weeks have been a mix of triaging jobs that have failed for one reason or another, and also trying to find ways to improve them a bit15:05
srwilkersi had a few points of discussion wrt the armada job15:05
srwilkersnow that we've moved to deploy ocata by default instead of newton, it makes sense to go ahead and get the armada job updated to reflect this change15:05
srwilkersthe change to do so is here: https://review.openstack.org/#/c/591808/15:05
srwilkerssemi related to this15:06
srwilkersthe armada manifest has the overrides required to enable the fluentd handlers and formatters for logging for each openstack service, as this was put together when we still supported newton as the default15:07
srwilkersbut now that's changed, do we want to consider enabling these handlers and formatters by default, which removes the need to override them in the armada manifest/15:07
roman_go/15:08
mattmceuensounds good to me naively - there's no real risk of breaking any dependencies on the old behavior, right?15:09
portdirectyeah this is my concern15:09
portdirectwould this not mean, always trying to push logs to fluent, even it does not exist?15:10
srwilkersi'd prefer to keep things as is honestly, but wanted to bring it up now that we deploy a version that supports fluentd by default15:10
portdirectroger15:11
portdirectalso with the work lamt did - are we not now deploying ocata in the armada check anyway?15:11
portdirectoh - sorry i saw your updated ps, ignore me15:12
lamtit should - (with a minor exception of ceilometer if that's being used)15:12
srwilkers:)15:12
srwilkersyeah, should probably update the commit message to reflect what's really happening now15:12
portdirect++ ;)15:12
srwilkersand i think ive talked myself out of my last point wrt armada, so i think im done here15:14
portdirectdoes that also cover Logging configuration ?15:14
srwilkersyeah15:15
portdirect#topic New repos15:15
*** openstack changes topic to "New repos (Meeting topic: openstack-helm)"15:15
portdirect1st i must applogise for not having got the docs repo up - I dropped the ball here15:15
portdirectand will pick it back up today, and get the repo done15:15
jayahnsorry to miss the previous meetings (two), pls let us know what you need.15:15
portdirectjayahn: at this point the action items are mine :(15:16
portdirectsoon as its up - we'll need ps's and reviews15:16
portdirect:)15:16
portdirectanother thing came up15:16
portdirectwe have sveral images that are being built for osh15:16
jayahnokay. jaesang is also here today, the one who will do ps's reviews.. :)15:16
portdirectand i was going to start working on building these in the gate15:17
portdirectbut evrardjp suggested a new repo to house these images15:17
portdirectI think that would be great - as it would clearly seperate concerns15:17
portdirectand let us reuse much of the logic from loci here15:17
portdirecti think as we have a qorum of cores here15:18
portdirectcan we decide today if this is a sane path or not?15:18
srwilkersim all for it15:18
lamtportdirect: can we use that image repo to deal with things like that healthcheck issue with the loci repo?15:18
lamtI think I still have an outstanding patch set there15:19
mattmceuenI'm good with a separate repo too15:19
jayahnportdirect: separate repo would be good. just want to know so what images will be hosted there vs. what images we will consume from external repo (registry)? any guideline?15:21
lamtportdirect: if so I will abandon that ps and put the change in the new repo15:22
portdirectjayahn: ideally the images repo would be empty ;)15:22
portdirectand i think thats the best guidance we can follow for it unfortunately - as we know it wont be (eg libvirt etc)15:22
portdirectok - so seems we have agreement15:23
portdirect#action portdirect to get images repo up.15:23
portdirecti think this brings us onto the last item today15:23
portdirect#topic Reviews15:24
*** openstack changes topic to "Reviews (Meeting topic: openstack-helm)"15:24
portdirectRemove fluentbit sidecars from ceph-mon and ceph-osd: https://review.openstack.org/#/c/608356/15:24
portdirectFeedback for Apparmor init container: https://review.openstack.org/#/c/608826/15:24
portdirectlamt: your one is interesting - I'd need to mull on it more15:25
portdirectbut in simple terms is this not asking the workload to define its own security policy?15:25
portdirectwhich though it may work - seems a bit like asking a poacher to keep an eye on the livestock?15:25
lamtportdirect: thanks for the review. I thought about that.15:26
srwilkersgood analogy15:26
lamtalternative might be we have an apparmor profiles utility to manage exceptional profiles15:27
lamtutility chart*15:27
lamtfor things that fall out of the "default"15:27
portdirectyeah - is see issues any way we do it - thats certainly nicer from a seperation of concerns pov15:27
portdirectbut could be a nightmare for management15:28
portdirecti suppose the tradeoff here is:15:28
portdirectdo we make it easy (the init approach) that may have some issues, but people can use with little overhead15:28
portdirector 'pure', were people may end up using it less?15:28
mattmceuenI haven't given the PS a review yet so I don't know the ins and outs but - are we really worried about protecting against the chart (e.g. init container), or are we trying to protect against a hijacked chart?15:29
mattmceuenSaid differently, if we can trust that only trusted charts get deployed, and the init container approach fits into that well and protects against post-deployment shenanigans, then that seems reasonable?15:30
portdirectthe latter really, though a chart could be hijacked by a lazy dev too ;)15:30
lamt:)15:30
mattmceuenlazy devs are the worst15:30
* srwilkers whistles15:31
* mattmceuen and everyone else leaves the roome15:31
* jayahn left the room 15:32
* lamt follows15:32
* portdirect now knows how to get some peace round here15:32
portdirect:)15:32
srwilkerswe can change that15:32
portdirecti think the point mattmceuen raises is valid15:33
portdirectand where im on the fence15:33
portdirecti just feel i need to highlight it15:33
portdirectfrankly - I'm for security people use15:33
portdirectwhich puts me in the camp of saying lets use the init container15:33
portdirectbut i need to strawman the alternative veiwpoint ;)15:34
mattmceuenyup15:34
portdirectwe ok to hash it out in review from here on?15:35
lamtI lean that way - but that's why it was coded that way.  but one can strongarm me to change that15:35
lamtportdirect: sounds good15:35
mattmceuen+115:35
portdirectok - any other ps's that need review attention?15:35
portdirect(other than all of them...)15:35
portdirectok - moving on15:36
portdirect#topic roundtable15:36
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:36
portdirect1st I'd really like to thank evrardjp - hes doing great work on the gates15:36
portdirecthaving a new set of eyes there has been fantasic15:36
portdirectas, as well as both improving our ansible15:37
portdirecthes been asking the hard questions15:37
portdirecteg: why? and 'but why?'15:37
lamt++, the ansible looks more sane15:37
mattmceuenagree - great work evrardjp & thanks!!15:38
lamtat least when I need to add new jobs - I can just list the scripts vs. what was done before15:38
portdirectok - we ok to wrap up for today i think15:44
portdirect#endmeeting15:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:44
openstackMeeting ended Tue Oct 16 15:44:48 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-16-15.02.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-16-15.02.txt15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-16-15.02.log.html15:44
*** gagehugo has left #openstack-meeting-515:47
*** skazi has joined #openstack-meeting-515:47
*** DanCrank has left #openstack-meeting-515:48
*** lemko has quit IRC16:14
*** john_W has quit IRC16:20
*** yamahata has quit IRC16:24
*** yamahata has joined #openstack-meeting-516:53
*** jaesang has quit IRC16:58
*** munimeha1 has quit IRC17:10
*** ralonsoh has quit IRC17:28
*** mjturek has quit IRC20:04
*** slaweq has quit IRC20:33
*** munimeha1 has joined #openstack-meeting-521:06
*** munimeha1 has quit IRC21:45
*** slaweq has joined #openstack-meeting-521:53
*** slaweq has quit IRC22:09
*** slaweq has joined #openstack-meeting-522:11
*** slaweq has quit IRC22:44
*** hongbin has quit IRC23:07
*** slaweq has joined #openstack-meeting-523:11
*** slaweq has quit IRC23:44

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