Re: [Openstack] issues with fixed_range blocking new instance creation?
On Thu, Sep 6, 2012 at 9:59 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: fixed range is likely fine. I suspect you created your network with a 10.0.0.0/24 though. It might be a bit tricky to switch to a larger range now. You may have to create the rest of your fixed ips manually in the db associated with the same network and then change the cidr entry on the network in the db to 10.0.0.0/16. You also might have to manually destroy the bridges and let nova-network recreate them. That does seem to be the case, if you'd asked me 24hr ago I'd have sworn I never put /24 anywhere but that's the only explaination that fits observed reality. Luckily I haven't quite called the system production yet so I'm taking a maintenance window now, terminating all instances and deleting and recreating network Being able to expand networks more easily would be a nice thing (and in a dhcp controlled world it's not too disruptive as long as you don't go pushing the gateway address around), but best I can tell this is what I've got right now. Thanks, -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] issues with fixed_range blocking new instance creation?
Hi All, my stack stopped launching instances last night I've been chasing my tail for a while but I think it think's it's out of fixed IPs. the system is Essex as packages on Ubuntu 12.04 using FlatDHCP, with multihost and a fixed range or 10.0.0.0/16 --multi_host=True --public_interface=eth0 --fixed_range=10.0.0.0/16 --flat_interface=eth1 --flat_network_bridge=br100 --network_manager=nova.network.manager.FlatDHCPManager the error I'm seeing for all attempts at launching is: 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py, line 69, in _get_configurations 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] 'ip_address': mapping['ips'][0]['ip'], 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] IndexError: list index out of range and I just noticed that the flat network interfaces are getting /24 netmasks NOT /16 this combined with 210 running instances and forty some compute nodes make me think it's out of addresses. is my syntax for the fixed range wrong, doc give 10.0.0.0/8 as the example and default so I don't think so. I'm fine with reverting to that, don't mind more addresses, but I would like to understand if this is actually my problem and even if it's not why it's not giving the mask I asked for. -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] issues with fixed_range blocking new instance creation?
fixed range is likely fine. I suspect you created your network with a 10.0.0.0/24 though. It might be a bit tricky to switch to a larger range now. You may have to create the rest of your fixed ips manually in the db associated with the same network and then change the cidr entry on the network in the db to 10.0.0.0/16. You also might have to manually destroy the bridges and let nova-network recreate them. Vish On Sep 6, 2012, at 7:36 AM, Jonathan Proulx j...@jonproulx.com wrote: Hi All, my stack stopped launching instances last night I've been chasing my tail for a while but I think it think's it's out of fixed IPs. the system is Essex as packages on Ubuntu 12.04 using FlatDHCP, with multihost and a fixed range or 10.0.0.0/16 --multi_host=True --public_interface=eth0 --fixed_range=10.0.0.0/16 --flat_interface=eth1 --flat_network_bridge=br100 --network_manager=nova.network.manager.FlatDHCPManager the error I'm seeing for all attempts at launching is: 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py, line 69, in _get_configurations 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] 'ip_address': mapping['ips'][0]['ip'], 2012-09-06 10:16:43 TRACE nova.compute.manager [instance: d5aa2d4b-76db-43b7-a655-24edeb7fc495] IndexError: list index out of range and I just noticed that the flat network interfaces are getting /24 netmasks NOT /16 this combined with 210 running instances and forty some compute nodes make me think it's out of addresses. is my syntax for the fixed range wrong, doc give 10.0.0.0/8 as the example and default so I don't think so. I'm fine with reverting to that, don't mind more addresses, but I would like to understand if this is actually my problem and even if it's not why it's not giving the mask I asked for. -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
