Bug 999240 - Values in packstack are hard coded in manifests
Values in packstack are hard coded in manifests
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
2.0 (Folsom)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 4.0
Assigned To: RHOS Maint
Nir Magnezi
Depends On:
  Show dependency treegraph
Reported: 2013-08-20 22:05 EDT by james labocki
Modified: 2013-09-20 06:20 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-20 06:20:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description james labocki 2013-08-20 22:05:22 EDT
Currently in packstack there are some variables that are not exposed through switches in the packstack command. Particularly in 


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

  $floating_range            = '',

Can this be changed to allow for an option during execution of packstack?
Comment 2 Martin Magr 2013-09-20 06:20:22 EDT
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.