Thursday, 2019-10-17

*** lseki has quit IRC00:01
*** Lucas_Gray has joined #openstack-meeting00:09
*** markvoelker has joined #openstack-meeting00:15
*** markvoelker has quit IRC00:20
*** markvoelker has joined #openstack-meeting00:22
*** mriedem_afk has quit IRC00:30
*** enriquetaso has quit IRC00:33
*** bbowen has joined #openstack-meeting00:40
*** liuyulong has quit IRC00:42
*** bnemec has quit IRC00:45
*** rfolco has joined #openstack-meeting00:49
*** rcernin has joined #openstack-meeting00:51
*** brinzhang has joined #openstack-meeting00:53
*** bnemec has joined #openstack-meeting00:56
*** bnemec has quit IRC01:07
*** Liang__ has joined #openstack-meeting01:10
*** brinzhang_ has joined #openstack-meeting01:11
*** brinzhang has quit IRC01:14
*** anastzhyr has quit IRC01:26
*** nanzha has joined #openstack-meeting01:30
*** brinzhang has joined #openstack-meeting01:34
*** brinzhang_ has quit IRC01:36
*** rfolco has quit IRC01:42
*** jamesmcarthur has joined #openstack-meeting01:53
*** jamesmcarthur has quit IRC01:53
*** jamesmcarthur has joined #openstack-meeting01:53
*** Lucas_Gray has quit IRC01:56
*** brinzhang_ has joined #openstack-meeting02:05
*** brinzhang_ has quit IRC02:05
*** yaawang_ has quit IRC02:06
*** yaawang_ has joined #openstack-meeting02:06
*** brinzhang has quit IRC02:08
*** apetrich has quit IRC02:10
*** jamesmcarthur has quit IRC02:26
*** jamesmcarthur has joined #openstack-meeting02:27
*** jamesmcarthur has quit IRC02:28
*** jamesmcarthur has joined #openstack-meeting02:28
*** jamesmcarthur has quit IRC02:29
*** jamesmcarthur has joined #openstack-meeting02:37
*** jamesmcarthur has quit IRC02:42
*** ricolin has joined #openstack-meeting02:55
*** jamesmcarthur has joined #openstack-meeting03:00
*** pleia2 has quit IRC03:04
*** jamesmcarthur has quit IRC03:08
*** yaawang_ has quit IRC03:08
*** yaawang_ has joined #openstack-meeting03:08
*** pleia2 has joined #openstack-meeting03:13
*** ykatabam has quit IRC03:22
*** dmacpher__ has joined #openstack-meeting03:23
*** dmacpher_ has quit IRC03:25
*** ykatabam has joined #openstack-meeting03:25
*** psachin has joined #openstack-meeting03:40
*** jamesmcarthur has joined #openstack-meeting03:42
*** larainema has joined #openstack-meeting03:55
*** Liang__ is now known as LiangFang04:05
*** rbudden has quit IRC04:09
*** igordc has quit IRC04:15
*** diablo_rojo has quit IRC04:17
*** pcaruana has joined #openstack-meeting04:18
*** jamesmcarthur has quit IRC04:35
*** jamesmcarthur has joined #openstack-meeting04:37
*** jamesmcarthur has quit IRC04:43
*** markvoelker has quit IRC04:45
*** lbragstad has quit IRC04:53
*** lbragstad has joined #openstack-meeting04:53
*** dmsimard has quit IRC04:54
*** dansmith has quit IRC04:54
*** dmsimard has joined #openstack-meeting04:54
*** ianw has quit IRC04:54
*** ianw_ has joined #openstack-meeting04:55
*** dansmith has joined #openstack-meeting04:55
*** ianw_ is now known as ianw04:56
*** Luzi has joined #openstack-meeting05:04
*** jamesmcarthur has joined #openstack-meeting05:05
*** jamesmcarthur has quit IRC05:12
*** jamesmcarthur has joined #openstack-meeting05:19
*** jamesmcarthur has quit IRC05:24
*** ociuhandu has joined #openstack-meeting05:26
*** ociuhandu has quit IRC05:31
*** sridharg has joined #openstack-meeting05:33
*** brinzhang has joined #openstack-meeting05:34
*** links has joined #openstack-meeting05:37
*** brinzhang has quit IRC05:39
*** takamatsu has quit IRC05:47
*** jawad_axd has joined #openstack-meeting05:59
*** jawad_ax_ has joined #openstack-meeting06:03
*** jawad_axd has quit IRC06:03
*** lpetrut has joined #openstack-meeting06:04
*** lpetrut has quit IRC06:05
*** lpetrut has joined #openstack-meeting06:05
*** jawad_ax_ has quit IRC06:07
*** whoami-rajat has joined #openstack-meeting06:12
*** jawad_axd has joined #openstack-meeting06:14
*** ykatabam has quit IRC06:15
*** janki has joined #openstack-meeting06:18
*** rcernin has quit IRC06:18
*** nanzha has quit IRC06:26
*** nanzha has joined #openstack-meeting06:28
*** LiangFang has quit IRC06:29
*** Liang__ has joined #openstack-meeting06:29
*** markvoelker has joined #openstack-meeting06:46
*** markvoelker has quit IRC06:51
*** trident has quit IRC06:55
*** slaweq has joined #openstack-meeting06:55
*** trident has joined #openstack-meeting06:58
*** gibi_off is now known as gibi07:02
*** links has quit IRC07:04
*** jraju__ has joined #openstack-meeting07:04
*** jraju__ is now known as links07:07
*** tesseract has joined #openstack-meeting07:09
*** takamatsu has joined #openstack-meeting07:18
*** ttsiouts has joined #openstack-meeting07:18
*** ttsiouts has quit IRC07:38
*** ttsiouts has joined #openstack-meeting07:39
*** ttsiouts has quit IRC07:43
*** Liang__ has quit IRC07:44
*** rpittau|afk is now known as rpittau07:52
*** ttsiouts has joined #openstack-meeting07:53
*** ralonsoh has joined #openstack-meeting07:57
*** tssurya has joined #openstack-meeting07:59
*** e0ne has joined #openstack-meeting08:01
*** ociuhandu has joined #openstack-meeting08:06
*** ociuhandu has quit IRC08:15
*** e0ne_ has joined #openstack-meeting08:17
*** e0ne has quit IRC08:17
*** whoami-rajat has quit IRC08:22
*** kopecmartin|off is now known as kopecmartin08:23
*** takamatsu has quit IRC08:32
*** ociuhandu has joined #openstack-meeting08:40
*** ociuhandu has quit IRC08:42
*** zbr has quit IRC09:07
*** janki has quit IRC09:09
*** zbr has joined #openstack-meeting09:10
*** e0ne has joined #openstack-meeting09:10
*** e0ne_ has quit IRC09:11
*** ociuhandu has joined #openstack-meeting09:21
*** ociuhandu has quit IRC09:25
*** ociuhandu has joined #openstack-meeting09:31
*** ociuhandu has quit IRC09:32
*** ociuhandu has joined #openstack-meeting09:33
*** ricolin has quit IRC09:50
*** brinzhang has joined #openstack-meeting09:57
*** Luzi has quit IRC10:00
*** whoami-rajat has joined #openstack-meeting10:00
*** ykatabam has joined #openstack-meeting10:25
*** ociuhandu has quit IRC10:27
*** ociuhandu has joined #openstack-meeting10:27
*** ttsiouts has quit IRC10:30
*** ttsiouts has joined #openstack-meeting10:31
*** brinzhang_ has joined #openstack-meeting10:34
*** ttsiouts has quit IRC10:36
*** brinzhang has quit IRC10:36
*** brinzhang has joined #openstack-meeting10:37
*** brinzhang_ has quit IRC10:38
*** Luzi has joined #openstack-meeting10:44
*** dmellado has quit IRC10:55
*** dmellado has joined #openstack-meeting10:57
*** brinzhang_ has joined #openstack-meeting10:57
*** brinzhang_ has quit IRC10:58
*** brinzhang has quit IRC11:00
*** jamesmcarthur has joined #openstack-meeting11:00
*** jamesmcarthur has quit IRC11:04
*** ykatabam has quit IRC11:19
*** ttsiouts has joined #openstack-meeting11:33
*** hyunsikyang has quit IRC11:41
*** ttsiouts has quit IRC11:44
*** ttsiouts has joined #openstack-meeting11:45
*** dviroel has joined #openstack-meeting11:45
*** ociuhandu has quit IRC11:47
*** ociuhandu has joined #openstack-meeting11:48
*** Luzi has quit IRC11:48
*** markvoelker has joined #openstack-meeting11:48
*** ttsiouts has quit IRC11:49
*** ociuhandu has quit IRC11:54
*** raildo has joined #openstack-meeting11:56
*** ociuhandu has joined #openstack-meeting12:03
*** Luzi has joined #openstack-meeting12:04
*** ociuhandu has quit IRC12:11
*** jamesmcarthur has joined #openstack-meeting12:11
*** ociuhandu has joined #openstack-meeting12:11
*** njohnston_ is now known as njohnston12:16
*** ociuhandu has quit IRC12:16
*** rfolco has joined #openstack-meeting12:23
*** larainema has quit IRC12:26
*** takamatsu has joined #openstack-meeting12:35
*** jamesmcarthur has quit IRC12:36
*** brinzhang has joined #openstack-meeting12:37
*** mriedem has joined #openstack-meeting12:42
*** number80 has joined #openstack-meeting12:44
*** jamesmcarthur has joined #openstack-meeting12:45
*** eharney has quit IRC12:45
*** Luzi has quit IRC12:48
*** Luzi has joined #openstack-meeting12:49
*** whoami-rajat has quit IRC12:50
*** whoami-rajat has joined #openstack-meeting12:52
*** brinzhang_ has joined #openstack-meeting12:54
*** dmsimard has quit IRC12:54
*** takashin has joined #openstack-meeting12:54
*** ttsiouts has joined #openstack-meeting12:54
*** tetsuro has quit IRC12:55
*** dmsimard has joined #openstack-meeting12:55
*** tetsuro has joined #openstack-meeting12:55
*** brinzhang has quit IRC12:56
*** lseki has joined #openstack-meeting13:00
*** rfolco is now known as rfolco|ruck13:03
*** rbudden has joined #openstack-meeting13:03
*** ttsiouts has quit IRC13:06
*** ttsiouts has joined #openstack-meeting13:07
*** ociuhandu has joined #openstack-meeting13:09
*** ttsiouts has quit IRC13:11
*** takamatsu has quit IRC13:12
*** ttsiouts has joined #openstack-meeting13:14
*** eharney has joined #openstack-meeting13:30
*** lbragsta_ has joined #openstack-meeting13:43
*** efried has joined #openstack-meeting13:46
*** efried is now known as efried_afk13:46
*** brinzhang has joined #openstack-meeting13:47
*** brinzhang_ has quit IRC13:50
*** diconico07 has joined #openstack-meeting13:51
*** jawad_axd has quit IRC13:52
*** jawad_axd has joined #openstack-meeting13:54
*** ociuhandu has quit IRC13:57
*** Luzi has quit IRC13:57
*** jawad_axd has quit IRC13:58
*** cdent has joined #openstack-meeting13:59
mriedem#startmeeting nova14:00
openstackMeeting started Thu Oct 17 14:00:11 2019 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova)"14:00
openstackThe meeting name has been set to 'nova'14:00
takashino/14:00
melwitto/14:00
cdento.14:00
mriedemefried is shuttling kids atm14:00
* cdent is only barely here14:00
stephenfino/14:00
dansmitho/14:00
gmanno/14:00
mriedem#link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting14:01
mriedem#topic Last meeting14:01
*** openstack changes topic to "Last meeting (Meeting topic: nova)"14:01
mriedem#link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-03-14.00.html14:01
mriedemactions:14:01
mriedem#link db migration placeholders (merged) https://review.opendev.org/#/c/686411/ (done)14:01
mriedem#link SEV bug warning patch https://review.opendev.org/#/c/686414/ (done)14:01
mriedem#link update contributor guide https://review.opendev.org/#/c/685630/ - done but more could be done14:01
mriedem#topic Release News14:01
*** openstack changes topic to "Release News (Meeting topic: nova)"14:02
mriedemTrain is released, stable/train is open for business.14:02
mriedem#link Nova Ussuri schedule https://wiki.openstack.org/wiki/Nova/Ussuri_Release_Schedule14:02
mriedemany questions about release stuff?14:02
dansmithhmm,14:02
dansmithso the compute alias patch finally landed, I guess I should propose that to train as well14:02
*** ociuhandu has joined #openstack-meeting14:02
mriedemi think it's optional,14:02
mriedemwhen looking at stein and rocky, we did one of those in it's target release and one after14:03
mriedembut didn't backport14:03
mriedemi can't remember which14:03
mriedemit doesn't hurt to backport either so whatever14:03
dansmithit is not critical, but it's confusing for it to not be consistent, just not a huge deal to hold it up14:03
dansmithyeha14:03
mriedemmoving on14:04
mriedem#topic Summit/PTG Planning14:04
*** openstack changes topic to "Summit/PTG Planning (Meeting topic: nova)"14:04
mriedemUssuri scope containment,14:04
mriedem#link Spec template update for "core liaison" is merged https://review.opendev.org/#/c/685857/14:04
mriedem^ had 2 cores vote on it so that makes 3 total that are aware of the new spec process,14:04
mriedemif people have issues with what was merged they can propose amendments14:05
* mriedem doesn't know what the new process is yet either really14:05
mriedemquestions?14:05
dansmithlol14:05
gmannso we still waiting for new process of spec selection right ?14:05
*** jawad_axd has joined #openstack-meeting14:05
gmanncore liaison is just for adding liaison things not the new process14:06
dansmithnot really "waiting" I don't think.. specs are being approved and implemented14:06
mriedemyou mean the capping14:06
gmannyeah14:06
gmannor we dropped the idea of capping14:06
mriedemi want to say eric intends on capping things as we get closer to a freeze date but not sure14:06
mriedemi don't think he dropped the idea of capping14:06
mriedembut i also haven't been paying much attention to it either so you'd have to ask eric14:06
gmannok14:07
mriedem#topic Stable branch status14:07
*** openstack changes topic to "Stable branch status (Meeting topic: nova)"14:07
mriedemas i said stable/train is open and i've been +2ing changes14:07
mriedem#link stable/train: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/train14:07
mriedemwe just recently-ish did a stein release,14:07
mriedem#link stable/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein14:07
*** ociuhandu has quit IRC14:07
mriedemwe did a rocky release last week,14:07
mriedem#link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky14:07
mriedemand we need to flush queens and do a release soon,14:08
mriedem#link stable/queens: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/queens14:08
mriedemqueens goes into extended maintenance in a couple of weeks14:08
mriedemoct 25 to be exact14:08
*** brinzhang_ has joined #openstack-meeting14:08
mriedem#help review stable/queens backports so we can flush the queue and do a final release before extended maintenance14:08
mriedemnote that some of the things proposed to queens are yet to be merged on the newer branches - basically everything gibi is pushing :)14:09
mriedemquestions about stable?14:09
mriedem#topic Bugs (stuck/critical)14:09
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)"14:09
mriedemthere is 1 critical bug,14:09
mriedem#link https://bugs.launchpad.net/nova/+bug/184849914:09
openstackLaunchpad bug 1848499 in OpenStack Compute (nova) "tests fail with networkx 2.4: "AttributeError: 'DiGraph' object has no attribute 'node'"" [Critical,In progress] - Assigned to Balazs Gibizer (balazs-gibizer)14:09
mriedemgibi has a patch: https://review.opendev.org/#/c/689152/14:10
mriedembut we're totally blocked in the gate until that lands14:10
mriedemso hold your rechecks14:10
mriedem#link 85 new untriaged bugs (+11 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New14:10
dansmithso,14:10
dansmiththat was not the failure I saw and rechecked for14:10
mriedemyeah it is14:10
dansmiththere were like five powervm unit fails14:10
mriedemit's the powervm driver tests,14:10
mriedemwhich use taskflow,14:10
mriedemwhich uses networkx14:10
dansmithoh, jeez, okay14:10
mriedemwhich just released and is uncapped14:11
mriedemturbugen14:11
*** bnemec has joined #openstack-meeting14:11
mriedemas seen from the numbers above we're falling behind in bug triage,14:11
mriedem#link 9 untagged untriaged bugs (+6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW14:11
mriedem#link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags14:11
mriedem#help need help with bug triage14:11
*** brinzhang has quit IRC14:12
mriedemwe do have a few random oslo.messaging/conductor related bugs sitting in triage that i don't know what to do with14:12
mriedemsince they are like, "rpc something, service crashed"14:12
mriedem*shrug*14:12
efried_afko/ sorry folks14:12
* efried_afk catches up14:12
*** efried_afk is now known as efried14:12
mriedemefried_afk: we're at gate status, you want me to just keep going?14:12
mriedemefried: ^14:13
mriedem#topic Gate status14:13
*** openstack changes topic to "Gate status (Meeting topic: nova)"14:13
mriedem#link check queue gate status http://status.openstack.org/elastic-recheck/index.html14:13
mriedemso we obviously have a few gate bugs, the one above being the main issue,14:13
mriedemhttp://status.openstack.org/elastic-recheck/index.html#1844929 is our other major gate bug,14:13
mriedemfor which i don't have an answer14:13
mriedemi have a couple of patches up to grenade and devstack gate to try and get more detailed mysql logs to see why mysql connections are getting aborted,14:14
mriedembut those patches aren't working yet and i haven't been prioritizing it14:14
mriedemso if someone can help that'd be cool14:14
efriedmriedem: yes please and thanks.14:14
mriedem#link 3rd party CI status (seems to be back in action) http://ciwatch.mmedvede.net/project?project=nova14:14
mriedemnot much to report on 3rd party ci status except i'm sure some jobs are still not working,14:15
*** ociuhandu has joined #openstack-meeting14:15
mriedemand i reported a thing to the hyper-v guys last week and it was already fixed by the time i reported it so thanks to them for being on top of their game14:15
mriedem#topic Reminders14:15
*** openstack changes topic to "Reminders (Meeting topic: nova)"14:15
mriedemthere is nothing in the agenda for reminders14:15
mriedem#topic Sub/related team Highlights14:16
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)"14:16
mriedemPlacement (cdent/tetsuro) ?14:16
mriedemi was just going to note https://review.opendev.org/#/c/688969/ if there was nothing else14:16
cdenttetsuro: posted an email about ptg topics for people who will be there14:16
mriedemas i said on there i'm a .5 meh14:16
cdentmelwitt made some updates to the consumer types stuff (thank you!)14:16
cdentthat's all I know14:16
mriedemack,14:17
efried#link placement ptg http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010182.html14:17
efried#link placement ptg etherpad https://etherpad.openstack.org/p/placement-shanghai-ptg14:17
melwittyeah, I just addressed my own test comments. stack has passed CI14:17
efriedre COMPUTE_NODE patch, if we can get that merged and released, I can roll up two versions in the placement catch-up.14:18
gibiefried: I will look at it soon ^^14:18
efriedthx14:18
mriedemdansmith: just so you're aware, and i don't remember if there is any reason not to do this,14:18
*** lpetrut has quit IRC14:18
mriedembut that patch is to add a generic COMPUTE_NODE trait to more easily filter compute node resource providers, like in sylvain's audit CLI14:18
mriedemi feel like we've talked about this a few times over the years but just never did it for whatever reason14:19
*** zaneb has quit IRC14:19
mriedemmoving on to,14:19
mriedemAPI (gmann)14:19
gmannI have not started updates for ussuri yet (may be after PTG I will collect the API works and status)14:19
gmannand reminder for review on policy spec  - https://review.opendev.org/#/c/686058/14:19
gmannthat's all from me today.14:20
mriedemok14:20
mriedem#topic Stuck Reviews14:20
*** openstack changes topic to "Stuck Reviews (Meeting topic: nova)"14:20
*** jamesmcarthur has quit IRC14:20
mriedemnothing in the agenda14:20
mriedem#topic Review status page14:20
*** openstack changes topic to "Review status page (Meeting topic: nova)"14:20
mriedem#link http://status.openstack.org/reviews/#nova14:20
mriedemCount: 456 (-1); Top score: 2133 (+42)14:20
mriedem#help Pick a patch near the top, shepherd it to closure14:20
mriedemjust a reminder on ^,14:20
mriedemif you abandon a change, update the related bug (mark it invalid if it's invalid, etc)14:21
mriedem#topic Open discussion14:21
*** openstack changes topic to "Open discussion (Meeting topic: nova)"14:21
mriedemsince we skipped last week's meeting we have a lot more than usual items here14:21
mriedem#help Volunteer core(s) for "Meet the Project Leaders" in Shanghai14:21
mriedemi think that is done14:21
mriedemefried: ^?14:21
efried...14:21
mriedemi thought stephenfin and gibi were signing up for all outreach work14:22
efriedYup, bauzas and stephenfin have volunteered14:22
mriedemok14:22
gmann#link https://etherpad.openstack.org/p/meet-the-project-leaders14:22
gibiI can be there if needed14:22
gmannstephenfin14:22
efriedthanks for that14:22
mriedemi'm assuming alex_xu will also be at the summit...?14:22
gmannboth14:22
mriedemseems like it would be good to have the one chinese nova core involved in that stuff while in china :)14:22
stephenfinyes, yes it would14:23
mriedem#help Volunteer for interop guidelines14:23
mriedem#link http://paste.openstack.org/raw/781768/14:23
mriedemnot sure if anyone signed up for this,14:23
mriedemFWIW I think this is the last time we added anything and it was the  first time we added a guideline that depended on a microversion: https://review.opendev.org/509955/14:23
mriedemthat was adding the 2.2 keypair type microversion to interop14:24
mriedemthat microversion was added in kilo....14:24
mriedemso you can see how far behind the guidelines are compared to the compute API14:24
mriedemi'm not signing up, but if someone is interested you could just look for something newer than kilo that would be non-admin and hypervisor-agnostic as a potential guideline14:25
mriedemmoving on,14:25
mriedem#link in-place numa rebuild https://blueprints.launchpad.net/nova/+spec/inplace-rebuild-of-numa-instances14:25
mriedemsean-k-mooney: ^14:25
mriedemi'm not sure why that's a blueprint rather than a bug?14:25
sean-k-mooneyya so its acatully 2 bugs14:26
gmannfor interop microversion, interop question was for corresponding tempest tests and we said we have exiting tests and if no tests then it can be added14:26
sean-k-mooneyi create a blue  pritn just to group them together14:26
sean-k-mooneyhttps://review.opendev.org/#/c/687957/ is 99% of the work addressing https://bugs.launchpad.net/nova/+bug/176376614:26
openstackLaunchpad bug 1763766 in OpenStack Compute (nova) "nova needs to disallow resource consumption changes on image rebuild" [Medium,In progress] - Assigned to sean mooney (sean-k-mooney)14:26
sean-k-mooneythe final step is skiping the numa toplogy filer on rebuild14:27
efriedif it's bugs, do it as bugs, save some paperwork.14:27
mriedemyou also can't backport blueprints generally14:27
mriedemso i'd nack the blueprint14:27
sean-k-mooneyi just wanted to make sure people were ok with that apparch14:27
gibiif this is more than one bug I think having a bp helps to track the work14:27
dansmiththis is a pretty big change though14:27
dansmiththe bugs are more "this was never implemented" which we've previously said are not good bugs14:28
sean-k-mooneydansmith: not really well feature wise maybe14:28
sean-k-mooneycode wise its small14:28
dansmithsean-k-mooney: I know14:28
dansmithseems like a BP to me14:28
sean-k-mooneyya which is the main reason i filled the blueprint14:28
sean-k-mooneyso honestly i dont mind either way14:29
sean-k-mooneybut im tracking it as an RFE downstream14:29
mriedemregarding changing rebuild to explicitly fail,14:29
mriedemwe did that as a bug fix for volume-backed servers when the image changes,14:30
mriedembecause we used to silently allow that and the image in the root volume never changed and confused everyone14:30
mriedemis this like that?14:30
sean-k-mooneyyep exactly14:30
sean-k-mooneywe do a noop claim14:30
sean-k-mooneyso the numa toplogy does not change14:30
sean-k-mooneyuntill you do a move operation14:30
mriedembut the image might have a different topology14:30
sean-k-mooneyyep14:31
mriedemi would only question if people have been relying on that behavior such that it's now a "feature",14:31
mriedemi.e. rebuild with new image with new topology and then migrate14:31
mriedemdansmith: is that your concern? ^14:32
*** takamatsu has joined #openstack-meeting14:32
sean-k-mooneyi debated adding a workaround config option to allow that for backport reaons. but going forword i would prefer not to support that14:32
sean-k-mooneykind of like the numa migration14:32
dansmithmriedem: no, I don't really have any concerns, I just think that it makes sense to call this a blueprint/feature addition14:33
dansmith"foo is not implemented" is not a bug to me14:33
dansmithwhich we've said several times14:33
dansmithbut we've already spent too much time on it here, so I'd say call it a pink elephant if you want, let's just move on and do it14:34
mriedemok moving on, i left some thoughts in the patch14:34
mriedem(melwitt) requesting approval for specless blueprint: https://blueprints.launchpad.net/nova/+spec/policy-rule-for-host-status-unknown14:35
melwittyeah, this is the same blueprint from last cycle that I had asked about. adding a new policy rule14:35
mriedemassuming melwitt's patch matches the conditions set in the blueprint whiteboard the last time we talked about this,14:35
mriedemi don't see why we wouln't approve14:35
melwittyes, the patch is implemented as described by mriedem in the bp whiteboard14:35
mriedemthen i'm +1 to approve14:36
mriedemgibi also said he was ok with it in the bp14:36
mriedemand i'm assuming efried is as well14:36
mriedemso barring any objections i'll approve after the meeting14:36
efriedgo for it14:36
melwittthank you14:37
*** links has quit IRC14:37
mriedem(stephenfin) approval for specless blueprint: https://blueprints.launchpad.net/nova/+spec/remove-xvpvncproxy14:37
*** jawad_axd has quit IRC14:37
* stephenfin perks up14:37
gibiok with me14:37
stephenfinonly complication is that there's an API here14:37
stephenfinbut we've removed (HTTP Gone) nova-network APIs in the past without specs so it should be okay, imo14:38
melwittthis would be done similar to how you removed os-cells right? is there anything different14:38
mriedemjust a 410, it's the same14:38
stephenfinnah, same thing14:38
melwittok, then yeah seems fine to me14:38
mriedemBobBall said in the mailing list before/around the denver ptg that no one is probably using this right?14:38
stephenfincorrect. I've a patch up and have linked to those discussions from it14:38
mriedemof course we don't know who uses xenserver, they seem to randomly show up14:38
stephenfinwe also included it in reno, and they have another option (noVNC)14:39
mriedemthe only point i wasn't clear on from bob's email was a replacement for this14:39
stephenfinnoVNC14:39
mriedemah14:39
mriedemok14:39
melwittyeah what I recall from the ML thread, it is safe to remove and an old legacy thing14:39
mriedemalright so barring objections (again) i'll approve after the meeting14:39
mriedem(mriedem): Need to discuss options for https://bugs.launchpad.net/nova/+bug/184736714:40
openstackLaunchpad bug 1847367 in OpenStack Compute (nova) "Images with hw:vif_multiqueue_enabled can be limited to 8 queues even if more are supported" [Undecided,Confirmed]14:40
*** gyee has joined #openstack-meeting14:40
*** ttsiouts has quit IRC14:40
mriedemso apparently we have hard-coded some tap queue limits in the libvirt driver vif module based on kernel version,14:40
sean-k-mooneymriedem: thats on my dodo list for this week14:40
mriedemkeep your doodoo to yourself sean14:40
sean-k-mooney:)14:41
efriedhah, I need to call it my dodo list. Work that's extinct.14:41
mriedembut centos has a patched kernel that allows more than what we have hard-coded14:41
mriedemi don't really want distro-specific checks in our code,14:41
sean-k-mooneyam its a long know bug14:41
sean-k-mooneybasically the limit should never have applied to vhost-user ports14:41
mriedemso another option is just having a workaround flag to allow deployers to set the value14:41
stephenfinyet another is that we just document this14:42
mriedemdocument what14:42
mriedem?14:42
melwittis it an option that we expect to eventually remove? that's the usual condition for [workarounds]14:42
stephenfinthat some distros are broken14:42
stephenfinyou want the fix, go bug your vendor to backport the fix a lá CentOS14:42
stephenfinassuming I've understood it correctly14:42
sean-k-mooneywell the issue is that rhel/centos backported chagnes form the 4.x kernel14:42
stephenfinah, wait, yeah, other way round14:43
stephenfinignore me14:43
melwittI think it's the opposite? we hard-coded something based on kernel version14:43
melwittyeah14:43
sean-k-mooneyyes14:43
*** ttsiouts has joined #openstack-meeting14:43
*** sridharg has quit IRC14:43
mriedemmelwitt: idk what the timeline would be for removal,14:43
sean-k-mooneyso we could add a workaorund flag for it as mriedem suggested14:43
mriedemwe don't really require min versions of kernels14:43
diconico07unless there is some procfile or sysfile magic to do here this is the best solution imo14:43
mriedemif not a workaround flag, it'd be a libvirt group flag14:43
mriedemi would default to None to let nova decide but allow you to override if you're using a patched kernel14:44
mriedemare people ok with that?14:44
sean-k-mooneythis is also applied to vhost-user ports today which it should nerver have been applie too so that is what i planned to work on tomorrow14:44
stephenfinwfm14:44
sean-k-mooneymriedem: that works for me14:45
mriedemsean-k-mooney: ok so you can mention vhostuser ports in the bug report i guess, sounds like those are separate changes14:45
melwittyeah. I can't decide whether it should be [workarounds] or not, but config option seems like the best way14:45
mriedem#agree add libvirt group option to override max tap limit for bug 184736714:45
openstackbug 1847367 in OpenStack Compute (nova) "Images with hw:vif_multiqueue_enabled can be limited to 8 queues even if more are supported" [Undecided,Confirmed] https://launchpad.net/bugs/184736714:45
sean-k-mooneymriedem: we applie the kernel limit to vhoust-user ports too14:45
sean-k-mooneyso ya its a sperate but related issue14:45
sean-k-mooneymriedem: do you want me to take this14:45
mriedemsean-k-mooney: you're talking to me about this like i know anything about vhostuser limits and max tap queues14:45
sean-k-mooneysince i was going to fix it for vhostuser anyway14:45
mriedemmoving on14:45
mriedemsean-k-mooney: separate bugs14:46
mriedemjust report a different bug14:46
sean-k-mooneyok14:46
mriedem(mriedem): Do we have a particular stance on features to the libvirt  driver for non-integration tested configurations, e.g. lxc [ https://review.opendev.org/#/c/667976/ ] and xen [ https://review.opendev.org/#/c/687827/  ], meaning if they are trivial enough do we just say the driver's  quality warning on startup is sufficient to let them land since these  are changes from casual contributors scratching an itch?14:46
mriedemmaybe ^ should be in the ML14:46
efriedyeah, that's a weird one.14:47
mriedembut these examples seem trivial enough to me to fall under part-time hobby contributor scratching an itch14:47
stephenfinprobably, yeah14:47
melwittyeah, maybe good for ML14:47
mriedemso saying "3rd party ci or die" won't fly14:47
stephenfinbut with that said14:47
*** ricolin has joined #openstack-meeting14:47
melwittand I agree, if trivial then ok to land14:47
stephenfinif it doesn't impact _other_ drivers, go nuts, I say14:47
mriedem#action mriedem to ask on the ML about accepting trivial feature patches for driver configs that don't get integration testing14:48
diconico07There is already a notice saying these drivers aren't integration tested14:48
mriedemi know, hence the "quality warning" thing in my line above14:48
clarkbalso we can test lc and xen upstream I think (xen might require some hax though)14:48
clarkb*lxc14:48
mriedemclarkb: "can" and "who is going to do and maintain that" are different things14:48
sean-k-mooneyclarkb: we could test xen more siplely if we had a xen image/lable14:49
mriedemmoving on,14:49
mriedemfinal item,14:49
mriedem(melwitt): requesting approval for specless blueprint: https://blueprints.launchpad.net/nova/+spec/nova-manage-db-purge-task-log14:49
mriedemmelwitt: i left a comment in there,14:49
clarkbI get that but telling soneone they can write a job is way easier that run an entore ci system14:49
mriedemsmells like a bug14:49
melwittI MLed about this awhile back14:49
melwittorly? I'm happy to treat it as a bug14:50
mriedemthe bug is that these records pile up and you have to go directly to the db to clean them up14:50
mriedemit's somewhere in between a super low priority bug and a feature i guess14:50
mriedemanyway, i'd probably just create a wishlist bug for it? idk what others think14:51
melwittour customers are using the task_log stuff by way of telemetry always enabling the audit API, so we have a lot of people affected by the record build up. and there are enough of them not otherwise truncating the table, it's all been one-offs14:51
mriedemwe don't have great process rules around adding ops tooling things for nova clis14:51
melwittok. I'm good either way so if ppl prefer a wishlist bug, I can do that14:51
mriedemi'm ok with a bug but others can overrule14:51
mriedemmaybe lobby for opions in -nova after the meeting, let efried decide14:52
mriedemanything else?14:52
melwittok14:52
mriedemok thanks for hanging in there everyone14:52
mriedem#endmeeting14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:53
openstackMeeting ended Thu Oct 17 14:52:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-17-14.00.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-17-14.00.txt14:53
efriedmriedem: thanks for covering.14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-17-14.00.log.html14:53
*** takashin has left #openstack-meeting14:53
*** gagehugo has joined #openstack-meeting14:53
*** efried is now known as efried_afk14:53
mriedemnp14:56
*** mhen has joined #openstack-meeting15:01
gagehugo#startmeeting security15:01
openstackMeeting started Thu Oct 17 15:01:15 2019 UTC and is due to finish in 60 minutes.  The chair is gagehugo. 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: security)"15:01
openstackThe meeting name has been set to 'security'15:01
gagehugo#link https://etherpad.openstack.org/p/security-agenda agenda15:01
fungigreetings15:01
*** andrebeltrami has joined #openstack-meeting15:03
*** diablo_rojo has joined #openstack-meeting15:03
gagehugolight agenda today15:03
fungii've been wrapped up in other things this past week, so not sure what there is to discuss15:05
gagehugosame15:05
fungithough we skipped last week15:05
gagehugoa busy october unfortunately15:05
fungiso we could talk about the octavia ossa15:06
fungithat was week before last15:06
gagehugosure15:06
fungi#link https://security.openstack.org/ossa/OSSA-2019-005.html OSSA-2019-005: Octavia Amphora-Agent not requiring Client-Certificate15:07
fungii thought this was actually a really cool first15:07
gagehugoyeah, the team there managed the process themselves for the most part15:07
fungithe octavia team followed the openstack vmt's process themselves, since that deliverable doesn't have a vulnerability:managed governance tag15:07
fungiso, yeah, the vmt just reviewed the ossa, octavia took care of the rest15:08
fungiit can't have been easy, so big kudos to them15:08
njohnstonfungi: I'll pass it on!  Very cool.15:08
* njohnston works closely with those folks15:09
johnsomo/15:09
fungialso i think it's our first ossa to link a story in storyboard instead of a bug in launchpad15:09
gagehugo\o/15:10
*** nanzha has quit IRC15:11
*** dmsimard has quit IRC15:11
fungiin more general news, there's quite a few patches proposed/merged/released for security hardening opportunities this month:15:11
fungi#link http://lists.openstack.org/pipermail/openstack-security/2019-October/thread.html15:11
funginot sure if anyone has any in particular they want to call out15:12
*** dmsimard has joined #openstack-meeting15:12
*** jamesmcarthur has joined #openstack-meeting15:12
fungi#link https://launchpad.net/bugs/1842749 CSV Injection Possible in Compute Usage History15:13
openstackLaunchpad bug 1842749 in OpenStack Dashboard (Horizon) "CSV Injection Possible in Compute Usage History" [High,Fix released] - Assigned to Adam Harwell (adam-harwell)15:13
*** nanzha has joined #openstack-meeting15:13
fungithat one was determined to be a security hardening opportunity 5 days ago, and the fix for it merged to master a few days later15:14
* gagehugo will take a look15:15
gagehugooh that's the windows one15:15
fungiyeah, i thought that was a rather obscure report, but nice to see folks thinking creatively about attack vectors15:16
*** cdent has left #openstack-meeting15:17
*** jamesmcarthur_ has joined #openstack-meeting15:17
*** mattw4 has joined #openstack-meeting15:18
gagehugoyeah, it's valid15:18
fungiwhat with everyone focused on train release prep the past few weeks, i expect there's just not much for us to talk about today15:21
gagehugoanything else for this week?15:21
gagehugoprobbaly15:21
gagehugoprobably*15:21
*** jamesmcarthur has quit IRC15:21
gagehugoWe can go ahead and cancel the meeting during the summit as well15:21
fungithat's likely for the best. thursday the 7th15:22
fungiof november15:23
fungii also doubt i'll be around for the meeting thursday october 31st as i'll be on my way to catch a flight to shanghai15:23
fungitechnically the one on november 7 is during the ptg not the summit, but close enough15:24
gagehugoyeah15:24
gagehugoI'll also be out the 21st of Nov15:24
fungiit's getting to be that time of year15:24
*** igordc has joined #openstack-meeting15:24
gagehugoyup15:25
gagehugowinter is coming15:25
fungiso anyway, plan to meet next week as usual, i'll miss the week after that, and then the following week is summit/ptg15:25
gagehugosounds good15:25
gagehugoanything else? floor is open15:26
gagehugothanks everyone, have a good rest of the week!15:28
gagehugo#endmeeting15:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:28
openstackMeeting ended Thu Oct 17 15:28:57 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/security/2019/security.2019-10-17-15.01.html15:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/security/2019/security.2019-10-17-15.01.txt15:29
openstackLog:            http://eavesdrop.openstack.org/meetings/security/2019/security.2019-10-17-15.01.log.html15:29
*** zbr has quit IRC15:29
*** zbr__ has joined #openstack-meeting15:29
fungithanks gagehugo!15:29
*** e0ne has quit IRC15:29
*** jawad_axd has joined #openstack-meeting15:32
*** enriquetaso has joined #openstack-meeting15:33
*** jamesmcarthur_ has quit IRC15:33
*** nanzha has quit IRC15:39
*** jamesmcarthur has joined #openstack-meeting15:49
*** brinzhang_ has quit IRC15:49
*** whoami-rajat has quit IRC15:50
*** brinzhang_ has joined #openstack-meeting15:50
*** brinzhang_ has quit IRC15:51
*** nanzha has joined #openstack-meeting15:52
*** ttsiouts has quit IRC15:54
*** donghao has joined #openstack-meeting15:55
*** tssurya has quit IRC16:00
*** enriquetaso has quit IRC16:02
*** armstrong has joined #openstack-meeting16:02
*** efried_afk is now known as efried16:02
*** rsimai_away is now known as rsimai16:08
*** rsimai is now known as rsimai_away16:08
*** ociuhandu_ has joined #openstack-meeting16:23
*** ociuhandu has quit IRC16:26
*** markvoelker has quit IRC16:26
*** rpittau is now known as rpittau|afk16:27
*** nanzha has quit IRC16:27
*** ociuhandu_ has quit IRC16:30
*** lpetrut has joined #openstack-meeting16:39
*** lpetrut has quit IRC16:40
*** lpetrut has joined #openstack-meeting16:40
*** geguileo has quit IRC16:46
*** enriquetaso has joined #openstack-meeting17:00
*** lpetrut has quit IRC17:01
*** markvoelker has joined #openstack-meeting17:05
*** zaneb has joined #openstack-meeting17:11
*** enriquetaso has quit IRC17:22
*** lpetrut has joined #openstack-meeting17:37
*** ociuhandu has joined #openstack-meeting17:38
*** zaneb has quit IRC17:41
*** enriquetaso has joined #openstack-meeting17:45
*** psachin has quit IRC17:46
*** armax has quit IRC17:48
*** andrebeltrami has quit IRC17:52
*** jamesmcarthur has quit IRC17:55
*** mriedem has quit IRC17:55
*** mriedem has joined #openstack-meeting17:56
*** jawad_axd has quit IRC17:59
SotK#startmeeting storyboard18:02
openstackMeeting started Thu Oct 17 18:02:24 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: storyboard)"18:02
openstackThe meeting name has been set to 'storyboard'18:02
diablo_rojoo/18:02
SotK#topic https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda18:02
*** openstack changes topic to "https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda (Meeting topic: storyboard)"18:02
diablo_rojoHeh, you mean link? ;)18:03
*** enriquetaso has quit IRC18:03
SotK#undo18:03
openstackRemoving item from minutes: #topic https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda18:03
SotKits that kind of day18:03
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda18:03
diablo_rojoNailed it :)18:04
SotKno announcements this week, and I assume the same for migration updates, since attachments aren't done yet18:04
diablo_rojoCorrect18:05
SotK#topic PTG + Forum18:06
*** openstack changes topic to "PTG + Forum (Meeting topic: storyboard)"18:06
SotK#link https://www.openstack.org/ptg/#tab_schedule Schedule18:06
SotKwe are on the schedule!18:06
SotK10:30am on Wednesday18:06
SotKthanks for organising that diablo_rojo18:06
diablo_rojoNo problem18:06
diablo_rojoWe've got two hours18:06
diablo_rojoI figured that should be alright.18:06
funginow if i just manage to get a visa so diablo_rojo isn't left answering questions alone18:06
diablo_rojoif we need more time we can always get more time friday18:07
diablo_rojofungi, you assume they will actually honor my 10 year visa ;)18:07
fungifair18:07
SotKI will be asleep I'm afraid18:08
fungii'll be struggling to stay awake18:08
diablo_rojoSotK, no worries. I will give you the lowdown at the next meeting or right after18:08
diablo_rojofungi, you and me both18:08
fungino coffee allowed in the ptg rooms! :/18:08
diablo_rojofungi, yeah. Not sure how this venue gets away with that.18:09
SotKdiablo_rojo: thanks18:09
diablo_rojoSotK, no problem18:09
SotKanything else PTGish to discuss?18:10
*** jawad_axd has joined #openstack-meeting18:11
diablo_rojoEhhh I dont think so.18:11
diablo_rojoIts going to be a wait and see sort of thing18:11
diablo_rojoSee who shows up that is18:11
SotKmakes sense18:12
SotKhopefully it goes well :)18:12
SotK#topic In Progress Work18:12
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"18:12
SotKto answer the question on the agenda, attachments are indeed still waiting for me18:12
diablo_rojoI guess we could send an email out to the discuss list annoucing we are doing onboarding there.18:12
SotKthat's a good idea18:12
diablo_rojoI can do that in like a week or so.18:13
diablo_rojoSotK, is there anything we can do to help?18:13
*** ociuhandu has quit IRC18:13
SotKthe main thing that needs doing is replacing swiftclient with openstack-sdk, but when I last tried openstack-sdk didn't work with the legacy swift auth used by the swift docker container I was using for testing18:15
fungiahh, yeah, it probably wants keystone?18:16
SotKyeah I expect so18:16
SotKso its a matter of me hunting down some alternatives that allow me to set up keystone and swift for testing easily and reliably, ideally in docker with the rest of the things18:17
diablo_rojoOkay so kinda sounds like a one person job then?18:19
SotKindeed18:19
fungithere's likely already something like that available which zuul is using to test their swift integration18:19
fungiso may not require much hunting18:20
SotKsounds probable, I'll try to find time to look/ask about what they're doing soon and get things moving again18:20
fungiwe can inquire in #zuul and probably get an answer, or i can go diving in the job configs18:20
SotKasking sounds easier, lets do it after this meeting I guess18:21
fungiwfm18:22
SotKwe also still have slow queries18:23
SotKiirc the worst offender was the general story browsing query, which makes sense18:23
SotKI've not done any drilling down into the details of why though18:23
diablo_rojoIf you want to try to point me somewhere to investigate I can try to info gather for you.18:24
*** ociuhandu has joined #openstack-meeting18:26
fungiif someone can give me the syntax for triggering that via the api, it'll probably speed up my ability to test the cache memory pressure theories too18:26
SotKI *think* the massive query was just the standard one generated by doing a GET on /api/v1/stories?limit=100 (with whatever extra filtering you fancy)18:28
*** lbragsta_ has quit IRC18:29
SotKmy first port of call was going to be seeding my dev instance with enough data to replicate the slowness we see in production, and then experiment with changing https://opendev.org/opendev/storyboard/src/branch/master/storyboard/db/models.py#L450-L47518:29
*** armax has joined #openstack-meeting18:30
SotKand/or adding some indexes to the relevant tables18:30
SotK(on task status for example)18:30
fungicool, that helps18:30
diablo_rojoNoted.18:30
fungirunning `time wget -qO/dev/null 'https://storyboard.openstack.org/api/v1/stories?limit=100'` gets me a baseline of "real 0m6.058s" at the moment18:31
fungiafter the meeting i'll run a battery of those and take averages before and after restarts of apache, mysql and rabbit18:32
*** zbr__ has quit IRC18:32
diablo_rojoSounds like a good plan to me.18:32
SotKnice, thanks18:32
fungias well as record the timestamps so we can correlate to cacti graphs of memory utilization18:32
fungi(and i'll get some direct memory utilization numbers from the server before and after each as well)18:32
*** zbr has joined #openstack-meeting18:33
diablo_rojoDo we want to throw all this research in a single etherpad?18:33
diablo_rojoI feel like it would be good to have it all + links to other slowquery logs in a single place.18:34
fungi#link https://etherpad.openstack.org/storyboard-query-performance-analysis18:34
fungii'll start doing it there18:34
diablo_rojoBeautiful.18:34
SotKexcellent18:34
diablo_rojoThanks fungi!18:35
SotKthe agenda also mentions the multiple task race condition issue18:36
SotKiirc we fixed that but caused a new bug with the fix18:36
SotKnew/similar18:36
SotKI think we'd come up with a solution but will need to dig in IRC logs to remember properly I expect18:36
diablo_rojoOh okay I forgot the solution.18:37
diablo_rojoIf we have one I can try to implement it.18:37
fungiyeah, i think the beer got to those memory cells for me18:38
diablo_rojoI would blame it on the 'too many things at once' state I live in18:38
fungiwould similarly need to go hunting for discussion or at least the commit we thought was fixing it18:38
fungiwas the fix one which came from an intern or prospective intern? i want to say it was18:38
diablo_rojoOh maybe18:39
diablo_rojoI feel like I should do a pass over all the open patches from outreachy folks18:40
diablo_rojoreviews + updates18:40
SotKyeah, we just added an oslo_db decorator that handles retrying on deadlock18:40
diablo_rojoOh thats easy.18:40
SotKbut it moved the issue to somewhere else18:40
diablo_rojoOh18:40
fungii think it had to do with it all happening within a transaction?18:41
SotKyeah, something along those lines18:41
*** armstrong has quit IRC18:41
fungiso retrying didn't help because it was all in the context of the same transaction18:41
diablo_rojoAh18:42
diablo_rojoThat makes sense18:42
fungibut also, retrying in the face of contention is a hack18:43
diablo_rojoYeah would be better to know what exactly is causing it.18:43
*** gagehugo has left #openstack-meeting18:43
fungiand i believe if that *had* actually "worked" it would have just shifted the limit on number of simultaneous tasks you can create to the number of retries you perform18:43
SotKindeed18:44
fungiso if you try 3 times then you'll break on simultaneous creation of 4 tasks18:45
funginot really a solution18:45
timburkeSotK, just catching up, but fwiw, swiftclient offers a v1password plugin for keystoneauth; i know i've had some success using it with openstackclient... might need https://review.opendev.org/#/c/687774/ though. but if the goal is to get rid of swiftclient *entirely*... i might not be in a position to help much ;-)18:46
*** lpetrut has quit IRC18:46
fungii think the goal was to simplify testing/local dev implementation18:46
fungibut the result is going to need to work with clouds which provide keystone authentication, so we're probably better off doing a keystone+swift for that testing anyway18:47
timburke👍18:47
*** jawad_axd has quit IRC18:50
SotKindeed, keystone + swift makes sense really18:51
SotKwe also wanted to discuss the js draft build issue18:51
diablo_rojo(8 min left)18:52
fungiyeah, i can cover that real quick18:52
diablo_rojoYes please18:52
fungisince opendev moved from hosting build artifacts/logs on a static logs.openstack.org server to publishing them to (swift) object storage, we can no longer easily predict what hostnames those are going to be served from18:52
*** ociuhandu has quit IRC18:52
fungithe storyboard api is currently designed to require you to whitelist the domain names of such deployments both for cors middleware and for openid auth18:53
fungibecause those domains are unpredictable, and because the storyboard-dev deployment they point to is not supposed to be used for sensitive information, i would like to basically turn off the cors and openid whitelisting for it18:54
fungithe easiest practical means of doing that is to allow the config fields for those to accept a wildcard indicator18:54
fungias a naive first implementation i'd like to just make them consider '*' to mean any hostname should be considered valid18:55
SotKthat seems like a good enough solution to me18:55
fungiit seems there was no disagreement in #storyboard when i suggested that, i just need to write the implementation. i've found what i believe are the affected codepaths18:56
fungiso it shouldn't take long18:56
fungibut would be nice to prioritize reviews of that once i get it proposed18:56
fungias i gather it's blocking us from having confidence in our reviews of webclient changes18:57
fungi(also i think the change will be pretty simple)18:57
fungianyway, that's all i've got on that topic18:57
SotKthanks fungi18:57
SotKI'll prioritize reviewing them when they're ready18:57
fungiappreciated. i'll try to get to that tomorrow18:58
diablo_rojoI am happy to review once I see the patches go up18:58
diablo_rojoSotK, after the meeting (while pinging the Zuul channel) would you mind reviewing that last show email patch I have out so that we can merge it?18:58
diablo_rojo(assuming its okay)18:58
SotKdiablo_rojo: yeah sure18:59
SotKand we're pretty much out of time, thanks for coming folks18:59
diablo_rojohttps://review.opendev.org/#/c/589713/18:59
fungiyeah, attempting to review that is what reminded me of the draft breakage18:59
diablo_rojoSotK, ^^18:59
* SotK opens19:00
SotK#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:00
openstackMeeting ended Thu Oct 17 19:00:16 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
diablo_rojofungi, ahhhh yeah that makes sense19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-10-17-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-10-17-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-10-17-18.02.log.html19:00
diablo_rojoThanks SotK!19:00
fungithanks SotK!19:00
*** tesseract has quit IRC19:07
*** rbudden has quit IRC19:12
*** lbragsta_ has joined #openstack-meeting19:17
*** lbragsta_ has quit IRC19:17
*** e0ne has joined #openstack-meeting19:25
*** e0ne has quit IRC19:34
*** ralonsoh has quit IRC19:47
*** pcaruana has quit IRC19:49
*** e0ne has joined #openstack-meeting19:52
*** e0ne has quit IRC19:53
*** bnemec has quit IRC20:03
*** bnemec has joined #openstack-meeting20:05
*** ricolin_ has joined #openstack-meeting20:06
*** ricolin has quit IRC20:09
*** efried is now known as efried_afk20:19
*** igordc has quit IRC20:26
*** jamesmcarthur has joined #openstack-meeting20:32
*** mattw4 has quit IRC20:48
*** mattw4 has joined #openstack-meeting20:48
*** mriedem has quit IRC20:49
*** eharney has quit IRC20:49
*** e0ne has joined #openstack-meeting20:57
*** igordc has joined #openstack-meeting20:58
*** trident has quit IRC20:58
*** jamesmcarthur has quit IRC20:59
*** raildo has quit IRC21:01
*** igordc has quit IRC21:03
*** trident has joined #openstack-meeting21:04
*** jamesmcarthur has joined #openstack-meeting21:08
*** panda has quit IRC21:08
*** igordc has joined #openstack-meeting21:09
*** lpetrut has joined #openstack-meeting21:11
*** panda has joined #openstack-meeting21:11
*** e0ne has quit IRC21:11
*** lbragstad has quit IRC21:14
*** rfolco|ruck has quit IRC21:17
*** lpetrut has quit IRC21:17
*** jamesmcarthur has quit IRC21:20
*** gyee has quit IRC21:20
*** ykatabam has joined #openstack-meeting21:22
*** lbragstad has joined #openstack-meeting21:24
*** jamesmcarthur has joined #openstack-meeting21:28
*** jamesmcarthur has quit IRC21:36
*** rcernin has joined #openstack-meeting21:39
*** markvoelker has quit IRC21:39
*** rcernin has quit IRC21:53
*** slaweq has quit IRC21:56
*** rcernin has joined #openstack-meeting22:09
*** ricolin_ has quit IRC22:10
*** slaweq has joined #openstack-meeting22:12
*** mmethot_ has quit IRC22:13
*** slaweq has quit IRC22:16
*** armax has quit IRC22:17
*** rcernin has quit IRC22:27
*** rcernin has joined #openstack-meeting22:27
*** radeks has joined #openstack-meeting22:44
*** diablo_rojo has quit IRC22:44
*** diablo_rojo has joined #openstack-meeting22:49
*** jbadiapa has quit IRC22:50
*** kopecmartin is now known as kopecmartin|off22:56
*** radeks has quit IRC22:57
*** mattw4 has quit IRC22:58
*** mattw4 has joined #openstack-meeting22:59
*** jbadiapa has joined #openstack-meeting23:04
*** jamesmcarthur has joined #openstack-meeting23:06
*** jbadiapa has quit IRC23:09
*** jbadiapa has joined #openstack-meeting23:16
*** jamesmcarthur has quit IRC23:29
*** Lucas_Gray has joined #openstack-meeting23:31
*** Lucas_Gray has quit IRC23:35
*** markvoelker has joined #openstack-meeting23:40
*** mattw4 has quit IRC23:41
*** jamesmcarthur has joined #openstack-meeting23:42
*** Lucas_Gray has joined #openstack-meeting23:44
*** markvoelker has quit IRC23:45

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