Tuesday, 2018-10-23

*** mjturek has quit IRC00:22
*** markvoelker has joined #openstack-meeting-501:25
*** yamahata has quit IRC01:40
*** munimeha1 has quit IRC03:01
*** yamahata has joined #openstack-meeting-503:48
*** roman_g has quit IRC04:10
*** yamahata has quit IRC04:19
*** yamahata has joined #openstack-meeting-504:19
*** skazi has quit IRC04:53
*** ralonsoh has joined #openstack-meeting-505:40
*** spsurya has joined #openstack-meeting-505:49
*** skazi has joined #openstack-meeting-506:18
*** slaweq has joined #openstack-meeting-506:43
*** njohnston has quit IRC06:47
*** njohnston has joined #openstack-meeting-506:47
*** skazi has quit IRC07:18
*** skazi has joined #openstack-meeting-507:31
*** derekh has joined #openstack-meeting-508:29
*** skazi has quit IRC09:11
*** skazi has joined #openstack-meeting-509:58
*** ianychoi has quit IRC10:22
*** ianychoi has joined #openstack-meeting-510:25
*** markvoelker has quit IRC11:45
*** markvoelker has joined #openstack-meeting-512:36
*** markvoelker has quit IRC12:37
*** markvoelker has joined #openstack-meeting-512:41
*** markvoelker has quit IRC12:56
*** skazi has quit IRC13:16
*** roman_g has joined #openstack-meeting-513:34
*** roman_g has quit IRC13:43
*** roman_g has joined #openstack-meeting-513:45
*** sgrasley has joined #openstack-meeting-513:46
*** mjturek has joined #openstack-meeting-513:47
*** hongbin has joined #openstack-meeting-514:00
*** njohnston has quit IRC14:03
*** annp_ has joined #openstack-meeting-514:04
*** skazi has joined #openstack-meeting-514:35
portdirecto/15:00
portdirect#startmeeting openstack-helm15:00
openstackMeeting started Tue Oct 23 15:00:23 2018 UTC and is due to finish in 60 minutes.  The chair is portdirect. 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
portdirecthey peeps, we'll give it a few mins for people to turn up15:00
jayahno/15:01
*** mattmceuen has joined #openstack-meeting-515:01
srwilkershello15:01
mattmceueno/15:01
portdirectlooks like etherpad is down :(15:01
portdirectlets use here instead for this meeting: https://beta.etherpad.org/p/yWMzLMvJTV15:02
jayahnYeap. Confirmed15:02
mattmceuennow that's a fancy etherpad15:02
*** cliffparsons has joined #openstack-meeting-515:02
jayahnLoading..15:02
jayahnOh, I always like beta15:03
portdirectok - I'm afraid people will have to copy topics over :(15:03
evrardjpo/15:05
evrardjpetherpad is up again15:05
portdirectlol15:05
portdirectso we also have this: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-10-2315:05
portdirecteveryone run to the other side of the ship!15:05
portdirectlets go15:05
portdirect#topic summit-prep15:06
*** openstack changes topic to "summit-prep (Meeting topic: openstack-helm)"15:06
portdirectso the berlin summit is fast approaching15:06
portdirectI'm aware of three items that directly touch on OSH15:06
portdirectare there any i missed?15:06
evrardjpthe indirect15:06
*** john_W has joined #openstack-meeting-515:07
portdirect;)15:07
roman_go/15:07
john_Wo/15:07
jayahnYou have osh hands-on?15:07
portdirectevrardjp: you know of any that should be on this - I know there are some cross cutting deployment tooling sessions15:07
portdirectjayahn: yes15:07
evrardjpDeveloping a Standard Deployment Tools Comparison and Deployment tools feedback (Thursday from 9:50 to 11:30) are the cross deployment tools sessions15:07
portdirectevrardjp: awesome - I'll be sure to attend these15:08
portdirectwho else is planning on being in berlin?15:08
evrardjpportdirect: disclaimer, some of those sessions have been attempted in the past and were not specially successful (to what I heard). I think it's still worth spending some cycles to at least hear/be present there.15:09
mattmceuenI will be there - I 'll try to make that too evrardjp is possible15:09
evrardjpI will be in Berlin15:09
jayahnI will be .. with 3 other folks.15:09
evrardjpjayahn: that's great news!15:09
portdirectevrardjp: sounds like open sauce - full of tomatoes.15:10
jayahnevrardjp: it is my honor to be good news.. :)15:10
evrardjp:)15:10
portdirectone thing I'd really appreciate help is on the: Project onboarding session15:11
evrardjpThat was my next question :p15:11
jayahnOkay.15:11
srwilkersi will not be :(15:11
portdirectas this is somthing we really need to get better at15:11
mattmceuenagree15:11
portdirecti'll start https://etherpad.openstack.org/p/openstack-helm-berlin-onboarding15:11
mattmceuenIf we can craft material for that that could be directly reusable in a non-summit context, that would be neat15:11
evrardjpI am not onboarded on this project, so I will attend to be onboarded :p I can give you a few tips but it's generally depending on the audience15:12
*** jamesgu_ has joined #openstack-meeting-515:12
portdirectbut please feel free to add your pain points, highlights etc15:12
evrardjpa few general 'project onboarding' tips*15:12
mattmceuen(the best example of "reusable summit material" being of course portdirect's hands-on scripts that turned into our gates :) )15:12
portdirectand the worst - i get both ends of the spectrum here i think ;)15:13
evrardjpI think it's a very important point portdirect15:13
evrardjp(the pain points)15:13
portdirectwhich neatly brings us onto the next topic i think15:14
evrardjpas these will be the friction elements and things harder to onboard.15:14
portdirect++15:14
portdirect#topic Gating questions15:14
*** openstack changes topic to "Gating questions (Meeting topic: openstack-helm)"15:14
portdirectevrardjp: the floor is yours15:14
evrardjpI thought the summit discussion was not over!15:15
portdirectoh - sorry!15:15
* evrardjp quickly takes existing notes :)15:15
portdirect#topic back-to-the-summit15:15
*** openstack changes topic to "back-to-the-summit (Meeting topic: openstack-helm)"15:15
portdirectanyone have anything else to add/raise?15:15
evrardjpI had a question for summit15:15
jayahnOh..15:16
evrardjpwho will be presenting the project update session?15:16
evrardjpportdirect I guess?15:16
mattmceuenportdirect! :p15:16
jayahnptl?15:16
mattmceuenI will be in the background with tomatos15:16
portdirectI will be, along with mattmceuen15:16
evrardjpwell I think it would be nice mattmceuen is there15:16
evrardjpgreat15:16
portdirectI cant think of a better person to describe where we came from than mattmceuen15:16
*** skazi has quit IRC15:16
evrardjpindeed ;)15:17
jayahnThen, I will be in the background with tomato!15:17
evrardjpother question -- is there any OSH have forum sessions in Berlin?15:17
portdirectits why hes coming to berlin :D15:17
portdirectnot directly15:18
srwilkersill throw tomatoes at his desk while hes gone15:18
portdirectI need to add them, but there are some that i think we have to attend15:18
portdirectthere is one on container security15:18
evrardjpsrwilkers: take pictures for sharing on the channel :)15:19
evrardjpportdirect: sounds nice. I think we should eventually find time to discuss together, maybe organise meal. But that can wait I guess :)15:19
roman_g🍅🍅🍅15:20
mattmceuenThere is a forum session for cross-container-team security, to share lessons-learned15:20
evrardjptogether == with the team15:20
portdirecthttps://www.openstack.org/summit/berlin-2018/summit-schedule/events/22797/cross-project-forum-securing-containerized-infrastructure15:20
mattmceuenso all container-related openstack teams are invited / encouraged to participate in that!15:20
evrardjp#link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22797/cross-project-forum-securing-containerized-infrastructure15:20
evrardjpthanks portdirect mattmceuen for the information!15:21
mattmceuenevrardjp let's definitely grab some grub as a team, good idea :)15:21
portdirectevrardjp: may need to be lunch - but we will find time15:22
evrardjpportdirect: as long as you're bringing the picture of srwilkers I guess we'll have enough 'team' presence? ;p15:23
srwilkersi have just the picture to send15:23
portdirectevrardjp: i wish that were the case15:23
portdirecta picture of srwilkers is one thing15:23
evrardjpI have nothing more to add on the summit topic15:23
portdirectbut the reality is so much more15:23
srwilkerscan also facetime me in -- i can adjust my sleep schedule as needed15:23
evrardjphaha15:24
portdirectit would have been great to get anticw and lamt there as well15:24
evrardjpindeed!15:24
portdirect#topic Gating questions15:24
*** openstack changes topic to "Gating questions (Meeting topic: openstack-helm)"15:24
portdirectyour up evrardjp ;) sorry for pulling the trigger early last time15:25
evrardjpthanks for giving me time on said questions15:25
evrardjpno worries portdirect :)15:25
evrardjpso two questions for you, to clarify something more that reporting the status, sorry for that.15:25
evrardjpfirst, I'd like to talk about pre-run and expectations15:25
evrardjpAre there any actions that needs to be taken in Zuul CI that contributors are expected to do before deploying OSH? Install docker? Update their systems? Configure specific networking on each host? Configure specific package source mirror?15:25
evrardjpI think clarity would help on the pre-run steps, aasnd I am not sure the documentation states the expectations properly (or I misread it, which is possible...)15:26
evrardjpas I am not sure*15:26
portdirectevrardjp: it does not spell this out fully :(15:27
evrardjpI'd also like to know the opinion of the community there: What is happening on their environment? Do you integrate more with your existing practices, or do you completely use from a clean system (ubuntu/centos/whatever)?15:27
portdirectthere was an effor to change this - though it dies on the vine15:27
evrardjpportdirect: the idea behind those questions is reduce unnecessary code and clarify scope15:28
portdirectevrardjp: i think most people are integrating with existing systems for dev work15:28
portdirectand occasionly spinning up fully 'clean' envs when requried15:28
portdirecti know this is how mattmceuen, srwilkers, lamt and myself are working at least15:29
jayahnWhat is exaxtly integrating witj existing system? Something like running it on your laptop?15:29
portdirect^ this is how i read it15:29
portdirectbut we should clarify :)15:29
evrardjpjayahn: like integrating with any existing infrastructure: ranges from a clean machine to  a machine with kubernetes installed , and a machine with docker installed is inbetweenn15:30
evrardjpstorage is another topic on "integration with any existing infrastructure"15:31
evrardjpif people are assumed to have a ceph deployed or a nfs deployed it's not the same.15:31
jayahnOkay got it. Will be back in 3min with answer. I am currently entering elevator at my apartment building15:32
evrardjpKeep in mind I don't mean removing any current developer "convenience" scripts. I am just wondering what is convenience and what is scope.15:32
evrardjpseparating said domains will help on simplifying gating down the line.15:32
evrardjpAnyway, I have my first set of questions asked to the community, I will wait for feedback next week, if you don't mind15:33
portdirecti think its in scope to have a 'devstack' like exp for developers15:33
evrardjpthat sounds understandable15:33
evrardjpportdirect: should we draft this goals/mission/delimiters somewhere in the docs?15:34
portdirectevrardjp: i think the etherpad you started would be a great place to start this15:34
mattmceuenagree15:34
evrardjp(complementing https://docs.openstack.org/openstack-helm/latest/readme.html#mission basically)15:34
portdirectI'll also reach out to rich wellum, we did a load of work there to make this clearer though i must confess we lost it :(15:35
evrardjpthanks. Keep in mind the idea is just for clarifying gate scope. I want to avoid "repeating ourselves" and putting barriers/limits helps at my work.15:35
*** ianychoi_ has joined #openstack-meeting-515:36
evrardjplet's go for the second question there?15:36
portdirectgo for it15:36
* portdirect notices rwellum is here - you still about?15:37
evrardjplet's talk about post-run. It's long and I am not sure how to parse it, how useful it is. I'd be willing to simplify it, but I am a noob. So I am proposing something: Is it okay to have multiple levels of debug, and by default having minimum output?15:37
portdirectevrardjp: its very-very useful15:37
portdirectthough it may capture too much in some places, and not enough in others15:38
mattmceuenis the idea that in gating, it would have lots of debug, and in a dev env it would not evrardjp?15:38
evrardjpI am thinking that people having failure could temporarily enable extra debugging on the post_run assuming we have defined that15:38
portdirecta refactor would certainly be good15:38
mattmceuenor just to leave big-debug for special occasions?15:38
evrardjpmattmceuen: the only impact would be in openstack ci15:38
evrardjphave a minimal debug like this (to be discussed/improved together): see comment in https://gist.github.com/evrardjp/a0f58e1304aaa78d3a8cacf7e546549215:39
portdirectevrardjp: i started a thing like that15:40
portdirect2 sec15:40
*** ianychoi has quit IRC15:40
portdirecthttps://review.openstack.org/#/c/550467/15:40
evrardjpthen the idea would be, should somewant want to increase logging, he can change the job definition in the repo to temporarily "increase logging"15:41
portdirectmay be worth updating?15:41
portdirectis there a reason you are wanting to decrease logging in the gate?15:41
evrardjpportdirect: yes, while we can increase post jobs timeouts, I am not so sure the resulting artifacts are useful for most of the runs15:42
evrardjpso we are taking infra disk space, inodes, and cpu resources for nothing15:42
evrardjp(because a lot of the things we gather are quite IO intensive)15:43
evrardjpor it looks like it, as sometimes it takes minutes to get responses from k8s...15:43
portdirectevrardjp: ok - just wanted to check you and i were thinking alike15:43
mattmceuenif something fails in gate, and we don't have the logs to troubleshoot it, would there be a way to trigger the job again with extra debug logging?15:43
mattmceuenor would it require a developer to ad-hoc run the gate locally?15:44
portdirecti think we can probably cut about 50% of some of the things at a sweep - eg we get yaml and txt output for many objects15:44
portdirectso we could prob just get yaml without loosing anything15:44
evrardjpmattmceuen: I'd say not without a code change, but it could be possible with a code change15:44
mattmceuengotcha15:44
portdirectit would just be a case of adding a conditional round a few things15:44
evrardjpprecisely15:45
portdirectcan we leverage zuul to increase longging on a retry automagicly?15:45
portdirect*logging15:45
evrardjpI doubt that, but I will check.15:45
jayahnautomagically...... Good word. :)15:46
evrardjpportdirect: ok so I'd like we discuss this together: talking about things we can sweep.15:46
srwilkerswould it be sane to have experimental jobs that can be triggered that include the difference between what's offered by default and the more "verbose" option?  not sure if that makes sense or not, but if i were to be messing with something that really required me to dig deep enough to need everything, it seems it'd be helpful to just fire off an experimental check instead of having to wait for a potential failure15:46
srwilkersbut maybe that's just me15:47
evrardjpCan we prepare this conversation for next week? (Goal: Explicitly listing what needs to be 'the minimum a developer expects from zuul' 'the maximum a developer could need from zuul'15:47
portdirectevrardjp: sure - i think that would help here15:47
evrardjpsrwilkers: I thought of that too. I might have a mix of both in my ideas.15:47
evrardjpbut I'd rather speak about what needs to be done now, rather than how.15:48
evrardjpthanks for listening to me, sorry if I took a long time in the meeting15:49
* evrardjp giving the mic back to portdirect15:49
portdirectevrardjp: you always bring the hard topics15:49
portdirectand thats somthing you should never be sorry for15:50
portdirect#topic roundtable & reviews15:50
*** openstack changes topic to "roundtable & reviews (Meeting topic: openstack-helm)"15:50
evrardjpI agree with you there, but it's still a community meeting, there are other people than me that deserve speak time15:50
portdirectwe are out of items on the Agenda15:51
portdirectare there any other topics people would like to bring up15:51
evrardjpwoot open discussion!15:51
evrardjpthanks for the reviews portdirect srwilkers and others!15:52
evrardjpthat's all I had to say.15:52
srwilkersevrardjp: of course :)15:52
srwilkersthe early morning chats are always a pleasure15:52
portdirectsrwilkers: before 9am is too early for humans15:53
jayahnㅜ.ㅜ......15:53
* srwilkers suddenly questions what he is15:53
portdirectwe all do srwilkers15:53
portdirectand with that cheap insult15:53
portdirectlets wrap up for today15:54
portdirect#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:54
openstackMeeting ended Tue Oct 23 15:54:08 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-23-15.00.html15:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-23-15.00.txt15:54
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-23-15.00.log.html15:54
evrardjpthanks portdirect for holding the meeting, thanks everyone for attending!15:54
*** john_W has quit IRC16:00
*** skazi has joined #openstack-meeting-516:04
*** annp_ has quit IRC16:16
*** iyamahat has joined #openstack-meeting-516:33
*** yamahata has quit IRC16:36
*** iyamahat has quit IRC16:41
*** cliffparsons has quit IRC16:45
*** derekh has quit IRC17:00
*** iyamahat has joined #openstack-meeting-517:05
*** iyamahat has quit IRC17:05
*** iyamahat has joined #openstack-meeting-517:06
*** iyamahat_ has joined #openstack-meeting-517:15
*** iyamahat has quit IRC17:18
*** yamahata has joined #openstack-meeting-517:24
*** skazi has quit IRC17:56
*** ralonsoh has quit IRC17:57
*** irclogbot_3 has joined #openstack-meeting-518:35
*** mjturek has quit IRC19:46
*** mjturek has joined #openstack-meeting-520:14
*** mjturek has quit IRC20:39
*** mjturek has joined #openstack-meeting-520:40
*** mjturek has quit IRC20:41
*** mjturek has joined #openstack-meeting-520:44
*** spsurya has quit IRC21:38
*** slaweq has quit IRC21:39
*** slaweq has joined #openstack-meeting-522:05
*** mjturek has quit IRC22:08
*** slaweq has quit IRC22:38
*** hongbin has quit IRC23:10
*** slaweq has joined #openstack-meeting-523:11
*** roman_g has quit IRC23:43
*** slaweq has quit IRC23:45
*** roman_g has joined #openstack-meeting-523:45
*** mjturek has joined #openstack-meeting-523:59

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