| dansmith | sean-k-mooney: I'm not sure why you added the skip though.. your comment says "I'm not an SME but approved" and then followed up with a skip :) | 00:08 |
|---|---|---|
| sean-k-mooney | i added the skip because extending the time out to 10 seconds worked in check and failed in gate after 12 seconds... | 01:27 |
| sean-k-mooney | so basically we said fi the longer time out did not work we would skip until we can find a better long term solution. | 01:27 |
| sean-k-mooney | we can leave it till tomorrow, no worries | 01:30 |
| gmann | it seems nova live migration job failing with "openstack server create: error: argument --image: expected one argument" | 01:44 |
| gmann | https://zuul.opendev.org/t/openstack/build/ae91e51ade8147bd8063218f0b88cc12/log/job-output.txt#20779 | 01:44 |
| gmann | anything changed in osc side? | 01:44 |
| gmann | oh, actual error is due to not able to talk to glance. "Failed to contact the endpoint at https://10.210.65.110/image for discovery. Fallback to using that endpoint as the base url." | 01:47 |
| gmann | and image_id is None and so osc error | 01:47 |
| opendevreview | melanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits https://review.opendev.org/c/openstack/nova/+/924110 | 02:02 |
| opendevreview | melanie witt proposed openstack/nova master: Add [quota]unified_limits_resource_(strategy|list) https://review.opendev.org/c/openstack/nova/+/924025 | 05:19 |
| frickler | bauzas: gibi: please have another look at https://review.opendev.org/c/openstack/os-vif/+/935653 , I'd really like to get the whole stack that is blocked by this done this week. and I do think we will also need a fresh os-vif release for that once the two fixes are merged | 06:37 |
| frickler | gmann: if you look further up in the log, devstack already failed while deploying glance. not sure about the root cause for that, though | 06:40 |
| *** __ministry is now known as Guest381 | 07:10 | |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Improve heal_instance_info_cache periodic https://review.opendev.org/c/openstack/nova/+/935858 | 08:55 |
| opendevreview | ribaudr proposed openstack/nova master: Amend ShareMappingStatus due to asynchronous call https://review.opendev.org/c/openstack/nova/+/908864 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Amend DB model add a unique constraint. https://review.opendev.org/c/openstack/nova/+/912518 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Use client token when talking to manila https://review.opendev.org/c/openstack/nova/+/925277 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part) https://review.opendev.org/c/openstack/nova/+/833090 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Mounting the shares as part of the initialization process https://review.opendev.org/c/openstack/nova/+/880075 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Deletion of associated share mappings on instance deletion https://review.opendev.org/c/openstack/nova/+/881472 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500 | 09:28 |
| 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 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/854824 | 09:28 |
| 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 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute manager part) https://review.opendev.org/c/openstack/nova/+/860285 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Allow to mount manila share using Cephfs protocol https://review.opendev.org/c/openstack/nova/+/883862 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Check shares support (compute manager) https://review.opendev.org/c/openstack/nova/+/885751 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (API) https://review.opendev.org/c/openstack/nova/+/836830 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/885753 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283 | 09: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 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087 | 09:28 |
| opendevreview | ribaudr proposed openstack/nova master: Manila shares admin guide documentation https://review.opendev.org/c/openstack/nova/+/871642 | 09:28 |
| 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 | 09:29 |
| opendevreview | Merged openstack/os-vif master: address test stablity under load https://review.opendev.org/c/openstack/os-vif/+/935653 | 11:08 |
| opendevreview | Merged openstack/os-vif master: Clean up Windows support https://review.opendev.org/c/openstack/os-vif/+/932436 | 11:08 |
| opendevreview | Stephen Finucane proposed openstack/nova master: api: Remove empty description field https://review.opendev.org/c/openstack/nova/+/935882 | 11:55 |
| 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 |
| yosef | if flavor properties is changed | 12:35 |
| 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 |
| sean-k-mooney | the only wasy to update the embeded flaovr in an instance today vai supproted methods is resize | 12:46 |
| sean-k-mooney | once a flavor is used you are not really ment to change any of the extra specs | 12:46 |
| 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:56 |
| 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 |
| opendevreview | ribaudr proposed openstack/nova master: Deletion of associated share mappings on instance deletion https://review.opendev.org/c/openstack/nova/+/881472 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500 | 12:58 |
| 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 |
| 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 |
| 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 |
| 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 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Allow to mount manila share using Cephfs protocol https://review.opendev.org/c/openstack/nova/+/883862 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Check shares support (compute manager) https://review.opendev.org/c/openstack/nova/+/885751 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (API) https://review.opendev.org/c/openstack/nova/+/836830 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/885753 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283 | 12:58 |
| 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 |
| opendevreview | ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087 | 12:58 |
| opendevreview | ribaudr proposed openstack/nova master: Manila shares admin guide documentation https://review.opendev.org/c/openstack/nova/+/871642 | 12:58 |
| 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 |
| 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 |
| sean-k-mooney | jkulik: https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html | 13:11 |
| 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:12 |
| 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. | 13:14 |
| 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 - | 14:23 |
| 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 |
| 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:22 |
| 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 |
| ildikov | sean-k-mooney: I'm sorry I wasn't able to phrase my point more clearly. | 15:26 |
| 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:28 |
| 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:30 |
| 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 |
| ildikov | ah, ok, I understand | 15:33 |
| ildikov | I didn't have that piece of information | 15:34 |
| sean-k-mooney | the 2 cycles before we use the gerrit review priority lable | 15:34 |
| ildikov | has the etherpad process fully replaced the Gerrit review label one? | 15:35 |
| sean-k-mooney | yes i actully had an action item to update the gerrrit config to remvoe it | 15:36 |
| sean-k-mooney | well i offeren to do that | 15:36 |
| sean-k-mooney | but we never decied to actuly go do it but at this point i think we can just for clarity | 15:36 |
| 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 |
| sean-k-mooney | yep so i can just go find the patch i used to add the labels and propose a revert | 15:38 |
| sean-k-mooney | cores stopped using it and moved to the etherpad | 15:39 |
| ildikov | +1 | 15:39 |
| 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 |
| ildikov | or should it be replaced with the description of how the new ether pad-based process works? | 15:40 |
| sean-k-mooney | perhapse if we do that it shoudl have a note saying its not used or strick through | 15:40 |
| sean-k-mooney | but its alwasy in git | 15:40 |
| sean-k-mooney | so im inclined to delete it | 15:40 |
| sean-k-mooney | we shoudl remove the section related to runways as well | 15:41 |
| ildikov | yeah, the target audience for those docs are newcomers and casual contributors for the most part | 15:41 |
| ildikov | so having only the information there that's currently relevant for them is probably the best approach | 15:42 |
| 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:42 |
| 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:43 |
| ildikov | I understand, it seems the team went through quite a few rounds of simplifications | 15:44 |
| 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:44 |
| sean-k-mooney | *contibutions | 15:45 |
| ildikov | understandable | 15:45 |
| sean-k-mooney | https://etherpad.opendev.org/p/nova-2025.1-status so we call it the status etherpad | 15:46 |
| ildikov | even with a bigger team size, I'm always a fan of simpler processes, when possible | 15:46 |
| 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 |
| sean-k-mooney | but its in etherpad so that anyone can edit it | 15:46 |
| ildikov | oh nice! | 15:47 |
| ildikov | it looks like a good overview of what the team is tracking throughout the release cycle | 15:47 |
| ildikov | gives the opportunity to do a bit of project management, but without being too heavy on the tooling | 15:48 |
| 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:48 |
| sean-k-mooney | its useful wehn lookign for cycle highlights or releasenotes too | 15:49 |
| sean-k-mooney | that why we have the complete bugs and features section | 15:49 |
| sean-k-mooney | you dont need ot have your review listed on the eptherpad for it to get reviewed or merged | 15:50 |
| sean-k-mooney | it just help publicise it so its simpler for reviewers to find | 15:50 |
| ildikov | I love that! | 15:52 |
| ildikov | sometimes it's hard to fish for cycle highlights, etc, so it's nice y'all have the pointers in the etherpad | 15:52 |
| ildikov | I have a meeting coming up, so will step away from IRC a bit | 15:53 |
| ildikov | I don't know enough about the processes to update the contributor docs myself | 15:53 |
| ildikov | what other ways can I help to make improvements and help new and casual contributors looking into Nova? | 15:54 |
| 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:57 |
| 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:58 |
| 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 | 15:59 |
| 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 |
| ildikov | sean-k-mooney: thank you for the nice chat and the guidance! | 16:00 |
| sean-k-mooney | no worries, enjoy your meeting :P | 16:00 |
| sean-k-mooney | ill revert https://review.opendev.org/c/openstack/project-config/+/787523 in the interim | 16:01 |
| 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:02 |
| bauzas | ildikov: sean-k-mooney : sorry I was awfully busy those days (and I don't wanna speak about last weeks-months) | 16:29 |
| bauzas | that's still a TODO on myself to rejuvanate the docs but I'll try to make it soon as I can | 16:29 |
| ildikov | bauzas: no worries | 16:52 |
| 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:52 |
| ildikov | bauzas: is it helpful to you if I create the docs bug that we talked about with Sean earlier? | 16:53 |
| 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 | 16:57 |
| opendevreview | Merged openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits https://review.opendev.org/c/openstack/nova/+/924110 | 17:13 |
| sean-k-mooney | is the wsgi app that is reloading | 17:15 |
| melwitt | you're saying the wsgi app is reloading? | 17:22 |
| sean-k-mooney | i was asking if it was | 17:24 |
| sean-k-mooney | so is it not exeitign becuase its failign but reloading on a new request ectra | 17:25 |
| sean-k-mooney | for example if you run it under nova-api console script it proably will exit like the other console scripts | 17:25 |
| melwitt | I wonder if this is a matter of wsgi app config like "exit-on-reload = false" | 17:26 |
| melwitt | yes I believe so | 17:27 |
| sean-k-mooney | melwitt: so to me that past loks like the app exited | 17:28 |
| sean-k-mooney | bhttps://paste.openstack.org/show/b7s0zWslkXznihw1Y3yB/ | 17:28 |
| sean-k-mooney | but i woudl guess apache/uwsgi will try and reload it on the next request | 17:28 |
| melwitt | yeah ... so why the process stays? I don't know much about this stuff | 17:28 |
| melwitt | oh | 17:28 |
| sean-k-mooney | which process is staying | 17:28 |
| sean-k-mooney | we have 2 apache and then uwsign behind it | 17:28 |
| melwitt | nova-apiuWSGI master and the workers | 17:29 |
| melwitt | nova-apiuWSGI worker 1 nova-apiuWSGI worker 2 nova-apiuWSGI worker 3 | 17:29 |
| sean-k-mooney | so i think those are the python interpreteres | 17:30 |
| sean-k-mooney | that will be used to load the app on requets | 17:30 |
| melwitt | yeah.. but we would want the interpreter to exit if the config raises ValueError or no? | 17:31 |
| sean-k-mooney | i think that is the same behaivor we have for any other early check | 17:42 |
| sean-k-mooney | so to me this is not unexpected | 17:42 |
| melwitt | ok. yeah I'm slowly realizing this too | 17:43 |
| sean-k-mooney | we may even have a exisitng "bug" for that as this feels vagly like familar ground | 17:43 |
| melwitt | I was concerned if the app failing to load but the interpreter continues to run would cause any problems for an operator knowing that nova-api did not start properly or what | 17:43 |
| sean-k-mooney | so it may | 17:44 |
| sean-k-mooney | what is the status of the systemd service | 17:44 |
| melwitt | it still says active and running :\ | 17:44 |
| sean-k-mooney | (when i say it may i think this is already the case) | 17:44 |
| * melwitt nods | 17:45 | |
| sean-k-mooney | ack so without a real healthcheck i dont think this woudl be visable | 17:45 |
| sean-k-mooney | but i woudl assuem the micro version endpoint does not work | 17:45 |
| sean-k-mooney | so if you were actully monitoring the api by calling it | 17:45 |
| sean-k-mooney | then you would see it as down | 17:45 |
| sean-k-mooney | proably with a 503 | 17:45 |
| melwitt | yeah, that makes sense | 17:46 |
| melwitt | yeah when I try to curl GET it hangs for a little bit then returns 500 | 17:49 |
| sean-k-mooney | ack ok i was not sure if it would be a 500 or 503 | 17:50 |
| melwitt | ok, so it sounds like there isn't more to do (in that this is a universal thing across the board that we have not created a way to deal with) | 17:52 |
| sean-k-mooney | https://uwsgi-docs.readthedocs.io/en/latest/articles/TheArtOfGracefulReloading.html#preforking-vs-lazy-apps-vs-lazy | 17:52 |
| sean-k-mooney | so i think this is also relevent | 17:52 |
| sean-k-mooney | no i dont thik there is anything we can do | 17:52 |
| melwitt | "lazy is discouraged!" | 17:53 |
| sean-k-mooney | there might be a uwsgi option like you said to make it exit | 17:53 |
| melwitt | in our config lazy-apps = true heh | 17:53 |
| sean-k-mooney | lol | 17:53 |
| melwitt | yeah I found some things while googling like the lazy-apps setting, need-app setting, etc | 17:53 |
| sean-k-mooney | oh so lazy not lazy-app is discussraged | 17:53 |
| sean-k-mooney | """Remember: lazy-apps is different from lazy, the first one only instructs uWSGI to load the application one time per worker, while the second is more invasive (and generally discouraged) as it changes a lot of internal defaults.""" | 17:54 |
| melwitt | oh ok | 17:54 |
| sean-k-mooney | so we are not using lazy so its fine | 17:54 |
| sean-k-mooney | but also this si configurable by the deployer | 17:55 |
| sean-k-mooney | so they can make there own choices | 17:55 |
| melwitt | I see | 17:55 |
| sean-k-mooney | melwitt: the lifecycle under appache is also differnt | 17:55 |
| sean-k-mooney | i.e. mod_wsgi | 17:55 |
| melwitt | that makes sense | 17:55 |
| sean-k-mooney | in devstack we run the applicaiton under uwsgin and use apache mod_proxy to allow us to enabel tls | 17:56 |
| sean-k-mooney | we shoudl change to "Zerg mode¶" just because i like the name | 17:57 |
| sean-k-mooney | it even brings topics liek "The Zerg Dance" | 17:58 |
| melwitt | oh yeah, that has to be good right | 17:58 |
| sean-k-mooney | im not a starcraft person but a zerg rush is a thing. it totally cant be bad in any way | 17:59 |
| melwitt | I'm not either but I do what the zerg rush is | 17:59 |
| melwitt | haha yeah | 17:59 |
| sean-k-mooney | i mean the pros secation specaks for its self "potentially the silver bullet" | 18:00 |
| melwitt | lol | 18:00 |
| sean-k-mooney | we never get to have those and shuold embrace them when they happen | 18:00 |
| sean-k-mooney | this is why software will never help with the warewolfe apocalapes | 18:01 |
| melwitt | 😆 | 18:01 |
| melwitt | only because of this | 18:02 |
| sean-k-mooney | its ironic becase most software engineers are clearly vampires, outside what is that :) | 18:03 |
| sean-k-mooney | ok im goign to get somethign to drink and ill see if i can review your chanage when i get back | 18:03 |
| melwitt | haha yeah | 18:04 |
| melwitt | kk | 18:05 |
| melwitt | bleh, recheck is already going to fail with a couple of rando errors | 18:07 |
| melwitt | NoValidHost and urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='200.225.47.58', port=443): Read timed out. (read timeout=90) | 18:09 |
| sean-k-mooney | thats presumable the placement call | 18:29 |
| sean-k-mooney | melwitt: instead of recheckign it hit the rebase button | 18:29 |
| sean-k-mooney | that will create a new revisison and kick the jobs out of the queue automatiically | 18:30 |
| opendevreview | Merged openstack/placement master: Drop db migration tool https://review.opendev.org/c/openstack/placement/+/932324 | 18:48 |
| yosef | sean-k-mooney: I dont get the by design part, would it create inconsistency if we add a command or an api to re-sync to the changed flavor? | 19:06 |
| sean-k-mooney | yosef: yes, so flavor are ment to be immutable | 19:08 |
| sean-k-mooney | the only reason you can change the extra specs is to allow you to create it adn add them wihtout doing it with a single command | 19:08 |
| sean-k-mooney | but once they are used the expectation is that you will not modify them | 19:08 |
| opendevreview | Merged openstack/nova master: Amend ShareMappingStatus due to asynchronous call https://review.opendev.org/c/openstack/nova/+/908864 | 19:08 |
| opendevreview | Merged openstack/nova master: Amend DB model add a unique constraint. https://review.opendev.org/c/openstack/nova/+/912518 | 19:09 |
| sean-k-mooney | yosef: the intented workflow is you create new flavor and retire the old one when you need to make changes | 19:09 |
| yosef | sean-k-mooney: we have libvirt network and qos quotas as legacy on our production with thosands of VMs, we are migrating to new neutron qos api by changing database by raw sql queries, as we can not resize every one and take down time, I thought if we could add something so anybody else would have a simpler migration | 19:12 |
| sean-k-mooney | its somethign that can be discssed nad could be done, but it would still be considerd bad pratice | 19:13 |
| sean-k-mooney | that does not mean it cant be facilated in a more graceful way | 19:14 |
| sean-k-mooney | unst that its a get our of jail card rather then how you should plan to operate yoru cloud on a day to day basis | 19:14 |
| yosef | Yep that is the end of discussion, I wanted to know if it is a good Idea and an issue I could contribute on, we have almost done on our migration... | 19:18 |
| sean-k-mooney | it can cause issue withthe exisitng instnace. i.e. if you change some parmaters the curent placmenet if the isntance may become inviald based on the other factors consitred by the schduler | 19:27 |
| sean-k-mooney | also if you dont do it correctly and update both the request spec and the copy in the cell db in the instance_extra table to have the same content then that will cause issues | 19:28 |
| sean-k-mooney | yosef: your not the first operator to do this however | 19:28 |
| sean-k-mooney | o/ night folks | 21:55 |
| opendevreview | melanie witt proposed openstack/nova master: WIP Retry _schedule if AllocationUpdatedFailed https://review.opendev.org/c/openstack/nova/+/935988 | 23:02 |
| ildikov | sean-k-mooney: bauzas: here's the bug report for the contributor docs updates: https://bugs.launchpad.net/nova/+bug/2089325 | 23:50 |
| sean-k-mooney | looks valid to me. interesting template i assuem that is used elsewhere | 23:51 |
| ildikov | sean-k-mooney: Thanks for checking! I just used the template LP gave me :) | 23:52 |
| sean-k-mooney | ah ok | 23:52 |
| sean-k-mooney | im not sure where that came from since this is our actul bug template https://paste.opendev.org/show/beOBq5Zm0gwkM9qRH0LW/ | 23:53 |
| ildikov | sean-k-mooney: I opened LP through the little bug icon in the top right corner of the docs. I think it might be specific to doc bugs? | 23:54 |
| sean-k-mooney | ah ok that is coming form the openstack docs theme then | 23:55 |
| sean-k-mooney | rather then form what we have configured on launchpad | 23:55 |
| sean-k-mooney | its fine either way | 23:55 |
| sean-k-mooney | most peopel ignow the bug text anyway :) | 23:55 |
| ildikov | I would assume so, I intentionally did not change the template I got, as I assumed that wherever it's coming from, it's there for a reason | 23:56 |
| ildikov | lol, I bet | 23:56 |
| ildikov | I used to be a core reviewer a long time ago, so I try my best to create decent bug reports :) | 23:57 |
| sean-k-mooney | its more actionable then a lot of the ones we get so you have not lost your touch | 23:57 |
| ildikov | thank you :) | 23:58 |
| sean-k-mooney | https://bugs.launchpad.net/nova/+bug/2085585 is a particallay fine example | 23:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!