Open Stack

On Wed, 26 Jun 2019 at 12:20, Kumari, Madhuri <madhuri.kumari at intel.com> wrote:
>
> Hi Mark,
>
>
> >>-----Original Message-----
> >>From: Mark Goddard [mailto:mark at stackhpc.com]
>
>
> >>Hmm, I hadn't realised it would be quite this restricted. Although this could
> >>make it work, it does seem to be baking more ironic specifics into nova.
> >>
> >>There is an issue of standardisation here. Currently we do not have standard
> >>traits to describe these things, instead we use custom traits. The reason for
> >>this has been discussed earlier in this thread, essentially that we need to
> >>encode configuration key and value into the trait, and use the lack of a trait
> >>as 'don't care'. We did briefly discuss an alternative approach, but we're a
> >>fair way off having that.
>
> I think the issue of standardization is not related to the specific use case we are discussing here. It applies to the current state of ironic virt driver as well as you said.
> The idea of using the flavor metadata can fix this but that’s in itself another piece of work.

That's not quite true. Currently we don't specify any trait values for
deploy templates anywhere in nova or ironic. They're entirely defined
by the operator (as are the deploy templates that reference them).
This would need to become standard if we're to add it to code.

>
> Regards,
> Madhuri