Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 999240

Summary:	Values in packstack are hard coded in manifests
Product:	Red Hat OpenStack	Reporter:	james labocki <jlabocki>
Component:	openstack-packstack	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0 (Folsom)	CC:	aortega, derekh, hateya, mmagr, yeylon
Target Milestone:	---
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-20 10:20:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description james labocki 2013-08-21 02:05:22 UTC

Currently in packstack there are some variables that are not exposed through switches in the packstack command. Particularly in 

/usr/lib/python2.6/site-packages/packstack/puppet/modules/openstack/manifests/provision.pp

the following value is set and cannot be changed via the packstack command during provisioning.

  $floating_range            = '172.24.4.224/28',

Can this be changed to allow for an option during execution of packstack?

Comment 2 Martin Magr 2013-09-20 10:20:22 UTC

All necessary values are filled from answer file to manifest templates by packstack. The one you are pointing to is a default value in provision class and it is indeed changed according to answer file in packstack/pupppet/templates/provision.pp line 9 (floating_range => '%(CONFIG_PROVISION_DEMO_FLOATRANGE)s',)