On Mon, 6 May 2019, Dan Smith wrote:
Still nova might want to fix this placement data inconsistency. I guess the new placement microversion will allow to update the consumer type of an allocation.
Yeah, I think this has to be updated from Nova. I (and I imagine others) would like to avoid making the type field optional in the API. So maybe default the value to something like "incomplete" or "unknown" and then let nova correct this naturally for instances on host startup and migrations on complete/revert. Ideally nova will be one one of the users that wants to depend on the type string, so we want to use our knowledge of which is which to get existing allocations updated so we can depend on the type value later.
Ah, okay, good. If something like "unknown" is workable I think that's much much better than defaulting to instance. Thanks.