Earlier  
Posted Nick Remark
#openstack-nova - 2022-10-21
15:37:56 gibi bauzas: thanks for running it
15:39:33 melwitt bauzas: thank you for connecting me with whoami-rajat for ptg, cinder team were able to fit me in the agenda and we had a good chat and a way forward
15:39:52 bauzas ++
17:02:19 whoami-rajat melwitt, thanks for joining and discussing it
17:02:46 melwitt ++
18:37:06 opendevreview Alex Chan proposed openstack/nova stable/xena: fix instance action log when deleting shelved instance https://review.opendev.org/c/openstack/nova/+/861951
19:14:12 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Fix pre_live_migration rollback https://review.opendev.org/c/openstack/nova/+/836016
19:14:13 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Adds regression test for bug LP#1944619 https://review.opendev.org/c/openstack/nova/+/862401
19:18:40 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Adds regression test for bug LP#1944619 https://review.opendev.org/c/openstack/nova/+/838332
19:18:41 opendevreview Erlon R. Cruz proposed openstack/nova stable/wallaby: Fix pre_live_migration rollback https://review.opendev.org/c/openstack/nova/+/836016
20:14:24 opendevreview Alex Chan proposed openstack/nova master: record action log when deleting shelved instance https://review.opendev.org/c/openstack/nova/+/862404
#openstack-nova - 2022-10-22
02:19:04 opendevreview melanie witt proposed openstack/nova master: DNM testing images_type = raw with resize enabled https://review.opendev.org/c/openstack/nova/+/862416
02:21:15 opendevreview melanie witt proposed openstack/nova master: DNM testing images_type = raw with resize enabled https://review.opendev.org/c/openstack/nova/+/862416
07:01:41 opendevreview melanie witt proposed openstack/nova master: DNM testing images_type = raw with resize enabled https://review.opendev.org/c/openstack/nova/+/862416
13:03:34 opendevreview melanie witt proposed openstack/nova master: DNM testing images_type = raw with resize enabled https://review.opendev.org/c/openstack/nova/+/862416
#openstack-nova - 2022-10-24
09:34:57 opendevreview Sahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state https://review.opendev.org/c/openstack/nova/+/858383
09:34:58 opendevreview Sahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state https://review.opendev.org/c/openstack/nova/+/858384
09:54:16 sean-k-mooney1 sahid: ill try to summerise the ptg discussion on the spec review but when we discussed you feature we agreed on two high level things.
09:55:06 sean-k-mooney1 1.) we wont ask you to fix all the drivers to not start the vms, we will file that as an existing bug and adress that later although your free to do that too once your feature is complete
09:55:38 sean-k-mooney1 2.) we dont wat to add a new api parmater. instead we woudl prefer the new micro verion to just make evacuate always evacuate to powered off
09:57:52 sean-k-mooney sahid: what that means for you is all the rpc changes you made are still correct and can be resused but you do not need to add a new api parmater, the new microversion means set the target state to stopped and old means dont pass it for the rpc call.
09:58:11 sean-k-mooney ill summerise this in the spec later today
09:58:57 sean-k-mooney sahid: it was basicaly the last topic of the ptg https://etherpad.opendev.org/p/nova-antelope-ptg#L451
09:59:58 sahid_ sean-k-mooney: o/ I had some connectivty issues, sorry for that, could you copy/past your last messages addressed to me?
10:17:31 frickler sahid_: unless you are referring to private messages, you could also check the channel log at https://meetings.opendev.org/irclogs/%23openstack-nova/latest.log.html
12:18:01 sahid frickler: ack thanks
12:24:36 sahid sean-k-mooney: i see, so now the prefererenc for evacuate would be to always evacuate to shutoff, right?
12:26:41 sahid btw thank to give me the chance to not update all the virt drivers :-) Should I open the bug report or have you already assigned someone during PTG to open it?
12:45:05 rm_work hey, hoping someone can help me understand how the fault reporting system works when retries are enabled... it seems like the "fault" field always just says "MaxRetriesExceeded" and gives that traceback, when I'd hope to be able to see the REASON for the failure (at least the latest failure)?
12:45:39 rm_work I am not sure how that would work, but I'm sure there must be some way to make that happen (and maybe we messed it up internally) because otherwise the "fault" field seems like it'd be pretty useless?
12:48:36 rm_work or maybe I'm expecting the wrong thing here, maybe that's right depending on the type of error?
12:52:23 rm_work I guess it's storing each fault in the DB on the server object somehow when it happens, so it'd be the last failure recorded that gets shown in the `server show` return?
13:01:55 sean-k-mooney sahid: we kind of felt it would be unfair to ask you do do that since its not actully required for your feature. its more just existing tech debt. sure please feel free to file one if not i can do it later. and yes the prefecne is to always evacuate to off when using the new microversion
13:02:51 sean-k-mooney baiscally because of a data integrety, power usage and encypted voluems we felt it would be better to alwasy evacuate as off
13:03:37 sean-k-mooney since evacuate is an admin only opeartion its not reasonable to assume the admin knows if its safe to restart the workload or not escially since there may be a posiablity of data curruption depending on howt eh host fails
13:04:04 sean-k-mooney so if we alwasy evacuate to off then the enduser who should know can decied if they want to start, rescue or delete the instace
13:05:02 sean-k-mooney sahid: for the encypted volume case it would be niceif you could handel and ignore the excption we get during spawn but that can be a follow up patch
13:05:48 sean-k-mooney sahid: evenutlaly we woudl like to split up rebuild/evacuate int 3 steps internally. 1 stop the instace, 2 rebuild the disk, 3 start it if requried.
13:09:52 sahid_ sean-k-mooney: if I understand, making it stop by default (the current spec), then in future have the internal clean that you are mentionning, and finally give users ability to choice active/stop, right?
13:11:40 sean-k-mooney no we dont want to give user a choice explictly. if they want the old behaivor they can use the old microverion but going forward we want evacuate to always mean evacuate to powerered off with the new micorversion
13:12:08 sean-k-mooney well its exiplcit in that its contorlled by the microversion but we dont want a new api parmater for it
13:12:39 sean-k-mooney so short term (A cycle) just allow evacuate to powered off
13:13:31 sean-k-mooney medeium term bug fix to not try and start the vm when the intended state is off as a non backporatble change to all drivers
13:14:04 sean-k-mooney that can be done in the A or later cycles
13:14:56 sean-k-mooney sahid_: does that sound ok to you.
13:26:21 sahid_ sean-k-mooney: yes understood, sounds good
13:26:38 sahid_ thank you for your help on it, I will update the spec to reflect that
13:27:02 sahid_ also open an issue
13:27:08 sean-k-mooney cool once updated ill be happy to re review
13:27:14 sahid_ ++
13:28:53 sahid_ are we agree with that I will still have to change the RPC and API to pass a targetState that will be based on the microversion, right?
13:29:59 sean-k-mooney yep
13:30:10 sean-k-mooney so you can keep all that code that you already wrote
13:30:33 sean-k-mooney its jsut that instead of having a parmater in the payload to set targetState
13:30:41 sean-k-mooney you will set it based on the micoversion
13:30:59 sean-k-mooney and with the new micorverison it will hardoced to off
13:31:21 sean-k-mooney with the old micorversion you dont need to pass it at all
13:31:24 sahid_ yeah i understand the whole process, perfect
14:22:32 bauzas (just typing here again, I was in the wrong chan)
14:22:39 bauzas man, my fingers bleed
14:22:48 bauzas just a bit of warning, I tried to summarize as much as I can for the PTG recap, but this will be a very long thread
14:22:58 bauzas I'm at 80% of the writing but I need to caffeinate
14:26:40 sean-k-mooney :)
14:26:52 sean-k-mooney well hopefully that means it was productive
17:26:35 dansmith bauzas: we already have --purge for archive that does the purge immediately, right?
17:27:51 sean-k-mooney dansmith: yep
17:28:04 sean-k-mooney dansmith: but we would like to have --deleted for pruge
17:28:22 sean-k-mooney so we can eventrully remove the use of arcive and make our purge work like all the opter project
17:28:46 sean-k-mooney the other service dont have shadow tables so there perge remove the deleted rows
17:28:49 dansmith so instead of archive --purge, purge --deleted ?
17:29:07 sean-k-mooney yep basically that
17:29:45 sean-k-mooney thats a lower priority item but purge everywhere else is the command to remove the deleted rows
17:29:53 dansmith meh, but okay
#openstack-nova - 2022-10-25
02:16:42 opendevreview shiyawei proposed openstack/nova master: fix bug: 1994018, the volume multiattach and in-use after retype another backend, then can not detach it Closes-Bug#1994018 https://review.opendev.org/c/openstack/nova/+/862355
06:01:39 opendevreview shiyawei proposed openstack/nova master: fix bug: 1994018, the volume multiattach and in-use after retype another backend, then can not detach it Closes-Bug#1994018 https://review.opendev.org/c/openstack/nova/+/862355
06:34:47 opendevreview shiyawei proposed openstack/nova master: fix bug: 1994018, the volume multiattach and in-use after retype another backend, then can not detach it Closes-Bug#1994018 https://review.opendev.org/c/openstack/nova/+/862355
06:36:55 opendevreview shiyawei proposed openstack/nova master: fix bug: 1994018, the volume multiattach and in-use after retype another backend, then can not detach it Closes-Bug#1994018 https://review.opendev.org/c/openstack/nova/+/862355
11:22:44 sean-k-mooney bauzas: you have not filed the bug for porting the clients to sdk yet have you
11:22:54 sean-k-mooney if not im going to file one for neutorn client now
11:23:38 bauzas no I had no time to actionate on the items yet
11:24:19 sean-k-mooney cool ill create one for neutron then to let ralonsoh have a bug to track
11:24:24 sean-k-mooney but i wont do the rest
11:33:18 sean-k-mooney bauzas: im not sure we need anytihng else in https://bugs.launchpad.net/nova/+bug/1994139
12:03:48 opendevreview Amit Uniyal proposed openstack/nova stable/ussuri: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/862603
12:03:49 opendevreview Amit Uniyal proposed openstack/nova stable/ussuri: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/862604
12:28:12 opendevreview Amit Uniyal proposed openstack/nova stable/ussuri: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/862603
12:28:13 opendevreview Amit Uniyal proposed openstack/nova stable/ussuri: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/862604
12:39:39 bauzas sean-k-mooney: bug report works for me
13:53:51 bauzas gibi: I forgot I have to visit a python meetup at 7pm so I'll need to either have a quick meeting today for the nova one, or just asking you to lead it after 15 mins
13:53:54 bauzas works for you ?
13:54:20 gibi works for me
13:54:33 gibi I can take the baton
13:59:48 bauzas gibi: cool
14:00:06 gibi but I also guess we will have a short one today
14:01:44 bauzas gibi: yup, hence me saying it should be quick
14:02:05 bauzas we have some questions about specless blueprints if we want but let's punt them for next week
14:51:49 zigo Nova unit tests are getting stuck, but I have no idea how to find out which one...
14:51:49 zigo Anyone knows about https://bugs.debian.org/1022733 ?
14:53:19 zigo I'm seeing 12 processes "[sh] <defunct>" started by stestr ... :/
14:53:30 zigo (that's the num of threads in my laptop, FYI)

Earlier   Later