Ask Your Question
1

WAN device to virtual instance on private network

asked 2014-08-11 04:17:42 -0600

jbmolle gravatar image

updated 2014-08-12 11:32:02 -0600

smaffulli gravatar image

Hi all,

I'm working on an expiremental project using Android and OpenStack. For now we have 3 servers running Ubuntu Server 14.04 and OpenStack Icehouse, one is the controller node, one the network node and the last one the compute node.

The aim of the project is to create a kind of cloud gaming platform for Android users. Until now we managed to have the server / client software running. Suppose an Android tablet owner is at home behind his router and my server public ip is 200.20.20.20. When the user click on the app button on his Android tablet, a socket connection will be created and the tablet will connect to the server at the server ip and port 12345. The server is running the game and sending back the images through the socket. That works.

Now we want to scale the service. So instead of having one physical server, we would like to have instances on an OpenStack cloud. We managed to install the cloud following the OpenStack documentation for Ubuntu and we created 3 instances VM1, VM2, VM3 with private ip 192.168.1.11, 192.168.1.12, 192.168.1.13 so that up to 3 clients can play at the same time with their tablets.

The problem is that we don't have 3 public IPs but just one. How could we solve our problem? What we would like to do is the following: - We have a webservice on IP 200.20.20.20 - We have an OpenStack Neutron router on IP 200.20.20.21 When the tablet launches the app, it connects to the webservice. The webservice tells the controller node to start a virtual instance (let's say VM2). The webservice tells the tablet that it should connect to VM2(with address 192.168.1.12) behind the router at public address 200.20.20.21.

Thanks for your help! JB

edit retag flag offensive close merge delete

Comments

The title of your question put me off. I think that Android has nothing to do with the problem you want to solve. Isn't this more of a classic NAT issue? maybe changing the title will make networking people more attracted to chime in.

smaffulli gravatar imagesmaffulli ( 2014-08-11 14:57:41 -0600 )edit

Hi smaffulli, I changed the title to be more broad on the question

jbmolle gravatar imagejbmolle ( 2014-08-12 00:46:14 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-08-11 12:12:41 -0600

fgorbat gravatar image

updated 2014-08-11 12:14:58 -0600

I guess LBaaS will help here.

Using LBaaS you can create custom configuration, that your clients/tables will use one floating IP (200.20.20.x) for connection to the server, while LBA will distribute/route the access to internal network (192.168.1.x)

More info: http://docs.openstack.org/admin-guide...

Good Luck!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-08-11 04:17:42 -0600

Seen: 239 times

Last updated: Aug 12 '14