If I use nova-network, is floating IP the only way to go?

asked 2014-10-13 20:47:23 -0500

gators gravatar image

I need to access my VMs from the wifi network they are on.

It's like this:

my wifi network is on 192.168.253.x. I don't have a way to reserve addresses to use as public ip address pool.

I have a single host devstack whose address is VM's are 10.0.0.x (x starts from 2).

I can access the wifi network from the VM. But the issue is that I need to access VM from the wifi. For example I need to rdp to win7 from mac

I did extensive experiment and seem to me the only way for this to work is I have some 192.168.253.y reserved as floating ip. I don't have the ability to do so.

Am I right? Is there a way to make it work with nova-network?

I think neutron should work but I am not sure how to configure a virtual router in devstack to make it work.


edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-10-14 09:34:19 -0500

jfarschman gravatar image


With nova-network you can make your FIXED space routable and just use that for everything. Ignore the FLOATING space altogether. I wasn't able to follow all the details of your setup, but if you provide nova-network with some IPs are routable on your network this will work. It's not how things are designed, but I've done this very successfully in a lab before. In nova.conf set things up to bridge



One problem you may have is that the FIXED network will try to take the entire space. For instance, if you build a FIXED network on it will want to start allocating all of the IPs in this space. You can address this by removing individual addresses from nova.fixed_ips table.... you may also need to properly assign you compute nodes in the same table.

edit flag offensive delete link more


this is good answer

SGPJ gravatar imageSGPJ ( 2014-10-14 09:51:34 -0500 )edit

I am not sure if I completely understand. My nova VMs use 10.0.0.x. I don't have any control with the company network 192.168.253.y. I think it's just a dhcp network. Are you saying that I can usenova.fixed_ips table to reserve some 192.168.253.y's addresses? Could you show an example? Thanks!

gators gravatar imagegators ( 2014-10-14 11:28:49 -0500 )edit

INSERT INTO fixed_ips (created_at, updated_at, deleted_at, id, address, network_id, allocated, leased, reserved, virtual_interface_id, host, instance_uuid, deleted) VALUES ('2013-08-06 21:15:54', '2013-08-06 21:15:54', NULL, 1030, '', 1, 0, 0, 0, ........

jfarschman gravatar imagejfarschman ( 2014-11-06 09:17:50 -0500 )edit

Sorry for the late comment, but yes, you guessed correctly. unless nova.fixed_ips had a reserved address that matches the address in your networking config it will break things.

jfarschman gravatar imagejfarschman ( 2014-11-06 09:18:54 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-10-13 20:47:23 -0500

Seen: 307 times

Last updated: Oct 14 '14