allow_resize_to_same_host=true should be the default

Bug #1251266 reported by Yogev Rabl on 2013-11-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

The flag allow_resize_to_same_host in the nova.conf file is set to 'false' as default. Thus, the the command 'nova resize <instance uuid>' will fail.
The function this flag offers doesn't rise any vulnerability in the system, but gives the freedom to the user to change the flavor of an instance.

There's no logic in create a functionality just to not give it in the default configuration.

affects: cinder → nova
Ray Chen (chenrano2002) wrote :

nova reize <instance uuid> with NO flavor ID mean it's going to do migration.

so you need to anable both allow_resize_to_same_host and allow_migrate_to_same_host to True in nova.conf

Andrew Laski (alaski) wrote :

I have used the resize command successfully on different deployments where allow_resize_to_same_host is False. So I would be interested in what setup you're having trouble with.

The default has worked well for a number of deployments and there will need to be a strong reason for changing it.

Changed in nova:
status: New → Confirmed
importance: Undecided → Wishlist
Liyingjun (liyingjun) wrote :

When there is an all in one deployment, we must define allow_resize_to_same_host=True in nova.conf, if we want to resize an instance. So i think make the default value to True is useful for end user.

Changed in nova:
assignee: nobody → Liyingjun (liyingjun)
Changed in nova:
status: Confirmed → In Progress

Change abandoned by Li Yingjun (<email address hidden>) on branch: master

Sean Dague (sdague) wrote :

This flag exists solely for all in one testing, and is not intended to be used on a real deployment.

Changed in nova:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers