[openstack-dev] [heat][horizon] Backward-incompatible changes to the Neutron API
Paul Michali
pc at michali.net
Thu Aug 27 01:02:27 UTC 2015
For details on the API/resource change, see the developer's reference
document that is under review: https://review.openstack.org/#/c/191944/
There is a section at the end, where I'm proposing a possible way to
support both versions of the API and provide backward compatibility. Feel
free to comment on the review.
Regards,
Paul Michali (pc_m)
On Wed, Aug 26, 2015 at 6:10 PM James Dempsey <jamesd at catalyst.net.nz>
wrote:
> Greetings Heat/Horizon Devs,
>
> There is some talk about possibly backward-incompatible changes to the
> Neutron VPNaaS API and I'd like to better understand what that means for
> Heat and Horizon.
>
> It has been proposed to change Neutron VPNService objects such that they
> reference a new resource type called an "Endpoint Group" instead of
> simply a Subnet.
>
> Does this mean that any version of Heat/Horizon would only be able to
> support either the old or new Neutron API, or is there some way to allow
> a version of Heat/Horizon to support both?
>
>
> Thanks,
> James
>
> --
> James Dempsey
> Senior Cloud Engineer
> Catalyst IT Limited
> +64 4 803 2264
> --
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150827/dd64ea7d/attachment.html>
More information about the OpenStack-dev
mailing list