On Sat, Oct 27, 2018 at 10:08 PM Gary Kotton wrote:
> Hi,
>
> Does heat support os-compute-api-version? Say for example I am using
> queens but have a use case via heat that requires a API parameter that was
> capped in the 2.56
>
There isn't a way to specify compute microversion in the template.
Till queens, heat client plugin for nova was using the base api version[1],
unless a specific feature/property requires a higher mircoversion[2]. So
features capped in newer api versions should be usable without any change.
However, we moved to use the "max api microversion supported" as the
default[3] since rocky to support new features without much changes and not
to have too many versioned clients. As a side-effect, features/properties
capped by new nova api microversions can't be used any more.
We probably have to look for a better way to handle this in the future.
[1]
https://github.com/openstack/heat/blob/stable/queens/heat/engine/clients/os/nova.py#L61
[2]
https://github.com/openstack/heat/blob/stable/queens/heat/engine/resources/openstack/nova/server.py#L838
[3]
https://github.com/openstack/heat/blob/stable/rocky/heat/engine/clients/os/nova.py#L100
> microversion.
>
> Thanks
>
> Gary
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Regards,
Rabi Mishra
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev