Open Stack

On Mon, May 6, 2019 at 5:51 PM Chris Dent <cdent+os at anticdent.org> wrote:

> 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.
>


okay, the spec will take this approach then.

Regards,
Surya.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190508/97ccfa59/attachment.html>