[Nova][Ironic] Reset Configurations in Baremetals Post Provisioning

Jay Pipes jaypipes at gmail.com
Thu Jun 6 15:36:59 UTC 2019


On 6/6/19 11:19 AM, Kumari, Madhuri wrote:
> In this case, the trait is stored with flavor so it is known to Nova. The new trait should be added in the database and the old one removed. For an ex:
> 
> An instance with flavor bm_hyperthreading with trait:CUSTOM_HYPERTHREADING_ON=required is created in Nova.
> Now the user wants to turn off the hyperthreading, than they could update the flavor with trait:CUSTOM_HYPERTHREADING_OFF=required.
> This should remove the trait:CUSTOM_HYPERTHREADING_ON and add trait:CUSTOM_HYPERTHREADING_OFF associated with the new flavor.

The absence of a trait on a provider should be represented by the 
provider not having a trait. Just have a single trait 
"CUSTOM_HYPERTHREADING" that you either place on the provider or do not 
place on a provider.

The flavor should then either request that the trait be present on a 
provider that the instance is scheduled to 
(trait:CUSTOM_HYPERTHREADING=required) or that the trait should *not* be 
present on a provider that the instance is scheduled to 
(trait:CUSTOM_HYPERTHREADING=forbidden).

Best,
-jay



More information about the openstack-discuss mailing list