Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

On network node Set the bridging correctly as

Assuming eth1 interface is having internet access and br-ex brige is set up ,

ovs-vsctl add-port br-ex eth1

This command would disconnect the access of network node, Login to console and set

ifcfg eth1 0

Also ensure that br-ex is having the public ip address or the inter access network ,

This would bring back the connectivity,

In your case ifconfig should return the

ifconfig br-ex = ip address of internet network (172.24.4.224) eth1 = This is up but no ip address is displayed

Check the ip routing table in network node ,assuming internet access is on 172.24.4.224 network

route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.24.4.1 0.0.0.0 UG 100 0 0 br-ex 10.40.96.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

ip route show default via 172.24.4.1 dev br-ex metric 100 172.24.4.0/24 dev br-ex proto kernel scope link src 172.24.4.224 . .

In above results i assume 172.24.4.1 is you default gateway of your internet network Ensure that the default path is set correctly , if not set it and check if the network node is able to resolve DNS ping google.com

After this you are done on CLI , Now login to dashboard and set the networking topology correctly

Create a public network.

Starting with the Openstack Dashboard, logged in as admin, create a public network is 172.24.4.0/28. The IP address 172.24.4.1 is the address of your hardware router, gateway to the internet. Network host is 172.24.4.224 . And Openstack needs a subnet, referred to as public, that sits in this address range.

Openstack Dashboard Menu: Admin->Networks->Create Network Name - Public Project - admin Admin state = yes External network = yes

Create network

Openstack Dashboard Menu: Admin->Networks->public->Create Subnet Subnet Name - public_subnet Network address - 172.24.4.0/28 IP Version - IPV4 Gateway IP - 172.24.4.224

Openstack Dashboard Menu: Admin->Networks->public->Create Subnet 2 Allocation Pools - Set the range of ip's free on 172.24.4.0/28 DNS servers - Set the DNS ip

openstack Dashboard Menu: Project->Network->Network Topology->Create Network — “private”

Network Name - Private Admin state = yes

Openstack Dashboard Menu: Project->Network->Network Topology->Create Network->Subnet Create subnet = yes Subnet name = Private subnet Network address - 192.168.0.0/24 (Please set this as per your enviroment IP Version - v4 Gateway IP = 192.168.0.1

Openstack Dashboard Menu: Project->Network->Network Topology->Create Network->Subnet Details Enable DHCP = yes Allocation Pools = 192.168.0.2,192.168.0.254 DNS - your DNS Servers

Create a router

Ok, there’s a public and a private subnet defined. Openstack Dashboard has a really simple way to connect them together with a router function. Create a router, define a default gateway and then add interfaces to private subnets.

Openstack Dashboard Menu: Projects->Network Topology->Create Router

Router name - router

Openstack Dashboard Menu: Project->Routers->Set Gateway External network - public

Openstack Dashboard Menu: Project->Routers->router->Add Interface Subnet - Private IP Address - 192.168.0.1

Verify Network Topology

All the steps upto this point were building a network into which virtual machines connect to the home LAN. Run the Dashboard command below to see two subnets connect to a router. The public subnet is on the home LAN. The private subnet is the address space where the guests instances will connect.

Now you can launch the instance with Private ip address

To Allocate a Floating IP address to instance for internet access

Openstack Dashboard Menu: Projects->Access & Security->Floating IPs->Allocate IP to Project Pool - Public

Associate the instance’s private IP address to an IP address on the public subnet.

Openstack Dashboard Menu: Project->Access & Security->Floating IP->Associate Select the public ip address

Select the port to be associated - Instance name: private ip address

Verify that the instance has two IP addresses and is running ok.

Openstack Dashboard Menu: Project->Instance

Hello,

I am writing this assuming the network diagram prepared in MS paint with black fonts

On network node Set the bridging correctly as

Assuming eth1 interface is having internet access and br-ex brige is set up ,

ovs-vsctl add-port br-ex eth1

This command would disconnect the access of network node, Login to console and set

ifcfg eth1 0

Also ensure that br-ex is having the public ip address or the inter access network ,

If not , se it via CLI

ifconfig br-ex 172.24.4.224 netmask 255.x.x.x up

This would bring back the connectivity,

In your case ifconfig should return the

ifconfig br-ex = ip address of internet network (172.24.4.224) eth1 = This is up but no ip address is displayed

Check the ip routing table in network node ,assuming internet access is on 172.24.4.224 network

route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.24.4.1 0.0.0.0 UG 100 0 0 br-ex 10.40.96.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

ip route show default via 172.24.4.1 dev br-ex metric 100 172.24.4.0/24 dev br-ex proto kernel scope link src 172.24.4.224 . .

In above results i assume 172.24.4.1 is you default gateway of your internet network Ensure that the default path is set correctly , if not set it and check if the network node is able to resolve DNS ping google.com

After this you are done on CLI , Now login to dashboard and set the networking topology correctly

Create a public network.

Starting with the Openstack Dashboard, logged in as admin, create a public network is 172.24.4.0/28. The IP address 172.24.4.1 is the address of your hardware router, gateway to the internet. Network host is 172.24.4.224 . And Openstack needs a subnet, referred to as public, that sits in this address range.

Openstack Dashboard Menu: Admin->Networks->Create Network Name - Public Project - admin Admin state = yes External network = yes

Create network

Openstack Dashboard Menu: Admin->Networks->public->Create Subnet Subnet Name - public_subnet Network address - 172.24.4.0/28 IP Version - IPV4 Gateway IP - 172.24.4.224

Openstack Dashboard Menu: Admin->Networks->public->Create Subnet 2 Allocation Pools - Set the range of ip's free on 172.24.4.0/28 DNS servers - Set the DNS ip

openstack Dashboard Menu: Project->Network->Network Topology->Create Network — “private”

Network Name - Private Admin state = yes

Openstack Dashboard Menu: Project->Network->Network Topology->Create Network->Subnet Create subnet = yes Subnet name = Private subnet Network address - 192.168.0.0/24 (Please set this as per your enviroment IP Version - v4 Gateway IP = 192.168.0.1

Openstack Dashboard Menu: Project->Network->Network Topology->Create Network->Subnet Details Enable DHCP = yes Allocation Pools = 192.168.0.2,192.168.0.254 DNS - your DNS Servers

Create a router

Ok, there’s a public and a private subnet defined. Openstack Dashboard has a really simple way to connect them together with a router function. Create a router, define a default gateway and then add interfaces to private subnets.

Openstack Dashboard Menu: Projects->Network Topology->Create Router

Router name - router

Openstack Dashboard Menu: Project->Routers->Set Gateway External network - public

Openstack Dashboard Menu: Project->Routers->router->Add Interface Subnet - Private IP Address - 192.168.0.1

Verify Network Topology

All the steps upto this point were building a network into which virtual machines connect to the home LAN. Run the Dashboard command below to see two subnets connect to a router. The public subnet is on the home LAN. The private subnet is the address space where the guests instances will connect.

Now you can launch the instance with Private ip address

To Allocate a Floating IP address to instance for internet access

Openstack Dashboard Menu: Projects->Access & Security->Floating IPs->Allocate IP to Project Pool - Public

Associate the instance’s private IP address to an IP address on the public subnet.

Openstack Dashboard Menu: Project->Access & Security->Floating IP->Associate Select the public ip address

Select the port to be associated - Instance name: private ip address

Verify that the instance has two IP addresses and is running ok.

Openstack Dashboard Menu: Project->Instance