Tuesday, 2019-11-19

*** abaindur has quit IRC00:05
*** macz has quit IRC00:08
*** abaindur has joined #openstack-nova00:14
*** zhanglong has quit IRC00:14
*** abaindur has joined #openstack-nova00:14
*** zhanglong has joined #openstack-nova00:17
*** chenhaw has joined #openstack-nova00:39
*** chenhaw has quit IRC00:39
*** abaindur has quit IRC00:43
*** abaindur has joined #openstack-nova00:44
*** sapd1 has joined #openstack-nova00:54
*** brinzhang has joined #openstack-nova00:56
*** nanzha has joined #openstack-nova01:04
*** redrobot has quit IRC01:07
*** nanzha has quit IRC01:10
*** slaweq has joined #openstack-nova01:11
*** nanzha has joined #openstack-nova01:13
*** huaqiang has joined #openstack-nova01:14
*** slaweq has quit IRC01:15
*** mvkr has quit IRC01:18
*** gyee has quit IRC01:29
*** mdbooth has quit IRC01:30
*** ociuhandu has joined #openstack-nova01:31
*** mdbooth has joined #openstack-nova01:32
*** zhanglong has quit IRC01:33
*** ociuhandu has quit IRC01:36
*** ociuhandu has joined #openstack-nova01:44
*** ociuhandu has quit IRC01:48
*** ociuhandu has joined #openstack-nova01:49
*** ociuhandu has quit IRC01:57
*** factor has quit IRC02:03
*** ricolin has joined #openstack-nova02:04
*** slaweq has joined #openstack-nova02:11
openstackgerritHuachang Wang proposed openstack/nova-specs master: Use PCPU and VCPU in one instance  https://review.opendev.org/66865602:11
ianwwith the drop python2 change @ https://review.opendev.org/#/c/687954/ ... it get that you got to switch at some point.  but devstack doesn't default to python3, so this basically breaks the default case02:15
ianwi feel like it has been done in the wrong order02:16
*** slaweq has quit IRC02:16
ianwfor example, https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/install-devstack doesn't work any more02:19
*** igordc has quit IRC02:21
*** zhanglong has joined #openstack-nova02:25
openstackgerritIan Wienand proposed openstack/nova master: Revert "Stop testing Python 2"  https://review.opendev.org/69489102:28
*** brinzhang_ has joined #openstack-nova02:30
*** brinzhang has quit IRC02:33
*** zhanglong has quit IRC02:34
brinzhang_ianw: I met the same issue with you, an run many times, the devstack cannot up easily ...02:38
*** jbernard_ has joined #openstack-nova02:48
sean-k-mooneythere are patches to change the default in devstack but we have to wait untill after m1 to change it02:52
sean-k-mooneydevstack also has had support for python3 for years02:52
sean-k-mooneyits trivial to set USE_PYTHON3=true02:52
ianwpersonally i don't see that as a good argument for breaking the defaults02:53
sean-k-mooneywe have untill december to drop python 2 testing for non lib projects02:54
sean-k-mooneythe only functional change in that patch is the lack of installing contextlib202:55
sean-k-mooneyi guess the requirement for py36+ as well02:56
*** ociuhandu has joined #openstack-nova02:56
ianwyes, and that's the sticking point for mine02:56
sean-k-mooneyleaving it work until december 12th?02:57
sean-k-mooneythe Ussuri release is not expected to have python 2 support in general02:57
brinzhang_Other project can do this until december 12th? it's not only exist in nova02:57
ianwbrinzhang_: well, yes, but nova is probably the biggest target :)02:58
ianwsean-k-mooney: my suggestion would be to have devstacking using USE_PYTHON3 by default, then switch it02:58
sean-k-mooneynova is proably the most visable02:58
ianwswitching to USE_PYTHON3 by default and waiting, say, a week, should probably give any issues time to shake out02:59
sean-k-mooneyyou mean merge https://review.opendev.org/#/c/649097/02:59
ianwsean-k-mooney: yes, well work out the issues related to that and get it in03:00
ianwas you say, many (most) people won't even notice the default changing, probably03:00
brinzhang_I agree03:00
*** ociuhandu has quit IRC03:01
sean-k-mooneyi know most deveolpoer i have talked to moved there default a release or two ago03:01
sean-k-mooneynot all but alot of devstack user have been using python3 since rocky or stien03:02
*** ociuhandu has joined #openstack-nova03:03
brinzhang_I think there are problem need to consider, about the base environment. In older centos/ubuntu it's dafault python is py2703:03
ianwsean-k-mooney: i think there's probably a long tail of gate jobs that people haven't converted03:03
sean-k-mooneyyep proably03:04
sean-k-mooneywe will find out shortly if they start exploding.03:04
sean-k-mooneyi think there was a seperate patch up to swap the defualt in devstack gate and anoutther in zuul devstack base job but i dont know what the state of those are03:05
brinzhang_at least, because of this change I have not build the devstack env now, it's terrible ..03:05
sean-k-mooneybrinzhang_: unstack and stack with python3 enabled03:05
*** abaindur has quit IRC03:05
*** abaindur has joined #openstack-nova03:06
sean-k-mooneywe proably could have watied to merge it for another week or too03:06
sean-k-mooneybut we do need to complete this this cycle03:07
*** ociuhandu has quit IRC03:07
sean-k-mooneyand as far as i am aware this is inline with the tc plan for the dropping of python 2 support03:07
ianwnot going to argue about the overall dropping of it at all.  just it seems a gentler approach to have devstack defaulting to python3, then switch projects to stop supporting python203:08
ianwi mean, realistically, with nova refusing to install on py2 it's not even a configuration option in devstack after that point03:09
*** ociuhandu has joined #openstack-nova03:10
sean-k-mooneythat is fair. althoguh all project were ment to have gate jobs running on python 3 last cycle so all project shoudl be able to at least run on python 303:10
sean-k-mooneyalso not all porject or jobs deploy nova03:10
sean-k-mooneyalot do but not all03:10
*** slaweq has joined #openstack-nova03:11
*** mvkr has joined #openstack-nova03:12
sean-k-mooneyprojects like keysone, swift and glance wont need nova in ther gate jobs in many cases. although i suspect in many cases they get it by default03:12
sean-k-mooneyanyway night o/ we proably coudl revert it temporailly but i would personally prefer to fix the broken jobs03:13
*** slaweq has quit IRC03:16
*** ociuhandu has quit IRC03:18
brinzhang_sean-k-mooney: can you provide some guide how to "unstack and stack with python3 enabled"?03:20
*** abaindur has quit IRC03:24
*** TxGirlGeek has quit IRC03:25
*** ociuhandu has joined #openstack-nova03:25
brinzhang_sean-k-mooney: I have encountered this problem several times, excute "python -m pip install --upgrade pip" and also raised the same issue.  http://paste.openstack.org/show/786318/03:27
*** ociuhandu has quit IRC03:30
*** ociuhandu has joined #openstack-nova03:32
*** ociuhandu has quit IRC03:36
ianwbrinzhang_: you want to set USE_PYTHON3 in your devstack localrc03:44
*** bhagyashris has joined #openstack-nova04:02
*** macz has joined #openstack-nova04:04
openstackgerritDong Ma proposed openstack/nova master: ZVM: Implement update_provider_tree  https://review.opendev.org/69489704:05
*** ociuhandu has joined #openstack-nova04:06
*** jbernard_ has quit IRC04:06
*** macz has quit IRC04:09
*** slaweq has joined #openstack-nova04:11
*** ociuhandu has quit IRC04:14
*** slaweq has quit IRC04:15
*** brinzhang has joined #openstack-nova04:27
*** brinzhang_ has quit IRC04:30
*** abaindur has joined #openstack-nova04:32
*** mkrai has joined #openstack-nova04:35
openstackgerritMerged openstack/nova stable/pike: Functional reproduce for bug 1852207  https://review.opendev.org/69381704:41
openstackbug 1852207 in OpenStack Compute (nova) pike "reschedule ignores requested availability zone" [Medium,In progress] https://launchpad.net/bugs/1852207 - Assigned to Balazs Gibizer (balazs-gibizer)04:41
*** brinzhang_ has joined #openstack-nova04:42
*** jmlowe has quit IRC04:42
*** brinzhang has quit IRC04:44
*** brinzhang has joined #openstack-nova04:46
*** brinzhang_ has quit IRC04:49
*** bhagyashris has quit IRC04:51
*** ratailor has joined #openstack-nova04:53
*** ociuhandu has joined #openstack-nova05:18
*** nanzha has quit IRC05:18
*** nanzha has joined #openstack-nova05:19
*** brinzhang_ has joined #openstack-nova05:20
*** abaindur has quit IRC05:22
*** ociuhandu has quit IRC05:22
*** abaindur has joined #openstack-nova05:23
*** brinzhang has quit IRC05:23
*** zhanglong has joined #openstack-nova05:24
*** elod is now known as elod_off05:28
*** ociuhandu has joined #openstack-nova05:30
*** brinzhang has joined #openstack-nova05:33
*** ociuhandu has quit IRC05:35
*** brinzhang_ has quit IRC05:36
brinzhangianw: thanks, I will try :)05:37
*** bhagyashris has joined #openstack-nova05:38
*** links has joined #openstack-nova05:40
*** pcaruana has joined #openstack-nova05:43
*** lennyb has joined #openstack-nova05:54
*** Luzi has joined #openstack-nova06:00
openstackgerritSundar Nadathur proposed openstack/nova master: ksa auth conf and client for Cyborg access  https://review.opendev.org/63124206:05
openstackgerritSundar Nadathur proposed openstack/nova master: Add Cyborg device profile groups to request spec.  https://review.opendev.org/63124306:05
openstackgerritSundar Nadathur proposed openstack/nova master: Define Cyborg ARQ binding notification event.  https://review.opendev.org/69270706:05
openstackgerritSundar Nadathur proposed openstack/nova master: Create and bind Cyborg ARQs.  https://review.opendev.org/63124406:05
openstackgerritSundar Nadathur proposed openstack/nova master: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML.  https://review.opendev.org/63124506:05
openstackgerritSundar Nadathur proposed openstack/nova master: Delete ARQs for an instance when the instance is deleted.  https://review.opendev.org/67373506:05
openstackgerritSundar Nadathur proposed openstack/nova master: Add cyborg tempest job.  https://review.opendev.org/67099906:05
openstackgerritSundar Nadathur proposed openstack/nova master: Refactor to extract Placement helper functions for functional tests.  https://review.opendev.org/69490606:05
*** openstackstatus has joined #openstack-nova06:09
*** ChanServ sets mode: +v openstackstatus06:09
*** slaweq has joined #openstack-nova06:11
*** slaweq has quit IRC06:15
*** lpetrut has quit IRC06:25
openstackgerritOpenStack Proposal Bot proposed openstack/nova stable/train: Imported Translations from Zanata  https://review.opendev.org/69491106:43
*** abaindur has quit IRC06:44
*** abaindur has joined #openstack-nova06:44
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata  https://review.opendev.org/69471706:51
*** pcaruana has quit IRC06:56
*** rcernin has quit IRC06:58
*** huaqiang has quit IRC07:00
*** dpawlik has joined #openstack-nova07:03
*** brinzhang_ has joined #openstack-nova07:03
*** nanzha has quit IRC07:04
*** brinzhang_ has quit IRC07:04
*** nanzha has joined #openstack-nova07:04
*** brinzhang_ has joined #openstack-nova07:04
*** brinzhang_ has quit IRC07:04
*** brinzhang has quit IRC07:05
*** udesale has joined #openstack-nova07:06
*** xek has quit IRC07:32
*** brinzhang has joined #openstack-nova07:41
*** dpawlik has quit IRC07:43
*** dpawlik has joined #openstack-nova07:44
*** ccamacho has joined #openstack-nova07:48
*** brinzhang_ has joined #openstack-nova07:49
*** brinzhang has quit IRC07:51
*** damien_r has joined #openstack-nova07:56
*** damien_r has quit IRC07:57
*** damien_r has joined #openstack-nova07:57
*** slaweq has joined #openstack-nova08:00
*** ivve has joined #openstack-nova08:17
*** tesseract has joined #openstack-nova08:18
openstackgerritSundar Nadathur proposed openstack/nova master: Create and bind Cyborg ARQs.  https://review.opendev.org/63124408:23
openstackgerritSundar Nadathur proposed openstack/nova master: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML.  https://review.opendev.org/63124508:23
openstackgerritSundar Nadathur proposed openstack/nova master: Delete ARQs for an instance when the instance is deleted.  https://review.opendev.org/67373508:23
openstackgerritSundar Nadathur proposed openstack/nova master: Add cyborg tempest job.  https://review.opendev.org/67099908:23
openstackgerritMerged openstack/nova stable/pike: doc: fix and clarify --block-device usage in user docs  https://review.opendev.org/69445008:35
*** pcaruana has joined #openstack-nova08:36
*** abaindur has quit IRC08:38
bauzasgood morning Nova08:42
*** luksky has joined #openstack-nova08:42
gibibauzas: good morning08:44
*** ralonsoh has joined #openstack-nova08:50
brinzhang_Hi gibi, good morning08:51
gibibrinzhang_: o/08:52
brinzhang_gibi: Can you review the flavor explosion patach, and sean-k-mooney leave some comments, and we have the different opinion in the model design08:53
gibibrinzhang_: it is on my list to review08:53
brinzhang_gibi: yeah, thanks.08:54
*** priteau has joined #openstack-nova08:55
*** tkajinam has quit IRC08:56
bauzasbrinzhang_: can you ping me again the spec URL ?08:57
bauzasI'll start reviewing some changes today hopefully, I'm late with this :(08:57
*** FlorianFa has joined #openstack-nova08:58
bauzasgibi: about the placement audit command, it'd be awesome if you could test again with the latest revision08:59
bauzashttps://review.opendev.org/#/c/670112/08:59
bauzasI fixed both issues08:59
gibibauzas: on my list too :)08:59
bauzasgibi: FWIW, I'm looking at how to fix the placementfixture issue08:59
bauzasgibi: <308:59
*** martinkennelly has joined #openstack-nova08:59
brinzhang_bauzas: https://review.opendev.org/#/c/663563/09:00
*** ociuhandu has joined #openstack-nova09:00
bauzasbrinzhang_: thanks09:01
*** brinzhang has joined #openstack-nova09:02
*** Luzi has quit IRC09:04
*** brinzhang_ has quit IRC09:05
*** rpittau|afk is now known as rpittau09:08
*** Luzi has joined #openstack-nova09:19
*** Luzi has quit IRC09:21
*** xek has joined #openstack-nova09:26
*** ratailor_ has joined #openstack-nova09:30
*** ratailor has quit IRC09:32
*** derekh has joined #openstack-nova09:38
*** martinkennelly has quit IRC09:42
*** ociuhandu has quit IRC09:43
*** zhanglong has quit IRC10:03
*** martinkennelly has joined #openstack-nova10:07
*** brinzhang_ has joined #openstack-nova10:29
*** brinzhang_ has quit IRC10:31
*** ociuhandu has joined #openstack-nova10:31
*** brinzhang_ has joined #openstack-nova10:32
*** brinzhang has quit IRC10:32
*** brinzhang has joined #openstack-nova10:33
*** tetsuro has quit IRC10:36
*** brinzhang_ has quit IRC10:37
*** tetsuro has joined #openstack-nova10:37
*** lpetrut has joined #openstack-nova10:40
*** dpawlik has quit IRC10:45
*** brinzhang_ has joined #openstack-nova10:51
*** mkrai has quit IRC10:52
*** mkrai_ has joined #openstack-nova10:52
*** brinzhang has quit IRC10:53
*** brinzhang has joined #openstack-nova10:54
* bauzas goes AWOL for gym10:55
*** mkrai_ has quit IRC10:56
*** mkrai__ has joined #openstack-nova10:56
*** brinzhang_ has quit IRC10:56
*** ratailor_ has quit IRC10:58
*** ratailor has joined #openstack-nova10:59
*** mkrai__ has quit IRC11:00
*** brinzhang_ has joined #openstack-nova11:07
*** brinzhang has quit IRC11:11
openstackgerritStephen Finucane proposed openstack/nova master: functional: Make '_wait_for_state_change' behave consistently  https://review.opendev.org/68918011:16
openstackgerritStephen Finucane proposed openstack/nova master: functional: Unify '_wait_until_deleted' implementations  https://review.opendev.org/68918111:16
openstackgerritStephen Finucane proposed openstack/nova master: functional: Make 'ServerTestBase' subclass 'InstanceHelperMixin'  https://review.opendev.org/68918211:16
*** udesale has quit IRC11:17
*** dpawlik has joined #openstack-nova11:21
*** brinzhang has joined #openstack-nova11:21
gibisean-k-mooney, bauzas, brinzhang_, dansmith, efried_pto: I left comments in the flavor explosion spec https://review.opendev.org/#/c/663563/ . I tried to summarize Dan's and Eric's problems behind the -2s and my answers to those the problems. Let's see if this helps or not.11:22
*** brinzhang has quit IRC11:22
*** brinzhang has joined #openstack-nova11:23
*** brinzhang_ has quit IRC11:24
*** dpawlik has quit IRC11:26
gibistable-cores: it seems that nova-live-migration job is sad on stable/pike  I repeatedly get error like  https://zuul.opendev.org/t/openstack/build/0a199eeccc334b98a2eaf67998eef8b5/log/job-output.txt#582111:27
*** awalende has joined #openstack-nova11:28
* lyarwood clicks11:28
lyarwood W: The repository 'http://mirror.dfw.rax.opendev.org/ubuntu-cloud-archive xenial-updates/ocata Release' is not signed.11:29
lyarwoodeh, why are we using that on stable/pike?11:29
*** dpawlik has joined #openstack-nova11:30
gibilyarwood: that is a good question11:30
lyarwoodI forget where that's all defined tbh11:31
gibiit seems that job uses the legacy-ubuntu-xenial-2-node nodeset11:35
gibithat explains xenial-updates to me11:36
gibihttps://github.com/openstack/nova/blob/9f2d653b4050dbff859c656144c1564ea7c6fa60/.zuul.yaml#L6611:37
gibihttps://github.com/openstack/nova/blob/9f2d653b4050dbff859c656144c1564ea7c6fa60/.zuul.yaml#L2711:37
*** tbachman has quit IRC11:38
*** dtantsur|afk is now known as dtantsur11:49
*** ociuhandu has quit IRC11:52
*** ociuhandu has joined #openstack-nova11:53
*** ociuhandu has quit IRC11:53
*** ociuhandu has joined #openstack-nova11:54
*** ociuhandu has quit IRC11:59
*** ratailor has quit IRC12:15
*** mgariepy has joined #openstack-nova12:17
*** dpawlik has quit IRC12:28
*** brinzhang_ has joined #openstack-nova12:31
*** dpawlik has joined #openstack-nova12:31
*** brinzhang_ has quit IRC12:32
*** brinzhang_ has joined #openstack-nova12:32
*** brinzhang_ has quit IRC12:33
*** brinzhang_ has joined #openstack-nova12:34
*** brinzhang has quit IRC12:34
*** brinzhang_ has quit IRC12:34
*** icey has quit IRC12:34
*** dave-mccowan has joined #openstack-nova12:34
*** ociuhandu has joined #openstack-nova12:36
*** udesale has joined #openstack-nova12:58
*** ociuhandu has quit IRC13:00
openstackgerritLee Yarwood proposed openstack/nova-specs master: Boot from volume instance rescue  https://review.opendev.org/69406313:00
*** ociuhandu has joined #openstack-nova13:01
*** ociuhandu has quit IRC13:17
*** ociuhandu has joined #openstack-nova13:18
*** hamzy has quit IRC13:19
*** ociuhandu_ has joined #openstack-nova13:22
*** davee__ has joined #openstack-nova13:22
*** awalende has quit IRC13:26
*** ociuhandu has quit IRC13:26
*** tbachman has joined #openstack-nova13:27
*** efried_pto is now known as efried13:28
*** corvus has joined #openstack-nova13:31
lyarwoodmdbooth: https://review.opendev.org/#/c/693537/ - apologies, thought I had added you to this a while ago, would you mind taking a look later today? Not a complete fix but it should avoid issues in some situations.13:32
*** liuyulong has joined #openstack-nova13:35
*** bhagyashris has quit IRC13:37
corvusefried, stephenfin: can you take a look at https://review.opendev.org/694891 asap please?13:39
efriedcorvus: saw that go by. So you're saying "devstack isn't ready for you yet"?13:40
corvusefried: yeah.  if someone downloads devstack and runs stack.sh, it'll break.13:41
sean-k-mooneythere is a patch up to change the defualt value of devstack13:41
*** eharney has quit IRC13:41
*** awalende has joined #openstack-nova13:41
sean-k-mooneycorvus: sure so why dont we just merge the other patch13:41
corvussean-k-mooney: https://review.opendev.org/649097 has set it to WIP13:42
sean-k-mooneyyes because it was depending on a change that has now merged13:42
*** awalende has quit IRC13:42
*** awalende has joined #openstack-nova13:42
*** mriedem has joined #openstack-nova13:42
kashyapHey, folks.  Now is the time to speak up, if you have comments on this: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010907.html ("On next minimum libvirt / QEMU versions for "V" release")13:42
stephenfincorvus: Yeah, I was waiting on mriedem to appear and decide what to do13:43
stephenfinas the owner of https://review.opendev.org/#/c/649097/113:43
stephenfinmriedem: for context: <corvus> efried, stephenfin: can you take a look at https://review.opendev.org/694891 asap please?13:43
corvusftr, you don't need to set wip to avoid something with a depends-on being merged.  zuul does that for you.13:43
sean-k-mooneyi know i think he might have been looking at the greneade failure too13:44
mriedemhow are changes in the nova jobs breaking everything else that's using devstack?13:44
sean-k-mooneyhe set it to wip because he tought it might need to be rebased on  https://review.opendev.org/#/c/688799/13:44
corvuseither way (whether we merge the revert or the default change), we should get USE_PYTHON3 out of the .zuul.yaml in nova -- that's the red flag here.  basically, if something is required for devstack to work, it should be in the devstack repo instead of nova; we should only set individual job config tweaks in nova's config.13:45
sean-k-mooneymriedem: the chagne prevents nova being installed in python 213:45
corvusyeah, the change simultaneously stopped all py2 testing on nova, and broke installing nova on py2.13:45
efriedcorvus, stephenfin, sean-k-mooney: I +2ed; now just convince mriedem...13:45
sean-k-mooneycorvus: USE_PYTHON3=true is not the problem13:46
mriedemthese aren't the only jobs setting the USE_PYTHON3=True flag outside of devstack13:46
mriedemneutron has at least one as well13:46
mriedemsean-k-mooney: why can't it install on py2? because of dependencies that were removed?13:47
sean-k-mooneythe reson other jobs broke is python-requires = >=3.613:47
*** mdbooth has quit IRC13:47
sean-k-mooneyin setup.cfg13:47
mriedemi'd like to know if we (nova) can switch our jobs to use py3 meanwhile leaving in whatever is needed to install nova on py2 until other jobs move over13:47
mriedemso let's revert that13:47
sean-k-mooneyif we just remove that it will allow nova to be installed on python 213:47
efriedBut doesn't "stop testing py2" leave us exposed there?13:47
mriedemwith a big ass TODO about dropping that when devstack has USE_PYTHON3=True by default13:48
* mriedem bites tongue13:48
mriedemeither we move, or we don't, i don't really care about dropping py2 support, but that's what the TC has been hammering on for yeras13:48
mriedem*years13:48
mriedemso then we do and things break, and omfg13:48
slaweqhi13:48
sean-k-mooneyhttps://review.opendev.org/#/c/694891/1/setup.cfg@913:48
mriedemso let's just do the minimum possible to get things working which is revert the setup.cfg change yeah13:48
mriedem?13:48
sean-k-mooneynova can move13:48
slaweqI just found out that patch https://review.opendev.org/#/c/687954/ which You are now talking about broke also neutron-grenade job13:49
*** mdbooth has joined #openstack-nova13:49
sean-k-mooneyif we remove that 1 line other can install it on python213:49
mriedemslaweq: yeah we're just talking about what to revert13:49
slaweqthis job is py2 job and is running in many projects13:49
slaweqmriedem: yes, I see. I just wanted to mention about this job which I just noticed that is broken13:50
sean-k-mooneyso in anycase by december 12 all project are ment to chagne to python 3 and drop python 2 testing13:50
sean-k-mooney* all non lib projects13:51
*** ociuhandu_ has quit IRC13:52
mriedemi've left comments on the change,13:53
*** ociuhandu has joined #openstack-nova13:53
mriedemthis is a clusterf*ck management-wise from my pov,13:53
mriedemso do whatever13:53
openstackgerritAlexandre arents proposed openstack/nova master: Do not update root_device_name during guest config  https://review.opendev.org/67000013:53
mriedemlet the tc work on getting devstack to use py3 by default13:53
corvusmriedem: if nova runs all devstack jobs with USE_PYTHON3 set to true, then the same thing can happen again13:54
*** tosky has joined #openstack-nova13:54
corvusif you don't want to revert that whole change, can you at least keep one py2 job running as long as py2 is the devstack default?13:55
mriedemthe same thing == not being able to install nova with py2, that's wrong, right? as long as we don't screw up setup.cfg,13:55
mriedemtempest tests could break if nova lands some code that doesn't work with py2, i get that13:56
mriedembut frankly i don't see that happening real soon, and if it does it can be fixed,13:56
mriedemand it's also motivation to get downstream projects to move to py3 as well13:56
corvusmriedem: right, i'm saying it's a testing hole.  someone could introduce a change that doesn't work with py2.13:56
mriedemwhich is what i thought everyone wanted in ussuri as a major community goal13:56
*** tkajinam has joined #openstack-nova13:56
*** tkajinam has quit IRC13:56
corvusmy only goal here is that "./stack.sh" always work for new users.13:56
*** tkajinam has joined #openstack-nova13:57
mriedem"always works" is pretty subjective13:57
mriedembugs are bugs13:57
mriedemi agree that if nova doesn't install it's a problem13:58
toskymriedem: please approve the revert - all the other projects are broken because nova does not start13:58
mriedemso revert the setup.cfg change13:58
mriedemsome other core can approve if they care13:58
mriedemi'd like the community to shit or get off this py3 pot13:58
corvusmriedem: yeah, but there's no testing of nova in the default devstack configuration.13:58
*** ociuhandu has quit IRC13:58
mriedemchrist we're talking about py3.8 gating in the tc threads these days already13:58
mriedemdo whatever stephenfin and efried want13:59
toskymriedem: I'm not sure why you are saying or implying that the community does not want to move - I think we want to move, just without blocking the work14:00
mriedemi've already said i'm good with fixing setup.cfg so nova can install again,14:02
*** luksky has quit IRC14:02
*** ociuhandu has joined #openstack-nova14:02
mriedemi don't think we should be gating on py2 though and if something slips through that's a py2 bug then we fix it14:02
mriedemotherwise just let the qa/tc/infra whoever team that cares about this manage it directly imo14:02
mriedemsince the projects obviously can't orchestrate this themselves14:03
toskyfine, but then probably you also need to revert the requirment change14:03
toskynot just setup.cfg14:03
mriedemdo whatever you guys want14:03
stephenfinSo someone needs to go first, and I thought it could be us since we're a service, not a library, but obviously that isn't the case14:04
stephenfinWhat's the hold up with DevStack switching to Py3 first though? Can't we just merge that?14:04
toskyI don't know14:05
mriedemsomeone has to care14:05
corvusplease have at least one test on nova that runs devstack in the default configuration.  otherwise, there is a very high risk that changes will merge to nova which will break it.14:05
stephenfinokay, makes sense. So can I go switch DevStack to use Python 3 by default14:05
corvusstephenfin: https://review.opendev.org/649097 is relevant14:06
sean-k-mooneyyes so it look lke we need to merge those 3 patches14:07
efriedsean-k-mooney: sorry, what's the third?14:07
efriedoh, the predecessor of --^ ?14:07
corvusmriedem: do you want to remove the wip setting on that change?14:07
sean-k-mooneyhttps://review.opendev.org/#/c/688799/5 https://review.opendev.org/#/c/649097/10 and https://review.opendev.org/#/c/649278/514:07
*** ociuhandu has quit IRC14:08
sean-k-mooneymriedem's change should be the last of the 314:08
sean-k-mooneythe other two can merge in any order i think14:08
sean-k-mooneyhttps://review.opendev.org/#/c/688799/5 already has 1 +214:09
stephenfinsean-k-mooney: Now that CentOS 8 is out, why wouldn't you just use that?14:10
stephenfinIMO if we're switching to Python 3-only we should be testing on Python 3-supporting distros, namely CentOS 814:10
toskystephenfin: we were discussing about CentOS 8/devstack support with frickler earlier today - it's not there yet14:10
sean-k-mooneyyou could but devstack may not work on it14:10
sean-k-mooneyim pretty sure you will need eple or ius repos to make it work14:11
stephenfintosky: can we disable CentOS-based jobs so?14:11
toskystephenfin: there is a review for it14:11
sean-k-mooneystephenfin: we can run python 3 on centos 714:11
sean-k-mooneybut we need pyton36 form eple or ius14:12
toskystephenfin: https://review.opendev.org/#/c/694967/14:12
stephenfinsean-k-mooney: we can, but we can also do it on CentOS 8. Both involve some work, and it seems obvious to me that the effort should spent on the latter option14:12
kashyap(On RPM-based distros, DevStack generally "works for me" on Fedora.  Never tried on CentOS, though.)14:12
mriedemcorvus: removing the WIP doesn't make it work, as you can see from the job results14:13
sean-k-mooneystephenfin: we can do both14:13
kashyapstephenfin: Just chiming in randomly, why can't one just stick to a Fedora-only job?  (IIRC, there was one; need to check if it's still maintained, or is rotting)14:13
mriedemas sean pointed out there are a series of changes so someone has to align that stuff14:13
mriedemthe one under my WIP has been sitting since april14:13
mriedemso clearly not a community priority14:13
mriedemkashyap: as far as i can recall the fedora jobs in openstack have been a garbage dump since forever14:14
mriedemi don't know of any projects in openstack that gate on fedora, maybe tripleo or some deployment projects14:14
kashyapmriedem: Right, need bodies.14:14
stephenfinkashyap: Fedora is too much of a moving target for CI, I'm afraid14:14
toskymriedem: maybe devstack jobs - tripleo was able to have f28 jobs14:14
sean-k-mooneymriedem: well that because fedora and ci is basically an anti pattern. it chagne too much and keeps breaking14:14
stephenfinAsk sean-k-mooney - they know all about it14:14
kashyapThe only one I know who worked on Fedora jobs was/is ianw14:14
stephenfinjinx :D14:14
stephenfinanyway, that's a different discussion14:15
*** nweinber has joined #openstack-nova14:15
kashyapYeah, agreed on Fedora being a "moving target"; if CentOS-8 is more manageable, by all means.14:16
kashyapsean-k-mooney: "Anti-pattern" for a cloud software probably; libvirt and QEMU upstream test on Fedora jobs just fine.14:16
sean-k-mooneykashyap: i think the main issue with centos 8 will be a lack of packages14:16
sean-k-mooneykashyap: libvirt and qemu are too of the main issues14:16
sean-k-mooneywe hit temproy brakages or chagnes in the output of things like qemu-img14:17
kashyap(Also, bear in mind -- most / all upstream kernel / Virt issues are fixed on Fedora first -- as most kernel / Virt upstream devs use it.)14:17
sean-k-mooneyya the kernel and gcc kept causing issues for compiling dpdk and ovs too14:18
sean-k-mooneyanyway thats a different topic14:18
stephenfincorvus, tosky: Can we combine https://review.opendev.org/#/c/649097/ and https://review.opendev.org/#/c/694967/ and just merge that?14:18
kashyapAnyway, this is all largely about having enough warm bodies that are incentivized to care.14:18
stephenfinSo switch DevStack to Python 3 and drop the CentOS 7 job, which will no longer work14:19
mriedemstephenfin: those non-ubuntu jobs aren't voting anyway so they don't matter14:19
stephenfinTrue14:19
toskystephenfin: maybe, I don't know; I'd wait for gmann too, even though I have some objections to his comment in https://review.opendev.org/#/c/649097/ as I wrote there14:20
mriedemif a job isn't voting it's not enough of a priority for people to care about it14:20
stephenfinI don't want to inflict pain on people, but as mriedem notes someone needs to start driving this and if I'm doing that from nova's side, then a straight up revert is what I want14:20
stephenfinIt sounds like we'd be kicking a can down the road. I'd rather help people pick up the pieces than do that14:20
sean-k-mooneymind if i just rebase the 3 devstack patch into the right order14:21
stephenfinsean-k-mooney: before you do, what are the three?14:21
toskystephenfin: it's too big right now - if you don't want to fully revert https://review.opendev.org/#/c/694891/, are you going to accept at least a revert of setup.cfg (the condition) and *requirements.txt  ?14:21
* mriedem looks at the ironic, ceph and lvm jobs that we run on nova changes being non-voting for a long time14:21
sean-k-mooneyHandle uninstalled python3 -> Handle localrc early enough in stackrc -> Change USE_PYTHON3=True by default14:21
sean-k-mooneythat fixes centos 7 then enable python 3 early then set it to the defaul14:22
stephenfinsean-k-mooney: again, I don't think we need "Handle uninstalled python3". Let's use CentOS 8 instead14:22
sean-k-mooneywe can do both14:22
stephenfinwe can, but it doesn't mean we should14:22
stephenfintosky: We can, but that means we'll no longer test against Python 2.714:23
sean-k-mooneyif we want to drop all centos testing until centos 7 works we could but why when its a trivial patch14:23
stephenfinso there's an implicit countdown before nova on py2.7 breaks anyway14:23
toskystephenfin: no, not directly - but it is really likely  that you are going to break py2 with a commit in the next 3 weeks?14:23
stephenfinno, it's not, in fairness14:24
stephenfinsean-k-mooney: for the reasons ianw has pointed out: no one has actually tested that it works14:24
stephenfinand it's not reflective of real-world use cases14:24
stephenfinbetter to disable the tests and focus on switching to centos8, imo14:25
*** awalende has quit IRC14:25
sean-k-mooneyi used to used centos 7 with python 3 as my dev env untill like july14:25
mriedemas i've said earlier, i would put the bare minimum effort into making nova work with py27, i.e. let it install but after that all bets are off14:25
mriedemif it doesn't work with py27 it's a bug until we can really say we no longer care14:25
*** awalende has joined #openstack-nova14:26
stephenfinmriedem: I also like that approach14:26
sean-k-mooneyya same14:26
sean-k-mooneywhich means remove 1 line in setup.cfg14:26
stephenfintosky: yeah, if you want to just revert the setup.cfg changes, I'll be happy with that14:26
mriedemstephenfin: and likely the requirements stuff14:26
stephenfinalso that, yes14:26
sean-k-mooneythe requirement chagne for contextlib2 is only half needed14:26
mriedemthere should probably be a TODO in the setup.cfg line saying to remove python-requires once devstack uses py3 by default14:26
sean-k-mooneythe way devstack works it will get installed by other projects but sure14:27
stephenfinand that, yup yup yup14:27
mriedemsean-k-mooney: but kolla!14:27
mriedemosa, etc14:27
mriedemanything running nova in a container or venv14:27
toskystephenfin: but don't you think that also reverting requirements.txt is needed? There is at least one condition which affects py2, and that may break as well14:27
mriedemtosky: we just said yes14:27
toskymriedem: sorry, missed in the stream14:27
stephenfintosky: it is. I missed that. Fortunately mriedem caught it (y)14:27
sean-k-mooneykolla is python3 by default alredy but yes fair point14:28
mriedemstephenfin: technically tosky brought up the requirements thing first so credit goes to him for that14:30
KeithMnemoniclyarwood do you think you may have time to review this patch this week? https://review.opendev.org/68300814:30
efriedso is someone going to modify ianw's patch or propose a new one? Probably the latter is better.14:32
sean-k-mooneymaybe we should send an update too the list too whith what our plan is14:33
openstackgerritLuigi Toscano proposed openstack/nova master: (Temporarily) readd bare support for py27  https://review.opendev.org/69500714:34
toskylet's see if it works ^^14:34
corvustosky: test results will not be helpful here -- there is no testing of py2714:34
toskycorvus: one monent14:35
sean-k-mooneyi dont think we should add the py 27 calssifier back14:35
sean-k-mooneybut otherwise it looks fine14:35
stephenfinsean-k-mooney: just left a comment to that effect14:35
sean-k-mooneyso did i :)14:36
openstackgerritLuigi Toscano proposed openstack/nova master: (Temporarily) readd bare support for py27  https://review.opendev.org/69500714:36
toskyI'm using this: https://review.opendev.org/69494914:37
toskyto test it14:37
stephenfintosky: one more comment, sorry /o\ (the Python 3 Only classifier still makes sense)14:37
toskystephenfin: oh14:38
stephenfinit's just metadata so you can keep it14:38
sean-k-mooneyas does the cpython on14:38
stephenfinyup14:38
stephenfinafter that, I'm +2 pending https://review.opendev.org/69494914:38
openstackgerritLuigi Toscano proposed openstack/nova master: (Temporarily) readd bare support for py27  https://review.opendev.org/69500714:38
corvusi'd really love for there to be a job which tests py2.7.  can we not just add one until the default switches?14:40
corvustesting with depends-on changes seems error-prone14:41
toskya non-voting one? A voting one?14:41
toskyI'd defer that to nova cores14:41
sean-k-mooneythe whole point of the orginal change was nova wanted to drop all python 2 support and therefor the testing14:42
sean-k-mooneybut yes we could14:42
sean-k-mooneygibi: im reviewing your comments on the composable flavors spec14:43
sean-k-mooneygibi: so far i more or less agree14:43
stephenfinif we were to add one, it'd have to be voting for it to be of any use but per above, I don't think we should add one14:43
corvussean-k-mooney: right, i'm just suggesting that given the importance of devstack, that we should endeavor to keep it working14:43
*** links has quit IRC14:44
dansmithI'm coming into this late, but what is the controversy?14:44
dansmithwhether or not we continue to work on py2 at all via a test?14:44
stephenfindansmith: we've marked nova as python3 only, but devstack defaults to installing stuff in python2 mode14:44
corvusstephenfin: i'm really puzzled -- i don't understand why there is so little concern about whether devstack works14:44
stephenfinso anyone that doesn't override the defaults is broken14:44
dansmithso how is this even a question?14:44
* dansmith is confused14:45
stephenfindansmith: It's not, we're reverting the part that broke everyone14:45
dansmithreverting what? the dropping of a py2 job?14:45
corvusbut there are no current plans to have tests to ensure that it doesn't happen again (and even the revert is only tested indirectly with a depends-on patch)14:45
stephenfindansmith: https://review.opendev.org/#/c/695007/14:45
dansmithcorvus: yeah, then you and I agree.14:46
sean-k-mooneydansmith: we had a require-pyton >= 3.6 line in setup config that prevented nova installing on less then our new supported version14:46
dansmithwhat's the argument for not having a py2 test until the devstack default switches? principle?14:46
stephenfinmostly, yeah14:47
corvusdansmith: https://review.opendev.org/694891 is the full revert which seems to be losing mindshare14:47
dansmithstephenfin: I'm not on board with that14:47
sean-k-mooneydansmith: that beeing testing py2 out of principal?14:47
sean-k-mooneyor breaking the devstack default14:47
sean-k-mooneybecause im really hoping we change that today14:48
dansmithsean-k-mooney: I'm not on board with us not testing nova in the default devstack config, and not okay with *not* doing that because of the principle that py2 is (soon) out of support14:48
dansmithif we change the devstack default, then fine not testing py214:48
dansmithif we don't, then we *have* to, IMHO14:48
sean-k-mooneyok that is a clear statement14:49
*** jaosorior has joined #openstack-nova14:49
*** bhagyashris has joined #openstack-nova14:49
*** ociuhandu has joined #openstack-nova14:49
dansmithwhat is the blocker for the devstack py3 default?14:50
sean-k-mooneythe devstack defautl in that case need to be change in the next 23 days or we cant drop py2 testing by m1 in nova per the tc plan14:50
stephenfinI figured someone needs to lead the way on this and it didn't seem anyone else was doing it. I also don't get why DevStack can't just change their default14:51
dansmithsean-k-mooney: I totes don't care about the tc's schedule as much as I care that devstack works out of the box14:51
dansmith(I don't care about the TC's schedule at all actually, but.. :P)14:51
dansmithI know mriedem was on top of the devstack py3 default,14:51
dansmithbut he approved the switch prior to that being ready, which surprises me14:52
mriedemi didn't know that the nova change meant you couldn't install nova on py2 anymore14:53
mriedemi thought it was (a) what we tested against and (b) classifiers / support statement14:53
dansmithack14:53
gmannmriedem: stephenfin dansmith tosky removing condition from setup.cfg should be ok as and add that once all projects moved to py3-only.14:54
dansmithmriedem: from the two patches and the votes, it looks like you want to re-allow install on py2, but not test it, yeah? problem is "it" is the "default devstack arrangement" right?14:54
stephenfinand I didn't know that this would break other people. I thought we were safe since we were consumers (a service), rather than the consumed (libs, clients). Didn't think of the DevStack implications14:54
gmannif nova is breaking on py2 by code then we do not need to fix and ask consumer to move to py3-only14:54
dansmithgmann: it's a matter of devstack working out of the box.. nothing to do with python versions, IMHO14:54
mriedemdansmith: correct14:55
dansmithif we're not testing devstack in remotely default form, that's a problem, IMHO14:55
gmannmy argument for devstack move to py3 by default can migrate all py2 jobs to py3 which is planned before schedule, like library etc14:55
mriedemdansmith: i want more people to give a shit14:55
mriedemand pain is usually how that happens14:55
stephenfin^ that, sadly14:55
dansmithmriedem: so you want it to break to prove a point? :)14:55
mriedemthat's assuming we're going to land nova changes that break on py2 in the next what, 3-4 weeks?14:56
efriedDoes anybody object to14:56
efried- Re-enable py2 (revert setup.cfg and requirements changes)14:56
efried- Re-add one py2 job, which can be a pretty small/basic one afaiac14:56
dansmithI still haven't heard why devstack's default can't move yet14:56
efried?14:56
mriedemi've asserted above that if we do, it's a bug and we just fix it14:56
stephenfindansmith: see gmann's comment above14:56
mriedembut i don't think we have high risk of landing non-py2 code in the next 3-4 weeks14:56
mriedemi still use six everywhere14:56
stephenfinand on the review14:56
efriedI agree with all of that, but "we probably won't break it" has never been a good reason not to test "it".14:56
stephenfinthat is my preferred direction, by far14:57
dansmithyeah, probably won't break it doesn't work for me14:57
stephenfin(switching DevStack to Python 3)14:57
gmanni do not prefer nova or any project keep py2 job.  but did not thought about min condition on setup.cfg14:57
efriedare we objecting to re-adding a py2 job because we're worried about gate resources?14:57
dansmiththat's like turning off gating for a bit because we'll be careful14:57
efried^ this14:57
dansmithstephenfin: I still don't really understand.. gmann is saying we can't switch the default because a lot of jobs don't specify and would break on py3?14:57
mriedemefried: we don't gate on ceph or ironic and yet people care about those right?14:58
sean-k-mooneyfor what its worth that is why iw as suggesting fixing py3 on centos7 instad of disabling cento7 job untill cento 8 works14:58
gmannyeah but it is deadlock seems and need to tradeoff with either one14:58
*** eharney has joined #openstack-nova14:58
stephenfindansmith: I think so, yeah14:58
efriedmriedem: Agreed that we can't test everything in the world. But a minimal canary to make sure devstack doesn't just shit all over itself seems appropriate.14:58
dansmithwell, the tradeoff, is, IMHO, what efried said, which is add back a single py2 devstack job14:58
mriedemand when can that be removed?14:59
dansmithmriedem: when the default switches14:59
mriedemwhen the tc fairy shows up in january to tell us we're ok?14:59
efriedwhen devstack is py3 by default and we can do the minimum thing.14:59
dansmithmriedem: I don't care about the date, I care about the default14:59
* dansmith prints a shirt14:59
stephenfinCan we just make devstack py3 by default?14:59
efried("the minimum thing" => restore the py3 minimum in setup.cfg)14:59
stephenfinWe know there's going to be some degree of pain here. By reverting anything in nova, we're kicking the can down the road15:00
efriedstephenfin: That's mriedem's patch, yes? I rechecked that a bit ago to see if it works yet. If so, maybe we can just pull the trigger.15:00
mriedemthen just efried and dansmith should approve ianw's revert15:00
gmanndefault switch was planned for ~Jan15:00
gmannok, let's move devstack to py3 and then if anyone need py2 testing (only lib and testing tools) can explicitly mention the py2 need15:00
efriedthough the predecessor also would need to go.15:00
stephenfinSwitching to Python 3 by default is at least forward-looking pain15:00
dansmithgmann: right so if the default flip is coming, I don't see what the big deal is15:00
gmannexcept swift everyone has to switch to py3-only in ussuri15:00
*** tkajinam has quit IRC15:00
mriedemdansmith: that devstack patch of mine has been on top of another patch that has been around since april15:00
stephenfinthen lets do that now15:00
dansmithstephenfin: I would agree except I don't know how many things will insta-fail on projects with few people working on them15:01
gmanni have patches upnfor all the projects (except clieent, testing tool and lib) so project can merge thsoe15:01
dansmithmriedem: I know15:01
dansmithmriedem: I'm not a py3 bigot, so I'm really in no rush :)15:01
stephenfindansmith: those projects are going to insta-fail at some point though15:01
dansmithstephenfin: yep, so if the TC wants to schedule that, and it's in Jan, I would be fine waiting and moving then as long as it happens15:01
dansmithbut, also fine now, I just don't want the disjoint default.. like I said, the date doesn't matter to me15:02
gmanndansmith: but it can be blocked other projects too and two times effort to get rid of py2. so i am ok to move devstack first15:02
mriedemdansmith: then just approve this https://review.opendev.org/#/c/694891/15:03
gmannbecause if nova or any other project say min version is py3 then it is fair because reno said the same.15:03
dansmithmriedem: I'm trying to reach consensus like everyone else, not force-merge anything15:04
dansmithif gmann is going to flip the devstack default, then we don't need to do anything, AFAICT15:04
stephenfinyup15:05
stephenfingmann: just so I'm 100% clear, what was the rationale for the proposed January switchover?15:05
stephenfinI missed whatever email discussed that so a link is fine :)15:05
dansmithJanuary is when the actual upstream support stops, AFAIK15:05
dansmithso I imagine it's aligned there so that the TC's deadline has weight15:05
gmannstephenfin: to keep testing py2 on client lib and lib, testing tool which were planned to drop py2 in jan15:05
gmannplan is like, consumers drop py2 first which is openstack services and then lib or testing tool15:06
sean-k-mooneygmann: it was planned for m2 in febuary15:06
stephenfinWe should probably switch over sooner than that then15:06
sean-k-mooneywell by m215:06
stephenfinWe need to keep clients and libraries on python 2 for longer to let the services switch everything over15:07
dansmithhonestly, switching the default in devstack at m2 seems crazy late to me15:07
dansmithjust for our cycle15:07
stephenfinso we should be switching devstack now to let the services fix whatever they need to fix15:07
stephenfinIMO, of course15:07
dansmiththat makes more sense to me for sure15:07
dansmithbreak early15:07
gmannstephenfin: yeah and all services has to switch before m-215:07
stephenfindansmith: we also have Xmas to worry about15:07
gmann+1.15:07
dansmithstephenfin: not nova's X-mas! :P15:08
dansmithbut yeah I get that for sure15:08
dansmithso, just tobe clear,15:08
dansmitheven if we push the devstack default, we need the partial revert so that py2-only projects can still install nova in their jobs15:08
*** bhagyashris has quit IRC15:08
*** TxGirlGeek has joined #openstack-nova15:08
sean-k-mooneydansmith: yes15:08
openstackgerritMark Goddard proposed openstack/nova master: Add functional regression test for bug 1853009  https://review.opendev.org/69501215:08
openstackbug 1853009 in OpenStack Compute (nova) "Ironic node rebalance race can lead to missing compute nodes in DB" [Undecided,In progress] https://launchpad.net/bugs/1853009 - Assigned to Mark Goddard (mgoddard)15:08
dansmithso we could push the default in devstack now, then revert our can-use-py2 part at m2 as the hard deadline yeah?15:08
gmannstephenfin: are you rebasing the mriedem patch and remove neutron-grenade job also in same patch to pass the gate15:09
stephenfinsean-k-mooney: why?15:09
dansmithstephenfin: so that trove (example) can still run py2 devstack jobs with nova15:09
sean-k-mooneywhy? so that if neutron need to keep a job on py2 for a day or two to fix it they can15:09
dansmithright15:09
gmanndansmith: they has to move as soon as any dependencies fail their gate15:10
stephenfinBut unless they're setting USE_PYTHON3=False in jobs, they'll inherit the default (now python3), no?15:10
dansmithyeah15:10
dansmiththat's my point, if nova can't run on py2 anymore (default or not) then they can't run jobs15:10
slaweqsean-k-mooney: what py2 job in neutron You are talking about?15:10
dansmithstephenfin: right, I'm sayingsome project that needs another month to be able to run devstack in default py315:11
stephenfinohhhh15:11
stephenfingotcha15:11
dansmithif we don't revert the minimum change, they physically can't install nova in unsupported py215:11
sean-k-mooneyslaweq: none it was just an example of a big project with many jobs that often need nova in them15:11
stephenfinokay15:11
*** dpawlik has quit IRC15:11
slaweqsean-k-mooney: ahh, ok :)15:11
gmannfor client lib which will happen later make sense to keep nova install-able on py2 , for service not15:11
stephenfinthen I'm also onboard with that15:11
dansmithstephenfin: that all hinges on gmann being willing to pull the trigger15:12
sean-k-mooneyby the way os-vif is currently broken as we have not swaped all the jobs to python 315:12
stephenfinso, revert the change to nova, merge the Python 3-ification patch to DevStack, wait a month and re-revert that change to nova15:12
dansmithstephenfin: just the half-revert15:12
sean-k-mooneywe can trivially but we need to wait as a lib project15:12
gmannrevert only setup.cfg and req right ?15:12
gmannyeah what dansmith mentioned15:12
dansmithstephenfin: revert the min, default devstack to py3, later un-revert the minimum15:13
gmann+115:13
stephenfinwhat about your concerns that we could accidentally break Python2 support in that time?15:13
stephenfindon't they still hold?15:13
dansmithstephenfin: those aren't my concerns15:13
dansmithstephenfin: my concerns are that we break the _default_ config in devstack15:13
dansmithif the default changes, I'm good15:13
stephenfinah15:13
* stephenfin is also good with this15:14
corvusi agree with dansmith (that's my concern too).  but it's unclear to me whether we can immediately change the default.  is that something we can do today?15:14
stephenfincorvus, tosky: have you been following along or do you need a recap?15:14
stephenfinwhoops15:14
dansmithsounds like gmann is willing15:14
gmannstephenfin: you are updating devstack patch? or should i do15:14
gmanngate will be fixed by nova revert15:15
stephenfingmann: I can...if you tell me what needs to be done?15:15
dansmithcorvus: we're going to do the half revert now as well, which I think will eliminate the actual devstack breakage immediately anyway15:15
gmannso default change happen today or tomorrow should be ok15:15
sean-k-mooneycorvus: i think we can change the default today15:15
toskystephenfin: a bit swamped with meetings, I think I may have got the gist of it though15:15
gmannstephenfin: sure, i will comment on patch15:15
toskylike: some reverting will land for now15:15
corvusthere was a bunch of devstack centos7 stuff earlier that i didn't understand, but if people who do understand agree that's all doable, then cool.  :)15:15
toskyand some other work is needed15:15
sean-k-mooneyif it cause gate failure then project can set it back to false in each job that broke15:15
toskywhich is a bit generic summary but I'm sure it fits :)15:16
stephenfintosky: got it in one15:16
dansmithstephenfin: I can summarize on the half-revert patch and +2, you can come back and +W when you're done with the devstack thing okay?15:16
stephenfinack15:16
gmanncorvus: i pushed patch to add centos8 job so i think we can  drop centos7 completely15:16
sean-k-mooneycorvus: centos ships with python 3.4 so it need to have py 3.6 installed form eple or we need to swap master jobs to centos 815:17
corvusand centos8 is ready?15:17
stephenfingmann shows up and fixes everything for us. This is excellent \o/15:17
toskygmann: see on #openstack-qa: some work is needed on centos 8, frickler was working on it15:17
sean-k-mooneywe just need to fix any gaps in devstack on centos 815:17
gmannmy bad and sorry for not considering the setup.cfg min py version things during composing the plan/goal15:17
toskygmann: and the requirements too :)15:17
gmannyeah :(15:17
stephenfingmann: Not your fault. I never thought about the DevStack default thing when putting that together15:18
*** Sundar has joined #openstack-nova15:18
mriedemstephenfin: your patch depended on the devstack default switch after i mentioned it, and then you dropped the depends-on15:18
mriedemlikely because we could just set USE_PYTHON3=True in our jobs15:18
stephenfinyup, exactly because of that :(15:19
stephenfinI thought the depends on was an optimization to avoid us having to set that stuff manually15:19
stephenfinTIL15:19
toskygmann: no problem, really; it happens, let's improve the process and continue15:19
mriedemslaweq: do you have a bug for this yet so i can track it in e-r15:20
mriedem?15:20
slaweqmriedem: no, I didn't open any bug for this15:20
*** markmcclain has quit IRC15:21
slaweqI just checked here that You're already talking about it so I didn't report a bug15:21
corvusi think the thing to watch out for in future reviews is: when setting a devstack option, is it something that is intrinsic to the specific job (okay in nova) or is it something that is recommended/required for any devstack users (should be in devstack).  if all the nova devstack jobs have an option, it's almost certainly the latter.15:21
*** markmcclain has joined #openstack-nova15:23
stephenfinmakes sense15:23
dansmithstephenfin: https://review.opendev.org/#/c/695007/315:29
dansmithefried: mriedem ^15:29
stephenfindansmith: LGTM15:31
efrieddansmith: so you've changed your mind on readding a minimal py2 job?15:32
dansmithefried: no, you must not have followed all of that, and.. did you read my wall of text?15:32
efriedI did15:32
dansmithefried: all I care about is that we're testing the devstack default.. if the default is changing, I'm cool with sticking with py3 only and letting py2 issues creep in15:32
sean-k-mooneyefried: im guessing your askign since this patch does not add the minimal job15:32
dansmithefried: if the default is not changing, I think we have to test and validate the default15:33
efriedwhat sean-k-mooney said. since this patch doesn't depend on the "switch the default to py3" patch, and there's no telling how long it will be until that actually merges, we have The Hole.15:33
dansmithefried: gmann said they'd merge it today15:34
mriedemyou have a gentlemans agreement for about the next 24 hours15:34
mriedemafter that courtney love shows pu15:34
efriedokaaay15:34
mriedem*up15:34
dansmithwe could block on that, but we're blocking a bunch of other people15:34
efriedyah, seems like it would have been easy to add one line to .zuul.yaml in that patch, but mebbe not.15:34
dansmithgmann: don't f*ck me over, okay?15:34
efriedanyway, it's on the way15:34
mriedemfor me it's not about ease15:34
dansmithefried: well, I'm fine with that if you want15:34
sean-k-mooneyefried: nova-dsvm-multinode-base is still python 2 i think15:34
mriedemsean-k-mooney: that's not a ojb15:35
mriedem*job15:35
mriedemthat's a base15:35
sean-k-mooneyso nova-live-migration will by python 215:35
mriedemit's not15:35
sean-k-mooneyya i know15:35
efriednope15:35
stephenfinsean-k-mooney: it can't be. if it was, it wouldn't work for us :)15:35
mriedemhi https://review.opendev.org/#/c/694787/15:35
*** nweinber_ has joined #openstack-nova15:35
sean-k-mooneyim looking at https://github.com/openstack/nova/blob/master/.zuul.yaml and i dont see python 3 enabled15:36
efriedbecause https://opendev.org/openstack/nova/src/branch/master/playbooks/legacy/nova-live-migration/run.yaml#L50 rite?15:36
mriedemit's in the legacy playbook15:36
mriedemyes that15:36
*** bhagyashris has joined #openstack-nova15:36
mriedemcue sean-k-mooney saying we should really move those jobs to zuulv315:36
stephenfinmriedem: on that, you need to keep the sphinx on py2 line in doc/requirements.txt15:36
stephenfini tried removing it and got the same thing you're seeing15:36
stephenfinthe tool is dumb15:36
sean-k-mooneyah ok15:37
gmann? anything changed ?15:37
dansmithgmann: no, we're just taking bets on whether or not you're really going to merge the devstack change today15:37
openstackgerritMatt Riedemann proposed openstack/nova master: FUP to Ie1a0cbd82a617dbcc15729647218ac3e9cd0e5a9  https://review.opendev.org/69478715:37
*** nweinber has quit IRC15:37
*** ivve has quit IRC15:37
dansmithgmann: efried and I will have to meet on the playground after school if not, and he'll kick my ass15:38
gmannok :)15:38
*** mkrai has joined #openstack-nova15:38
*** damien_r has quit IRC15:41
openstackgerritMerged openstack/nova master: functional: Make '_wait_for_state_change' behave consistently  https://review.opendev.org/68918015:43
gmannmriedem: sean-k-mooney for legacy jobs i am explicitly setting py3 via d-g var for other projects. waiting to move them to zuulv3 +py3 might take time.15:47
gmannstephenfin: on requirement changes.  I am removing the py2 only req also for other projects and if any project break anyone (which is rare case for all non-core/small projects) then we revert otherwise keep dropping those.15:49
stephenfinack15:50
mriedemstephenfin: i'm going to drop the misleading comment on https://review.opendev.org/#/c/694789/2/playbooks/legacy/nova-grenade-multinode/run.yaml@3515:50
stephenfinfine by me15:50
*** pcaruana has quit IRC15:50
*** pcaruana has joined #openstack-nova15:51
openstackgerritMatt Riedemann proposed openstack/nova master: Drop neutron-grenade-multinode job  https://review.opendev.org/69478915:52
openstackgerritMatt Riedemann proposed openstack/nova master: Drop neutron-grenade-multinode job  https://review.opendev.org/69478915:52
*** bhagyashris has quit IRC15:55
openstackgerritPavel Gluschak (scsnow) proposed openstack/nova master: Don't delete compute node, when deleting service other than nova-compute  https://review.opendev.org/69475616:00
*** udesale has quit IRC16:00
*** awalende has quit IRC16:01
openstackgerritArchit Modi proposed openstack/nova stable/pike: Revert "openstack server create" to "nova boot" in nova docs  https://review.opendev.org/69323616:02
*** alex_xu has quit IRC16:03
openstackgerritArchit Modi proposed openstack/nova stable/pike: Revert "openstack server create" to "nova boot" in nova docs  https://review.opendev.org/69323616:05
*** gyee has joined #openstack-nova16:05
*** awalende has joined #openstack-nova16:08
*** mlavalle has joined #openstack-nova16:09
*** awalende has quit IRC16:12
*** awalende has joined #openstack-nova16:12
*** awalende has quit IRC16:13
*** awalende has joined #openstack-nova16:14
*** awalende has quit IRC16:14
artomsean-k-mooney, FWIW, I'm not going to hassly you about the softer wording stuff in your NUMA rebuild patches. There's still enough stuff there to warrant a respin on both (albeit the top one is just typos)16:15
artom*hassle16:15
*** mkrai has quit IRC16:15
*** ociuhandu has quit IRC16:17
*** nanzha has quit IRC16:17
openstackgerritStephen Finucane proposed openstack/nova master: functional: Make '_IntegratedTestBase' subclass 'InstanceHelperMixin'  https://review.opendev.org/68918216:18
openstackgerritStephen Finucane proposed openstack/nova master: functional: Unify '_build_minimal_create_server_request' implementations  https://review.opendev.org/69502416:18
*** awalende has joined #openstack-nova16:19
*** TxGirlGeek has quit IRC16:20
sean-k-mooneyartom: i am going ot resping them for the typos yes16:20
artomAnd the unit tests :)16:21
artomMostly the unit tests16:21
sean-k-mooneyi actully intionally did not add them but yes im going to add some for the neew fucntion16:24
sean-k-mooneymainly because functional tests and exsiting test provide equal or better coverage in general but as noted ill add the test for the function you highlighted16:25
openstackgerritThierry Carrez proposed openstack/nova master: Start README.rst with a better title  https://review.opendev.org/69502516:29
mgoddardmriedem: hi. The more I pick at this thing (rebalance) the more it comes apart :)16:32
openstackgerritMerged openstack/nova master: (Temporarily) readd bare support for py27  https://review.opendev.org/69500716:32
gmanneveryone,  sent the ML for making devstack py3 default and other suggestion we agreed today- http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010938.html16:33
mgoddardmriedem: I have a few related but separable changes, and a functional tests. Does nova tend to prefer separate commits where possible, or shall I bung it all in one?16:33
*** jmlowe has joined #openstack-nova16:33
mriedemmgoddard: i can't speak for all of nova but i prefer separate commits if possible - easier to review, easier to revert if necessary16:34
mgoddardmriedem: sure.16:34
mriedemmgoddard: and i'm not surprised rebalance has issues since it's never had functional testing16:35
kashyapmgoddard: On separate commits, this is a good reminder: https://wiki.openstack.org/wiki/GitCommitMessages#Structural_split_of_changes16:35
mriedemthe only way i found the race bug in the first place was digging into ironic multinode grenade logs looking for some other issue16:35
kashyap(Bearing in mind things like bisectability, etc)16:35
mgoddardmriedem: separate commits should be quite neat as each will fix a different part of the functional test16:35
bauzasgibi: mriedem: do you think it would be worth inspecting the args when calling PlacementFixture ?16:36
bauzas(related to the microversion/version issue)16:36
mgoddardthanks kashyap. I generally prefer them, although it's not universal16:37
* kashyap nods16:37
*** abaindur has joined #openstack-nova16:39
efriedbauzas: can you point me to the change in question please?16:39
efried(It's somewhere on my list, been meaning to weigh in, but don't want to dig it up rn)16:39
efriedif this is a functional test, the PlacementFixture should be doing the right thing with its kwargs. And there should usually not be a reason to (re-)mock a method on the fixture.16:40
bauzasefried: https://review.opendev.org/#/c/670112/8/nova/cmd/manage.py@286716:40
bauzascontext is that I used a wrong argument : 'microversion' instead of 'version'16:41
bauzasso I could rather use utils.getargspec()16:41
efriedI understand, gimme sec.16:41
bauzasI mean, in the PlacementFixture16:41
bauzasefried: ie. something around there https://github.com/openstack/nova/blob/master/nova/tests/functional/fixtures.py#L10316:42
efriedoh, crap, yeah, I remember trying to unwind this _fake_* gorp a while back and back-burnering it because it turned out to be hard.16:43
*** TxGirlGeek has joined #openstack-nova16:44
efriedyeah, this is (still) awful to have in the way of the actual placement fixture16:44
efriedit will mask all kinds of problems, like the one you're running into.16:44
efriedegads, we should also be making self._client a sdk proxy now as well.16:45
bauzasyou know what ? I'll provide a separate change16:46
bauzasefried: ^16:46
efriednot that it's hugely different16:46
efriedbauzas: Totally agree a separate change is in order.16:46
bauzask16:46
efriedIf you can't completely kill the _fake_* methods, they should at least be avoiding massaging the args as much as possible.16:47
gmannstephenfin: can you rebase this on top of slaweq patch to dropneutron-grenade from devstack (commented on review) - https://review.opendev.org/#/c/649097/1016:47
*** jaosorior has quit IRC16:48
stephenfinack16:48
*** tesseract has quit IRC16:51
openstackgerritMerged openstack/nova stable/pike: Revert "openstack server create" to "nova boot" in nova docs  https://review.opendev.org/69323616:51
stephenfingmann: done16:52
gmannstephenfin: thanks, only thing we need to care is neutron-grenade job which will not work on devstack-py3-default. slaweq has patches up to migrate its usage to grenade-py3 but not all are merged. so i am making neutron-greande explicitly say py216:55
stephenfingmann: Makes sense. Do we need https://review.opendev.org/#/c/649097/ to depend on that so?16:56
gmannstephenfin: yeah, i am pushing the neutron patch (neutron-grenade is in neutron repo) and ping you16:56
gibibauzas: tested your placement audit patch. The basic functionality seems to work with even bandwidth involved. But I think --delete is broken somehow. (See my comment in the review)16:58
bauzasgibi: k, will look16:58
bauzasgibi: and thanks :)16:58
gibinp16:59
* gibi ends the day16:59
bauzasgibi: I can't see your comment on delete ?16:59
bauzasanyway, let's discuss this tomorrow16:59
bauzasthanks gibi a lot16:59
bauzasah, nevermind17:00
bauzasCtrl-R17:00
*** jaosorior has joined #openstack-nova17:02
*** nweinber__ has joined #openstack-nova17:04
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'os-consoles' API  https://review.opendev.org/68790717:04
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'nova-console' service, 'console' RPC API  https://review.opendev.org/68790817:04
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'nova-xvpvncproxy'  https://review.opendev.org/68790917:04
*** nweinber_ has quit IRC17:06
*** rpittau is now known as rpittau|afk17:06
*** awalende has quit IRC17:09
*** awalende has joined #openstack-nova17:17
*** dtantsur is now known as dtantsur|afk17:20
*** awalende has quit IRC17:20
*** awalende_ has joined #openstack-nova17:20
*** ivve has joined #openstack-nova17:21
*** ociuhandu has joined #openstack-nova17:22
*** ccamacho has quit IRC17:23
*** awalende_ has quit IRC17:24
*** ociuhandu has quit IRC17:27
*** Sundar has quit IRC17:29
*** munimeha1 has joined #openstack-nova17:50
*** igordc has joined #openstack-nova17:52
mriedemdansmith: you want to move this bottom cross-cell patch along? https://review.opendev.org/#/c/642591/ - you should already be familiar with this one17:59
*** derekh has quit IRC18:01
*** ociuhandu has joined #openstack-nova18:04
*** ricolin has quit IRC18:04
*** ociuhandu has quit IRC18:08
dansmithmriedem: yeah, sorry I need to re-find my way on those18:10
mriedembauzas: easy bug fix https://review.opendev.org/#/c/694756/18:13
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Bump MIN_{LIBVIRT,QEMU}_VERSION for "Ussuri"  https://review.opendev.org/69505618:15
*** ociuhandu has joined #openstack-nova18:17
*** ociuhandu has quit IRC18:21
*** dpawlik has joined #openstack-nova18:30
*** martinkennelly has quit IRC18:45
*** abaindur has quit IRC18:46
openstackgerritBoris Bobrov proposed openstack/nova master: Also enable iommu for virtio controllers and video in libvirt  https://review.opendev.org/68482518:58
*** davee__ has quit IRC18:59
*** ralonsoh has quit IRC19:03
*** TxGirlGeek has quit IRC19:03
*** TxGirlGeek has joined #openstack-nova19:11
openstackgerritMerged openstack/nova master: FUP to Ie1a0cbd82a617dbcc15729647218ac3e9cd0e5a9  https://review.opendev.org/69478719:19
*** abaindur has joined #openstack-nova19:23
*** abaindur has quit IRC19:28
*** abaindur has joined #openstack-nova19:28
*** abaindur has quit IRC19:29
*** abaindur has joined #openstack-nova19:30
efriedmriedem: Do you remember seeing/fixing this recently? https://zuul.opendev.org/t/openstack/build/ac433b3305ba454f845990f98a3bf481/log/logs/grenade.sh.txt.gz#3874919:32
efriedI don't see it in e-r19:33
*** ociuhandu has joined #openstack-nova19:37
*** dpawlik has quit IRC19:41
mriedemefried: weren't you hitting something like that with trying to get osc to gate on py3?19:45
efriedthis is what I don't remember.19:46
efriedfwiw this is trying to see whether barbican will gate on py319:46
*** ociuhandu has quit IRC19:47
mriedemso it's probably installing py27 on the old side and then trying to upgrade to py3 on the new side and packages are getting mixed up19:47
mriedemsee https://review.opendev.org/#/c/694237/19:48
mriedemand https://github.com/openstack/grenade/blob/master/playbooks/legacy/grenade-py3/run.yaml19:48
*** dpawlik has joined #openstack-nova19:48
mriedemdo the same in https://github.com/openstack/barbican/blob/master/playbooks/legacy/grenade-devstack-barbican/run.yaml19:49
mriedemto make your barbican py3 dreams come true19:49
efriedmriedem: "the same" meaning add19:51
efriedexport DEVSTACK_GATE_USE_PYTHON3=True19:51
efried?19:51
mriedemyeah19:52
efriedack, trying, thanks.19:52
*** artom has quit IRC19:53
*** artom has joined #openstack-nova19:55
*** gmann is now known as gmann_afk19:57
dansmithlet it be known gmann_afk is a gentleman and his word is his bond19:59
openstackgerritMatt Riedemann proposed openstack/nova master: Allow disabling cold migration to the same host  https://review.opendev.org/67602220:21
*** dpawlik has quit IRC20:22
dustincdansmith: If you have a minute, would you mind taking a peek at this real quick and offering your opinion? https://review.opendev.org/#/c/693414/20:26
*** tosky has quit IRC20:27
openstackgerritMatt Riedemann proposed openstack/nova master: Allow disabling cold migration to the same host  https://review.opendev.org/67602220:28
openstackgerritEric Fried proposed openstack/nova-specs master: Spec: Ussuri: Encrypted Emulated Virtual TPM  https://review.opendev.org/68680420:30
efrieddansmith: Updated per your comments, but some of them left more questions than answers. I could use some help, please, when you get a chance.20:30
efriedjroll: ^ might come down to "are we dead in the water if we simply can't support shelve-offload (and possibly others)?"20:31
* efried feeds face20:31
openstackgerritArtom Lifshitz proposed openstack/nova master: Functional tests for NUMA live migration  https://review.opendev.org/67259520:31
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA LM: Add func test for bug 1845146  https://review.opendev.org/68740420:31
openstackbug 1845146 in OpenStack Compute (nova) train "NUMA aware live migration failed when vCPU pin set" [High,Fix committed] https://launchpad.net/bugs/1845146 - Assigned to Dan Smith (danms)20:31
dansmithdustinc: my opinion on what? whether it's fundamentally okay?20:34
*** openstackgerrit has quit IRC20:35
dustincdansmith: Yes, efried suggested an alternative and I wanted help figuring out what makes more sense20:36
*** ociuhandu has joined #openstack-nova20:38
efrieddansmith: Trying to address what happens when the same node appears more than once in provider configs. Due to e.g. ironic rebalance we can't just fail, because the "conflict" might not appear until we're already running. So we have to set some kind of precedence rules for ``$COMPUTE_NODE`` vs explicit uuid and name20:39
dansmithohh, I clicked on the wrong link20:40
efriedIn practice, I think this could only possibly be an issue at runtime in an ironic deployment when a rebalance happens, I think. At which point a new node will "appear" and we have to decide whether it has a provider config.20:40
dansmithI have to run an errand, so I should probably not try to squeeze in a quick read of that before I go.20:40
efriedIf we commit to this only being an issue in that ^ scenario, then I *think* the fact that ironic node RP name == uuid (doesn't it?) would let us hardcode an unambiguous solution pretty easily.20:41
efriedI need to food and then school run, will check back on this later.20:41
dansmithI would punt to mriedem on that as I think he has the most ironic RP stuff in his head20:41
dansmithbut yeah, will leave this open for later20:42
*** ociuhandu has quit IRC20:42
*** ociuhandu has joined #openstack-nova20:43
*** dpawlik has joined #openstack-nova20:45
*** openstackgerrit has joined #openstack-nova20:45
openstackgerritMatt Riedemann proposed openstack/os-traits master: Add COMPUTE_SAME_HOST_COLD_MIGRATE trait  https://review.opendev.org/66660420:45
openstackgerritMerged openstack/nova master: Fix driver tests on Windows  https://review.opendev.org/51852520:47
*** eharney has quit IRC20:48
*** igordc has quit IRC20:50
mriedem"ironic node RP name == uuid (doesn't it?)" yes20:50
mriedemironic node RP name/uuid == compute node hypervisor_hostname and uuid == ironic node id20:51
*** mgariepy has quit IRC20:53
*** dpawlik has quit IRC20:58
*** ociuhandu has quit IRC20:58
*** gmann_afk is now known as gmann21:03
*** igordc has joined #openstack-nova21:15
*** awalende has joined #openstack-nova21:15
*** dpawlik has joined #openstack-nova21:17
dansmithefried: dustinc I don't understand.. you can just use ironic node uuid and be properly unique and specific no?21:18
*** dpawlik has quit IRC21:23
dustincdansmith: well we need to make sure that whoever put it in the file did so correctly...the original spec required that if two different entries referenced the same provider, it would cause nova to fail to init, but since we realized that we cannot be sure if a specific uuid and $COMPUTE_NODE reference the same provider until _after_ init, we need to not fail so had to come up with another plan21:25
*** ociuhandu has joined #openstack-nova21:29
*** awalende has quit IRC21:30
dansmithdustinc: I think it's expected that "whoever put" anything in the file did so correctly21:32
dansmithIMHO, the solution is to use the ironic uuid there, regardless of which compute host gets that node in the rebalance, I think that's fine21:32
*** awalende has joined #openstack-nova21:45
*** ociuhandu has quit IRC21:48
*** mriedem has quit IRC21:48
*** eharney has joined #openstack-nova21:48
*** lpetrut has quit IRC21:50
*** mriedem has joined #openstack-nova21:51
*** rcernin has joined #openstack-nova21:59
*** awalende has quit IRC22:01
*** rcernin has quit IRC22:01
*** rcernin has joined #openstack-nova22:01
*** rcernin has quit IRC22:01
*** rcernin has joined #openstack-nova22:02
*** nweinber__ has quit IRC22:05
dustincdansmith: Well the issue is that we need to decide what to do in the case the node is defined more than once in the configuration files. I proposed that we use the first entry that identifies the node and ignore the rest, but efried proposes that we use the $COMPUTE_NODE as a catch all and the specific uuid/name identification should take precedence if both exit (this makes sense the more I think about it)22:06
dustincthe remaining issue we _might_ run into is what happens if the node is identified by name and uuid?22:06
efrieddustinc: let me go check whether the ironic node RP name and uuid are in fact the same in placement...22:13
*** awalende has joined #openstack-nova22:14
*** priteau has quit IRC22:15
efrieddustinc: o look, a comment right at the top of ironic driver's update_provider_tree:22:15
efried        # nodename is the ironic node's UUID.22:15
efrieddansmith: lacking a better idea, do you think "create a glance image for the virtual device file" is an acceptable (if unlovely) path forward?22:16
dustincok so we can identify name/uuid identification conflicts before init with ironic...but what about nova? how can we be sure a name and uuid don't identify the same node? what should we do in the case that happens?22:17
efrieddustinc: that we should be able to determine the *first* time the RT hits this code, i.e. on startup.22:17
efriedfor non-ironic, that is. Because we're looking at the compute node RP already.22:18
*** awalende has quit IRC22:19
efriedTo cover ironic, we just put an extra check that cfg1['name'] != cfg2['uuid'] for all (cfg1, cfg2). It's a tad specific, but it would be insanity for node[name] on one node to be the same as node[uuid] on another, so I don't feel awful about doing that.22:19
*** awalende has joined #openstack-nova22:21
efriedbtw, to anticipate (ironic) scaling issues, probably a good idea to index the configs by identifier. Which, since we're forbidding name/uuid conflicts, actually helps make ^ seem saner :P22:21
efriedso, the load-up logic becomes simply:22:23
efriedif identifier in cfgs:22:23
efried    puke22:23
efriedcfgs[identifier] = cfg22:23
efriedAnd then when we're processing a node:22:23
efriedif node.name in cfgs:22:23
efried    cfg = cfgs[node.name]22:23
efriedelif node.uuid in cfgs:22:23
efried    cfg = cfgs[node.uuid]22:23
efriedelif '$COMPUTE_NODE' in cfgs:22:23
efried    cfg = cfgs['$COMPUTE_NODE']22:23
efriedelse:22:24
efriedor more terser:22:24
efriedcfg = cfgs.get(node.uuid, cfgs.get(node.name, cfgs.get('$COMPUTE_NODE')))22:24
efriedif cfg: ...22:24
*** awalende has quit IRC22:29
*** awalende has joined #openstack-nova22:29
*** pcaruana has quit IRC22:33
*** awalende has quit IRC22:35
*** slaweq has quit IRC22:39
*** ociuhandu has joined #openstack-nova22:41
efrieddansmith: procedurally, to get things moving, how would you feel about "resize/migration/shelve/others will be addressed in a subsequent spec"?22:44
*** jaosorior has quit IRC22:45
*** ociuhandu has quit IRC22:46
*** slaweq has joined #openstack-nova22:48
*** munimeha1 has quit IRC22:49
*** jaosorior has joined #openstack-nova22:49
*** jaosorior has quit IRC22:52
*** slaweq has quit IRC22:53
*** slaweq has joined #openstack-nova23:03
*** ociuhandu has joined #openstack-nova23:07
*** tkajinam has joined #openstack-nova23:07
*** abaindur has quit IRC23:07
*** ociuhandu has quit IRC23:09
*** abaindur has joined #openstack-nova23:09
efriedmriedem: Is grenade *supposed* to use py2 on the "old" side?23:10
*** ociuhandu has joined #openstack-nova23:11
*** ociuhandu has quit IRC23:16
*** slaweq has quit IRC23:16
melwittmriedem: new tempest test shenanigans you might have an opinion about https://review.opendev.org/693096 tl;dr is downstream we want to be able to test with the config_drive: True request param for POST /servers and one way to add it would result in dupe test coverage in the gate23:19
*** priteau has joined #openstack-nova23:20
gmannefried: for ussuri jobs no. py2->py3 does not work and required more fixes on pckg installation etc. it was decided to do py3->py3 in grenade ussuri jobs.23:22
melwittgmann: hey, could you hit up the unified limits spec again? john updated to address your latest comments23:24
*** tosky has joined #openstack-nova23:24
*** slaweq has joined #openstack-nova23:25
efriedgmann: Gotcha. How do I make the "old" side run py3 then?23:25
gmannmelwitt: done.23:26
melwittthanks gmann23:26
*** tosky has quit IRC23:26
efriedgmann: note that https://review.opendev.org/#/c/695052/ still failed with the old side running py2, so23:26
efried  export DEVSTACK_GATE_USE_PYTHON3=True23:26
efriedapparently isn't correct/sufficient.23:26
gmannefried: is it, this should make use_python3=True on old node23:27
gmanni did in all other patches also - https://review.opendev.org/#/q/topic:drop-py27-support-devstack-default-py3+(status:open+OR+status:merged)23:27
gmannand grenade-py3 job is doing that only.23:27
*** slaweq has quit IRC23:30
*** efried has quit IRC23:30
*** ociuhandu has joined #openstack-nova23:30
gmannfor example, watcher patch is working fine - https://review.opendev.org/#/c/695097/123:33
*** abaindur has quit IRC23:34
gmannfrom log it seems like DEVSTACK_GATE_USE_PYTHON3 is not set on d-g side23:36
*** abaindur has joined #openstack-nova23:36
*** ociuhandu has quit IRC23:40
*** slaweq has joined #openstack-nova23:42
*** slaweq has quit IRC23:47
*** efried has joined #openstack-nova23:49
efriedgmann: sorry, I didn't mean to bail on you there, I was trying to get to zuul.o.o/jobs and it crashed my machine. This has been happening for a while, I should learn.23:50
efriedAnyway, now I *do* need to bail. I'll try to catch up with you tomorrow about the grenade business.23:50
gmannefried: sure.23:51
*** ivve has quit IRC23:54
*** Liang__ has quit IRC23:54
*** slaweq has joined #openstack-nova23:57
*** ociuhandu has joined #openstack-nova23:58

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