Akihiro, can you look at the developer's reference I posted (191944), where
there is the overall API plan and a proposal for handling backward
compatibility.
Thanks!
Paul Michali (pc_m)
On Thu, Aug 27, 2015 at 11:12 AM Akihiro Motoki wrote:
> As Mathias said, Horizon worked (and in many cases
As Mathias said, Horizon worked (and in many cases works) cross releases.
Horizon determines supported features based on keystone catalogs,
extension list from back-end services (like nova, neutron).
Micro-versioning support may come in future (though it is not supported).
For backward incompatib
On 26/08/15 23:55, James Dempsey 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 ob
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 comme
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 cal
