'nova-manage network create ...' populates incorrect data in database

Network create tries to split up whatever you put in the private range by the network_size. The problem is that you are putting in 14 for network_size. If you want to use the full /28, use /28 1 16. In fact don't ever use non-power of twos for network size. If you want to reserve some ips, then create the network and manually set the reserved flag on some of the addresses.

Vish

On Feb 7, 2011, at 8:52 PM, Wayne A. Walls wrote:

> Public bug reported:
>
> ---Background---
> OS: Ubuntu 10.04 LTS
> Nova: 2011.2~bzr650-0ubuntu0ppa1~lucid1
> FlatManager
> mySQL DB
> -----------------------
>
> When running the 'nova-manage network create ..." command, I always get
> a CIDR that is +1 from the one that I originally entered, e.g.
>
> /usr/bin/python /usr/bin/nova-manage network create 184.106.73.80/28 1
> 14
>
> -----enters into mySQL-----
>
> mysql> select * from networks\G
> *************************** 1. row ***************************
> created_at: 2011-02-08 04:26:29
> updated_at: 2011-02-08 04:26:30
> deleted_at: NULL
> deleted: 0
> id: 1
> injected: 0
> cidr: 184.106.73.80/29
> netmask: 255.255.255.248
> bridge: br100
> gateway: 184.106.73.81
> broadcast: 184.106.73.87
> dns: NULL
> vlan: NULL
> vpn_public_address: NULL
> vpn_public_port: NULL
> vpn_private_address: NULL
> dhcp_start: 184.106.73.82
> project_id: wayneproject
> host: NULL
> cidr_v6: NULL
> ra_server: NULL
> 1 row in set (0.00 sec)
>
> #####
>
> There are a couple of issues that arise from this:
>
> A) I have to manually go in and set my CIDR, netmask, broadcast, and
> gateway (from what I can tell whatever network you create nova-manage
> assume the first two IPs are the network and gateway IP). This is fine
> in some cases, but I've found myself having to set my gateway manually
> almost every time.
>
> B) This also causes a problem with 'nova.fixed_ips', as my available
> IPs are now from a /29 block, and not a /28.
>
> C) Networking is totally broke due to this, and requires all these
> changes in order to reach any instances that are spun up.
>
> This doesn't keep Nova from running, it just makes configuration a bit
> more difficult from the networking perspective.
>
>
> Apologies in advance if this is already a known issue, I couldn't find any references so I thought I'd submit a new bug...
>
> cheers
>
> ** Affects: nova
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/714986
>
> Title:
> 'nova-manage network create ...' populates incorrect data in database
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> ---Background---
> OS: Ubuntu 10.04 LTS
> Nova: 2011.2~bzr650-0ubuntu0ppa1~lucid1
> FlatManager
> mySQL DB
> -----------------------
>
> When running the 'nova-manage network create ..." command, I always
> get a CIDR that is +1 from the...

Nice, thanks for the clarification on this, Vish! I'll be sure to fill out the entire range I plan to use per project to get past this ;)

cheers

Closing as Invalid, please reopen if I read the story wrong.