[nova] VM ending up in a different availability zone after resizing vm instance
VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?
On Wed, 2022-03-09 at 14:40 -0600, hai wu wrote:
VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?
if the vm was created without a AZ requested tehn when it is resized i think it can change AZ but that woudl only happen if you chagne the defautl AZ or have different AZ configured on different schedulers i think.
Is it possible to add AZ information to existing VMs (not during VM creation)? We did not configure AZ initially, so by default they are with 'nova' default zone. AZ was added on a later stage.. I don't think we have different AZ configured on different schedulers. we have to toggle host's AZ all the time in order to be able to migrate VMs around..
On Wed, Mar 9, 2022 at 5:11 PM Sean Mooney smooney@redhat.com wrote:
On Wed, 2022-03-09 at 14:40 -0600, hai wu wrote:
VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?
if the vm was created without a AZ requested tehn when it is resized i think it can change AZ but that woudl only happen if you chagne the defautl AZ or have different AZ configured on different schedulers i think.
Hello,
Didn’t you ask this recenty in thread [1] ? You have the answer there, it’s based on the request spec saved in the request_specs table in the database.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024007.ht...
On 10 Mar 2022, at 01:57, hai wu haiwu.us@gmail.com wrote:
Is it possible to add AZ information to existing VMs (not during VM creation)? We did not configure AZ initially, so by default they are with 'nova' default zone. AZ was added on a later stage.. I don't think we have different AZ configured on different schedulers. we have to toggle host's AZ all the time in order to be able to migrate VMs around..
On Wed, Mar 9, 2022 at 5:11 PM Sean Mooney smooney@redhat.com wrote:
On Wed, 2022-03-09 at 14:40 -0600, hai wu wrote:
VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?
if the vm was created without a AZ requested tehn when it is resized i think it can change AZ but that woudl only happen if you chagne the defautl AZ or have different AZ configured on different schedulers i think.
Does this mean that with request_specs populated with AZ information for each existing VM, this particular issue would never happen again later?
Also I never figured out how to use oslo_versionedobjects to update request_specs table for each existing VM. Do you have any sample code to do that?
On Thu, Mar 10, 2022 at 10:12 AM Tobias Urdin tobias.urdin@binero.com wrote:
Hello,
Didn’t you ask this recenty in thread [1] ? You have the answer there, it’s based on the request spec saved in the request_specs table in the database.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024007.ht...
On 10 Mar 2022, at 01:57, hai wu haiwu.us@gmail.com wrote:
Is it possible to add AZ information to existing VMs (not during VM creation)? We did not configure AZ initially, so by default they are with 'nova' default zone. AZ was added on a later stage.. I don't think we have different AZ configured on different schedulers. we have to toggle host's AZ all the time in order to be able to migrate VMs around..
On Wed, Mar 9, 2022 at 5:11 PM Sean Mooney smooney@redhat.com wrote:
On Wed, 2022-03-09 at 14:40 -0600, hai wu wrote:
VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?
if the vm was created without a AZ requested tehn when it is resized i think it can change AZ but that woudl only happen if you chagne the defautl AZ or have different AZ configured on different schedulers i think.
participants (3)
-
hai wu
-
Sean Mooney
-
Tobias Urdin