| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2024-11-21 | |||
| 11:08:20 | opendevreview | Merged openstack/os-vif master: address test stablity under load https://review.opendev.org/c/openstack/os-vif/+/935653 | |
| 11:08:21 | opendevreview | Merged openstack/os-vif master: Clean up Windows support https://review.opendev.org/c/openstack/os-vif/+/932436 | |
| 11:55:24 | opendevreview | Stephen Finucane proposed openstack/nova master: api: Remove empty description field https://review.opendev.org/c/openstack/nova/+/935882 | |
| 12:35:35 | yosef | Hi, what is the best way to renew flavor properties of a created VM? I mean it is copied to a separate table and without down time it is not possible to refresh its contents | |
| 12:35:49 | yosef | if flavor properties is changed | |
| 12:46:10 | sean-k-mooney | yosef: so the short answer is you cant do that by desgin the long answer is the flavor is embeded in 2 diffent dbs. there is a copy in the request_spec in the api db and a copy in the instance_extra table in the cell db | |
| 12:46:44 | sean-k-mooney | the only wasy to update the embeded flaovr in an instance today vai supproted methods is resize | |
| 12:46:59 | sean-k-mooney | once a flavor is used you are not really ment to change any of the extra specs | |
| 12:56:45 | jkulik | We built a nova-manage command for that in our cloud: https://github.com/sapcc/nova/blob/stable/xena-m3/nova/cmd/manage.py#L3207 - reason was that we would have to change properties on flavors and wanted them used on live- and offline migrations to prohibit them from going to hypervisors with a new trait | |
| 12:58:14 | opendevreview | ribaudr proposed openstack/nova master: Deletion of associated share mappings on instance deletion https://review.opendev.org/c/openstack/nova/+/881472 | |
| 12:58:14 | opendevreview | ribaudr proposed openstack/nova master: Mounting the shares as part of the initialization process https://review.opendev.org/c/openstack/nova/+/880075 | |
| 12:58:15 | opendevreview | ribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/854823 | |
| 12:58:15 | opendevreview | ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500 | |
| 12:58:16 | opendevreview | ribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/860284 | |
| 12:58:16 | opendevreview | ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/854824 | |
| 12:58:17 | opendevreview | ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/860285 | |
| 12:58:18 | opendevreview | ribaudr proposed openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287 | |
| 12:58:18 | opendevreview | ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286 | |
| 12:58:20 | opendevreview | ribaudr proposed openstack/nova master: Check shares support (compute manager) https://review.opendev.org/c/openstack/nova/+/885751 | |
| 12:58:20 | opendevreview | ribaudr proposed openstack/nova master: Allow to mount manila share using Cephfs protocol https://review.opendev.org/c/openstack/nova/+/883862 | |
| 12:58:22 | opendevreview | ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/885753 | |
| 12:58:22 | opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (API) https://review.opendev.org/c/openstack/nova/+/836830 | |
| 12:58:24 | opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028 | |
| 12:58:24 | opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501 | |
| 12:58:26 | opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282 | |
| 12:58:26 | opendevreview | ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029 | |
| 12:58:28 | opendevreview | ribaudr proposed openstack/nova master: Reports instance events to the DB regarding attaching and detaching a share https://review.opendev.org/c/openstack/nova/+/927088 | |
| 12:58:28 | opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283 | |
| 12:58:30 | opendevreview | ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087 | |
| 12:58:30 | opendevreview | ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086 | |
| 12:58:32 | opendevreview | ribaudr proposed openstack/nova master: Refactor test_server_shares: Mock in Base Class and trait verification https://review.opendev.org/c/openstack/nova/+/935861 | |
| 12:58:32 | opendevreview | ribaudr proposed openstack/nova master: Manila shares admin guide documentation https://review.opendev.org/c/openstack/nova/+/871642 | |
| 13:11:28 | sean-k-mooney | jkulik: you can do that without modifying existing flavor using isolating aggreates in placment to declare the new trait as required | |
| 13:11:46 | sean-k-mooney | jkulik: https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html | |
| 13:12:15 | sean-k-mooney | we have talked about adding a simiar command to the image property update a few times but no one has had the time to move it forward | |
| 13:14:01 | jkulik | cool, I didn't know about that filter. I'm not sure if we did more changes in addition to traits, though. Very helpful, though. | |
| 14:23:44 | mnasiadka | https://opendev.org/openstack/monasca-api/src/commit/c36c2c69a4227e0c1da04f3044bfa4b059a55781/monasca_api/config.py#L83 - due to https://github.com/benoitc/gunicorn/issues/2286. Anybody has any ideas? | |
| 14:23:44 | mnasiadka | Hello there, was doing a small experiment to switch from apache/mod_wsgi to gunicorn in Kolla (since uwsgi is in maintenance mode, so I'd prefer to do it once than switch again when the wind blows in other direction), but it seems gunicorn does not support pyargv - so I guess the only option is to do what Monasca did - | |
| 15:22:03 | ildikov | sean-k-mooney: Hi Sean, I'm sorry for being on and off yesterday. I looked into the Nova contributor docs links you shared. The documentation seems to be very extensive, which is great. At the same time, it seems like there are a few areas that need some updates to reflect what processes the team is currently using, since y'all are continuously evolving those. Is my understanding accurate? | |
| 15:26:31 | ildikov | sean-k-mooney: I also understand your frustration about the feedback towards Nova regarding docs. In my case, my feedback was influenced by the conversation I had with bauzas at the OpenInfra Summit about the new etherpad process not being in the Nova docs yet. I intended to focus on fixing that, rather than implying that Nova doesn't have documentation in these areas at all. | |
| 15:26:34 | ildikov | sean-k-mooney: I'm sorry I wasn't able to phrase my point more clearly. | |
| 15:28:03 | ildikov | One thing I got curious about while looking at the docs, is how much people discover and use them. I think there should be some stats available somewhere at least on the level of page views. | |
| 15:30:12 | ildikov | Do you think that would be useful information to have? What other metrics do you think would be worth while to look into to figure out how to improve the content and visibility of the docs? | |
| 15:33:19 | sean-k-mooney | ya so usign the etherpad was new last cycle and bauzas didnt get aroudn to updatign the process doc with that | |
| 15:33:54 | ildikov | ah, ok, I understand | |
| 15:34:08 | ildikov | I didn't have that piece of information | |
| 15:34:40 | sean-k-mooney | the 2 cycles before we use the gerrit review priority lable | |
| 15:35:15 | ildikov | has the etherpad process fully replaced the Gerrit review label one? | |
| 15:36:08 | sean-k-mooney | yes i actully had an action item to update the gerrrit config to remvoe it | |
| 15:36:18 | sean-k-mooney | well i offeren to do that | |
| 15:36:32 | sean-k-mooney | but we never decied to actuly go do it but at this point i think we can just for clarity | |
| 15:38:21 | ildikov | I understand, these processes need implementation steps and people to get used to them, so it can get harder to decide to remove them | |
| 15:38:55 | sean-k-mooney | yep so i can just go find the patch i used to add the labels and propose a revert | |
| 15:39:16 | sean-k-mooney | cores stopped using it and moved to the etherpad | |
| 15:39:18 | ildikov | +1 | |
| 15:40:03 | ildikov | do you think it makes sense to leave the description in the docs as an archive to remind people what the team tried in the past? | |
| 15:40:21 | ildikov | or should it be replaced with the description of how the new ether pad-based process works? | |
| 15:40:43 | sean-k-mooney | perhapse if we do that it shoudl have a note saying its not used or strick through | |
| 15:40:48 | sean-k-mooney | but its alwasy in git | |
| 15:40:55 | sean-k-mooney | so im inclined to delete it | |
| 15:41:08 | sean-k-mooney | we shoudl remove the section related to runways as well | |
| 15:41:27 | ildikov | yeah, the target audience for those docs are newcomers and casual contributors for the most part | |
| 15:42:06 | ildikov | so having only the information there that's currently relevant for them is probably the best approach | |
| 15:42:57 | sean-k-mooney | ildikov: the history is we used to track priority the nova wiki, then that moved to the spec repo about 10 years ago, then we decied that was too heavy weight and we moved to "runways" in etherpad 6-8 years ago, then that hadd too much load on the ptl to we went to review priority lable about 3 years ago and back to a lighter weigher etherpad last year | |
| 15:43:39 | sean-k-mooney | over all that time specs/bluepirnts/bug usage has not changed. just where we keep the list of items ready to review and the prioriteis to review | |
| 15:44:16 | ildikov | I understand, it seems the team went through quite a few rounds of simplifications | |
| 15:44:54 | sean-k-mooney | as the team size got smaller and smaller and contonutions dropped off the cost of the more complex approches just didnt make sense | |
| 15:45:06 | sean-k-mooney | *contibutions | |
| 15:45:18 | ildikov | understandable | |
| 15:46:01 | ildikov | even with a bigger team size, I'm always a fan of simpler processes, when possible | |
| 15:46:01 | sean-k-mooney | https://etherpad.opendev.org/p/nova-2025.1-status so we call it the status etherpad | |
| 15:46:36 | sean-k-mooney | basically because it a light weight way to highlight the progress or lack there of of somethign that peropsl are activly working on | |
| 15:46:48 | sean-k-mooney | but its in etherpad so that anyone can edit it | |
| 15:47:24 | ildikov | oh nice! | |
| 15:47:53 | ildikov | it looks like a good overview of what the team is tracking throughout the release cycle | |
| 15:48:20 | ildikov | gives the opportunity to do a bit of project management, but without being too heavy on the tooling | |
| 15:48:54 | sean-k-mooney | yep this is the dalmaition one https://etherpad.opendev.org/p/nova-dalmatian-status and caracal https://etherpad.opendev.org/p/nova-caracal-status | |
| 15:49:14 | sean-k-mooney | its useful wehn lookign for cycle highlights or releasenotes too | |
| 15:49:38 | sean-k-mooney | that why we have the complete bugs and features section | |
| 15:50:01 | sean-k-mooney | you dont need ot have your review listed on the eptherpad for it to get reviewed or merged | |
| 15:50:24 | sean-k-mooney | it just help publicise it so its simpler for reviewers to find | |
| 15:52:02 | ildikov | I love that! | |
| 15:52:51 | ildikov | sometimes it's hard to fish for cycle highlights, etc, so it's nice y'all have the pointers in the etherpad | |
| 15:53:30 | ildikov | I have a meeting coming up, so will step away from IRC a bit | |
| 15:53:46 | ildikov | I don't know enough about the processes to update the contributor docs myself | |
| 15:54:20 | ildikov | what other ways can I help to make improvements and help new and casual contributors looking into Nova? | |
| 15:57:53 | sean-k-mooney | ildikov: its litrally just a normal review. so if you think you can rupdate it to help in anyway and have time to submit a reivew to the docs then please do, you could track it as a docs bug if you wanted too. | |
| 15:58:47 | sean-k-mooney | creating a bug for this and addign it to the meeting adgenda (the open discussion section) woudl proably be a good way forward | |
| 15:59:11 | sean-k-mooney | im not sure that ill have time to go do the doc update but perhaps that is somethign bauzas can help drive as ptl | |
| 16:00:14 | ildikov | sean-k-mooney: Sounds good. I'll create a docs bug later today, that is easy to do. We can then figure out next steps from there. | |
| 16:00:34 | ildikov | sean-k-mooney: thank you for the nice chat and the guidance! | |
| 16:00:49 | sean-k-mooney | no worries, enjoy your meeting :P | |
| 16:01:28 | sean-k-mooney | ill revert https://review.opendev.org/c/openstack/project-config/+/787523 in the interim | |
| 16:02:05 | sean-k-mooney | a striat revert wont work becasue we updated them in https://review.opendev.org/c/openstack/project-config/+/837595 but it wont take long to create a patch to do this | |
| 16:29:09 | bauzas | ildikov: sean-k-mooney : sorry I was awfully busy those days (and I don't wanna speak about last weeks-months) | |
| 16:29:37 | bauzas | that's still a TODO on myself to rejuvanate the docs but I'll try to make it soon as I can | |
| 16:52:39 | ildikov | bauzas: no worries | |
| 16:52:50 | melwitt | sean-k-mooney: ok so with an invalid config for the resource list, the error is raised during startup but it is not causing the nova-api process to exit https://paste.openstack.org/show/b7s0zWslkXznihw1Y3yB/ | |
| 16:53:16 | ildikov | bauzas: is it helpful to you if I create the docs bug that we talked about with Sean earlier? | |
| 16:57:37 | melwitt | sean-k-mooney: the oslo.service based processes do exit with a bad config (like nova-conductor). so the wsgi app case needs a bit more to cause an exit of the process | |