15:00:14 #startmeeting openstack-helm 15:00:14 Meeting started Tue Mar 17 15:00:14 2020 UTC and is due to finish in 60 minutes. The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:18 The meeting name has been set to 'openstack_helm' 15:00:25 #link https://etherpad.openstack.org/p/openstack-helm-meeting-2020-03-17 agenda 15:01:07 Good morning 15:01:13 o/ 15:03:08 \o 15:03:15 o/ 15:04:31 o/ 15:04:37 hey - sorry im late 15:04:53 no worries 15:05:14 #topic Midcycle virtual PTG 15:05:52 So due to the lack of responses for time, this time next week is probably one of the better times to host this 15:06:26 Was looking at 1400-1700 UTC (0900 to 1200) for central time folks 15:06:37 On the 24th 15:06:47 Any objections/opinions to this? 15:07:36 sounds good to me 15:08:04 Works for me as well 15:08:31 wfm :D 15:09:13 I'll send out an email announcing this timeslot 15:09:20 was also just going to use webex, as it's pretty simple 15:09:42 sounds good 15:09:52 #topic loci 15:10:06 portdirect: I assume this is you? 15:10:13 yes 15:10:31 so OSH is very dependent on LOCI 15:10:43 however LOCI has not been well recently 15:10:57 for various reasons we lost virtually all the cores on the project 15:11:25 and I also am lacking the time to put into it that it deserves 15:11:51 in the past chris hoge proposed that osh absorbed loci 15:12:24 and we collectivley felt that it was worth giving it another shot at surviving as an independant project 15:12:35 unfortuanly thats proven not to really be viable 15:12:55 as a result, i'd like to propose again to the OSH community that we absorb LOCI 15:13:14 any thoughts? 15:13:41 I think with the current situation and our dependence on it, that's probably a good idea at this point 15:13:42 I support it 15:13:58 stevthedev / megheisler ? 15:14:19 LOCI patches often hold up fixes in the OSH-images repo 15:14:40 I'm not sure what LOCI is to be honest but don't see and issue absorbing it if it's not otherwise being taken care of 15:14:52 Q: What needs to be done for LOCI to maintain it, and what are the needs of LOCI on development side? In short. 15:15:04 especially if we rely heavily on it 15:15:28 roman_g: not that much! the project is very mature, hence the low rate of changes proposed to it 15:15:41 with regard to the development side - just docker, and git :D 15:16:05 Q2: could maintenance of LOCI be split and moved into each component's repo? 15:16:21 or add osh cores to the loci repo? 15:16:41 roman_g: that was the original intent of loci - but in practive makes little sense 15:16:52 its a single dockerfile that can build any openstack project 15:17:24 lamt: i think rather than a core injection, moving under goverenance of the one project that activly consumes it makes sense 15:17:36 portdirect: yes, but gates are separate 15:18:19 roman_g: note we currently dont actually gate loci images, other than for 'do they build' 15:18:47 but we also build them twice - once in loci, and then again in osh-images 15:19:55 portdirect: hmm. Thank you for explanation. 15:20:03 ok - I'll talk to the tc, and then get somthing out to the ml with their feedback 15:20:07 * roman_g looks at https://review.opendev.org/#/q/project:openstack/loci 15:20:35 cool 15:20:39 thanks portdirect 15:20:48 #topic open discussion 15:21:00 Does anyone else have anything they want to discuss? reviews? 15:21:23 https://review.opendev.org/#/c/709114/ really needs some eyes 15:21:55 im not sure how i feel about it to be honest 15:22:06 in that for keystone etc - we have never needed it 15:22:35 and it introduces some opinionation to apache configs - potentially making over-rides etc harder 15:24:04 hmm 15:24:21 most LMA charts have an httpd configuration which is a lot of boilerplate - although there are some chart specific directives included. Sourcing the boilerplate from htk might clean things up 15:24:59 lets get this convo into gerrit 15:25:07 not sure about security setting though 15:25:29 the authors really deserve both the feedback, and to be looped into this convo 15:26:07 ++ 15:26:56 Anything else for this week? Otherwise we can end early 15:28:55 Sorry I was on another call during this discussion, but interested to hear back from LOCI tc and the direction we move with it 15:29:16 double booked :) 15:30:45 thanks everyone, have a good week 15:30:49 #endmeeting