Earlier  
Posted Nick Remark
#openstack-nova - 2024-11-21
17:53:04 melwitt "lazy is discouraged!"
17:53:08 sean-k-mooney there might be a uwsgi option like you said to make it exit
17:53:16 melwitt in our config lazy-apps = true heh
17:53:24 sean-k-mooney lol
17:53:37 melwitt yeah I found some things while googling like the lazy-apps setting, need-app setting, etc
17:53:59 sean-k-mooney oh so lazy not lazy-app is discussraged
17:54:21 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:53 melwitt oh ok
17:54:58 sean-k-mooney so we are not using lazy so its fine
17:55:12 sean-k-mooney but also this si configurable by the deployer
17:55:17 sean-k-mooney so they can make there own choices
17:55:27 melwitt I see
17:55:30 sean-k-mooney melwitt: the lifecycle under appache is also differnt
17:55:36 sean-k-mooney i.e. mod_wsgi
17:55:56 melwitt that makes sense
17:56:12 sean-k-mooney in devstack we run the applicaiton under uwsgin and use apache mod_proxy to allow us to enabel tls
17:57:56 sean-k-mooney we shoudl change to "Zerg mode¶" just because i like the name
17:58:19 sean-k-mooney it even brings topics liek "The Zerg Dance"
17:58:31 melwitt oh yeah, that has to be good right
17:59:08 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:30 melwitt I'm not either but I do what the zerg rush is
17:59:58 melwitt haha yeah
18:00:27 sean-k-mooney i mean the pros secation specaks for its self "potentially the silver bullet"
18:00:41 melwitt lol
18:00:46 sean-k-mooney we never get to have those and shuold embrace them when they happen
18:01:30 sean-k-mooney this is why software will never help with the warewolfe apocalapes
18:01:43 melwitt 😆
18:02:30 melwitt only because of this
18:03:03 sean-k-mooney its ironic becase most software engineers are clearly vampires, outside what is that :)
18:03:51 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:04:40 melwitt haha yeah
18:05:16 melwitt kk
18:07:19 melwitt bleh, recheck is already going to fail with a couple of rando errors
18:09:36 melwitt NoValidHost and urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='200.225.47.58', port=443): Read timed out. (read timeout=90)
18:29:31 sean-k-mooney thats presumable the placement call
18:29:41 sean-k-mooney melwitt: instead of recheckign it hit the rebase button
18:30:35 sean-k-mooney that will create a new revisison and kick the jobs out of the queue automatiically
18:48:31 opendevreview Merged openstack/placement master: Drop db migration tool https://review.opendev.org/c/openstack/placement/+/932324
19:06:06 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:08:10 sean-k-mooney yosef: yes, so flavor are ment to be immutable
19:08:34 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:51 sean-k-mooney but once they are used the expectation is that you will not modify them
19:08:55 opendevreview Merged openstack/nova master: Amend ShareMappingStatus due to asynchronous call https://review.opendev.org/c/openstack/nova/+/908864
19:09:05 opendevreview Merged openstack/nova master: Amend DB model add a unique constraint. https://review.opendev.org/c/openstack/nova/+/912518
19:09:14 sean-k-mooney yosef: the intented workflow is you create new flavor and retire the old one when you need to make changes
19:12:52 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:13:50 sean-k-mooney its somethign that can be discssed nad could be done, but it would still be considerd bad pratice
19:14:06 sean-k-mooney that does not mean it cant be facilated in a more graceful way
19:14:37 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:18:11 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:27:51 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:28:30 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:50 sean-k-mooney yosef: your not the first operator to do this however
21:55:23 sean-k-mooney o/ night folks
23:02:45 opendevreview melanie witt proposed openstack/nova master: WIP Retry _schedule if AllocationUpdatedFailed https://review.opendev.org/c/openstack/nova/+/935988
23:50:04 ildikov sean-k-mooney: bauzas: here's the bug report for the contributor docs updates: https://bugs.launchpad.net/nova/+bug/2089325
23:51:35 sean-k-mooney looks valid to me. interesting template i assuem that is used elsewhere
23:52:18 ildikov sean-k-mooney: Thanks for checking! I just used the template LP gave me :)
23:52:31 sean-k-mooney ah ok
23:53:44 sean-k-mooney im not sure where that came from since this is our actul bug template https://paste.opendev.org/show/beOBq5Zm0gwkM9qRH0LW/
23:54:55 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:55:20 sean-k-mooney ah ok that is coming form the openstack docs theme then
23:55:33 sean-k-mooney rather then form what we have configured on launchpad
23:55:39 sean-k-mooney its fine either way
23:55:50 sean-k-mooney most peopel ignow the bug text anyway :)
23:56:20 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:32 ildikov lol, I bet
23:57:04 ildikov I used to be a core reviewer a long time ago, so I try my best to create decent bug reports :)
23:57:40 sean-k-mooney its more actionable then a lot of the ones we get so you have not lost your touch
23:58:12 ildikov thank you :)
23:59:46 sean-k-mooney https://bugs.launchpad.net/nova/+bug/2085585 is a particallay fine example
#openstack-nova - 2024-11-22
00:01:43 ildikov lol, wow
00:02:37 ildikov there's technically no usable information in that one
00:03:28 sean-k-mooney i was hopign it was a duplicate of https://bugs.launchpad.net/nova/+bug/2088341 since it has the same title but that is fileed by someone else
00:05:50 ildikov I mean, with the amount of information in the first one, saying it's a duplicate is just as accurate as saying it's not
00:06:14 ildikov maybe the two people know each other and worked smh together :)
00:07:34 sean-k-mooney i think they just took oru generic api error header too litrally
00:07:37 sean-k-mooney "Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible."
00:08:20 sean-k-mooney some other software project put an identifyer that allows them to track wehre the issue came form in messages like that
00:08:24 s3rj1k reporter fact-proved that "Unexpected API Error" exists
00:09:13 sean-k-mooney hopefully there issue either went away or they cna come back and tell us a littel more
00:09:29 sean-k-mooney anywya im going to drop again for the night o/
00:12:53 ildikov ah, I see
00:13:09 ildikov I have my fingers crossed they'll come back if the issue persists!
00:13:20 ildikov thanks again for checking my bug report!
00:13:25 ildikov good night!
02:19:14 opendevreview melanie witt proposed openstack/nova master: Add [quota]unified_limits_resource_(strategy|list) https://review.opendev.org/c/openstack/nova/+/924025
09:07:30 tkajinam bauzas, hi could you check https://review.opendev.org/c/openstack/releases/+/935892 when you have time ?
09:09:44 bauzas tkajinam: just did
09:21:40 tkajinam bauzas, thanks 1
09:21:42 tkajinam !
09:48:33 opendevreview renliang proposed openstack/nova master: Update documentation link for openSUSE index. https://review.opendev.org/c/openstack/nova/+/927705
12:37:42 stephenfin gmann: Thanks for the very thorough review on https://review.opendev.org/c/openstack/nova/+/915743 That must have taken you a while. I appreciate it and will respin quickly 🙏
12:38:51 ratailor bauzas, sean-k-mooney could you please check https://review.opendev.org/c/openstack/nova/+/934294 https://review.opendev.org/c/openstack/nova/+/873901
12:42:24 ratailor gibi, could you please check this https://review.opendev.org/c/openstack/nova/+/927732 its clean cherry-pick and required 1 more +2.
12:47:14 gibi ratailor: done
12:47:58 ratailor gibi, Thanks!
12:50:10 ratailor gibi, also is this approach looks good. WDYT https://review.opendev.org/c/openstack/nova/+/933107
14:06:57 s3rj1k sean-k-mooney: can you please take a look at https://bugs.launchpad.net/nova/+bug/2089386 when you have time, thanks
14:08:20 sean-k-mooney s3rj1k: so we dont really recomemnt usign the periodic in production

Earlier   Later