Earlier  
Posted Nick Remark
#openstack-nova - 2022-03-08
17:31:50 dansmith don't make them read double the release notes, as compiled by a computer
17:32:01 dansmith bring forward the important bits (i.e. likely the content of the prelude)
17:32:06 sean-k-mooney an operator goign form tick 1 to tick 2 need to know everythign that happend in tock 1 right
17:32:20 dansmith they can read the intermediate release notes if they want, but don't just concat them
17:32:35 sean-k-mooney i guess
17:32:51 sean-k-mooney i hate having to look in mulitple places
17:32:56 gmann we can add a line in the top or so that 'to know all change from tick1->tick2 read these tock releasenotes too'
17:32:57 sean-k-mooney but you coudl do it either way
17:32:57 dansmith just MHO, but I think we're already incredibly verbose on the renos
17:33:19 sean-k-mooney dansmith: i mean perhaps prelude and upgrades section maybe
17:33:40 sean-k-mooney i guess we will figure it out
17:33:47 gmann will there be any upgrade section in tock? i mean we want to avoid those like depreaction right
17:33:59 dansmith gmann: sometimes features bring upgrade items I think
17:34:00 sean-k-mooney gmann: there should be
17:34:17 sean-k-mooney gmann: i really dont thinik we shoudl try to avoid either in a tock
17:34:22 gmann ah new feature. got it
17:34:32 sean-k-mooney if we do it will slow down devleopment
17:34:54 sean-k-mooney gmann: addin a db migraition for a new feature woudl be an upgrade impact i coudl see in a tock
17:35:05 dansmith sean-k-mooney: remember this is a compromise, some things will have to change.. hopefully less with this than the alternative
17:35:09 gmann making release notes page too verbose and long make them hard to read good things. I think link to tock releease notes in tick releasenotes should be fine
17:35:21 dansmith gmann: agree
17:35:55 sean-k-mooney dansmith: right but if we cant do db changes in a tock or rpc change for example then tha tis not a compromise
17:36:20 dansmith sean-k-mooney: as noted, I think it's totally fine to *add* things to db and rpc in tock
17:38:48 bauzas yup
17:39:00 bauzas we can rpc bump things in a tock
17:39:12 bauzas if we have rpc compat of courser
17:39:25 bauzas we can add a db upgrade script too
17:40:06 bauzas we can even remove a rpc compat on a tock release if compat was there on the previous tick
17:40:22 bauzas rpc aliases will continue to exist
17:40:31 bauzas and microversions too
17:41:18 bauzas but somehow we need to settle a couple of rules we gonna write on our contrib docs
17:41:54 bauzas that's why I want us to agree on the impacts for nova so we can write it down
17:42:27 gmann bauzas: +1.
17:43:07 gmann bauzas: sean-k-mooney added it on TC+PTL slots, L27 - https://etherpad.opendev.org/p/tc-ptl-interaction-zed
17:45:07 sean-k-mooney gmann: thanks
17:45:44 sean-k-mooney bauzas: yes we have time to figure that out before AA
17:53:24 sean-k-mooney ok im hungery so im going to grab something to eat i might be on irc later but i will likely just work on some reviews for the evning
17:53:48 opendevreview Sylvain Bauza proposed openstack/nova master: Add the Yoga prelude section https://review.opendev.org/c/openstack/nova/+/832292
17:54:07 bauzas gmann: dansmith: melwitt: sean-k-mooney: gibi: new revision for the Yoga prelude ^
17:55:46 gibi bauzas: +2 from me
17:55:53 bauzas thanks
17:55:53 gibi thanks for writing it up
17:58:13 dansmith bauzas: looks good content-wise to me, but a bunch of nit corrections
18:08:12 opendevreview ribaudr proposed openstack/python-novaclient master: Microversion 2.91: Support specifying destination host to unshelve https://review.opendev.org/c/openstack/python-novaclient/+/831651
#openstack-nova - 2022-03-09
06:55:39 ygk_12345 hi all
06:55:51 ygk_12345 can we change a flavor from public to private ?
07:08:00 ygk_12345 can we convert a private flavor to public ?
07:08:01 gibi ygk_12345: I think you cannot change it to public, but you can add tenants to the access list to see the private flavor
07:08:34 ygk_12345 gibi: ok
08:26:40 bauzas fortunately, my coffee machine has water in its tank :)
08:34:54 dmitriis gibi: o/ if you have time https://review.opendev.org/c/openstack/nova/+/829974
08:38:49 rribaud__ bauzas, hello, I hope it will be fixed soon.
08:39:10 bauzas rribaud__: hopefully :crossed_fingers!
08:40:35 kashyap bauzas: Bonjour. I have a soft -1 with a suggestion on the Yoga prelude. :)
08:40:46 rribaud__ bauzas, usually water maintenance people are reactive, that should not be long.
08:40:46 bauzas kashyap: /me looks
08:41:17 bauzas rribaud__: actually, this is fixed by the last hour but the pressure is bad
08:42:37 kashyap bauzas: No rush, just a phrasing part
08:43:56 bauzas revising it
08:46:36 bauzas kashyap: thanks for your comments, good explanation why we don't want it for production use
08:46:56 kashyap No prob
08:47:04 opendevreview Sylvain Bauza proposed openstack/nova master: Add the Yoga prelude section https://review.opendev.org/c/openstack/nova/+/832292
08:47:05 bauzas there it goes...
08:47:22 bauzas dansmith: gibi: amended the prelude based on dan's comment
08:49:52 bauzas elodilles: today and tomorrow will be busy days for merging things
08:50:13 bauzas elodilles: I guess we will only be able to amend the nova rc1 yaml by the end of our day
08:50:32 bauzas (tomorrow I mean)
08:53:33 bauzas hah, all water issues fixed, let me visit my shower :)
09:26:54 opendevreview ribaudr proposed openstack/os-traits master: Attach Manila shares via virtiofs(traits) https://review.opendev.org/c/openstack/os-traits/+/832769
09:38:37 elodilles bauzas: ack, if the patch is -1'd then the release managers won't force-approve the patch without pinging you ;)
09:38:53 bauzas yah I know
09:39:08 bauzas elodilles: but I wanted to explain we need to merge a few changes before removing the -1
09:39:18 bauzas so it would be a bit late tomorrow
09:39:25 elodilles bauzas: cool, roger :)
09:39:34 bauzas (as we need to wait for the merge)
09:39:38 opendevreview ribaudr proposed openstack/os-traits master: Add 'COMPUTE_STORAGE_VIRTIO_FS', 'COMPUTE_MEM_BACKING_FILE' https://review.opendev.org/c/openstack/os-traits/+/832769
09:39:51 elodilles i'll be around, so no problem :)
09:40:25 elodilles and thanks for the heads-up
09:41:07 bauzas elodilles: haha, https://www.youtube.com/watch?v=IC7pZSd8iRg
09:56:24 elodilles yepp, that's classic ;)
10:22:16 rribaud__ hello, question, I have modified os-trait locally. What is the best way to use it with tox (nova) ?
10:33:16 opendevreview Merged openstack/nova master: Follow up for unified limits https://review.opendev.org/c/openstack/nova/+/830918
11:27:11 ygk_12345 Folks, in which database is the nova flavor details stored ?
11:27:34 ygk_12345 for all the created flavors I mean
11:36:54 ygk_12345 any idea ?
11:40:56 rribaud__ ygk_12345, I think it is in nova_api --> flavors table
11:51:15 ygk_12345 rribaud__: thanks for the info
12:35:00 opendevreview ribaudr proposed openstack/os-traits master: Add 'COMPUTE_STORAGE_VIRTIO_FS', 'COMPUTE_MEM_BACKING_FILE' https://review.opendev.org/c/openstack/os-traits/+/832769
12:55:33 sean-k-mooney1 rribaud__: you just do .tox/py3/bin/pip install ../os-traits
12:56:04 sean-k-mooney1 so after you have created the tox env if you need a local os-traits just install it and run tox again
12:56:26 sean-k-mooney1 or run the command tox would run manuatlly
12:56:43 sean-k-mooney1 .tox/py3/bin/stestr ...
13:45:00 opendevreview Merged openstack/nova master: Adds regression test for bug LP#1944619 https://review.opendev.org/c/openstack/nova/+/821840
13:53:21 rribaud__ sean-k-mooney1, thx.
13:53:56 rribaud__ sean-k-mooney1++
14:08:33 opendevreview Alexey Stupnikov proposed openstack/nova master: Add functional tests to reproduce bug #1960412 https://review.opendev.org/c/openstack/nova/+/830010
14:17:11 opendevreview Alexey Stupnikov proposed openstack/nova master: Clean up when queued live migration aborted https://review.opendev.org/c/openstack/nova/+/828570
14:20:59 erlon bauzas: hey, in the pre_live_migration fix, what you mean with 'Can you please provide a FUP for this', to implement seans' suggestion?
14:27:13 bauzas erlon: sorry, FUP means "a follow-up patch"
14:27:37 bauzas erlon: that means I can +W this patch if you agree with providing a separate patch for modifying the reno file

Earlier   Later