registry team mailing list archive

[Ryan Lucio <658762@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I updated to HOL this morning, 10/11.  Using my previous test config:

rlucio@box3:/etc/nova$ cat nova-network.conf
--networks_path=/var/lib/nova/networks
--logfile=/var/log/nova/nova-network.log
--sql_connection=mysql://root:nova@192.168.0.63/nova
--dhcpbridge=/usr/bin/nova-dhcpbridge
--s3_host=192.168.0.63
--rabbit_host=192.168.0.63
--redis_host=127.0.0.1
--verbose
--cc_host=192.168.0.63
--flat_network=true
--flat_network_gateway=192.168.2.1
--flat_network_netmask=255.255.255.0
--flat_network_network=192.168.2.0
--flat_network_ips=192.168.2.220,192.168.2.221,192.168.2.222
--flat_network_bridge=br0
--flat_network_broadcast=192.168.2.255

I was getting instances launching with 10.0.0.X addresses.  I took a
quick look at the flags in nova/network/manager.py and saw that there
was a new flag for a private IP range.  I updated my file to include the
private_range flag in place of the flat_network_ips flag and restarted
the nova-network daemon:

--private_range=192.168.2.64/26

However I still get my instances being allocated with the default ip
range:

rlucio@box3:/etc/nova$ euca-describe-instances
RESERVATION     r-n6mq4b6o      admin
INSTANCE        i-powbiy        ami-t9yxzfpy    10.0.0.12       10.0.0.12       scheduling      None (admin, None)      0               m1.small        2010-10-11 21:49:59
RESERVATION     r-9zf556s9      admin
INSTANCE        i-h4pzd0        ami-t9yxzfpy    10.0.0.7        10.0.0.7        shutdown        None (admin, p2n1)      0               m1.small        2010-10-08 22:05:41

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

- I updated to HOL this morning, 10/11.  Using my previous config:
+ I updated to HOL this morning, 10/11.  Using my previous test config:
  
- rlucio@box3:/etc/nova$ cat nova-network.conf 
+ rlucio@box3:/etc/nova$ cat nova-network.conf
  --networks_path=/var/lib/nova/networks
  --logfile=/var/log/nova/nova-network.log
  --sql_connection=mysql://root:nova@192.168.0.63/nova
  --dhcpbridge=/usr/bin/nova-dhcpbridge
  --s3_host=192.168.0.63
  --rabbit_host=192.168.0.63
  --redis_host=127.0.0.1
  --verbose
  --cc_host=192.168.0.63
  --flat_network=true
  --flat_network_gateway=192.168.2.1
  --flat_network_netmask=255.255.255.0
  --flat_network_network=192.168.2.0
+ --flat_network_ips=192.168.2.220,192.168.2.221,192.168.2.222
  --flat_network_bridge=br0
  --flat_network_broadcast=192.168.2.255
  
  I was getting instances launching with 10.0.0.X addresses.  I took a
  quick look at the flags in nova/network/manager.py and saw that there
  was a new flag for a private IP range.  I updated my file to include the
- following and restarted the nova-network daemon:
+ private_range flag in place of the flat_network_ips flag and restarted
+ the nova-network daemon:
  
  --private_range=192.168.2.64/26
  
  However I still get my instances being allocated with the default ip
  range:
  
- rlucio@box3:/etc/nova$ euca-describe-instances 
+ rlucio@box3:/etc/nova$ euca-describe-instances
  RESERVATION     r-n6mq4b6o      admin
  INSTANCE        i-powbiy        ami-t9yxzfpy    10.0.0.12       10.0.0.12       scheduling      None (admin, None)      0               m1.small        2010-10-11 21:49:59
  RESERVATION     r-9zf556s9      admin
  INSTANCE        i-h4pzd0        ami-t9yxzfpy    10.0.0.7        10.0.0.7        shutdown        None (admin, p2n1)      0               m1.small        2010-10-08 22:05:41

-- 
nova flat networking will not accept non-default ips
https://bugs.launchpad.net/bugs/658762
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.