Ask Your Question
0

External Network Floating IP Assignment

asked 2015-03-28 01:27:34 -0500

ethode gravatar image

I am setting up a fairly simple 4 node cluster (controller, network, compute and storage).

I am about to setup the external network and ran into a question ( http://docs.openstack.org/juno/install-guide/install/apt/content/neutron_initial-external-network.html (http://docs.openstack.org/juno/instal...) )

In the IP address range they're using, they do not specify if this range is the public static IP range given to them by their ISP, Fiber provider etc OR if those IPs and ranges are actually of an internal range.

Thanks in advance!

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-04-01 06:25:13 -0500

Charles Benon gravatar image

Hi Ethode people,

The IP range can be what you want. The only condition will have to have this range IP reachable from other points of your network or outside (depending of what you are doing with your Openstack environment).

For example, on my lab, I have 2 pools of external ranges:

  • One for management which use the IP subnet dedicated for me in the lab (from there, I can the outside world)
  • A second one for pure testing going to a closed network

With the type of service you are offering, I guess both of the option would make sense. As well, an direct external access would work (on Neutron, you have a firewall to avoid anyone messing up with your servers)

Does it make sense ?

edit flag offensive delete link more

Comments

Right now we have the tenant network - but we need the ext-network so that we can assign external IP address to instances using floating IPs. However, I think the disconnect for me is that in my physical router needs to NAT those IP's some where and I have no clue where so that openstack uses them

ethode gravatar imageethode ( 2015-04-02 14:15:00 -0500 )edit

In this case, you get few options: - router acting as a modem or transparent mode - router doing NAT (for example 1 to 1 mapping) - router routing to internal public IPs going to your floating pool (/32 address on the public physical interface and /xy for the internal public pool)

Charles Benon gravatar imageCharles Benon ( 2015-04-04 06:33:07 -0500 )edit

I'd like these instances to be available via the Internet and then also have an internal tenant network. The tenement network even if it can only talk to other stack servers and nothing else that's fine. My assumption is that I could send all my public ips to network node and let it do DHCP

ethode gravatar imageethode ( 2015-04-04 08:33:08 -0500 )edit

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: 2015-03-28 01:27:34 -0500

Seen: 238 times

Last updated: Apr 01 '15