Open Stack

On 4/1/2019 9:39 AM, Massimo Sgaravatto wrote:
> Is this the case also if the extra_specs field attribute was set for the 
> flavor and the AggregateInstanceExtraSpecsFilter filter is used ?
> Aren't there problems rescheduling an instance created with that flavor ?

Rescheduling uses the RequestSpec, which contains a copy of the Flavor 
from the last resize or when the server was initially created. The 
RequestSpec is around for the lifetime of the instance, so you can 
delete the original flavor and still reschedule.

Now if you created a server or resized a server with a given flavor, and 
then modified that flavors extra_specs, that won't be reflected back in 
the persisted RequestSpec, but it's probably not a great idea in general 
to modify extra_specs on public flavors which are already being used.

-- 

Thanks,

Matt