How to Configure OpenStack Network to Enable Access to OpenStack Instances

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Matei Cezar

I’am a computer addicted guy, a fan of open source and linux based system software, have about 4 years experience with Linux distributions desktop, servers and bash scripting.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

11 Responses

  1. Rahul says:

    This manual could work only on bridge interface in virtual box,but will not work in host only network. If you don’t have internet connection in later stage,you will not be able be to access the instance using floating IP.

  2. kostya_h says:

    Hello author,
    Why did not you tell that users need to install ovs bridge first? Without it your manual does not work and service network shows an error: network is unavailable! I have wasted two days to find the root cause of this error!

    You should understand that there not all users are so much experienced like you that is why you need mention all details in your manual to avoid any questions why it does not work who followed it but did not do that you did not write but what should be done in order to make it work!

    • Chinmay says:

      Hello kostya_h, I am facing same issue, i am new to Linux can you tell me how have you resolved this issue ?

      • kostya_h says:

        Hello,
        Sorry for the last answer. Just already have noticed your reply.
        I was not able to make it work (ovs-bridge) using this manual.

        I used little bit another config files for interfaces (here they are):

        [ifcfg-br-ex]

        =Ethernet
        BOOTPROTO=none
        DEFROUTE=yes
        NAME=br-ex
        DEVICE=br-ex
        ONBOOT=yes
        IPADDR=192.168.176.130 -your IP
        PREFIX=24
        GATEWAY=192.168.176.2 -your GATEWAY ( check it with “route -n”, it will be it the 1-st output line under the GATEWAY column)
        PEERDNS=no
        NM_CONTROLLED=no

        [ifcfg-ens33]

        DEVICE=ens33
        ONBOOT=yes
        DEVICETYPE=ovs
        TYPE=OVSPort
        OVS_BRIDGE=br-ex

        I have used the following command to make it work:

        sudo ovs-vsctl add-port br-ex ens33; systemctl restart network –general command which adds port to the mentioned bridge
        (this command does not work for me and i was forced to do next):

        sudo ovs-vsctl del-port ens33 –delete existing port

        systemctl restart network —–restart network to apply changes

        sudo ovs-vsctl del-br br-ex –delete existing bridge

        systemctl restart network —–restart network to apply changes

        sudo ovs-vsctl add-br br-ex —–adding ovs bridge

        systemctl restart network —–restart network to apply changes

        and finally:
        sudo ovs-vsctl add-port br-ex ens33 —–adding port to mentioned bridge where ‘ens33’ is my network interface. In your case it may be another, for example etho, enp123 e.t.c, it depends of VM that you are using. VmWare default naming is like this one.

        sudo service network restart —-aplying changes again.

        checking:
        ip a —- checking network configuration. you should see something like this:
        2: ens33: mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000

        [[email protected] network-scripts]$ route -n
        Kernel IP routing table
        Destination Gateway Genmask Flags Metric Ref Use Iface
        0.0.0.0 192.168.176.2 0.0.0.0 UG 0 0 0 br-ex
        169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 ens33
        169.254.0.0 0.0.0.0 255.255.0.0 U 1013 0 0 br-ex
        192.168.176.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex

        if everything is fine you can open openstack dashboard http://192.168.176.130/dashboard/ and be able to ‘ping 8.8.8.8’
        When i followed tecmint guide my network stopped to work and i lost external internet connection until i founded another working solution.

        I hope it will help you.

  3. Sarang Kher says:

    You are a superstar, long live tecmint.

  4. Rahul Joshi says:

    Hello Matei,

    You are awesome..

    I have one query. Can we create multiple routers & multiple networks (Priv/Pub) on the above same setup.

    Like Priv1 10.0.0.0/8 Pub1 192.168.60.0/24 & Priv2 172.16.0.0/16 Pub2 192.168.61.0/24
    Public network range is our local subnets/ vlans .

    Any idea??
    Appreciate your efforts in above tutorial.

    Thanks

  5. Matei Cezar says:

    Investigate your logs (mysql, keystone, glance) maybe there’s a clue on what might went wrong and post a topic on openstack specialized forums. Also, try a system reboot.

  6. brnf says:

    At the end of step 3.3 I lost access to the dashboard. I got the following message on the browser: “Unable to establish connection to keystone endpoint.” I’ve double checked interfaces config, and it seems right. Can you share any ideas to what might be wrong? Thanks! Keep up the good work!

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *