Tuesday, 2018-01-02

*** markvoelker has joined #openstack-meeting-500:27
*** markvoelker has quit IRC00:31
*** markvoelker has joined #openstack-meeting-501:28
*** markvoelker has quit IRC01:32
*** yamamoto has quit IRC03:27
*** markvoelker has joined #openstack-meeting-503:29
*** markvoelker has quit IRC03:34
*** yamamoto has joined #openstack-meeting-504:01
*** yamamoto has quit IRC04:17
*** markvoelker has joined #openstack-meeting-504:30
*** markvoelker has quit IRC04:35
*** yamamoto has joined #openstack-meeting-504:36
*** yamamoto has quit IRC04:41
*** yamamoto has joined #openstack-meeting-505:44
*** yamamoto has quit IRC05:50
*** tuanla____ has joined #openstack-meeting-506:22
*** markvoelker has joined #openstack-meeting-507:32
*** skazi has joined #openstack-meeting-508:16
*** derekh has joined #openstack-meeting-509:55
*** ricolin has joined #openstack-meeting-510:31
*** markvoelker has quit IRC10:32
*** MarkBaker has joined #openstack-meeting-510:37
*** markvoelker has joined #openstack-meeting-511:32
*** markvoelker has quit IRC11:37
*** markvoelker has joined #openstack-meeting-512:34
*** markvoelker has quit IRC12:38
*** tuanla____ has quit IRC12:40
*** annp has joined #openstack-meeting-513:28
*** markvoelker has joined #openstack-meeting-513:28
*** annp has quit IRC13:43
*** annp has joined #openstack-meeting-513:53
*** zaneb has joined #openstack-meeting-514:05
*** hoangcx_ has joined #openstack-meeting-514:08
*** pall is now known as pabelanger14:45
*** hoangcx_ has quit IRC14:51
*** annp has quit IRC14:53
*** mattmceuen has joined #openstack-meeting-514:59
*** d|k has joined #openstack-meeting-514:59
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Jan  2 15:00:43 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
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
mattmceuen#topic rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
srwilkerso/15:01
icolwello/15:01
*** jayahn has joined #openstack-meeting-515:01
mattmceuenGM all!  Agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-01-0215:01
portdirectO/15:01
mattmceuenPlease add in anything else you'd like to discuss15:01
*** sj019q has joined #openstack-meeting-515:01
jayahno/15:01
d|ko/15:01
mattmceuenYou have a big head this morning @portdirect, it must be your birthday or something :-D15:01
* srwilkers didnt know it needed to be a special occasion15:01
d|kprolly still throbbing from NYE15:01
mattmceuenHappy New Year everyone15:02
sj019qHappy new year.15:02
jayahnHppy new year!15:02
*** gmmaha has joined #openstack-meeting-515:02
gmmahao/15:03
mattmceuenSo on the agenda are some of my new years resolutions for the OSH team :-D15:03
jayahnI already spent two full days in 2018. not new anymore. :)15:03
mattmceuen#topic Brainstorm making OSH more accessible to new contributors15:03
*** openstack changes topic to "Brainstorm making OSH more accessible to new contributors (Meeting topic: openstack-helm)"15:03
mattmceuenThere's still a lot of 2018 left jayahn!15:03
MarkBakero/15:04
*** gmaurer has joined #openstack-meeting-515:04
mattmceuenSo upon reflection, it's become clear to me and others that OSH can be a tough beast to "get into"15:04
mattmceuenTo a large degree, that just comes with the territory.  OSH is the intersection of many different technologies, and very rarely do folks come having mastered them all already15:05
jayahnprobably too many new stuff to know, container, kubernetes, helm..15:05
jayahnyeap15:05
mattmceuenexactly15:05
*** Harsha has joined #openstack-meeting-515:05
portdirectAlso high hardware reqs15:06
mattmceuenSo our challenge to to make the ramp-up process more friendly and successful, so that folks don't get overwhelmed and go home :)15:06
mattmceuenAnd to help it go as smoothly and quickly as possible15:06
sj019qI made an etherpad about onboarding to OSH. Should I go ahead and share it?15:07
mattmceuenI have a few embryonic ideas for how to approach this, around 1) more formalized mentoring relationships, 2) enhancing the onboarding docs to help folks learn the "prereqs"15:07
mattmceuenLet me start a new etherpad15:07
portdirectBoth of those sound like good starting points15:07
mattmceuenIt is a good idea but I suggest let's start with brainstorming15:07
mattmceuenThe key being to come up with stuff that's generally applicable to anyone in the community, whether folks starting in a telco, in the OpenStack community, or the k8s community15:08
mattmceuenIn AT&T we're going to kick off some more formalized mentoring relationships, so stay tuned, those to whom that applies :)  but I'd really like to make that a broad concept in our community team15:09
mattmceuenDo any of you have experience with formal mentoring in a community context?  I know OpenStack has a program like that, but I haven't been through it.  Ideas for how to get it started or pitfalls to avoid?15:10
* mattmceuen sips coffee15:10
jayahncloud you define "mentoring relationships" a bit more? one-to-one or one to several?15:11
portdirectOffice hours?15:11
alanmeadowsProfessor Mceuen?15:11
mattmceuenSo what I think we need is to basically pair up a new team member with someone who knows the ropes already, so that they don't feel / aren't "on their own"15:11
mattmceuenalanmeadows you have a much more professorly demeanor15:12
srwilkersportdirect: ++15:12
mattmceuenoffice hours - great idea portdirect15:12
srwilkersi think the office hours approach works well15:12
jayahnoffice hours sounds good.15:12
mattmceuenwould those be office hours be in common for everyone, or would different... "professors" :) have different office hours?15:13
portdirectusing the material from openstack university would be a great starting point too.15:13
mattmceuen+115:14
portdirectI'd be willing to do an hour a week for office hours, would love to do more but time is a scarce resource atm..15:15
alanmeadowsOne artifact that is time intensive to produce but would pay dividends as an adjucnt to traditional improved documentation would be several animations showing certain key things "at play" and how they work - I have heard feedback that the small animation they produced for the "undercloud" at the OS edge summit finally allowed several people to understand what it was all for15:15
portdirectseems like we have a US, and SK based quorums?15:15
portdirectalanmeadows: you have a link to that?15:16
alanmeadowsI am searching for it now15:16
portdirectwe have some powerpoint masters here in STL.15:16
jayahnthere can be so many thing going "wild" while trying to do osh for the first time. office hour will be good to have, but can fall into "not really helpful" hours. we must have a good docs for anyone to follow to minimize unnecessary questions. (sorry, frankly speaking, i have not checked the recent osh doc progress)15:16
jayahnanimantion would be very good tools to make it easy to follow. :)15:16
alanmeadowshttps://youtu.be/BdIzryvX7gc?t=11m37s15:16
srwilkersyeah, they'd go hand in hand jayahn.  portdirect has been doing really great work in making sure that the docs we reference are gated and functional15:16
mattmceuenWhat would you recommend for getting up to speed on k8s?  I've heard K8s The Hard Way a lot, but that seems more deep than broad and more ops than dev, so I'm wondering if there's anything good that has a dev perspective15:17
portdirectre the docs - I've been doing all i can to make sure they work, and are gated, but have not had time to add anywhere near the level of explanation that is really required for a quality product, would be great for people to take this task on.15:18
portdirectmattmceuen: thats a can-o-worms :) openstack-the-hard-way anyone?15:19
srwilkersportdirect: i've been gradually building up the lma docs.  i'll start branching out and submitting patches for getting the other doc bits shored up as im able and waiting for gate runs15:20
mattmceuenI definitely think that we should focus our own documentation efforts on OSH, rather than documenting k8s or openstack15:20
gmmahamattmceuen: pulling out the steps of installing the required packages and init followed by a nginx or busybox container would be good to show how k8s run. (i was inducted that way and thoyght it was good)15:20
mattmceuen(and instead linking to existing high-quality curated resources for openstack and k8s)15:20
portdirect++ to that mattmceuen15:21
portdirectk8s is just as big a world as openstack, there is no point reinventing the wheel.15:21
mattmceuengmmaha - I like that approach.  Start simple before digging deep.  Do you know whether there's a good guide out there that takes that approach?15:22
mattmceuentutorial-grade?15:22
gmmahamattmceuen: i don't. someone had that in their gisdt and that's what i followed.15:22
gmmahabut we can write one for OSH15:23
mattmceuenWell, in the interest of time, we may need to table the convo and defer it to the etherpad I created, and revisit next week -- that will give us all a chance to google.  Sound good?15:23
mattmceuenhttps://etherpad.openstack.org/p/osh-onboarding-brainstorming15:23
gmmaha+115:23
alanmeadowsAt some point, it may make sense to create a map of the k8s concepts we employ, with links to their specific k8s documentation, but that seems like a nice-to-have.  This would just help augment a basic k8s education.  In other words, OSH leverages the following: Init Containers, Annotations, Life Cycle, ...  Thats a rather simple task of building that link skeleton.15:23
d|kit seems to me there are two, perhaps overlapping, audiences for the documentation: people who want to bring up OSH and use it, and contributors who need to understand how best to fit their work into the structure.15:23
mattmceuenCool.  I jotted down a couple things we touched on but not all yet15:23
mattmceuenGood thought alanmeadows15:23
mattmceuengood start to this topic guys - please add more ideas/resources to the etherpad, and let's continue discussing next week!15:24
mattmceuen#topic Connecting the OSH team to the wider community15:25
*** openstack changes topic to "Connecting the OSH team to the wider community (Meeting topic: openstack-helm)"15:25
mattmceuenThis follows from the previous topic15:25
mattmceuenWe are basically dragging folks into new communities that they were not a part of before, and we need to make sure they get properly introduced :)15:25
portdirectso we need to get better at being advocates :)15:26
mattmceuenAnd once they are, that we're sharing knowledge15:26
mattmceuenExample:  I come from OpenStack, and I only recently learned that there's a SIG-OpenStack k8s group.  I'm planning to start joining that one15:26
mattmceuenThat would be good stuff to share within the team15:26
mattmceuenAlso letting folks know the latest news in the k8s world - the key bits from release notes, etc15:27
mattmceuenThis is stuff we learn but don't always share - let's start getting them into the OSH chat room as things-of-interest15:28
mattmceuenOther thoughts on we can use OSH as a bridge between communities, specifically getting new team members plugged in in meaningful ways?15:29
mattmceuenIf you think of any more, jot 'em down in the same etherpad above15:31
portdirectI think exploding openstack is a great way to go as a bridge, I'm currently working on a superuser piece for using ironic with osh15:31
portdirectand another for stand alone cinder15:31
mattmceuennice!15:31
mattmceuen#topic Feedback welcome and encouraged!15:32
*** openstack changes topic to "Feedback welcome and encouraged! (Meeting topic: openstack-helm)"15:32
mattmceuenThis is just a Public Service Announcement15:32
mattmceuenI'm eager to serve you as your PTL - please don't hesitate to let us all know feedback and ideas in the OSH chat room, or to PM me if it's something you'd like to let me know in private.15:33
mattmceuenLet me know what I can do, and I'll do the same :)15:33
jayahnsure. :) you are always being a very good help.15:33
mattmceuenthanks jayahn15:34
mattmceuen#topic CICD focus meeting next week?15:34
*** openstack changes topic to "CICD focus meeting next week? (Meeting topic: openstack-helm)"15:34
mattmceuenWe have had one, very successful, automation / CI / CD / testing oriented meeting so far15:34
mattmceuenIt was intended to be monthly, then holidays happened15:34
mattmceuenWant to kick it off again, next week?15:34
jayahnYes, as planned. (we said the every second week of the month, didn't we?)15:35
portdirectthink so15:35
mattmceuenoh did we? I forgot.  Well that gets us right back on schedule.15:35
mattmceuenLet me get the agenda to you early then:  https://etherpad.openstack.org/p/openstack-helm-meeting-2018-01-0915:36
mattmceuenLet's start adding in any topics we'd like to discuss, and that'll also help make sure we get all the right folks in the meeting15:36
jayahngood :)15:37
mattmceuen#topic  Show and tell15:37
*** openstack changes topic to "Show and tell (Meeting topic: openstack-helm)"15:37
mattmceuenJust one more New Years Resolution15:38
mattmceuenOftentimes the topics in our weekly meetings are around someone expouding on the work they're doing in some corner of OSH15:38
mattmceuenI think these are incredibly valuable, and help keep us from getting too isolated in our own charts15:38
mattmceuenSo I want to add a standing agenda item to solicit ideas15:39
mattmceuen... for what to include next time.  The basically - what would you like to learn?15:40
mattmceuenTalking about it in team meeting gives folks a whole week to prepare :)15:40
jayahnI am not following.15:40
mattmceuenLet me try again15:40
mattmceuenMy boss came and tapped me on the shoudler during that exchange and threw me off15:41
jayahnah.. now i am getting it.15:41
jayahna week advance noticement (or request) on things want to hear next time.15:42
jayahnam i right on this?15:42
mattmceuenThere have been really good topics in our weekly meetings where folks describe the context and an overview for the things they're working on.  Lots of team members don't understand all the spooky corners of OSH yet, and every week I want to solicit ideas from the team of things they'd like to discuss "next time"15:42
mattmceuenyup!15:42
mattmceuenWould this be valuable?15:42
jayahnokay. got it.15:42
sj019qI think seeing what people are working on would help ramp me up for user stories.15:43
mattmceuenperfect15:43
gmaurerI agree with sj019q15:43
jayahnyes, I think it can help. since we are not a team seeing everytime, everyday. this type of communication method will be good to have15:43
mattmceuenYeah - I'll call it "knowledge sharing", that sounds more professional than "show and tell" :)15:44
mattmceuenwhich for those who did not grow up in the U.S. is something kindergarteners do in school15:44
mattmceuenSo on that note - are there any topics you guys would like to learn more about in an upcoming meeting?  If they're test automation related, we can cover them next week, and otherwise the following week15:45
jayahnah.. that has that backgroud meaning15:45
mattmceuenjayahn:  yes, like "look at the macaroni picture I made of my family"15:46
mattmceuen... which is the topic to beat15:46
jayahnhow testing is done in osh gate. (probably i just need to read docs and code)15:46
mattmceuenI will assign srwilkers to do a macaroni picture if we don't come up with something better.  Whew, jayahn saved you Steve15:47
jayahnto learn how to contribute "test" side of osh gate15:47
srwilkersmattmceuen: my life is nothing but making macaroni charts, so this will be easy ;)15:47
jayahndamn.. i like srwilkers doing macaroni picture better than what I just typed15:47
mattmceuenhahaha15:47
srwilkershahaha15:47
mattmceuenjayahn - that's a good one, portdirect, could you give a quick overview of that next week?15:48
jayahnWe will compare that with our test method to figure out how we can minimize differences and so more contribution. :)15:48
mattmceuen+115:49
mattmceuenOk - last but not least15:49
mattmceuen#PS needing eyes and reviews15:49
jayahnhm can i do armada one here?15:49
mattmceuen#topic PS needing eyes and reviews15:50
*** openstack changes topic to "PS needing eyes and reviews (Meeting topic: openstack-helm)"15:50
jayahnsince alanmeadows is here. :)15:50
mattmceuenjayahn sure, we'll share it with the armada team :)15:50
jayahnhttps://review.gerrithub.io/#/c/389047/ >> feat(override): Add to override list type of value15:50
jayahnsimeple addition, and seems like no one has a serious issue. :)15:51
jayahnpls review it.15:51
jayahnthat ps will make us very happy to use armada more. :)15:51
mattmceuenOn it.15:52
mattmceuenSome of the Armada guys had lots of vacation in Dec, and I'll make sure we get much better traction now in the new year.15:53
*** ricolin has quit IRC15:53
mattmceuenalright15:53
jayahnportdirect:15:53
mattmceuen#topic roundtable15:53
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:53
jayahnthis is for preventing zombie process? https://review.openstack.org/#/c/530599/15:53
jayahnpls add hyunsun as reviewer. :)15:54
portdirectjayahn: not explicity, but to add robustness to the network namespaces that the neutron agents manage, without shared mounts i wouldnt use it15:54
portdirectI should really add (DNM) to the title15:54
portdirectbut I do have something i'd like to bring up15:55
portdirecthow do people feel about making heat a required service for osh?15:55
portdirectso that the default bootstrap jobs could leverage it15:55
portdirectthis goes counter to my usual stance of make eveything as loose as possible15:56
jayahnsomething I need to talk with folks in my team.15:56
portdirectbut I'm continually mulling it over in my mind..15:56
portdirectjayahn: would be great for your peeps to have a think about it15:57
jayahnyeap.15:57
portdirectI'm totally up for being told "dont be so silly port direct" ;)15:57
jayahnyou have ps on this, right?15:57
mattmceuenportdirect is there any good way for the bootstrap job to use it "if it's there", and skip if it's not?15:57
portdirectjayahn: no15:57
portdirectmattmceuen: there is, but its a bit ugly/verbose15:57
jayahni remember seeing heat somewhere.....  in dream?15:57
jayahnah. okay15:58
alanmeadowsportdirect: what does that forced requirement buy?15:58
alanmeadowsis there something you can do there that you cant without it?15:58
alanmeadowsjayahn: I think we call that a nightmare15:58
jayahnah.. https://review.openstack.org/#/c/530592/15:59
jayahnthis one :).. consilidating heat... i remembered. :)15:59
mattmceuenWe're about out of time - let's move this one to the OSH chat15:59
jayahnnot important. :)15:59
mattmceuenthanks all!15:59
portdirectalanmeadows: it allows cleaner management of things like flavours/images15:59
mattmceuen#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Jan  2 16:00:01 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
portdirectbut does not by us anything we cant do without some good old bash16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-01-02-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-01-02-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-01-02-15.00.log.html16:00
*** gmmaha has left #openstack-meeting-516:00
*** sj019q has quit IRC16:00
*** d|k has left #openstack-meeting-516:01
*** gmaurer has quit IRC16:04
*** renmak__ has joined #openstack-meeting-516:13
*** iyamahat has joined #openstack-meeting-516:20
*** iyamahat has quit IRC16:24
*** iyamahat has joined #openstack-meeting-516:31
*** mattmceuen has left #openstack-meeting-517:18
*** iyamahat has quit IRC17:32
*** iyamahat has joined #openstack-meeting-517:33
*** iyamahat has quit IRC17:33
*** iyamahat has joined #openstack-meeting-517:35
*** iyamahat has quit IRC17:35
*** iyamahat has joined #openstack-meeting-517:36
*** derekh has quit IRC17:59
*** renmak__ has quit IRC18:02
*** renmak__ has joined #openstack-meeting-518:20
*** renmak__ has quit IRC18:21
*** renmak_ has joined #openstack-meeting-518:58
*** MarkBaker has quit IRC20:01
*** gmaurer has joined #openstack-meeting-520:07
*** gmaurer has quit IRC20:07
*** MarkBaker has joined #openstack-meeting-520:16
*** iyamahat has quit IRC20:30
*** yamahata has quit IRC20:35
*** renmak_ has quit IRC21:48
*** Harsha has quit IRC22:29
*** iyamahat has joined #openstack-meeting-523:00
*** yamahata has joined #openstack-meeting-523:18

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