Ask OpenStack: Q&A Site for OpenStack Users and Developers - Latest question feed and answers OpenStack CommunityenCopyright of the authors unless stated otherwiseThu, 09 Mar 2017 12:55:33 -0600can't set allocation pools for subnets created from subnet pools I'm trying to configure a Neutron BGP speaker. Part of the process involves creating a subnet from a subnet pool, from an address scope. This is the exact command from the docs: $ neutron subnet-create --name provider --subnetpool provider \ --prefixlen 24 --allocation-pool start=,end= \ --gateway provider The problem is that it returns an error about the `--allocation-pool` option not being available when creating a subnet from a subnet pool. Bad subnets request: allocation_pools allowed only for specific subnet requests.. I would love to simply leave the option out. However this is an external/physical network, and VRRP is being used on the routers. The resulting subnet without the `--allocation-pool` option would assign the `.2` address to some virtual entity when both the `.1` and `.2` address are used by the physical gateways on that external network.xdaxdbThu, 09 Mar 2017 12:55:33 -0600 a subnet with DHCP my compute node, I have an interface that connects to a provider network. I want to be able to assign a different /29 subnet that does exist on that interface to my VMs (think: secondary network). I don't need to route those /29 addresses, which means I can use all 8. But openstack only seems to let me DHCP the 6 it thinks are usable, which is incorrect in this case. It's a bit of an unusual network setup, I'll admit, but I assure you it's correct and is possible to do without openstack. Any suggestions? Do I need to use floating ips?ripnetFri, 18 Nov 2016 14:50:56 -0600 shows different IP than given by external DHCP server am using neutron and I have a subnet created with `--disable-dhcp`, e.g., neutron subnet-create --tenant-id 5edf2827a9454de49a45fafd3f5ab8df --name subnet_a_b_c --ip-version 4 --gateway a.b.c.3 --disable-dhcp ext_net_a_b_c a.b.c.0/24 At the same time, I have another physical DHCP server providing IP address from `a.b.c.0` subnet. When an instance is launched, `nova show <instance-id>` still shows an IP address (but a wrong one). I wonder if openstack just blindly pick one IP from `a.b.c.0`. Is there a way to let the real IP address show up in "nova show <instance-id>"?ChrisFri, 28 Mar 2014 14:39:34 -0500