| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-08-02 | |||
| 14:23:05 | gibi | I think so | |
| 14:25:18 | gibi | kashyap: one thing i see is that nova stores the image meta in instance.system_metadata['image_hw_machine_type'] so that even if the image is changed later the instance has its machine type persisted | |
| 14:25:59 | kashyap | Yeah, we do store it in system_metadata (Lee did that work) | |
| 14:26:07 | gibi | also if an admin want to query the machine_type of an instance then it can be done via nova-manage | |
| 14:26:08 | kashyap | https://docs.openstack.org/nova/latest/admin/hw-machine-type.html | |
| 14:26:29 | gibi | ack, that is the one | |
| 14:26:30 | kashyap | gibi: What about the tenant user? (Perhaps via `openstack image show`? | |
| 14:27:10 | gibi | openstack image show only valid the the image properties are not changed after the instance is booted (I'm not sure the image meta could change) | |
| 14:27:27 | bauzas | oh the q35 saga | |
| 14:27:31 | bauzas | forgot about it | |
| 14:27:41 | bauzas | hence the nova-manage command | |
| 14:27:59 | bauzas | actually, 4 given I reply | |
| 14:28:02 | kashyap | gibi: Oh, right: "nova-manage image_property show $instance_uuid $property" | |
| 14:28:28 | kashyap | --^ The above is for tenant too, right? | |
| 14:29:18 | kashyap | So, it'd be: `nova-manage image_property show $instance_uuid hw_machine_type` | |
| 14:31:16 | gibi | the tenant does not have access to nova-manage | |
| 14:31:23 | gibi | that is an admin tool | |
| 14:31:26 | gibi | afaik | |
| 14:31:33 | kashyap | Yes, you're right | |
| 14:39:59 | opendevreview | Stanislav Dmitriev proposed openstack/nova master: Add support for sync writes with block migration https://review.opendev.org/c/openstack/nova/+/851892 | |
| 14:43:32 | opendevreview | Merged openstack/placement master: doc: Comment out language option https://review.opendev.org/c/openstack/placement/+/844855 | |
| 15:00:35 | opendevreview | Balazs Gibizer proposed openstack/nova master: Prevent instance.save() under mutated migration context https://review.opendev.org/c/openstack/nova/+/850746 | |
| 15:00:35 | opendevreview | Balazs Gibizer proposed openstack/nova master: Do not mutate migration context for rollback_live_migration_at_destination https://review.opendev.org/c/openstack/nova/+/851832 | |
| 15:01:05 | gibi | artom, dansmith: when the other direction ^^. I don't find anything that breaks when I remove the mutation from rollback_live_migration_at_destination so I did so | |
| 15:01:13 | gibi | s/when/went/ | |
| 15:12:43 | elodilles | bauzas: are you updating the meeting page right now, or is it OK if i edit it? | |
| 15:13:02 | bauzas | elodilles: I'm piling a lot of stuff, please do it by now and then I'll do it | |
| 15:13:33 | elodilles | bauzas: ack, one sec | |
| 15:15:40 | elodilles | bauzas: done (i tried to be quick :)) | |
| 15:25:45 | opendevreview | Balazs Gibizer proposed openstack/nova master: Prevent instance.save() under mutated migration context https://review.opendev.org/c/openstack/nova/+/850746 | |
| 15:35:41 | bauzas | reminder : nova meeting in 25 mins here | |
| 15:37:50 | gibi | stephenfin: if you have time, this makes py310 happy with unittest.mock https://review.opendev.org/c/openstack/nova/+/851445/ | |
| 15:47:55 | opendevreview | Merged openstack/python-novaclient master: Microversion 2.91: Support specifying destination host to unshelve https://review.opendev.org/c/openstack/python-novaclient/+/831651 | |
| 15:54:44 | Uggla | gibi, maybe dumb question but how do you properly set in instance in "failure" ? | |
| 15:57:51 | Uggla | instance.vm_state = vm_states.ERROR and instance.save() ? | |
| 15:59:01 | gibi | it depends on where and when the ERROR condition happened | |
| 15:59:14 | Uggla | I especially wonder about the error msg. | |
| 15:59:15 | gibi | you might need to report error on an instance event | |
| 16:00:04 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:04 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:04 | opendevmeet | Meeting started Tue Aug 2 16:00:04 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:04 | bauzas | #startmeeting nova | |
| 16:00:12 | bauzas | hi folks | |
| 16:00:18 | Uggla | o/ | |
| 16:00:39 | gibi | o/ | |
| 16:01:45 | bauzas | ok, let's start so people will join | |
| 16:01:53 | ratailor | o/ | |
| 16:01:55 | elodilles | o/ | |
| 16:02:02 | bauzas | #topic Bugs (stuck/critical) | |
| 16:02:09 | bauzas | #info No Critical bug | |
| 16:02:16 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 11 new untriaged bugs (+1 since the last meeting) | |
| 16:02:24 | bauzas | #link https://storyboard.openstack.org/#!/project/openstack/placement 27 open stories (+0 since the last meeting) in Storyboard for Placement | |
| 16:02:35 | bauzas | I had a small time for looking at the bugs | |
| 16:02:54 | bauzas | but I provided an etherpad https://etherpad.opendev.org/p/nova-bug-triage-20220726 | |
| 16:03:15 | bauzas | I only triaged two, as at least 3 other bugs need to be looked more | |
| 16:03:33 | bauzas | that's it | |
| 16:03:41 | opendevreview | Merged openstack/python-novaclient master: Add support for 2.92 : keypair import mandatory https://review.opendev.org/c/openstack/python-novaclient/+/851231 | |
| 16:03:55 | bauzas | any bug to discuss ? | |
| 16:04:46 | bauzas | btw. I had fun with https://bugs.launchpad.net/nova/+bug/1983263 | |
| 16:05:19 | bauzas | looks we only accept Ussuri computes for Ussuri :p | |
| 16:05:43 | bauzas | could be a FFU issue :) | |
| 16:06:36 | bauzas | just sayin' :) | |
| 16:06:47 | bauzas | anyway, moving on | |
| 16:07:01 | bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | |
| 16:07:15 | bauzas | elodilles: do you want to get the bug baton for this week ? :) | |
| 16:08:04 | elodilles | bauzas: yes please! \o/ | |
| 16:08:07 | elodilles | :) | |
| 16:08:12 | bauzas | suuuuure | |
| 16:08:23 | bauzas | #info Next bug baton is passed to elodilles | |
| 16:08:27 | bauzas | that's it for bugds | |
| 16:08:34 | bauzas | #topic Gate status | |
| 16:08:41 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:08:48 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status | |
| 16:08:58 | bauzas | #link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly&skip=0 Centos 9 Stream periodic job status | |
| 16:09:05 | bauzas | #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs | |
| 16:09:15 | bauzas | I've look at all of above ^ | |
| 16:09:19 | bauzas | looked | |
| 16:09:24 | bauzas | no issues I found | |
| 16:09:39 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:09:45 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:09:58 | bauzas | really, please stop saying 'recheck' | |
| 16:10:21 | bauzas | last time, we found 50% nova rechecks that were blind | |
| 16:10:33 | bauzas | I mean, 50% of all the nova rechecks | |
| 16:11:37 | bauzas | moving on ? | |
| 16:12:21 | gibi | nope | |
| 16:12:25 | bauzas | #topic Release Planning | |
| 16:12:35 | bauzas | #link https://releases.openstack.org/zed/schedule.html | |
| 16:12:40 | bauzas | #info Zed-3 is in 4 weeks | |
| 16:12:55 | bauzas | now, hopefully you've seen my email from yesterday | |
| 16:13:28 | bauzas | #link https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029789.html | |
| 16:13:56 | bauzas | I propose now to look at the etherpad I created | |
| 16:14:09 | bauzas | #link https://etherpad.opendev.org/p/nova-zed-microversions-plan | |
| 16:14:23 | bauzas | we have 3 open changes asking for a microversion | |
| 16:15:57 | bauzas | so I'd like to ask you folks how we could organize and triage those 3 between them for a microversion | |
| 16:16:46 | gibi | for me it depends on how close they are to land | |
| 16:17:20 | bauzas | two of them were already modified to use 2.92 | |
| 16:17:36 | bauzas | so it looks to me both can be priorital | |
| 16:17:48 | bauzas | one is touching the /servers API | |
| 16:18:07 | bauzas | but only by a single rebuild action | |
| 16:18:51 | bauzas | the other one is technically a WIP and adding a new API resource /os-server-shares | |