Bug 1042176

Summary:	[RFE][heat]: Configuration option to include/exclude resource registration
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-heat	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	markmc, mlopes, sbaker, sdake, shardy, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/heat/+spec/exclude-resources-option
Whiteboard:	upstream_milestone_icehouse-1 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	This enhancement allows the exclusion of certain resources from appearing in the default list. Cloud providers may not want certain resources to be loaded, for example, those in the AWS namespace. As a result, specified resources are not loaded by the cloud environment.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-22 19:08:59 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-12 21:16:55 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/exclude-resources-option.

Description:

Currently when heat engine starts, all the in-tree resources get registered by default.
There should be an option to exclude some resource registration. For example, some cloud provider might not want to expose some cloud resources through heat orchestration.
(Please ignore/close this blueprint if this does not look like a valid scenario)

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:47:49 UTC

Moving to POST based on upstream status (Implemented).