14:59:28 #startmeeting OpenStack-Helm 14:59:29 Meeting started Tue Jun 11 14:59:28 2019 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:59:32 The meeting name has been set to 'openstack_helm' 14:59:36 #topic Rollcall 15:00:25 Hi everybody -- here's our agenda today, please add anything to discuss: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-06-11 15:00:45 o/ 15:00:48 \o 15:00:56 since folks are still joining and may have missed it: agenda :) https://etherpad.openstack.org/p/openstack-helm-meeting-2019-06-11 15:01:20 hi there 15:01:22 portdirect is incapacitated by work today 15:01:38 decimated, even 15:01:41 o/ georgk! 15:02:17 We have a -very- light agenda today so far, only requests for code review 15:02:51 I will post them here, and let's see if any discussion is needed for them while we have the eyeballs 15:02:58 o/ 15:03:01 https://review.opendev.org/#/c/660572/ --> Rafactoring volume mount variables in db sync job 15:03:01 https://review.opendev.org/#/c/659993/ --> Add volumes mount variables in the nova-cell-setup job 15:03:02 https://review.opendev.org/#/c/660544/ --> rabbitmq: set hostPath for rabbitmq-data 15:03:02 https://review.opendev.org/#/c/662426/ --> Creating directory from ${APACHE_RUN_DIR} variable 15:03:02 https://review.opendev.org/#/c/662603/ --> Enable hugepage support in HTK resources snippet 15:03:02 https://review.opendev.org/#/c/662992/ --> htk: provide default domain env and secrets 15:03:02 https://review.opendev.org/#/c/662993/ --> keystone: default domain fix 15:03:03 https://review.opendev.org/#/c/663130/ --> Add SUSE image for Selenium to be used in helm tests 15:03:07 o/ gagehugo 15:03:08 o/ 15:04:04 whats the output of the friday discussion with portdirect regarding the poll to be sent for the meeting times mattmceuen? 15:04:15 awesome, I patch is already in the list :-) 15:04:20 i == my 15:04:42 itxaka the output was that I hoped noone would remember that this week as portdirect and I failed to sort that out 15:04:48 lmao 15:05:02 I will redouble my efforts this week, apologize 15:05:53 o/ 15:06:02 o/ evrardjp howell 15:06:21 #topic Roundtable 15:06:31 Any questions / thoughts on the patchsets above? 15:07:05 none 15:07:30 one question 15:07:34 Any other topics that everyone would like to discuss today? 15:07:39 a generic one 15:07:43 go for it 15:07:46 #topic generic one 15:07:51 thanks! 15:08:15 the OVS image in openstack-helm-images is a source build of OVS 2.8.1 15:08:31 the LOCI images of the openstack components use the distro provided OVS 2.5.4 15:08:50 does anybody happen to know why this is the case? 15:09:16 like is there a historical technical reason for adding a 2.8 source build which is not 100% compabile with 2.5.4 15:09:25 just curious 15:09:39 I'm looking now - I'm not aware of any reason 15:10:54 looks like an attempt was made to bump it to 2.10.1, which was reverted 15:11:11 yeah, this was me and evrardjp... 15:11:54 we, the little group around the OVS-DPDK people, try to find the best way out of the following: 15:11:57 have the incompatibilities between 2.8 and 2.5 manifested themselves in any issues? 15:12:28 yes, there is at least one problem related to querying mtu sizes 15:12:30 the opensuse image is using 2.11.0 15:12:34 georgk: I would prefer to not having source builds if it's possible to rely on packages 15:13:00 it means less maintenance burden 15:13:01 we should probably sync both :( 15:13:23 itxaka: not really. Syncing versions between OSes is a nightmare 15:13:34 so, we cannot get 2.5.4 in neutron-ovs-agent to work with OVS 2.10 15:13:46 I expect similar problems with 2.11... 15:13:48 ahh 15:13:48 I believe we should use the native OS version as much as we can, because this is properly tested by the packagers/distros 15:14:16 does it work for you with opensuse? 15:14:39 georgk: we are consistent in versions 15:14:47 we are using OS provided versions 15:14:52 for all the charts 15:15:02 ah, right, sure, you are not using the debian images for the OVS-agent :-) 15:15:03 which is why I think it's easier if you have a ppa/mirror 15:15:06 stupid me 15:15:08 georgk: correct 15:15:58 or go back to a 2.5.4 image of OVS itself -> coming back to my original question of why tehre is a 2.8.1 source build 15:17:19 I am not sure, and the git history only goes back to late last year. evrardjp, do you know where that one lived prior to openstack-helm-images? 15:19:05 mattmceuen: it's still in osh-infra afaik 15:19:08 we didn't remove it yet 15:19:26 I was waiting for the gates to move to use osh-images first 15:20:14 https://github.com/openstack/openstack-helm/tree/master/tools/images/openvswitch 15:20:19 I was wrong it was osh 15:20:28 ahh there it is 15:20:53 ah, yes 15:20:57 lightweight image 15:20:58 I asked in the past the reason for versions, but without deep details answered. I can maybe find that in the logs. 15:21:14 Long story short, not a real explanation anywhere, because it wasn't written in the commit messages 15:21:23 So the original commit from portdirect says "This PS moves to use a lightweight build of OvS 2.8.1 using the 15:21:23 offical k8s network base image." -- I think we'll need to ask him if there's a reason 15:21:24 just "bump image" or things like that 15:21:35 seems so 15:22:09 #action mattmceuen to sync w/ portdirect on OvS 2.8.1 15:22:21 not sure what's the action point there though 15:22:27 mattmceuen: awesome, thank you 15:22:35 you want to figure out why we are using this version, or why can't we bump? 15:22:53 Yes :) 15:23:00 the answer to the first one impacts the second one 15:23:11 evrardjp: I am hesitent to bump using a ppa, to be honest 15:23:11 I understood with Yes :) 15:23:25 georgk: why? It would be consistent across neutron and ovs image 15:23:46 else you have to carry this kind of code everywhere. 15:24:06 (Except if you plan to extract said data from a docker container to another, which sounds even messier) 15:24:11 true, but we would have to carry the code to build a ppa package, too 15:24:29 and even worse: maintain a ppa which other people might want to use, too 15:24:45 against collaboration on said ppa? :p 15:25:50 well, collaboration is highly welcome 15:25:57 I think it would be easy to have a container that builds said package, and use that container for installing the package on the different images, at worst, but that sounds very tedious 15:27:01 if we were to use bionic default ovs, you would have 2.9.2, which is already better than 2.8.1 btw 15:27:05 how does that differ from having a source build in the debian images? 15:27:21 true 15:27:34 I mean maintaining a source build is expensive 15:27:35 the Loci images are still Xenial, right? 15:27:45 or did I miss bionic builds? 15:27:50 it's what we decide it to be 15:28:16 right now, we are building xenial, but we could work on bionic 15:29:10 georgk, for the ovs dpdk work you want to achieve, is 2.9.2 sufficient for that? Or need 2.10? 15:29:49 mattmceuen: 2.9.2 should be fine. The problem is rather in the version difference between the OpenStack component images and the OVS image itself 15:30:35 so, we either try to make it work on 2.5.4 as community maintained version using the Xenial image or move to Bionic loci images 15:30:36 which is why a package is winning in this case, because reusing 15:30:45 yep gotcha 15:30:56 but I guess it's not up to me :) 15:31:20 I am not fighting this, I just think it will become quite messy when it's about building the neutron images :p 15:31:25 I think switching to bionic will require some input from our PTL, but it sounds good to me :) 15:31:44 ok, ok 15:31:55 I assume switching to bionic has a larger impact 15:32:04 mattmceuen: I think it makes sense to have a message for those who want the latest and greatest --- that they can have a different base os 15:32:14 so produce more images basically 15:32:27 because that enters the realm of the multi-os spec 15:32:29 so, we need to look into 2.5.4 first (which is quite old) and if that doesn't cut it, we need to bump to bionic... 15:33:01 +1 to both evrardjp and georgk 15:33:22 georgk: maybe also having a look at UCA would be useful 15:33:36 UCA? 15:33:42 ubuntu cloud archive 15:33:49 * portdirect shudders 15:33:50 ah, ok 15:33:55 :-) 15:34:06 or not, portdirect? 15:34:52 UCA is not exactly 'reliable' 15:35:30 it is, assuming you are consistent with its use. 15:35:43 do not mix uca and non uca for example :p 15:35:55 we've been using UCA in OSA for years without issue. 15:36:02 it's not epel 15:36:14 and there we differ - i like epel ;D 15:36:31 but I'd fully support a move to bionic - its high time we did 15:36:56 * mattmceuen cheers 15:38:31 evrardjp do you have any idea how much bigger than a breadbox moving to bionic would be? any hidden gotchas or concerns? 15:38:51 I don't know I haven't tried. 15:39:01 but the work for suse was straightforward 15:39:04 it would be very simple 15:39:11 so I don't expect big issues 15:39:15 great 15:39:20 just change the source image refs 15:39:23 we are also building neutron with 1804 15:39:28 right now 15:39:28 and also the gate/test host 15:39:29 and it works 15:39:31 yup 15:39:39 great, I'll take it 15:39:41 so I suppose it wouldn't be that hard to build the 1804 images for everyone 15:39:42 :-) 15:39:52 famous last words 15:39:59 hahah 15:40:00 thanks georgk 15:40:03 ha! 15:40:19 this still supposes the fact to run on the same host, I expect bumping host to bionic needs to happen too, and might require more work 15:40:21 wait, I'll take the resulting images 15:40:36 georgk: that's not what I understood :p 15:40:42 too late georgk 15:40:43 too late georgk 15:40:46 lmao 15:40:46 I know! 15:40:48 hahah 15:40:52 that's a sign 15:40:58 we all understood it that way :p 15:41:24 yes, yea, the entire community... 15:41:30 hahaha 15:41:43 I am happy to help 15:42:30 I might need some pointers 15:43:08 evrardjp would you be able to collaborate with georgk on that? Hopefully it "just works" 15:43:12 sure, don't hesitate to ask :) 15:43:40 yeah I am fine with helping. 15:43:47 tytyty 15:43:48 but everyone can help :p 15:43:55 for sure 15:44:44 thanks 15:44:57 alright - I think we've discussed this one pretty well. Other topics? 15:45:41 ok - in that case we can call it a day! 15:45:48 thanks everyone for joining 15:45:51 ok, thank you all! 15:45:59 appreciate your time & your brainpower 15:46:06 #endmeeting