Bug 999240 - Values in packstack are hard coded in manifests
Summary: Values in packstack are hard coded in manifests
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.0
Assignee: RHOS Maint
QA Contact: Nir Magnezi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 02:05 UTC by james labocki
Modified: 2013-09-20 10:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-20 10:20:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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',)
Note You need to log in before you can comment on or make changes to this bug.