Open Stack

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 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?
> 
In the past, Horizon worked cross releases.

The way horizon works is, it looks out for a networking endpoint in
keystone catalog. We don't really care, if it's nova or neutron
answering. The rest should be discoverable via API.
Horizon uses neutronclient rather than directly talking to neutron by
using its API interface.

If you make it discoverable, and you'd add that to neutronclient,
horizon could support both.

Matthias