Tuesday, 2018-08-28

*** slaweq has joined #openstack-meeting-500:11
*** slaweq has quit IRC00:16
*** yamahata has quit IRC01:25
*** slaweq has joined #openstack-meeting-502:11
*** slaweq has quit IRC02:16
*** ricolin has joined #openstack-meeting-503:08
*** slaweq has joined #openstack-meeting-504:11
*** slaweq has quit IRC04:15
*** slaweq has joined #openstack-meeting-505:11
*** slaweq has quit IRC05:16
*** slaweq has joined #openstack-meeting-505:28
*** slaweq has quit IRC05:33
*** slaweq has joined #openstack-meeting-506:11
*** radeks has joined #openstack-meeting-506:12
*** radeks_ has joined #openstack-meeting-506:14
*** slaweq has quit IRC06:16
*** radeks has quit IRC06:16
*** yamahata has joined #openstack-meeting-506:32
*** slaweq has joined #openstack-meeting-507:02
*** dims has quit IRC07:08
*** dims has joined #openstack-meeting-507:10
*** skazi has quit IRC08:26
*** skazi has joined #openstack-meeting-509:11
*** ricolin has quit IRC11:24
*** skazi has quit IRC13:18
*** skazi has joined #openstack-meeting-513:59
*** skazi has quit IRC13:59
*** mjturek has joined #openstack-meeting-514:00
*** amotoki has quit IRC14:03
*** portdirect has joined #openstack-meeting-514:09
*** ricolin has joined #openstack-meeting-514:17
*** skazi has joined #openstack-meeting-514:21
*** gagehugo has joined #openstack-meeting-514:22
*** markvoelker has joined #openstack-meeting-514:45
*** markvoelker has quit IRC14:49
*** tdoc has joined #openstack-meeting-514:55
*** srwilkers has joined #openstack-meeting-514:55
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Aug 28 15:00:04 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
mattmceuenGM/GE folks!15:00
tdochi all15:00
srwilkerso/15:00
srwilkerstuesday again15:00
mattmceuenHere's our agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-08-2815:00
mattmceuenIt's very Tuesday15:00
mattmceuenplease add anything you'd like to discuss, we'll get started in a min15:01
portdirecto/15:02
*** jayahn has joined #openstack-meeting-515:03
mattmceuenAlright let's get started.  We have several topics that got carried over from last week, so we'll need to stay on topic today15:03
mattmceuen#topic ETA for 1.015:03
*** openstack changes topic to "ETA for 1.0 (Meeting topic: openstack-helm)"15:03
portdirectwhich ptl want to take this one?15:04
mattmceuenhttps://storyboard.openstack.org/#!/worklist/34115:04
mattmceuen^^^^^^^^^^^^^^15:04
mattmceuenThese are the todos for us to get to 1.015:04
tdocYep, was just curious where we are...15:04
mattmceuenA good chunk of the way through15:05
mattmceuenwith a good chunk to go15:05
mattmceuena lot of what are left on there are adding helm tests15:05
mattmceuenwhich are great for new contributors -- any help with those would be welcome!15:05
portdirectalso - we really need the spec for values15:06
mattmceuenyup15:06
portdirectas one of the major commitments we have, is that a 1.0 is upgradeable15:06
srwilkersyeah, ive dropped the ball on that one -- i was meant to take that and run with it, but have been dealing with other priorities15:06
portdirectall good dude, thats been a hot potato to say the least ;)15:06
mattmceuenyou've had a lot on your plate srwilkers :)15:07
srwilkersjust need a bigger plate is all15:07
tdocok, so i guess nobody dares putting a rough eta? ;)15:08
mattmceuenAny other thoughts on the 1.0 target?  my gut says 2 months if we can focus on it as a team15:08
mattmceuenbut this is not the first time I've said 2 months ;-)15:08
portdirectthat seems about right15:08
portdirectbut we as you have pointed out, said that before!15:08
tdocok, thanks15:08
portdirectit very much dpends on how much time people have to put into it15:08
portdirecttheres about a month of work for the current active devs15:09
evrardjpo/15:09
jayahnespecially, upgradable part would be so important since some of us is soon putting openstack-helm charts into production. :)15:09
portdirectbut being able to do that, without the whole "real job" thing getting in the way...15:09
mattmceuen++ jayahn15:09
portdirectsome of us, already have them in "semi" prod...15:09
jayahnnot only version to version upgrade,15:10
portdirectexactly jayahn15:10
jayahnreally careful about things blocking upgrade, for example, chart name changes, pv stuff, ... etc15:10
portdirectthats why we need to be careful as to when we rubber stamp "1.0"15:10
portdirectim much happier with "unstable" than"stable, but lol we broke you"15:11
tdocyup, ok, i think that's pretty clear then...15:11
mattmceuenCool.  Any other thoughts on this topic before we move on?15:11
mattmceuen#topic OSH user/dev survey15:12
*** openstack changes topic to "OSH user/dev survey (Meeting topic: openstack-helm)"15:12
mattmceuen'zis one you Pete?15:12
portdirectyeah  - this kinda leads into a thing i want to do at the ptg15:12
portdirectbut i think its time to get a user and dev survey out15:12
portdirectas the users/devs of osh are growing15:12
*** jamesgu has joined #openstack-meeting-515:13
jayahnportdirect: siri had a happy time to deal with upgrade issues from changes in chart. :)15:13
portdirectand i dont know if we (as a core team) are fully aware of how people are using osh now15:13
portdirectand if we are to do the best we can for this community, we need to15:13
portdirecthow about a quick roundtable now, just to get a straw poll of whos coming to these meetings?15:13
portdirectand then i can follow up in the ml15:14
mattmceuenah - great idea15:14
portdirecti could go 1st?15:14
mattmceuenthe floor is yours15:15
jayahnso, r u saying you would do user/dev survey on openstack-helm? r we referring a specific ml thread?  just try to catch up15:15
portdirecthello everyone, im pete (portdirect) and I spend my days putting telco infrastructure into kubernetes pods, leading the effort for a large telco. As a result im very lucky to get to work with the airship team, who produces a k8s platform for me to use. I probabaly get to spend about 20% of my time working upstream - which is awesome!15:17
portdirectsrwilkers: want the stick?15:18
srwilkersim steve, and i spend most of my days playing with services that provide an interface for operators to know whether or not the services we're building are meeting their needs through monitoring, alarming, and logging (the really fun stuff).  i'd say about 30% of my time is working upstream.15:19
srwilkerstdoc: your turn15:20
srwilkers:)15:20
evrardjpothers?15:22
tdocHi, I'm Teun (tdoc), I work for as a dev for a company that makes infrastructure management so15:22
tdocftware. We focus on the HPC space, but have also had our own OpenStack deployment tools for se15:22
tdocveral years now. We're looking to integrate OSH into our solutions. At the moment we have just15:22
tdoc been evaluating but soon plan to start contributing. Our devs are base in Amsterdam.15:22
evrardjpcool15:22
portdirectevrardjp: would be great to get to know you a bit better ;)15:22
srwilkerstdoc: awesome :)15:23
evrardjphaha15:23
evrardjpI am close of tdoc geographically, I am new to k8s world, so still learning. Evaluating the possibility to make a product out of OSH+Airship for my employer.15:23
jayahnso, all of us is doing this now?15:24
evrardjpyou're it jayahn15:24
portdirectoh - another one pops up ;)15:24
portdirectjayahn: want to tell us a bit about yourself?15:24
evrardjpportdirect: ;)15:24
mattmceuentdoc, what kind of workloads will you ned OSH to support - normal cloud workloads, NFVs, other things?15:25
mattmceuenSame q for you evrardjp :)15:26
mattmceuenI think this kind of discussion will help ensure OSH is meeting needs of its users15:26
portdirectmattmceuen: you havent intoduced yourself yet ;)15:26
mattmceuenI'm mattmceuen -- I do airship and openstack-helm development, on behalf of telco use cases such as 5G VNF workloads.  I probably spend  30% of my time on upstream dev proper as well.  Note: the rest of the time is not consumed by downstream dev (we just do upstream) but rather integration and unrelated stuff.15:26
jayahnHi, I'm Jaesuk Ahn (jayahn),  I work for as a team lead for sk telecom, spend most of my time checking issues, fighting with boss, communicating with potential osh users, etc... skt is currently deploying three production openstack based on osh, vdi case, big data case, and private cloud. soon, i have to do a deep discussion with our network operation team on putting osh into 5g se env.15:26
mattmceuenHad it sitting in paste!15:26
portdirectlol - that cover everyone here?15:27
mattmceuenlol jayahn fighting with boss15:27
jayahnyeah.... one catch is my boss does not know that15:27
portdirectif so then - mattmceuen those are two really important questions15:27
jamesgui can go next...   Hello, I'm James, working for an open source Linux product company (coincidently same employer as evrardjp). I am still new to OSH, evaluating and prototyping to integrate OSH and Airship into our Openstack distribution. We are looking forward to contribute OSH very soon.15:27
mattmceuenhey jamesgu!15:27
jamesguHi Matt15:28
evrardjpfighting with boss is indeed priceless jayahn :p15:28
portdirectevrardjp/jamesgu: what workloads are you looking to run on osh/airship?15:29
tdocmattmceuen: "normal cloud", also HPC, our customer base is pretty spread out.15:29
jamesguwhat is "normal cloud" here?15:29
portdirectso - everything ;)15:29
evrardjpportdirect: you have a million dollar? Cause that's a million dollar question15:29
tdoctenant spinning up vm's that do god knows what :p15:29
mattmceuen"normal cloud" = the proverbial wordpress I guess? :)15:30
mattmceuenhahaha15:30
mattmceuenthat sounds normal to me tdoc15:30
jamesgu@portdirect: from a a few nodes to hundreds15:30
portdirecttdoc: of course http://images6.fanpop.com/image/photos/33200000/dr-evil-austin-powers-33220839-480-386.jpg15:30
*** hongbin has joined #openstack-meeting-515:30
evrardjpI am still curious on how does it matter portdirect :)15:31
mattmceuenSo portdirect:  your thought is to do this a little more formally @ the PTG, and perhaps get into a little more detail?15:31
portdirectyeah - this is a great start15:31
tdocI also operate our internal private cloud, about 20 nodes, some 500+ VMs for CI purposes.15:31
mattmceuennice15:31
mattmceuenthanks all for sharing, this is very helpful15:31
evrardjpmattmceuen: the PTG is a great place for that, as it is also face to face, so you create stronger bonds between ppl enduring the same pains :p15:31
portdirectI'll get a proper tread started this week, but my initial thought is to create some personas for osh users15:32
mattmceuen+115:32
mattmceuenthanks portdirect15:32
portdirectso we can try to account for these while doing specs/dev15:32
evrardjpportdirect: persona is very important as it can face your documentation15:32
jamesgu+115:32
evrardjpportdirect: maybe start with the docs spec that spread the documentation by areas?15:32
mattmceuenAlright, gotta keep movin' !15:32
portdirect++15:32
mattmceuenhere comes the topic change15:32
mattmceuen#topic Plans to support nodes with different interface names15:32
*** openstack changes topic to "Plans to support nodes with different interface names (Meeting topic: openstack-helm)"15:32
mattmceuentdoc this is you sir15:32
tdocyup15:33
mattmceuenI believe we support this today -- overriding interface names on a per-host basis.15:33
mattmceuenportdirect do we have (or need) a list of what is or is not overridable on a per-host basis to clear up confusion?15:33
tdochmm, i guess I don't know how then...15:33
portdirectmattmceuen: id need to double check, im pretty sure we have some gaps15:34
portdirectmost of our tooling uses magic to ensure consistent names accross hardware.15:34
portdirect(use airship yo!)15:34
tdocI was looking at auto bridge add values in ovs charts and looked like it wasn't there...15:34
portdirectyeah - jayahn's team pulled that out some time ago15:35
mattmceuenThis would be the approach15:35
mattmceuenhttps://docs.openstack.org/openstack-helm/latest/devref/node-and-label-specific-configurations.html15:35
portdirecti think the same functionality should be in the neutron chart15:35
portdirectbut would need to check15:35
portdirectmattmceuen: the issue here is that some of the config values we define are not under the 'conf' key15:35
mattmceuenahh15:35
mattmceuenCan we take this one as a follow-up tdoc?15:36
tdochmm, yeah I might have to dig harder trying to understand all of this15:37
mattmceuenI'll add a flup to next week to report out findings15:37
mattmceuenif you need it sooner though let's chat in #openstack-helm on this topic15:37
mattmceuen#topic Roadmap for Armada15:37
*** openstack changes topic to "Roadmap for Armada (Meeting topic: openstack-helm)"15:37
mattmceuenBroadly speaking about Armada roadmap - it's a part of Airship and is part of the target state of that platform15:38
mattmceuenAlso a standalone deployer that will continue to deploy collections of helm charts in flexible ways15:38
tdocthat was me too, though someone else asked if this is within scope of this meeting...15:38
mattmceuenThere will be a PTG session for AIrship, and it will be a great place to discuss Armada roadmap!15:38
jayahnI did asked that. tdoc.15:39
mattmceuenthe #airshipit channel would be a good place to pose any specific questions (and the PTG)15:39
jayahni was wondering if osh community official recognize armada as a default deployment method? hens, deal armada manifest as first citizen.15:39
mattmceuenArmada is the default way that a number of the OSH contributors plan to consume it15:40
jayahnjust want to check what voice osh community is delivering to users. :)15:40
mattmceuenAnd it's what many of us would recommend (that's why it was built :) )15:40
mattmceuenBut I don't think we want to tie OSH to it in any way strictly speaking15:41
tdocSome on our team watched the presentation from the Austin and kinda got the impression it was presented as more of a poc back then, but it sounds to me like it's much more than that?15:41
mattmceuenOh yes15:41
jayahnOh yes15:41
mattmceuenIt's being used in prod by AT&T & SKT15:41
tdocWe're also evaluating and probably will be using it.15:42
jayahnfor us, only Armada, not other parts of airship.15:42
tdoc+1 here, most likely15:42
mattmceuencool tdoc - the armada devs hang out in #airshipit, and would be eager for any feedback and to help :)15:42
mattmceuenI will move us on15:43
mattmceuen#topic Helm 2.10 - finally TLS is coming to OSH properly15:43
tdocyup15:43
*** openstack changes topic to "Helm 2.10 - finally TLS is coming to OSH properly (Meeting topic: openstack-helm)"15:43
mattmceuenyay!15:43
mattmceuenhttps://review.openstack.org/#/c/588085/15:43
mattmceuenThis is a good one to share15:43
mattmceuenAdding in Helm 2.10 opens the door15:44
mattmceuenportdirect and others are working to get us through it15:44
mattmceuenAnd then cluster TLS bliss15:44
mattmceuenanything else to share or questions?15:45
mattmceuen#topic Ceph - whats going on next?15:45
*** openstack changes topic to "Ceph - whats going on next? (Meeting topic: openstack-helm)"15:45
mattmceuenThis topic is a bit vague :)  Can anyone clarify the intent?  The owner got lost in my copy & paste from last week15:46
srwilkersim not sure what it was meant for, but i hijacked it15:46
mattmceuenlol15:46
mattmceuen    Moving ceph to osh-infra15:46
mattmceuen    https://review.openstack.org/#/c/596880/15:46
mattmceuen    https://review.openstack.org/#/c/596881/15:46
mattmceuen    https://review.openstack.org/#/c/596891/15:46
mattmceuengood call srwilkers15:47
srwilkersthis is likely to be contentious, but i think it's time to move ceph to openstack-helm-infra15:47
srwilkersbonus: it's one of the items on the 1.0 roadmap15:47
mattmceuenIn terms of contentiousness and timing - is the only concern that there's a lot of active work going on in the ceph charts now?  Or additional reasons?15:48
srwilkersyeah, largely because there's a lot of work hitting the ceph charts right now15:48
mattmceuenyup15:48
srwilkersalong with the elasticsearch snapshot work ive been doing15:48
srwilkersonce ceph hits osh-infra though, we can deploy the Elasticsearch s3 snapshot repo backed by rgw's s3 api by default, and expand the elasticsearch helm tests to verify it works15:49
mattmceuenAlright - let's keep moving for now, we can add more specific topics to following week agendas15:49
mattmceuen#topic Team meeting time - any other times that would work well for most team members?15:49
*** openstack changes topic to "Team meeting time - any other times that would work well for most team members? (Meeting topic: openstack-helm)"15:49
srwilkerscould also do some cool stuff, like snapshot the logs gathered during the gate runs and provide them as part of the gate post-run jobs15:49
srwilkersok15:49
mattmceuenSo the OSH team meeting has been at this time for a while15:50
mattmceuenIt doesn't work well for our Korean teammates15:50
mattmceuenBut we also have a lot of north american and european team members who come frequently15:50
jayahntrue, but finding a good time for everyone would be very difficult, since we now have people from europe.15:50
mattmceuenThis is a general poll, not for specific times (that'll take more time) but just for ranges15:50
*** john_W has joined #openstack-meeting-515:51
mattmceuenAre there any general time ranges that would be reasonable for everyone?15:51
mattmceuenjayahn would end of day or beginning of day be better?15:51
jayahndepending on which exact time.15:52
mattmceuensame for tdoc evrardjp jamesgu ?15:52
jamesguI am in NA, west coast15:52
mattmceuenCool - we have several other folks from that time zone as well15:53
evrardjptdoc and I am Europe, so ...15:53
jayahnI am in Korea...15:53
evrardjpso it won't be possible to please everyone, so maybe start rotating?15:53
*** radeks_ has quit IRC15:53
evrardjpif that matters15:53
mattmceuenDoes anyone have any experience with rotating meetings on other teams?  Best practices?15:54
mattmceuenWe may need to put the final stamp on this at the PTG15:54
jayahnlet's get survey on this.15:54
mattmceuenI think a survey is a great idea15:54
mattmceuenI did one once before15:54
jamesgu+115:54
tdocthis is a tough one indeed, current time works for us, though it's pretty late in the day...15:54
jayahnwithout some sort of automatic timezone translator, it is difficult to get an idea no others' time15:55
mattmceuenOk - I am determined to get thru our agenda!15:55
mattmceuen#topic "OpenStack-Helm  Authors" -> "OpenStack Foundation" copyright update15:55
*** openstack changes topic to ""OpenStack-Helm Authors" -> "OpenStack Foundation" copyright update (Meeting topic: openstack-helm)"15:55
mattmceuenwe discussed this a few months ago in the team meeting, and I finally got un-lazy enough to put in a PS15:55
mattmceuenhttps://review.openstack.org/#/q/status:open+branch:master+topic:copyright/osf15:56
mattmceuenThis is just an FYI since it's wide ranging.... ~1400 one line comment changes :)15:56
mattmceuen"OpenStack-Helm Authors" is not a legal entity, and these PS update *just those* copyrights to the OpenStack Foundation.15:56
mattmceuenFinally15:57
mattmceuen#topic PTG Etherpad15:57
*** openstack changes topic to "PTG Etherpad (Meeting topic: openstack-helm)"15:57
mattmceuenReminder to please add content to the etherpad to discuss -- https://etherpad.openstack.org/p/openstack-helm-ptg-stein15:57
mattmceuen#topic Roundtable15:57
*** openstack changes topic to "Roundtable (Meeting topic: openstack-helm)"15:57
mattmceuenjayahn shared some PS needing review15:57
mattmceuenhttps://review.openstack.org/#/c/590184/15:57
mattmceuen    Prometheus-alertmanager: modify wrong variables.15:57
mattmceuenhttps://review.openstack.org/#/c/587812/15:57
mattmceuen    Node-Exporter: allows to set collectors enable/disable15:57
mattmceuenhttps://review.openstack.org/#/c/549824/15:57
mattmceuen    Cinder: add pass message for enabling application15:57
mattmceuenhttps://review.openstack.org/#/c/593991/15:57
mattmceuen    Tempest: add option to execute cleanup always15:57
mattmceuenI will add them to the #openstack-helm channel as well since we are out of time15:57
mattmceuenAlso FYI -- next week portdirect will be leading these! :)15:58
mattmceuenAny other closing thoughts team?15:58
evrardjpnone15:59
evrardjpthanks!15:59
mattmceuenIn that case -- thanks everyone, and have a great week15:59
mattmceuen#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Aug 28 15:59:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-08-28-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-08-28-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-08-28-15.00.log.html15:59
*** gagehugo has left #openstack-meeting-516:08
*** mjturek has quit IRC16:10
*** mjturek has joined #openstack-meeting-516:26
*** njohnston has joined #openstack-meeting-516:30
john_Wquit16:37
john_W!q16:37
openstackjohn_W: Error: "q" is not a valid command.16:37
*** njohnston_ has joined #openstack-meeting-516:38
*** john_W_ has joined #openstack-meeting-516:39
*** njohnston has quit IRC16:39
*** njohnston_ is now known as njohnston16:39
*** john_W_ has quit IRC16:39
*** john_W has quit IRC16:42
*** yamahata has quit IRC17:08
*** yamahata has joined #openstack-meeting-517:41
*** ricolin has quit IRC17:50
*** markvoelker has joined #openstack-meeting-517:51
*** mjturek has quit IRC18:24
*** markvoelker has quit IRC18:32
*** mjturek has joined #openstack-meeting-518:44
*** mjturek has quit IRC18:52
*** mjturek has joined #openstack-meeting-519:00
*** markvoelker has joined #openstack-meeting-519:20
*** radeks_ has joined #openstack-meeting-519:32
*** njohnston has quit IRC19:42
*** njohnston has joined #openstack-meeting-519:43
*** hongbin has quit IRC19:50
*** hongbin has joined #openstack-meeting-519:52
*** slaweq has quit IRC20:40
*** slaweq has joined #openstack-meeting-520:40
*** radeks__ has joined #openstack-meeting-520:41
*** radeks_ has quit IRC20:44
*** radeks__ has quit IRC20:56
*** markvoelker has quit IRC21:05
*** skazi has quit IRC21:51
*** hongbin has quit IRC23:15

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