Friday, 2019-03-08

openstackgerritMerged openstack/loci master: Pass python3 flag to bindep  https://review.openstack.org/64131301:41
*** jsuchome has joined #openstack-loci06:57
evrardjphogepodge: great07:39
openstackgerritJean-Philippe Evrard proposed openstack/loci master: Revert "For OpenSUSE Leap, use more recent version of zVMCloudConnector"  https://review.openstack.org/64195707:45
evrardjphogepodge: I have prepped the patch already for the revert in loci, should the patch in requirements merge. So that we can vote on Jiri's patch first.07:46
evrardjpI would still prefer we discuss, at the meeting, an approach for this kind of hacks07:46
jsuchomedo you think we need it becase it could take a long time to merge the requirement patch?07:54
openstackgerritMerged openstack/loci master: Fix mismatched mod_wsgi for python3  https://review.openstack.org/64174109:26
openstackgerritItxaka Serrano Garcia proposed openstack/loci master: add missing libvirt package for suse  https://review.openstack.org/64198511:30
openstackgerritItxaka Serrano Garcia proposed openstack/loci master: add missing libvirt package for suse  https://review.openstack.org/64198511:41
openstackgerritItxaka Serrano Garcia proposed openstack/loci master: add missing libvirt package for suse  https://review.openstack.org/64198511:44
*** jsuchome has left #openstack-loci14:24
hogepodgeevrardjp: Ah, I didn't want to block and thought you had signed off on it for Suse.14:41
evrardjpo/15:00
hogepodge#startmeeting loci15:01
openstackMeeting started Fri Mar  8 15:01:40 2019 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: loci)"15:01
openstackThe meeting name has been set to 'loci'15:01
hogepodgeping portdirect15:01
hogepodge#topic agenda15:02
*** openstack changes topic to "agenda (Meeting topic: loci)"15:02
hogepodge#link https://etherpad.openstack.org/p/loci-meeting agenda15:02
evrardjphogepodge: we'll need to reap votes indeed15:02
itxakao/15:04
hogepodge#topic zVMCloudConnector15:05
*** openstack changes topic to "zVMCloudConnector (Meeting topic: loci)"15:05
hogepodgeevrardjp: go ahead15:05
hogepodgesorry about merging that, I saw your +2 then missed your -115:05
evrardjpthanks15:05
evrardjpI don't think there is an issue yet hogepodge :)15:06
evrardjplet me clarify what's up15:06
evrardjpzVMCloudCOnnector cannot build with python3.6 -- which means impossible to build in leap15.15:06
evrardjpthis will be a problem for queens and below15:06
evrardjpI have submitted a patch for requirements, which is unlikely to get accepted15:07
evrardjpSo I propose we merge the workaround in loci, with a revert should the one in requirements be accepted15:07
evrardjpworkaround is here: https://review.openstack.org/#/c/641647/15:07
evrardjprevert is here: https://review.openstack.org/#/c/641957/1 which depends on https://review.openstack.org/#/c/641738/15:08
evrardjpif we merge the first one, that unblocks SUSE15:08
evrardjpyet -- I believe we should not pile up those kind of hacks15:08
evrardjpSo I propose instead to build a blacklist file, with default content, that we COPY at the beginning of the process, and use that to simplify life of deployers -- We can by default list the ones we have, and deployers can extend15:09
evrardjpCOPY or ADD, depends on the willingness here15:09
hogepodgeI can merge it right now15:10
evrardjpthat would totally help hogepodge15:10
evrardjpshould we, at next step, think about blacklisting for a "permanent" solution?15:10
evrardjpif no one is interested by that, we can continue piling up hacks, I am fine with that15:12
hogepodgeso https://review.openstack.org/#/c/641647/ is good to go?15:12
evrardjpit's better that we share those hacks anyway15:12
evrardjphogepodge: yes15:12
evrardjpplease +W :D15:12
hogepodgeok, think I got it all15:13
evrardjpside note: if we can't get portdirect to vote on https://review.openstack.org/#/c/637963/ I would totally love if you could +w it too15:13
hogepodgeI think we need to try and grow the core team, or relax two core voting rules15:13
hogepodge(assume a core's patch would come with an implicit +2 for example)15:14
evrardjpthat's fair15:14
evrardjpI guess I hope I can see a few reviews from colleagues like itxaka :D15:15
hogepodge:-)15:15
hogepodgehi itxaka!15:15
hogepodge#topic branching15:16
*** openstack changes topic to "branching (Meeting topic: loci)"15:16
evrardjpcan I switch to a new topic?15:16
evrardjphaha you did15:16
evrardjpperfect15:16
itxakamaybe, but I dont want to mass vote on all my colleagues patches just because :P15:16
itxakayou'll have to earn those votes ;)15:16
evrardjpitxaka: great mindset, but you can vote also on other patches :D15:16
evrardjphogepodge: branching \o/15:17
itxakabranching yay \o/15:17
hogepodgeso, I'm wondering how heavy a profiles-based approach would be vs a branching approach15:17
hogepodgeIf we can make profiles work without it being a giant pile of hacks, I would be all for that.15:17
hogepodgeStable branch management is a slog and we don't really have the team depth to handle it.15:17
hogepodgeevrardjp: you have ideas?15:18
evrardjpyou can have a branch named stable without subscribing to stable maint team15:18
evrardjpteam process*15:18
evrardjpbut IMO, we shouldn't branch loci for now15:18
hogepodgeit's not even the formality of it, it's that every time you send a patch up you have to decide if it's appropriate to cherry pick back to every other stable branch.15:18
evrardjpyeah15:19
evrardjptotally15:19
evrardjpthat's what I consider the pain15:19
evrardjpI haven't seen any code of loci itself that deserved branching15:19
hogepodgeIf it's just in changing which packages are installed, I'd much rather have business logic to handle it rather than infrastructure logic15:19
evrardjptotally15:19
evrardjpwhich is why I believe the bindep approach is better15:19
evrardjpbut there are two ways to do it now15:19
evrardjpone could be to insert openstack branch names into profiles15:20
evrardjpthe other would be having multiple bindeps15:20
evrardjpin the latter form, we could have a conditional use of the bindep file based on PROJECT_REF15:21
evrardjpI would prefer the former tbh, and maybe grow into the latter15:21
itxakaboth sounds good, would we have a generic-non attached to any branch bindep as to not duplicate things in the second case?15:21
evrardjpitxaka: have you seen many packages in bindep/pydep that are branch dependent?15:21
itxakajust one I think15:21
evrardjpitxaka: we can indeed15:21
hogepodgeitxaka: I was thinking the same thing15:22
evrardjpright now there is this15:22
itxakaok, then Im ok with both, not sure if we will use it much but it would be good to have a plan just in case we need to15:22
evrardjphttps://github.com/openstack/loci/blob/master/Dockerfile#L2915:22
hogepodgeitxaka: evrardjp: a primary bindep then an stable-branch overrides bindep15:22
evrardjpwe can have bindep which is common15:22
evrardjpand then extra_bindep can be set to the extra ones15:23
hogepodgethe question is what happens when there are conflicting bindep entries?15:23
evrardjpright now there is no merge of those15:23
evrardjpit's just literally sequential calls of bindeps15:23
evrardjpbecause bindep cannot be passed multiple files, AFAIK15:23
evrardjpwe can write a merge function, if necessary15:24
hogepodgeok, so what I might find helpful is just a quick write-up of the proposed solutions as a spec, which I know is more work but we're going to have to live with whatever decision is made15:24
evrardjpthat sounds fair15:25
hogepodgeI was thinking of primary bindep, with branch overrides (that default to something like master), then stable/<release>, and have a tool to merge in favor of what is in the stable15:25
evrardjpquestion for the merge resolution15:26
evrardjpif a line appears in default, and stable, but don't have the same matchers, what happens?15:26
evrardjponly the package name in stable is retained, and only the matcher from stable applies?15:26
evrardjpthat sounds fair to me15:26
evrardjpbut all of this seem far more complex than just adding profiles into regular bindep right now15:27
hogepodgeI guess? A spec would help to visualize it and work through the logic15:27
evrardjpso I am wondering if we are heading the right direction15:27
evrardjpitxaka: can you tackle this>15:27
itxakawill do15:27
evrardjpyou have this: https://review.openstack.org/#/c/640711/15:27
evrardjpthat's a good example of branching content for the spec15:28
hogepodgemy only concern with profiles in regular bindep is explosion of complexity within one file, and stale branch information that we'd constantly have to be going back and pruning15:28
evrardjpfair15:28
evrardjpto simplify code, we can also not write a merge function15:29
hogepodgeI'm open to suggestions though, tbh. My first instinct is often not the right one15:29
evrardjpbut declare if there is a need of branching, then it is automatically removed from the default15:29
evrardjphogepodge: haha15:29
evrardjpok15:29
itxakaI dont think we are gonna use it too much tbh, so we should keep it as simple and dumb as possible15:29
evrardjpgood to know15:29
evrardjpitxaka: I agree on keep it simple15:29
hogepodge+1 to that15:29
itxakaI'll write the blueprint on that soon-ish15:30
evrardjpgreat15:30
hogepodge#topic open discussion15:31
*** openstack changes topic to "open discussion (Meeting topic: loci)"15:31
hogepodgeany other topics?15:31
evrardjphow is your test framework going?15:31
evrardjplocistack iirc?15:31
hogepodgeevrardjp: stalled out this week because of other work, hoping to get a patch up today or Monday once I clear my morning meeting block15:31
evrardjp:D15:32
evrardjpgood to hear15:32
hogepodgeevrardjp: one patch I need to use in my framework is try to take advantage of profiles correctly, I'm kind of building in specific packages but that means I'm not using stock images15:32
hogepodgefor correctness some have to be built with profiles for AIO, like Cinder for example15:33
evrardjpinteresting, how are you using that?15:33
hogepodgeapparently Sam had an AIO installer also, which I should take a look at.15:33
evrardjpdifferent bindep?15:33
evrardjpoh I didn't know15:33
evrardjpproves I am young in this project :p15:34
hogepodgehttps://github.com/hogepodge/locistack/blob/master/build/Makefile#L915:34
hogepodgewhich gets applied down here https://github.com/hogepodge/locistack/blob/master/build/Makefile#L7315:35
evrardjpoh god, it totally looks like what I am writing15:35
hogepodgeHaha it helps cut down on layers and additional builds15:36
hogepodgeBut you can't use stock builds which is kind of the point anyway.15:37
evrardjpI am just templating this using bash instead of a makefile, but meh15:37
evrardjpI should maybe convert to make15:37
hogepodgeI really like make for... making things15:38
evrardjp:D15:38
hogepodgeok, anything else?15:39
evrardjpnone15:39
hogepodgethanks! have a great weekend!15:40
evrardjpyou too!15:40
hogepodge#endmeeting15:40
*** openstack changes topic to "Build image -- `docker build https://github.com/openstack/loci.git --build-arg PROJECT=keystone` || Review patches -- https://review.openstack.org/#/q/projects:openstack/loci+status:open"15:40
openstackMeeting ended Fri Mar  8 15:40:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/loci/2019/loci.2019-03-08-15.01.html15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/loci/2019/loci.2019-03-08-15.01.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/loci/2019/loci.2019-03-08-15.01.log.html15:41
itxakao/15:41
itxakagood weekend15:41
hrwtoo late.15:43
evrardjpoh hrw I saw your patch was still up, I didn't know if I should brought it up15:50
evrardjpmaybe next week?15:50
openstackgerritMerged openstack/loci master: For OpenSUSE Leap, use more recent version of zVMCloudConnector  https://review.openstack.org/64164715:51
openstackgerritMerged openstack/loci master: Support self-signed certificates docker registry  https://review.openstack.org/63796315:52
hrwevrardjp: nothing changed with it15:55
openstackgerritMerged openstack/loci master: add missing libvirt package for suse  https://review.openstack.org/64198515:56
hrwevrardjp: and no plans so far for working on it15:57
hrwevrardjp: working on py3inzing Kolla images15:58
evrardjpk15:58
evrardjphave fun I'd say? :p15:58
hrwha! my calendar just said "loci meeting"16:00
hrwevrardjp: convincing others that they have to rewrite their yet-not-merged patches16:01
evrardjpshould bump this :p16:01
hrwTasks: 940, 3158 thr, 2087 kthr; 17 running16:02
*** itxaka has quit IRC16:43
*** e0ne has joined #openstack-loci17:03
*** e0ne has quit IRC17:08
*** irclogbot_1 has quit IRC20:13
*** e0ne has joined #openstack-loci20:24
*** e0ne has quit IRC21:03
*** irclogbot_1 has joined #openstack-loci23:02

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