Ask Your Question
0

DevStack, Floating IPs and VMs not connected on Internet...

asked 2018-06-12 10:45:22 -0500

dchiaramello gravatar image

Hello all.

In short: after days of unsuccessful attempts, I am failing to reach my VM with its Floating IP, and the VM is failing to reach outside world...

First, I apologize: I'm new to OpenStack, and my "mission" is to evaluate what needs to be done to go from a "classic" existing application to the NFV (Network Functional virtualization) world. So, I started to read a lot about NFV, and ended up to OpenStack world - this explains why I am here, and why many Openstack notions are new and somehow "immature" in my mind...

To understand better this new (for me) world, I decided to install Devstack on an Ubuntu 16.04.4 VM provided to me by my organization through ESX Vmware.

The VM (named nfv01) was assigned on network interface ens162 the 10.26.106.68 static IP address. I also asked for a second network interface (ens160) I was expecting OpenStack to use for its private networking stuff. The initial ifconfig result is the following (skipping "lo" interface):

ens160    Link encap:Ethernet  HWaddr 00:0c:29:aa:e4:3a
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:feaa:e43a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20050 errors:0 dropped:29 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1445845 (1.4 MB)  TX bytes:648 (648.0 B)

ens192    Link encap:Ethernet  HWaddr 00:0c:29:aa:e4:30
          inet addr:10.26.106.68  Bcast:10.26.107.255  Mask:255.255.254.0
          inet6 addr: fe80::20c:29ff:feaa:e430/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25468 errors:0 dropped:38 overruns:0 frame:0
          TX packets:2876 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7470992 (7.4 MB)  TX bytes:221641 (221.6 KB)

I was also dedicated by my organization the 10.26.106.187...191 IP addresses to be used as Floating IPs.

For DevStack installation, I configured the following lines in the local.conf file used by stack.sh script:

HOST_IP=10.26.106.68

FLAT_INTERFACE=ens160
FIXED_RANGE=192.168.0.1/24

PUBLIC_INTERFACE=ens192
FLOATING_RANGE=10.26.106.68/23
PUBLIC_NETWORK_GATEWAY=10.26.106.1
Q_FLOATING_ALLOCATION_POOL=start=10.26.106.187,end=10.26.106.191

Devstack works: I am able to create instances, and to allocate floating IPs to instance. After security group update, I'm able to ping and SSH my VM from nfv01 server, and my VM can ping and SSH nfv01 and is also able to ping the gateway (10.26.106.1). But my VM is NOT able to reach the rest of my network (10.26.106.100, for example), nor the external world (8.8.8.8), while nfv01 can do all these things ... (more)

edit retag flag offensive close merge delete

Comments

What OpenStack and devstack version? What do you use neutron plugin?

You mean that your VM can reach 10.26.106.1 but cannot reach 10.26.106.100, right? It's not related floating IP. Neutron L3 supports NAT and I guess that the issue is related to it. It might be the issue about routing table or NAT

ichihara-hirofumi gravatar imageichihara-hirofumi ( 2018-06-27 21:37:33 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2018-06-18 02:39:03 -0500

dchiaramello gravatar image

Hello.

"This post is awaiting moderation" since 6 days - I'm afraid my post has been lost in /dev/null...

Reminder: I'm failing to configure DevStack's neutron for following situation:

  1. I have been provided an ESX VMWare VM running Ubuntu 16.04.4 by my company
  2. It runs on static IP 10.26.106.68 (interface ens192, inet addr:10.26.106.68 Bcast:10.26.107.255 Mask:255.255.254.0)
  3. It has access to public internet and to other company's servers on 10.26.106.X (Mercurial)
  4. I have been reserved IPs 10.26.106.87...91 to use as floating IPs
  5. The gateway is 10.26.106.1
  6. Promiscuity mode is on
  7. It was initially provided a second network interface, but I disabled it since it appears that it's not useful
  8. SSH and ICMP have been enabled
  9. A Floating IP is assigned to the instance
  10. I would like that the instances have access to public internet as well as to other company's servers on 10.26.106.X

I tested many local.conf variations found in various sites without any success for now (reloading initial VM snapshot each time) - I'm feeling like an alchemist in front of numerous samples of herbs and mixing them randomly hoping to find a remedy against the Plague, since my general network knowledge is really weak...

Thanks for your attention, Daniel

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: 2018-06-12 10:45:22 -0500

Seen: 83 times

Last updated: Jun 18 '18