Ask Your Question
0

Packstack Stein - Networking Configuration

asked 2019-10-09 06:00:11 -0500

MWeber gravatar image

Hello,

I want to install a POC Openstack installation by using packstack, after running the packstack installation (allinone) and tweaking the answer file a bit to my setup and what services I want to deploy I managed to have an Openstack cloud running, upload images and start some instances (although I am having trouble getting to run Windows Instaces)

My Main problem though is the Networking aspect of Packstack and Openstack, my VM on which i wanted to install the system has 1 physical Interface(eth0) with a static IP that has Internet Access.

Now Packstack creates the br-ex by default and gives it the IP-range 172.18.24.0/24, I figured that this Network is used to deploy Instances, but when I start an Instance it doesn't get an IP from the DHCP and even if I configure a static one from the pool of 172.18.24.0/24 addresses I can't connect to the internet nor can my Host VM connect to the Instance

I looked over some guides online and the packstack answer file configuration options in the Network section, but haven't figured out what to do, to make it work.

My thought was that openstack uses its own Network (some private IP range) and the connection to the internet is managed by routing traffic through my HostVM, but haven't found anything online yet that lets me accomplish that If by chance anyone can give me a quick guideline what settings to use for the packstack deployment to make it work, that would be great.

edit retag flag offensive close merge delete
add a comment

3 answers

Sort by ยป oldest newest most voted
1

answered 2019-10-09 08:47:57 -0500

Bernd Bausch gravatar image

Two problems. First, there is no DHCP server on the external network, which explains why your VM doesn't get an IP address. The default deployment of Packstack assumes that instances are connected to tenant networks, not the external network. You can however add a DHCP server to the external network.

Second, the "external" network is in reality isolated in the Packstack server. This is by design; you don't need instances with internet access to try out OpenStack. With a little modification, you can connect the external network to the real i ternet: https://www.rdoproject.org/networking....

Now, the Stein version introduced a new default network infrastructure (ML2 mechanism driver OVN instead of Openvswitch, and type driver Geneve instead of VXLAN), and I don't know whether these instructions work with the Stein or Train versions of Packstack. Still worthwhile trying, I think.

edit flag offensive delete link more

Comments

I followed the Instructions you provided to the T, but I dont seem to be able to reach the Internet from my Instances,

I can ping my eth0 addr from inside the instances but do not reach the Gateway of my public net

MWeber gravatar imageMWeber ( 2019-10-10 02:53:23 -0500 )edit

As I said, I am not sure if the instructions work with OVN, the default Packstack networking setup since Stein.

Perhaps you can benefit from my experience with Stein Packstack: https://ask.openstack.org/en/question...

Bernd Bausch gravatar imageBernd Bausch ( 2019-10-10 04:41:47 -0500 )edit

I looked at your Information as well, and used it as a guideline.

I managed to solve the issue of Internet connectivity by enabling routing on my bridge with iptables

MWeber gravatar imageMWeber ( 2019-10-10 06:56:16 -0500 )edit
add a comment
0

answered 2019-12-29 21:35:02 -0500

UHL-Services gravatar image

Have you followed this: https://www.rdoproject.org/networking/neutron-with-existing-external-network/ (https://www.rdoproject.org/networking...) ?

edit flag offensive delete link more
add a comment
0

answered 2019-10-09 09:41:16 -0500

MWeber gravatar image

Ok I have had some progress,

after searching more and finding some old, but still usefull guides I managed to rerun the packstack install to a (mostly) working configuration.

I know have and the following situation, the bridge br-ex has 2 Ip adrresses, 1 is my "normal" (former eth0) IP Addr for Internet access and the second is the "external" Openstack IP Add( in my case 10.0.1.1/24), openstack has the internal network 10.0.0.0/24 for the Demo User as well, so now if I start an Instance it correctly gets an IP adrr from the 10.0.0.0 internal Net, and if I add a Floating IP from the 10.0.1.0 Net I can also reach the Instance from my HostVM, which is running the openstack cloud.

1 Probem persists so far though, I still cant access the Internet from inside the Instance, and if I enter the router Namespace with "ip netns exec ..." and ping from the router to 8.8.8.8 I get a redirected Host notification (Nexthop beeing my eth0 Gateway)

I would love to solve this.

edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2019-10-09 06:00:11 -0500

Seen: 897 times

Last updated: Oct 09 '19

Related questions

Stein: keystone doesn't use 35357, while heat doc still uses it [closed]

Openstack "stein": Kubernetes-cluster stuck in "CREATE_IN_PROGESS"

openstack packstack ussri installation fails Centos 8

cinder failed to login in to solidfire backend when creating volume

Not able to set max connections in Mariadb for Openstack Stein Version

While installing stein on Centos 8 the follwoing error comes "No match for argument: centos-release-openstack-stein"

Stein : Unable to ping ip of instance

Packstack installation failed for multi node setup.

Unable to establish connection to keystone endpoint.

MP-BIOS bug: 8254 timer not connected to IO-APIC please suggest something to make it work.