Bug 1042565

Summary:	[RFE][neutron]: Extending LBaaS functionality using a "template" engine
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/lbaas-template-engine
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:20:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-13 00:22:25 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/lbaas-template-engine.

Description:

Eugene, has proposed a generic mechanism to allow vendors to extend the basic **aaS mechanism.
We would like to use this capability and implement a "declarative" template mechanism in which additional parameters and "features" on top of the basic model can be exposed by vendor's driver such that it can be "consumed" by Horizon and the API.

Specification URL (additional information):

None