Tuesday, 2018-03-20

*** yamamoto has quit IRC00:26
*** yamamoto has joined #openstack-meeting-500:28
*** yamamoto has quit IRC00:28
*** diman has joined #openstack-meeting-501:00
*** diman has quit IRC01:04
*** yamamoto has joined #openstack-meeting-501:07
*** wxy has joined #openstack-meeting-501:10
*** yamamoto has quit IRC01:27
*** iyamahat has quit IRC02:20
*** yamahata has quit IRC02:21
*** skazi has joined #openstack-meeting-503:08
*** yamamoto has joined #openstack-meeting-503:52
*** ricolin has joined #openstack-meeting-503:55
*** yamamoto has quit IRC04:01
*** yamamoto has joined #openstack-meeting-504:04
*** yamamoto has quit IRC04:08
*** yamamoto has joined #openstack-meeting-504:09
*** yamamoto has quit IRC04:14
*** yamamoto has joined #openstack-meeting-504:16
*** yamamoto has quit IRC04:27
*** diman has joined #openstack-meeting-504:28
*** yamamoto has joined #openstack-meeting-504:28
*** radeks_ has joined #openstack-meeting-504:33
*** diman has quit IRC04:33
*** radeks__ has joined #openstack-meeting-504:34
*** radeks_ has quit IRC04:37
*** yamamoto has quit IRC04:43
*** yamamoto has joined #openstack-meeting-504:46
*** radeks_ has joined #openstack-meeting-507:02
*** radeks__ has quit IRC07:05
*** MarkBaker has joined #openstack-meeting-509:04
*** derekh has joined #openstack-meeting-509:40
*** ricolin has quit IRC09:54
*** yamamoto has quit IRC10:04
*** yamamoto has joined #openstack-meeting-510:09
*** yamamoto has quit IRC10:14
*** yamamoto has joined #openstack-meeting-511:10
*** yamamoto has quit IRC11:12
*** yamamoto has joined #openstack-meeting-511:12
*** yamamoto has quit IRC11:40
*** yamamoto has joined #openstack-meeting-511:41
*** ricolin has joined #openstack-meeting-511:44
*** ricolin has quit IRC12:29
*** ricolin has joined #openstack-meeting-512:29
*** ricolin has quit IRC12:45
*** mjturek has joined #openstack-meeting-512:46
*** mjturek has quit IRC13:11
*** iyamahat has joined #openstack-meeting-513:18
*** iyamahat_ has joined #openstack-meeting-513:19
*** iyamahat has quit IRC13:22
*** d|k` has joined #openstack-meeting-513:58
*** yamamoto_ has joined #openstack-meeting-514:12
*** yamamoto has quit IRC14:12
*** seaneagan has joined #openstack-meeting-514:21
*** felipemonteiro has joined #openstack-meeting-514:27
*** felipemonteiro_ has joined #openstack-meeting-514:29
*** felipemonteiro has quit IRC14:32
*** wxy| has joined #openstack-meeting-514:54
*** seaneagan has quit IRC14:56
*** mjturek has joined #openstack-meeting-514:57
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Mar 20 15:00:20 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
mattmceuen#topic rollcall15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
d|k`hihi!15:00
mattmceuenGM!15:00
mattmceuenAgenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-03-2015:00
srwilkers¯\_(ツ)_/¯15:00
*** d|k` is now known as d|k15:00
*** d|k is now known as Guest9476115:01
portdirecthello15:01
mattmceuengiving folks 2min to join15:01
*** Guest94761 is now known as d|k`15:01
*** eeiden has joined #openstack-meeting-515:01
* portdirect taps feet15:01
mattmceuenGM all15:02
*** gmmaha has joined #openstack-meeting-515:02
gmmahao/15:02
eeideno/15:02
*** seaneagan has joined #openstack-meeting-515:02
mattmceuenHere we go15:03
mattmceuen#topic kubernetes-entrypoint enhancement15:03
*** openstack changes topic to "kubernetes-entrypoint enhancement (Meeting topic: openstack-helm)"15:03
mattmceuen@seaneagan made an update to k8s entrypoint to target pods - sean, want to share?15:03
seaneagandocs:  https://github.com/stackanetes/kubernetes-entrypoint#pod  kubernetes-entrypoint pull request and release:  https://github.com/stackanetes/kubernetes-entrypoint/pull/31 https://github.com/stackanetes/kubernetes-entrypoint/releases/tag/v0.3.0  osh support patchsets:  nova: https://review.openstack.org/#/c/552572/ neutron: https://review.openstack.org/#/c/553622/ other charts: https://review.openstack.org/#/c/5542615:04
mattmceuenawesome, I'll add to the agenda notes15:04
portdirectthis is a big win :)15:04
portdirectthanks seaneagan15:04
portdirectI's love to see this for jobs as well :)15:05
mattmceuenyes thanks seaneagan!15:06
mattmceuenportdirect or seanegan, can you please illustrate an example cases for this work?15:06
seaneagannp, I'll look into that as well15:06
seaneaganThe initial use case for this is to use them in conjunction with daemonset overrides, which enable overriding daemonset configuration by by node labels and/or individual hosts, via separate daemonsets for each configuration.  We can thus no longer depend an individual daemonset, but instead on a pod owned by one of these daemonsets, which all share a set of labels.  We chose to depend on pod labels rather than daemonse15:06
seaneaganhttps://github.com/openstack/openstack-helm/blob/dbb778a7840d33ae589d4d875bb623970b449988/helm-toolkit/templates/utils/_daemonset_overrides.tpl15:07
portdirectI'm working on a PS that i hope to have up later today that will leverage this15:08
portdirectallowing us to have both host/label specific nova compute and neutron agent pods on a host15:09
seaneagan(to finish my sentence): we can depend on a set of pod labels regardless of how they got there, daemonset or otherwise15:09
portdirectthe only minor issue i have with this - is we probably should have called out that it is 'pod on same host' not 'pod in cluster'15:10
portdirectthough i think seaneagan has ideas for how to handle this15:10
mattmceuenthis was a non-trivial and extremely important feature that we need for real-world use.  Any questions on this topic?15:11
seaneaganwe should be able to extend "pod dependencies" by taking advantage of the extensibility of json, such as by adding a `local: <true|false>` field to take care of that15:11
portdirect+++15:12
mattmceuenWant to make sure everyone is looped in on the "why" and the "how to use" -- please refer to Sean's links above if you find yourself with a dependency on something host-specific15:12
mattmceuenneat15:12
portdirect`extensibility of json`15:13
portdirectqotd15:13
mattmceuen:-D15:13
mattmceuenportdirect, you want to discuss SRIOV support yet, or save that for next time?15:14
mattmceuen(see I am whetting peoples' appetites)15:14
srwilkershe does15:14
mattmceuen#topic SRIOV Support15:15
*** openstack changes topic to "SRIOV Support (Meeting topic: openstack-helm)"15:15
srwilkershe said he needs a few minutes and to come back around to it15:15
mattmceuendeal15:16
mattmceuen#topic Slack integration going away15:16
*** openstack changes topic to "Slack integration going away (Meeting topic: openstack-helm)"15:16
mattmceuen:(15:16
mattmceuenhttps://get.slack.help/hc/en-us/articles/201727913-Connect-to-Slack-over-IRC-and-XMPP15:16
mattmceuenSlack is unfortunately deprecating the gateway functionality that facilitates Slack<->IRC mirroring, effective May 1515:17
d|k`@slack: grrrrrrr15:17
mattmceuenI will be posting a few messages in slack before and after the move to try to wrangle folks to IRC15:17
mattmceuenSo the question for y'all is:  is it worth keeping the OSH Slack channel as a secondary chat room?15:18
mattmceuenPro:  more newbies may run across it15:18
mattmceuenCon:  more chat room15:18
mattmceuenI have an opinion which is informed by having more blinky lights on my computers than I can keep up with already15:20
* portdirect has finished his nap15:20
mattmceuenI propose we leave it there with a note that sets expectations, e.g. "main conversation has moved to the IRC #openstack-helm channel on freenode, please expect very delayed responses in this channel" or something15:20
portdirectI think we should focus the slack channel on user support? and irc on dev?15:21
portdirector is that a horrrible idea?15:21
srwilkerswithout something mirroring the chat, i think it's going to be difficult to maintain two separately.15:21
srwilkersthats a horrible idea15:21
srwilkersdoes the openstack kubernetes sig have a slack channel?  i think that'd be an appropriate place to lurk if we're going to suggest having two disjoint chat rooms15:22
portdirectwfm15:22
srwilkersas it'd help push that initiative15:22
mattmceuenthat is a good idea15:22
mattmceuenI'll plan to set up a note directing folks to both #openstack-helm IRC and sig-openstack slack15:23
mattmceuen#topic The legend of SRIOV15:24
*** openstack changes topic to "The legend of SRIOV (Meeting topic: openstack-helm)"15:24
mattmceuenportdirect take it away15:24
portdirectso we merged this recently :)15:25
portdirectthough theres more working coming15:25
portdirectthe big hitters here were seans work, and the sr-iov agent15:26
portdirectwhich introduced to neutron the ability to use multiple backends15:26
portdirectand leveraged the conditional deps work we brought in a few weeks ago15:27
portdirectalso we are using some ubuntu:18.04 images15:27
portdirectto let us enable promisc and trusted mode on newer nics15:27
*** yamamoto_ has quit IRC15:27
jayahno/ late for the game.15:27
mattmceueno/ jayahn!15:28
portdirectI'm hoping that today/tomorrow I'll have a ps up that will also let us target hosts for diff configs for all the neutron agents15:28
portdirectthough dev time has been in short supply lately ;)15:28
portdirectthink thats it15:28
jayahnportdirect: i am pretty sure hyunsun will have her own idea on this. we let this ps merged since it seems urgent.15:29
mattmceuendoes hyunsun have a different approach to multi-backend in mind?15:30
jayahnbut hope we cloud've had more chance to discuss upfront. (that is all I heard from her. :) )15:30
d|k`portdirect: dumb question: is there anything nic-specific in the sriov patchset, and if so are there particular nic models it's known to work with?15:30
jayahnnot really, she has some idea on improving it as long as i know15:30
portdirectjayahn: it was a wip for three weeks15:31
mattmceuenAwesome, would love to discuss it - can she bring it up in the irc channel or the ML?15:31
portdirectwould have been great to have her feedback as I added her as a reviewer on the 1st ps :)15:31
portdirecthttps://review.openstack.org/#/c/547890/15:32
jayahnit was titled with sriov, so we did not keep our eye on it first time. :) then, reallized it has more in it.15:32
mattmceuenWould like her input in any case15:32
jayahnsure thing.15:33
mattmceuenCan you please share this meeting transcript with her jayahn?15:33
portdirectd|k`: nothing nic specific really, other than 18.04 lets us use fancy new 25g nics :)15:33
mattmceuenThe background on the k8s entrypoint pod targeting will be valuable context15:33
jayahni will.15:33
mattmceuenawesome15:33
d|k`portdirect: thx. since those are prolly what i'll end up poking at it's worth knowing.15:34
mattmceuen#topic Source code copyright attribution15:34
*** openstack changes topic to "Source code copyright attribution (Meeting topic: openstack-helm)"15:34
mattmceuenSo, we have as a somewhat historical remnant a copyright attribution of "The Openstack-Helm Authors" in the majority of our source, sometimes along with additional copyright for any code that has been comingled in our source15:35
mattmceuenThis was the approach used in the beginning as it follows common community conventions15:35
portdirect(from when we were thinking of kube-incubator as a home for us)15:36
mattmceuenHowever, the norm for official openstack projects is to assign copyright to the "OpenStack Foundation" when feasible (the Foundation itself is very flexible)15:36
mattmceuenThe biggest driver for changing is that the OpenStack Foundation is a legal entity, and the OpenStack-Helm Authors is not :)15:37
mattmceuenNow that we are an official project, I'd like to reassign copyright to the OpenStack Foundation from the OpenStack-Helm Authors, under the merit that they're approximately the same thing, we have a more legally-grounded assignment, and we're following the conventions of core OS projects that way.15:38
portdirectI'm happy for all work I contributed prior to 13th March 2017 under the guise of `OpenStack-Helm Authors` to be re-assigned to `OpenStack Foundation`15:38
mattmceuenNote:  that would only be a search an replace of those two terms; it would not impact any OTHER copyright in the code15:38
portdirectafter then its up to my employer to decide ;)15:38
mattmceuenAny objections or concerns team?15:39
jayahnnope15:39
mattmceuenAwesome.  Let's consider this the plan of record, and allow some additional time for folks to chew on it and present any other opinions.15:40
mattmceuen#topic Senlin, Magnum, Mistral Broken15:41
*** openstack changes topic to "Senlin, Magnum, Mistral Broken (Meeting topic: openstack-helm)"15:41
mattmceuenI didn't even realize that these three were broken, unfortunately15:41
mattmceuenWhich illustrates:  these charts aren't necessarily used as heavily by as many folks in the community15:41
portdirectI had a poke around15:42
mattmceuenIt would be great for someone to take a look at these, why they stopped functioning, and get 'em gated15:42
mattmceuenAny insight portdirect?15:43
portdirectand it looks like theres an issue with the messaging between the apis and engines15:43
portdirectmay be simple, or a bit more in depth to solve, ive just not had the b/w to look into it15:43
portdirectbut would be a great onboarding problem to solve15:43
mattmceuenAgree - good opportunity to learn more of how the charts fit together15:44
mattmceuenAny volunteers?  Or is anyone aware of actual users of these charts, who might be able to help contribute to OSH?15:45
portdirectI would like to see helm test added for each of these15:46
mattmceuen+115:46
portdirectI was actually doing that when i discovered they were broken15:46
portdirect:)15:46
portdirectI have no immediate plans for these charts in a professional capacity15:46
mattmceuenyeah, those are remnant of the days when we were more laisses-faire...15:46
portdirectbut would really like to see magnum working again15:46
portdirectas it closes the loop of osh15:47
portdirectand gives us a nice sandwich proposition to the community15:47
*** felipemonteiro_ has quit IRC15:48
*** felipemonteiro_ has joined #openstack-meeting-515:49
mattmceuenI'll socialize some bugs for these to try to get some support from the community15:49
mattmceuen#topic Release Schedule and rational spec (portdirect)15:50
*** openstack changes topic to "Release Schedule and rational spec (portdirect) (Meeting topic: openstack-helm)"15:50
portdirectoh hai15:50
portdirectso during the PTG we used a variety of props to try and hash out a release plan and rational15:50
portdirectI was wondering if it would be helpful to translate where we ended up into a spec15:51
portdirectif applicable i think LOCI would like to follow the same format15:51
portdirectthough that will be up to the PTL and other cores over there to decide15:52
portdirecti could try and get something up before the next meeting15:52
portdirectunless anyone else wanted to take this on?15:52
mattmceuenNext week sounds like a good plan to get the spec out for our 1.0 readiness that I committed to as well :)15:54
mattmceuenI think the release plan will be highly valuable portdirect15:54
mattmceuenIt will help illustrate the differences between OSH releases & OpenStack releases, and how they fit together15:55
jayahn+++15:55
portdirectYup - and how being release independent is the path15:55
portdirectto openstack bliss when you are trying to provide paths from one to the other15:56
portdirect:)15:56
mattmceuenyikes we're running low on time15:57
mattmceuenso much bliss this week15:57
mattmceuen#topic topics to discuss next time15:57
*** openstack changes topic to "topics to discuss next time (Meeting topic: openstack-helm)"15:57
mattmceuenjayahn - log: multiline support issue15:57
jayahni saw some discussion on openstack-helm channel.15:58
jayahnpls let's discuss over this week, if you can share idea on email, it would be super great for us to follow up, but, irc would be also okay.15:58
mattmceuenI will add that one to the agenda for next time and make sure we're ready to discuss15:58
mattmceuenperfect - will do15:59
mattmceuenabout out of time but15:59
mattmceuen#topic Roundtable15:59
*** openstack changes topic to "Roundtable (Meeting topic: openstack-helm)"15:59
mattmceuenjayahn added some of our talks that got accepted to our agenda https://etherpad.openstack.org/p/openstack-helm-meeting-2018-03-2015:59
mattmceuenwooooo15:59
mattmceuenPlease add any other OSH or related talks from our team to that agenda, so we can all be aware15:59
jayahnyeap. thanks folks for much efforts.15:59
mattmceuenAgree!16:00
mattmceuen#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Mar 20 16:00:07 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
mattmceuenthanks all16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-20-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-20-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-20-15.00.log.html16:00
*** gmmaha has left #openstack-meeting-516:00
*** saneax has quit IRC16:01
*** d|k` has left #openstack-meeting-516:01
*** felipemonteiro_ has quit IRC16:06
*** ricolin has joined #openstack-meeting-516:15
*** wxy|_ has joined #openstack-meeting-516:22
*** wxy| has quit IRC16:22
*** yamamoto has joined #openstack-meeting-516:28
*** ricolin has quit IRC16:32
*** yamamoto has quit IRC16:34
*** sshank has joined #openstack-meeting-516:40
*** eeiden has quit IRC16:41
*** felipemonteiro has joined #openstack-meeting-516:55
*** MarkBaker has quit IRC17:02
*** felipemonteiro_ has joined #openstack-meeting-517:04
*** mjturek has quit IRC17:05
*** mjturek has joined #openstack-meeting-517:07
*** felipemonteiro has quit IRC17:08
*** felipemonteiro has joined #openstack-meeting-517:08
*** felipemonteiro_ has quit IRC17:11
*** wxy|_ has quit IRC17:12
*** MarkBaker has joined #openstack-meeting-517:24
*** yamamoto has joined #openstack-meeting-517:30
*** yamamoto has quit IRC17:36
*** derekh has quit IRC17:52
*** yamamoto has joined #openstack-meeting-518:32
*** yamamoto has quit IRC18:37
*** sshank has quit IRC18:41
*** mjturek has quit IRC19:28
*** yamamoto has joined #openstack-meeting-519:34
*** yamamoto has quit IRC19:39
*** mjturek has joined #openstack-meeting-519:39
*** sshank has joined #openstack-meeting-520:03
*** sshank has quit IRC20:16
*** radeks_ has quit IRC20:18
*** iyamahat_ has quit IRC20:20
*** iyamahat_ has joined #openstack-meeting-520:20
*** yamamoto has joined #openstack-meeting-520:35
*** yamamoto has quit IRC20:41
*** felipemonteiro_ has joined #openstack-meeting-520:51
*** felipemonteiro has quit IRC20:54
*** sshank has joined #openstack-meeting-521:07
*** mjturek has quit IRC21:08
*** sshank has quit IRC21:17
*** MarkBaker has quit IRC21:34
*** yamamoto has joined #openstack-meeting-521:37
*** yamamoto has quit IRC21:43
*** seaneagan has quit IRC21:48
*** MarkBaker has joined #openstack-meeting-521:49
*** felipemonteiro_ has quit IRC22:18
*** yamamoto has joined #openstack-meeting-522:39
*** sshank has joined #openstack-meeting-522:43
*** MarkBaker has quit IRC22:44
*** yamamoto has quit IRC22:45
*** yamamoto has joined #openstack-meeting-523:41
*** yamamoto has quit IRC23:46

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