Monday, 2019-09-09

*** bobh has joined #openstack-oslo00:11
*** bobh has quit IRC00:17
*** rcernin has quit IRC00:30
*** rcernin has joined #openstack-oslo01:45
*** dave-mccowan has quit IRC01:58
*** bobh has joined #openstack-oslo02:37
*** bobh has quit IRC03:14
*** Luzi has joined #openstack-oslo04:48
*** jaosorior has joined #openstack-oslo05:03
*** e0ne has joined #openstack-oslo06:09
*** jbadiapa has joined #openstack-oslo06:13
*** e0ne has quit IRC06:18
*** snapiri has quit IRC06:35
*** snapiri has joined #openstack-oslo06:36
*** snapiri has quit IRC06:36
*** snapiri has joined #openstack-oslo06:49
*** shachar has joined #openstack-oslo06:58
*** snapiri has quit IRC07:00
*** rcernin has quit IRC07:02
*** trident has quit IRC07:10
*** tesseract has joined #openstack-oslo07:13
*** trident has joined #openstack-oslo07:21
*** hberaud|gone is now known as hberaud07:38
*** pcaruana has joined #openstack-oslo07:49
*** ralonsoh has joined #openstack-oslo08:18
*** e0ne has joined #openstack-oslo08:19
openstackgerritMichal Arbet proposed openstack/osprofiler master: Fix osprofiler usage in horizon  https://review.opendev.org/63029809:31
*** shachar has quit IRC09:53
*** snapiri has joined #openstack-oslo09:53
*** hberaud is now known as hberaud|school-r09:54
*** lpetrut has joined #openstack-oslo09:55
*** hberaud|school-r is now known as hberaud|afk10:03
*** hberaud|afk is now known as hberaud10:03
*** rcernin has joined #openstack-oslo10:08
*** hberaud is now known as hberaud|lunch10:48
*** dave-mccowan has joined #openstack-oslo10:52
*** shachar has joined #openstack-oslo11:02
*** snapiri has quit IRC11:03
*** kgiusti has quit IRC11:26
*** shachar has quit IRC11:48
*** ansmith has quit IRC11:51
*** moguimar has quit IRC11:52
*** goldyfruit has quit IRC11:56
*** boden has joined #openstack-oslo11:56
*** moguimar has joined #openstack-oslo12:00
*** snapiri has joined #openstack-oslo12:02
*** raildo has joined #openstack-oslo12:02
*** hberaud|lunch is now known as hberaud12:04
*** rcernin has quit IRC12:22
*** kgiusti has joined #openstack-oslo12:38
*** ansmith has joined #openstack-oslo12:45
*** e0ne has quit IRC13:19
*** camelCaser has quit IRC13:28
*** Luzi has quit IRC13:34
*** e0ne has joined #openstack-oslo13:50
*** mriedem has joined #openstack-oslo13:53
mriedembeekneemech: lbragstad: got a question about oslo.policy,13:54
*** beekneemech is now known as bnemec13:54
mriedemwhen placement was in nova, we had to define a separate policy file for placement since nova used oslo_policy.policy_file,13:54
mriedemnow we want to deprecate the placement.policy_file option and use oslo_policy.policy_file,13:54
mriedembut for train need to have compat for the deprecation,13:54
mriedemso i'm poking through oslo.policy trying to figure out the best way to determine if the placement policy file is used or the oslo_policy policy file13:55
mriedemlike, would i try to create an Enforcer to load up the rules from the [oslo_policy]/policy_file config and handle any errors and fallback to loading up from [placement]/policy_file?13:56
lbragstadmriedem that's a portion of oslo.policy i'm not entirely familiar with13:57
mriedemi'd think i'd handle some kind of error here https://opendev.org/openstack/placement/src/branch/master/placement/policy.py#L4713:57
mriedemthe docstrings aren't clear about what kind of exceptions can be raised up though13:58
mriedemlike OSError if trying to load a policy file and the policy file doesn't exist?13:58
lbragstadbut i want to say oslo.policy has the ability to load policies from multiple files (e.g., /etc/nova/policy.d/13:58
lbragstad)13:58
mriedemyeah https://docs.openstack.org/oslo.policy/latest/configuration/index.html#oslo_policy.policy_dirs13:58
lbragstadso - you'd want nova to load a placement policy file and use those policies if they are there (because placement also has default policies in code, right)13:59
mriedemnot nova, placement13:59
bnemecWe don't raise on a missing policy file: https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py#L56014:00
mriedembnemec: yeah i saw that14:00
lbragstadit's this for compatibility with nova running with placement in nova still? like the migration to using placement as an external service?14:00
mriedemlbragstad: yeah placement has policy defaults in code14:00
lbragstadisn't*14:00
mriedemlbragstad: no nova is not involved at all14:00
lbragstadoh14:00
mriedemthis is cleaning up old stuff from when placement was in nova14:01
mriedembnemec: so my other thought was just checking if [placement]/policy_file exists and if so, use it14:01
lbragstadgot it - so you just want to update the configuration to look for the policy file in a standard place, but check the old location (for migration purposes)14:01
mriedemyes14:01
bnemecYeah, you might have to explicitly check, and log a warning if the old file is found.14:02
lbragstadyeah - i don't think we've ever had a case like this, because i don't think we've ever had someone forcing namespacing in the way nova had to for placement14:02
bnemecI don't think we really expose the location that a policy rule was loaded from.14:02
mriedemi think i can use ConfigOpts.find_file for that existence check yeah?14:03
mriedemsince policy_file can be absolute or relative to the config file14:03
lbragstadright14:03
lbragstadthe defaults to being relative iirc14:03
lbragstadit defaults*14:03
bnemecYeah, that's what oslo.policy is using: https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py#L81814:04
mriedemyup, that's how i found it :)14:04
mriedemok i'll try that, thanks14:04
mriedemi'm not sure i can even warn if [placement]/policy_file is used...14:05
mriedemit defaults to policy.yaml,14:05
mriedemand if you configured [oslo_policy]/policy_file to policy.yaml,14:05
mriedemand they are in the same location,14:05
mriedemthey'd look the same14:05
mriedemso maybe i need to look for [oslo_policy]/policy_file first? that defaults to policy.json so if that doesn't exist it would be more obvious that you haven't migrated yet14:06
lbragstadyeah - or you're just using the defaults in code14:06
mriedemugh, true14:07
lbragstadso 1.) check if [oslo_policy]/policy_file exists, if so use it 2.) check if [placement]/policy_file exists, if so use it 3.) load everything from defaults in code (which should happen regardless to fill in the gaps in an existing policy file)14:08
lbragstadand eventually - i think you could just remove the second case14:08
lbragstad(cases 1 and 3 are essentially oslo.policy's default behavior)14:09
*** hberaud is now known as hberaud|school-r14:23
mriedemyup i think i've got something here, will post the wip and see if it makes sense14:26
mriedemtrying to be extra cautious14:26
*** lpetrut has quit IRC14:30
lbragstadsounds good14:32
*** hberaud|school-r is now known as hberaud14:39
bnemec#startmeeting oslo15:00
bnemecCourtesy ping for bnemec, jungleboyj, moguimar, hberaud, kgiusti, redrobot, stephenfin, johnsom15:00
bnemec#link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting15:00
openstackMeeting started Mon Sep  9 15:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is bnemec. 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: oslo)"15:00
openstackThe meeting name has been set to 'oslo'15:00
hberaudo/15:00
moguimaro/15:00
jungleboyjo/15:00
johnsomo/15:00
*** jroll has joined #openstack-oslo15:00
ansmitho/15:01
bnemec#topic Red flags for/from liaisons15:02
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"15:02
kgiustio/15:02
johnsomNothing to raise from Octavia team15:02
moguimarNothing from Oslo15:03
moguimaroops15:03
moguimarbarbican15:03
bnemecmoguimar: :-)15:03
moguimar:facepalm:15:03
bnemecThe one major thing to note from the Oslo side is that we have merged the sighup fix so that services won't be completely restarted when using mutable config.15:04
bnemecIf you see any weird behavior as a result please let us know ASAP.15:04
jungleboyjnothing from Cinder15:04
bnemecOkay, sounds like we're good.15:05
bnemec#topic Releases15:05
*** openstack changes topic to "Releases (Meeting topic: oslo)"15:05
jungleboyj\o/15:06
bnemecWe're in feature freeze, so releases from here on out should be bugfix only, unless an FFE is granted.15:06
bnemecAlso note that I released all the things last week. We need to do that so when branches are cut they include all of the doc and test changes we normally don't release.15:07
*** goldyfruit has joined #openstack-oslo15:08
bnemecOtherwise I would expect release activity to slow down a bit here as we come to the end of the cycle.15:08
bnemecI think that's all I've got.15:09
bnemec#topic Action items from last meeting15:09
*** openstack changes topic to "Action items from last meeting (Meeting topic: oslo)"15:09
bnemec"bnemec add gsantomaggio to oslo.messaging core list"15:09
bnemecDone. \o/15:09
gsantomaggio@bnemec thank you15:09
bnemecMy pleasure. :-)15:10
bnemec"bnemec to ask keystone team about https://review.opendev.org/#/c/662830"15:10
bnemecPretty sure I did that, but still haven't heard anything back.15:10
bnemecAt this point I'm inclined to just go ahead and merge it.15:11
moguimarlbragstad: ^15:11
bnemecSince it's a bug fix we could do that now. I'm not sure how high priority this is though.15:11
moguimarbnemec: lbragstad and I are working in the same DFG now15:12
*** jaosorior has quit IRC15:12
bnemecHandy. :-)15:12
moguimaryep15:12
lbragstadi can take a look at that today if needed15:13
bnemecThe other thing is that since this is a bugfix we could wait until next cycle and backport it.15:13
bnemeclbragstad: I'm mostly just looking for a sanity check that this isn't horribly violating any keystone expectations of how tokens get used.15:14
lbragstadbnemec cool - that sounds good15:15
bnemecOkay, we'll wait for lbragstad's input on that one then.15:16
bnemec#topic Feature freeze15:16
*** openstack changes topic to "Feature freeze (Meeting topic: oslo)"15:16
bnemecI mentioned it earlier, but we're in feature freeze now, both for Oslo and non-client libs.15:17
bnemecThat means nobody should merge any patches that would require a feature release from now until we branch stable/train.15:17
bnemecUnless an FFE has been granted, and at this point I think we'd need approval from both me and the release team since we're out of the Oslo-specific freeze period.15:18
bnemecOn a related note...15:18
bnemec#topic Deprecation of oslo.i18n Message.translate function15:18
*** openstack changes topic to "Deprecation of oslo.i18n Message.translate function (Meeting topic: oslo)"15:18
bnemecA bug was pointed out on the mailing list a couple of weeks ago that there was an issue with the Message.translate function.15:19
bnemecIt turns out we shadowed a unicode built-in function in our Message subclass.15:19
bnemecThat causes problems when we pass a Message object as a unicode to external libraries that try to use it as a non-i18n call.15:20
bnemecI have a two-part fix up for this, starting at https://review.opendev.org/#/c/679092/15:20
bnemecThe first one we can merge because it's exclusively a bug fix.15:21
bnemecThe followup is more of a question because it deprecates the existing function.15:21
bnemec#link https://review.opendev.org/#/c/679321/115:21
bnemecHowever, I would like to ask for an FFE to get that in this cycle so we can do the removal ASAP.15:21
bnemecIf we wait til next cycle we'll have to wait an extra cycle before removing it, per our deprecation policy.15:22
bnemecIt's a pretty low risk thing since we don't document calling that function directly. Translation is supposed to happen via the i18n.translate module-level function.15:22
bnemecI don't see any deprecation warnings logged in the tempest jobs on the patch, so I don't think any of the projects we're testing with call it directly.15:23
bnemecSo I wanted to bring this up for two reasons: 1) To get another core to look at that so we can have it ready to merge if we get an FFE15:24
bnemec2) To see if anyone has any objections to me asking for an FFE on it15:24
bnemecIf I hear no objections during the meeting I'll probably go ahead and take it to the list.15:26
bnemecOkay, moving on then.15:27
bnemec#topic PTG/Forum15:27
*** openstack changes topic to "PTG/Forum (Meeting topic: oslo)"15:27
bnemec#link https://etherpad.openstack.org/p/oslo-shanghai-topics15:27
bnemecForum session proposals are now open.15:27
gsantomaggiocan't go :(15:28
bnemecI don't have any topics planned, but if anyone has anything that they think would benefit from a broad discussion at the Forum please feel free to submit and add to the etherpad.15:28
moguimarbnemec: feel free to ping me for the castellan demo15:28
bnemecThere's a lot of that going around. :-/15:28
bnemecmoguimar: Cool, I was planning on that. :-)15:28
bnemecI don't have a lot else to say on that, other than to always keep in mind that if you run across anything you think would benefit from discussion at the PTG, please add it to the etherpad too.15:30
bnemec#topic Cycle highlights15:30
*** openstack changes topic to "Cycle highlights (Meeting topic: oslo)"15:30
bnemecNow that we're coming to the end of the cycle, it's time for cycle highlights.15:30
bnemecI believe there was an email to the ML about this, but basically it's some marketing bullet points for each project.15:31
bnemecWe don't always have them for Oslo because a lot of our work is not user-facing, so it's not terribly marketable.15:31
bnemecHowever, if you worked on anything this cycle that you think should show up in the OpenStack marketing materials please let me know ASAP.15:32
bnemecOslo-related of course. ;-)15:32
moguimarwas castellan driver this or last cycle?15:33
bnemecLast cycle, I believe.15:34
bnemecI'm pretty sure I included it in the cycle highlights last time.15:35
bnemecFor reference, here's the cycle highlights from last time:15:36
bnemec#link https://review.opendev.org/#/c/64501915:36
bnemecBasically all config-related.15:36
bnemec#topic Weekly Wayward Review15:38
*** openstack changes topic to "Weekly Wayward Review (Meeting topic: oslo)"15:38
bnemecThis one catches my eye:15:39
bnemec#link https://review.opendev.org/#/c/672781/15:39
bnemecIt's a kind of important fix since it results in broken rules in the generated policy.15:40
bnemeclbragstad: I'm thinking I might go ahead and +2 since we've both reviewed each other's changes, and I only touched the tests.15:40
bnemecAnd maybe that will get cmurphy's attention. I hesitate to ping her since I don't know if she's caught up from PTO yet.15:41
moguimarbnemec: I can review it tomorrow morning15:42
bnemecmoguimar: Sounds good, thanks.15:42
bnemec#action moguimar to review https://review.opendev.org/#/c/672781/15:42
bnemecAlright, we'll call that good. At some point here I'll probably stop doing the wayward review section until ussuri opens up since we don't want to be forcing patches in late in the cycle.15:43
bnemec#topic Open discussion15:43
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"15:43
bnemecAnything else this week?15:43
moguimarnot on my end15:44
lbragstadthanks moguimar15:44
bnemecOkay, let's give everyone 13 minutes back. Thanks for joining!15:47
bnemec#endmeeting15:47
*** openstack changes topic to "OpenStack Common Libraries | https://wiki.openstack.org/wiki/Oslo"15:47
openstackMeeting ended Mon Sep  9 15:47:16 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
moguimaryay15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-09-09-15.00.html15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-09-09-15.00.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-09-09-15.00.log.html15:47
mriedembnemec: lbragstad: this is whati came up with https://review.opendev.org/#/c/681047/1/placement/policy.py15:59
*** tesseract has quit IRC16:07
*** e0ne has quit IRC16:10
lbragstadmriedem nice - does that work locally16:13
mriedemhaven't tried yet16:14
mriedemprobably won't be able to today either16:14
*** trident has quit IRC16:58
*** hberaud is now known as hberaud|gone16:59
*** trident has joined #openstack-oslo17:06
*** camelCaser has joined #openstack-oslo17:19
*** camelCaser has quit IRC17:28
*** camelCaser has joined #openstack-oslo17:28
*** mriedem has left #openstack-oslo17:38
*** ralonsoh has quit IRC17:49
*** goldyfruit_ has joined #openstack-oslo17:51
*** goldyfruit has quit IRC17:53
*** e0ne has joined #openstack-oslo18:12
*** e0ne has quit IRC18:34
*** jbadiapa has quit IRC19:00
*** e0ne has joined #openstack-oslo19:03
*** e0ne has quit IRC19:09
*** e0ne has joined #openstack-oslo19:10
*** jbadiapa has joined #openstack-oslo19:13
*** goldyfruit_ has quit IRC19:15
*** bnemec has quit IRC19:27
*** bnemec has joined #openstack-oslo19:32
*** goldyfruit has joined #openstack-oslo19:33
*** trident has quit IRC20:15
*** trident has joined #openstack-oslo20:27
*** kgiusti has left #openstack-oslo20:29
*** trident has quit IRC20:32
*** trident has joined #openstack-oslo20:33
*** ansmith has quit IRC20:49
*** boden has quit IRC20:53
*** raildo has quit IRC20:58
*** ansmith has joined #openstack-oslo21:24
*** e0ne has quit IRC21:40
*** snapiri has quit IRC21:41
*** lbragstad_ has joined #openstack-oslo21:44
*** lbragstad has quit IRC21:44
*** goldyfruit has quit IRC22:01
*** goldyfruit has joined #openstack-oslo22:08
*** lbragstad_ is now known as lbragstad22:11
*** goldyfruit_ has joined #openstack-oslo22:21
*** goldyfruit has quit IRC22:24
*** bobh has joined #openstack-oslo22:37
*** bobh has quit IRC22:45
*** goldyfruit_ has quit IRC22:51
*** rcernin has joined #openstack-oslo22:59
*** threestrands has joined #openstack-oslo23:14

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