OpenStack Compute (nova)

floating IP - creating an IP pool on devstack

Asked by dubi

devstack (Essex) comes with an existing pool of floating IPs (nova,test) which are not relevant to my local network.
my devstack was installed on one host ( all components there) . I have created instances and run them.

I want to add a new IP range from my local network so that I can access an instance from outside the cloud .

I am using: nova-manage floating create --ip_range=<Ip/range> . The commad finishes with no comment
But I cannot see the IP on the output of : nova-manage floating list . That output remains with the original list of IPs.
Even if I erase them one by one and add mine last it is not added or at least no shown and not offered when I
try to allocate Ip to a project from the dashboard or from nova command line

Any idea what is causing the problem or I have to use a different command syntax than explained
in :http://docs.openstack.org/essex/openstack-compute/admin/content/associating-public-ip.html

my nova.conf has :
my_ip=9.148.4.71
public_interface=br100
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0

and my host interface looks like :

br100 Link encap:Ethernet HWaddr 00:01:c9:00:00:18
          inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: 2001:bf8:2000:2004:201:c9ff:fe00:18/64 Scope:Global
          inet6 addr: fe80::b84b:16ff:fe86:2727/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1705710 errors:0 dropped:913 overruns:0 frame:0
          TX packets:432444 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:455514661 (455.5 MB) TX bytes:209287142 (209.2 MB)

eth0 Link encap:Ethernet HWaddr 00:01:c9:00:00:18
          inet6 addr: 2001:bf8:2000:2004:201:c9ff:fe00:18/64 Scope:Global
          inet6 addr: fe80::201:c9ff:fe00:18/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2337140 errors:0 dropped:0 overruns:0 frame:0
          TX packets:716028 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:908411286 (908.4 MB) TX bytes:135346694 (135.3 MB)
          Interrupt:17 Memory:d8000000-d8012800

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:670528 errors:0 dropped:0 overruns:0 frame:0
          TX packets:670528 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7513813131 (7.5 GB) TX bytes:7513813131 (7.5 GB)

virbr0 Link encap:Ethernet HWaddr 6a:d2:5d:16:55:65
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vnet0 Link encap:Ethernet HWaddr fe:16:3e:47:0d:8a
          inet6 addr: fe80::fc16:3eff:fe47:d8a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:48399 errors:0 dropped:0 overruns:0 frame:0
          TX packets:946361 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:7732666 (7.7 MB) TX bytes:190306082 (190.3 MB)

vnet1 Link encap:Ethernet HWaddr fe:16:3e:0f:f9:31
          inet6 addr: fe80::fc16:3eff:fe0f:f931/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:175843 errors:0 dropped:0 overruns:0 frame:0
          TX packets:529030 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:147108837 (147.1 MB) TX bytes:250893655 (250.8 MB)

and here is the output of: iptables --list at the host:
Chain INPUT (policy ACCEPT)
target prot opt source destination
nova-network-INPUT all -- anywhere anywhere
nova-compute-INPUT all -- anywhere anywhere
nova-api-INPUT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
nova-filter-top all -- anywhere anywhere
nova-network-FORWARD all -- anywhere anywhere
nova-compute-FORWARD all -- anywhere anywhere
nova-api-FORWARD all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
nova-filter-top all -- anywhere anywhere
nova-network-OUTPUT all -- anywhere anywhere
nova-compute-OUTPUT all -- anywhere anywhere
nova-api-OUTPUT all -- anywhere anywhere

Chain nova-api-FORWARD (1 references)
target prot opt source destination

Chain nova-api-INPUT (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere lnx-openstack.haifa.ibm.com tcp dpt:8775

Chain nova-api-OUTPUT (1 references)
target prot opt source destination

Chain nova-api-local (1 references)
target prot opt source destination

Chain nova-compute-FORWARD (1 references)
target prot opt source destination

Chain nova-compute-INPUT (1 references)
target prot opt source destination

Chain nova-compute-OUTPUT (1 references)
target prot opt source destination

Chain nova-compute-inst-1 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
nova-compute-provider all -- anywhere anywhere
ACCEPT udp -- 10.0.0.1 anywhere udp spt:bootps dpt:bootpc
ACCEPT all -- 10.0.0.0/24 anywhere
nova-compute-sg-fallback all -- anywhere anywhere

Chain nova-compute-inst-4 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
nova-compute-provider all -- anywhere anywhere
ACCEPT udp -- 10.0.0.1 anywhere udp spt:bootps dpt:bootpc
ACCEPT all -- 10.0.0.0/24 anywhere
nova-compute-sg-fallback all -- anywhere anywhere

Chain nova-compute-local (1 references)
target prot opt source destination
nova-compute-inst-1 all -- anywhere 10.0.0.2
nova-compute-inst-4 all -- anywhere 10.0.0.3

Chain nova-compute-provider (2 references)
target prot opt source destination

Chain nova-compute-sg-fallback (2 references)
target prot opt source destination
DROP all -- anywhere anywhere

Chain nova-filter-top (2 references)
target prot opt source destination
nova-network-local all -- anywhere anywhere
nova-compute-local all -- anywhere anywhere
nova-api-local all -- anywhere anywhere

Chain nova-network-FORWARD (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere

Chain nova-network-INPUT (1 references)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain

Chain nova-network-OUTPUT (1 references)
target prot opt source destination

Chain nova-network-local (1 references)
target prot opt source destination

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
John Garbutt (johngarbutt) said : 		#1

Not sure why that command is failing, but you can take a look at adding a setting in your localrc file to adjust the range created by DevStack:
FLOATING_RANGE=${FLOATING_RANGE:-172.24.4.224/28}

See:
https://github.com/openstack-dev/devstack/blob/master/stack.sh#L285

Looking at the docs, try without the --ip_range flag:
http://docs.openstack.org/developer/nova/runnova/nova.manage.html#nova-floating-ips

The example commands in devstack are:
# Create some floating ips
$NOVA_DIR/bin/nova-manage floating create $FLOATING_RANGE
# Create a second pool
$NOVA_DIR/bin/nova-manage floating create --ip_range=$TEST_FLOATING_RANGE --pool=$TEST_FLOATING_POOL

Can you help with this problem?

Provide an answer of your own, or ask dubi for more information if necessary.

To post a message you must log in.