Ask Your Question

Openstack public network question

asked 2019-05-04 04:26:00 -0500

steven_A gravatar image

updated 2019-05-12 04:58:55 -0500


i have a DevStack environment (OpenStack server) running on a bridged virtualbox environment ( Now, in OpenStack i want to be able to communicate with my instance. My instances can communicate with each other through their private IP addresses. Should i enter as my public network then? I want to be able to communicate with an OpenStack instance (floating ip) from my bridged virtualbox environment.

Note: i added FLOATING_RANGE= to my local.conf after that i configured the br-ex interface

Every suggestion is really appreciated.


edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted

answered 2019-05-05 12:15:50 -0500

steven_A gravatar image

updated 2019-05-12 04:57:59 -0500

Hi, thank you for the information. I'm able to communicate with my created instances now. The br-ex interface was down while i knew that my openstack configuration was OK. This gave me quite a headache but i'm glad that I found it in the end. The interface was shut down on a reboot or so. So, if you come accross the same problem please check your br-ex interface with ifconfig or ip a.

Note: I am able to ping from the OpenStack server to the instance. I can't ping the instance from any other server in my public network (

edit flag offensive delete link more


Devstack is not made for rebooting. It’s meant to create a cloud for testing OpenStack code, which is then unceremoniously destroyed. Swift and Cinder are unlikely to work after a reboot either and need to be repaired as well.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-05 14:08:31 -0500 )edit

answered 2019-05-04 08:51:10 -0500

To reach instances from outside their private network, you need to assing floating IPs to them.

In addition, to reach the instances from outside the Devstack server, the publicnetwork must be mapped to the network that the Devstack server is attached to ( in your case), as you correctly assumed. See to achieve that.

edit flag offensive delete link more


my openstack server can ping the instance and the instance can ping the openstack server. But, other servers (not instances) in my network can't ping the instance. Any suggestions?

steven_A gravatar imagesteven_A ( 2019-05-11 17:35:12 -0500 )edit

If you talk about floating IPs, I used to have a similar problem. Floating IPs on a Virtualbox/Windows-based Devstack cloud were not reachable from outside. An identical KVM-based Devstack had no problem. I was unable to fix this with Virtualbox on Windows and have been using KVM since.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-11 20:34:43 -0500 )edit

So it is not able to do so on a Devstack system deployed on a Windows host? kvm-ok is giving me a negative outcome so i'm guessing the same thing. I tried for a while but i think I wil do the same thing. So pinging is possible when DevStack is deployed from a Linux KVM host? Just to be clear.

steven_A gravatar imagesteven_A ( 2019-05-12 05:02:10 -0500 )edit

Yes, I can access instances on a Devstack cloud that is deployed on a KVM machine. Whether Virtualbox really blocks certain traffic, and whether and how this can be changed, I don’t know, but I did have similar problems as you with VBox-based Devstack clouds.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-12 06:41:21 -0500 )edit

Confirmed, I installed on a KVM host and everything works fine with the same setup. Thank you very much for you help, it probably spared me hours of my time. I might research the VirtualBox problem in my thesis for school.

steven_A gravatar imagesteven_A ( 2019-05-12 14:30:46 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-05-04 04:26:00 -0500

Seen: 197 times

Last updated: May 12 '19