Tuesday, 2018-10-09

*** mjturek has quit IRC00:04
*** TuanVu has quit IRC00:12
*** lemko has quit IRC00:43
*** slaweq has joined #openstack-meeting-501:11
*** slaweq has quit IRC01:15
*** iyamahat__ has quit IRC01:55
*** skazi has quit IRC05:05
*** lemko has joined #openstack-meeting-505:42
*** iyamahat has joined #openstack-meeting-505:44
*** skazi has joined #openstack-meeting-505:51
*** skazi has quit IRC05:51
*** slaweq has joined #openstack-meeting-506:58
*** ralonsoh has joined #openstack-meeting-507:24
*** roman_g has joined #openstack-meeting-507:49
*** markvoelker has joined #openstack-meeting-510:25
*** markvoelker has quit IRC10:58
*** TuanVu has joined #openstack-meeting-511:15
*** TuanVu has quit IRC11:20
*** markvoelker has joined #openstack-meeting-511:51
*** njohnston has joined #openstack-meeting-512:46
*** hongbin has joined #openstack-meeting-513:48
*** annp_ has joined #openstack-meeting-513:56
*** mjturek has joined #openstack-meeting-513:56
*** mugsie has joined #openstack-meeting-514:14
*** gagehugo has joined #openstack-meeting-514:54
*** munimeha1 has joined #openstack-meeting-514:56
portdirecto/15:00
mattmceuen\o/15:00
portdirect#startmeeting openstack-helm15:00
openstackMeeting started Tue Oct  9 15:00:40 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
portdirect#topic rollcall15:00
*** openstack changes topic to "rollcall (Meeting topic: openstack-helm)"15:00
mattmceueno\15:00
roman_go/15:01
lamt\o15:01
srwilkerso/15:01
srwilkerslook at mattmceuen slapping himself on the head15:01
portdirectlets give it 2 mins for anyone else to to turn up15:01
mattmceuenthat is me hanging upside down15:01
jamesguo/15:01
portdirectok - lets kick off15:03
portdirectthink it may ba quick on this week :)15:04
portdirect#topic Image building in infra15:04
*** openstack changes topic to "Image building in infra (Meeting topic: openstack-helm)"15:04
portdirectso - for a long time we have been pretty lax in our image building15:04
evrardjpo/15:04
portdirectthis week i really want to move that to infra15:04
portdirectand so will get the image build jobs up15:05
portdirectI'll probably just use the loci jobs if i can15:05
evrardjpso you want to move ALL image building business into -infra ?15:05
evrardjpincluding openstack ones?15:05
portdirectyeah i think so15:05
portdirectapart from them :)15:06
evrardjpok15:06
evrardjpthat's fine for me, it's a common place then.15:06
portdirecti'd like to get those out of the repo if possible - but we need to start somewhere15:06
portdirectand theres a few that are kinda osh specific - eg our libvirt image15:06
portdirectand some of the lma stack15:06
evrardjpwell I was thinking of using a different job for image building so putting them all in the same place makes thing easier.15:06
portdirect++15:06
portdirecti dont think theres too much more here atm?15:07
portdirectok to move on?15:07
jamesgucool. In the same area, we are starting the dev work add opensuse based docker files and loci.sh: https://storyboard.openstack.org/#!/story/2004014, https://storyboard.openstack.org/#!/story/2004015. Probably should holding check in after the relocation is completed?15:07
jamesguhold checking in*15:08
portdirectfor the 1st ones - I think the dockerfiles can come in anytime15:08
jamesguokay15:08
portdirectfor the openstack service themselves - maybe this would be the perfect time to move those jobs out of openstack helm completely?15:08
* roman_g would start with stock images and work on migration Ubuntu->SUSE in other parts of projects15:09
jamesgudo you mean move to openstack-helm-infra or?15:10
evrardjpportdirect: OSH needs images right now, and we cannot move them out to LOCI quite yet (I cannot do it without discussion+help at least)15:10
portdirectI understand that evrardjp  - though we should get the ball rolling there15:10
portdirectcan we get this as a topic in the next loci meeting?15:11
evrardjpso it makes sense for me to do it in two phases... 1) to get it moved in osh-infra 2) move images building everywhere upstream where possible15:11
evrardjpportdirect: that sounds nice to me15:11
portdirectwe need to find the stone SamYaples been hiding under15:11
evrardjpportdirect: must be a big one15:12
evrardjpdue to the fact I didn't see him recently15:12
portdirectyeah - i think hes been snowed under with work :(15:12
portdirectok - lets move on15:13
portdirect#topic Gate status15:13
*** openstack changes topic to "Gate status (Meeting topic: openstack-helm)"15:13
portdirectsteve - I think this was yours?15:13
srwilkersyeah, it was15:13
evrardjpI think it's good to sync, as there are many efforts started15:13
srwilkersso it's clear there's a lot of work going on with the gates at the moment, and i think it's trying to tackle multiple things at once15:14
portdirectoh wait: I'm not sure i put the etherpad link anywhere: https://etherpad.openstack.org/p/openstack-helm-meeting-2018-10-0915:14
* portdirect sorry for inter-ruption15:14
srwilkersi really think we should approach this as a multiple step process instead of trying to solve everything all at once15:14
evrardjpsrwilkers: I agree15:14
srwilkersin my mind, the issues we need to solve are:15:14
evrardjpsrwilkers: we have written these in an etherpad, right?15:15
evrardjpI sadly have lost said etherpad link15:15
srwilkers1. get all of our failing jobs passing, with the goal of getting our nonvoting jobs back to voting15:15
evrardjpstep 1 can be done without gate changes in itself15:16
portdirectmattmceuen: is steve still here?15:17
evrardjpbut that's still a gate state :)15:17
evrardjpsrwilkers: step 2 is?15:17
portdirectevrardjp: mostly i agree, i think this is very much tied to steves 2nd point in the etherpad15:18
portdirect2. Reduce overlap between jobs where possible (ie: don't deploy services we don't need for a particular job, especially if it's deployed in a job already15:18
portdirecti know hes been doing some work here for infra already15:18
srwilkerssorry, got pulled away for a second15:19
evrardjpI am working on 3 and 4 of the etherpad myself. It will allow an easier way to step in to gating for newcomers, IMO. It would also be re-usable.15:19
srwilkersyeah.  the second point is mostly an extension of the first point.  the majority of our single node gate failures are a result of pushing single nodepool vm deployments too hard15:19
srwilkersevrardjp: yeah, that would be great.  thats why i thought it'd be great to approach this with multiple sequential steps15:20
portdirecti think this sounds like a sound approach15:20
evrardjpI think 1 is orthogonal to 3 and 4 so it can be done in parallel15:20
srwilkersonce we get the gate jobs happy again, we can plug them into the consolidation/cleanup work you've been focused on15:20
portdirectthe one thing i'd like to see though is this https://review.openstack.org/#/c/608045/ coming in to make 1/2 easier15:21
evrardjpagreed15:21
portdirectas it does not change the logic of what is run today, jut makes it easier to tweak15:21
portdirectand if you could build off this evrardjp it may flow easier?15:21
evrardjpportdirect: I have built another runner, a little bit more complete15:22
evrardjpbut it is fine if we go that way, my runner could re-use the work done there.15:22
evrardjpsee https://review.openstack.org/#/c/608750/4/zuul.d/playbooks/run-scripts.yml15:22
portdirecti had a look this morning - it looks nice15:22
evrardjpanyway I will continue my work in the background, and will not disturb you in step 1 and 215:23
portdirectid need to check though - I split mine out into a role - as it offered better feedback in zuul ara15:23
srwilkersevrardjp: 'disturb' is a bit harsh :)15:24
evrardjpwe can discuss those in the reviews -- my point was that I will focus on element 3 and 4 from the etherpad, as this will at some point be helpful for my employer to add opensuse support.15:24
mattmceuenima here15:25
portdirectok - so i think we only have one item left atm:15:25
mattmceuensorry, I was pretending to be a scrum master - catching up :)15:25
portdirect#topic User UID's15:25
*** openstack changes topic to "User UID's (Meeting topic: openstack-helm)"15:25
evrardjpfor step 3 and 4, I will give you a hint of how I will do this: I will migrate job per job, instead of working with the current state.15:25
portdirectsorry - i'll wait untill your done - me jumping the gun again15:26
evrardjpIf nobody is against that method we can continue15:26
evrardjpportdirect: I am done now15:27
evrardjpwe can discuss in the channel if further conversations need to happen too.15:27
portdirectevrardjp: i think what your saying sounds good, though code always helps :D15:27
portdirectso - on user uids - I've come across a few instances where we colide with 'host' users15:28
evrardjpI will dump other patches soon for reimplementing the base job's pre-run plays with less code, and will continue to iterate.15:28
portdirectwhich makes audit hard15:28
portdirectthe lma stack is pretty spread here i think15:28
portdirect(I was accusing a colleague of running fluentbit recently...)15:29
portdirectfor the openstack images we use 42424 atm15:29
portdirectdo we have the abillity of either doucmenting, or controlling the uids that containers run as simply?15:29
portdirectwould allow us to define ranges for pam etc on the host to use that dont overlap15:30
portdirectsrwilkers / lamt : you have any insight here?15:30
srwilkersadmittedly, havent looked at it much.  but should be able to document those i would imagine15:31
lamtI think we can document that, not sure we can effectively control the uid so they don't overlap though15:33
portdirecti was wondering, if we declare these users in the chart, could we at a min have a script that gets them out of our values.yaml?15:33
lamtyes via yq15:34
lamtdo we want to add a script into the tools folder for this?15:35
portdirectit would be worth making a ps i think15:35
portdirecti know of deployments that certainly need this15:35
portdirectyou ok to take this on?15:36
portdirectlamt: has volunteered :D15:36
portdirectnice - thanks dude15:36
lamtsure15:37
portdirectok - so that kinda wraps it up i think15:37
* lamt was busy grabbing more caffeine.15:37
portdirect#topic roundtable15:37
*** openstack changes topic to "roundtable (Meeting topic: openstack-helm)"15:37
srwilkerswell, i don't have anything, i dont think15:39
*** ianychoi has quit IRC15:39
lamtI am good.15:39
portdirectok - lets give everyone some time back15:39
portdirect#endmeeting15:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:39
openstackMeeting ended Tue Oct  9 15:39:52 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-09-15.00.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-09-15.00.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-10-09-15.00.log.html15:39
evrardjpI had something15:41
evrardjphaha15:41
evrardjpnever mind, next week!15:41
evrardjp:p15:41
*** munimeha1 has quit IRC15:43
*** ralonsoh has quit IRC16:22
*** gagehugo has left #openstack-meeting-516:24
*** iyamahat has quit IRC16:59
*** annp_ has quit IRC17:14
*** iyamahat has joined #openstack-meeting-517:14
*** iyamahat_ has joined #openstack-meeting-517:17
*** iyamahat has quit IRC17:20
*** ralonsoh has joined #openstack-meeting-517:28
*** yamahata has joined #openstack-meeting-517:39
*** ralonsoh has quit IRC17:40
*** markvoelker has quit IRC19:09
*** markvoelker has joined #openstack-meeting-519:09
*** markvoelker has quit IRC19:15
*** markvoelker has joined #openstack-meeting-519:17
*** spiette has quit IRC19:58
*** slaweq has quit IRC22:17
*** lemko has quit IRC22:52
*** hongbin has quit IRC22:58
*** slaweq has joined #openstack-meeting-523:11
*** slaweq has quit IRC23:16

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