The so called multivendor work is dependent now on the flavors
framework. Patches were presented in the Icehouse release to enable
multivendor support using the service-type-framework, however there
were concerns on the use of that framework, and hence those patches
were not approved in time.
A
we need to correct the previous reply.
Both should still be considered experimental because of
the multivendor work was NOT completed in Icehouse.
We can use only one service backend for each service and
there are no way to choose a backend when creating a service instance.
In addition,
On Apr 23, 2014, at 6:20 PM, McCann, Jack jack.mcc...@hp.com wrote:
Are VPNaaS and FWaaS APIs still considered experimental in Icehouse?
For VPNaaS, [1] says This extension is experimental for the Havana release.
For FWaaS, [2] says The Firewall-as-a-Service (FWaaS) API is an experimental
Thanks Mark.
What steps are necessary to promote these APIs beyond experimental?
- Jack
-Original Message-
From: Mark McClain [mailto:mmccl...@yahoo-inc.com]
Sent: Thursday, April 24, 2014 11:07 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Are VPNaaS and FWaaS APIs still considered experimental in Icehouse?
For VPNaaS, [1] says This extension is experimental for the Havana release.
For FWaaS, [2] says The Firewall-as-a-Service (FWaaS) API is an experimental
API...
Thanks,
- Jack
[1]
