1. devstack
  2. Commit 27c06950cda2e4efc49325546f580af2be1d6aef
Browse code

Deprecate use of fixed_range flag in nova conf

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

mathrock authored on 2013/03/13 13:23:18
Showing 1 changed files
lib/nova
History View file @ 27c0695
... ... 
@@ -371,7 +371,7 @@ function create_nova_conf() {
371 371 
     iniset $NOVA_CONF DEFAULT compute_scheduler_driver "$SCHEDULER"
372 372 
     iniset $NOVA_CONF DEFAULT dhcpbridge_flagfile "$NOVA_CONF"
373 373 
     iniset $NOVA_CONF DEFAULT force_dhcp_release "True"
374 
-    iniset $NOVA_CONF DEFAULT fixed_range "$FIXED_RANGE"
374 
+    iniset $NOVA_CONF DEFAULT fixed_range ""
375 375 
     iniset $NOVA_CONF DEFAULT default_floating_pool "$PUBLIC_NETWORK_NAME"
376 376 
     iniset $NOVA_CONF DEFAULT s3_host "$SERVICE_HOST"
377 377 
     iniset $NOVA_CONF DEFAULT s3_port "$S3_SERVICE_PORT"