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 patch was presented in FWaaS to address the router/service insertion issue, however that was blocked as well. With the new blueprint process in place, the process on all of the above patches has pretty much been reset. Thanks, ~Sumit. On Fri, Apr 25, 2014 at 6:48 AM, Akihiro Motoki <mot...@da.jp.nec.com> wrote: > 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, FWaaS API does not provides a way to specify > a router which a firewall instance is applied to. > It will be addressed in the service insertion blueprint. > > Akihiro > > (2014/04/25 6:55), McCann, Jack wrote: >> 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: [openstack-dev] [neutron] status of VPNaaS and FWaaS APIs in >>> Icehouse >>> >>> >>> 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,  says "This extension is experimental for the Havana >>>> release." >>>> For FWaaS,  says "The Firewall-as-a-Service (FWaaS) API is an >>>> experimental >>> API..." >>> >>> >>> Thanks for asking. Both should still be considered experimental because of >>> the >>> multivendor work was completed in Icehouse. >>> >>> >>>>  >>>> http://docs.openstack.org/api/openstack-network/2.0/content/vpnaas_ext.html >>>>  http://docs.openstack.org/admin-guide-cloud/content/fwaas.html >>>> >>>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStackfirstname.lastname@example.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackemail@example.com >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev