openstack/devstack
Code Issues Proposed changes

Deprecate use of fixed_range flag in nova conf

Browse Source 
Since a3786b4b8aa47cf19b9dc2babb4df85f578a1280 merged into nova we
now can default to setting fixed_range in nova.conf to "". This will
cause nova to do automatic NAT set up based on the networks
configured rather than relying on the user to set fixed_range to the
largest subnet that includes the networks they've configured.

Leave the stack.sh default value of $FIXED_RANGE alone because it is
used for creating the networks, etc.

Change-Id: Iad13588af3dcf22ce81823de301b73b05cf2aae9
This commit is contained in:
mathrock 2013-03-13 00:23:18 -04:00
parent f69ce0bce5
commit 27c06950cd
1 changed files with 1 additions and 1 deletions

2
lib/nova

@ -371,7 +371,7 @@ function create_nova_conf() {
iniset $NOVA_CONF DEFAULT compute_scheduler_driver "$SCHEDULER"
iniset $NOVA_CONF DEFAULT dhcpbridge_flagfile "$NOVA_CONF"
iniset $NOVA_CONF DEFAULT force_dhcp_release "True"
iniset $NOVA_CONF DEFAULT fixed_range "$FIXED_RANGE"
iniset $NOVA_CONF DEFAULT fixed_range ""
iniset $NOVA_CONF DEFAULT default_floating_pool "$PUBLIC_NETWORK_NAME"
iniset $NOVA_CONF DEFAULT s3_host "$SERVICE_HOST"
iniset $NOVA_CONF DEFAULT s3_port "$S3_SERVICE_PORT"