Revision history [back]

unable to configure ovs bridge rightly

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

https://www.rdoproject.org/Neutron_with_existing_external_network

However, when I restart the network service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

unable to configure ovs bridge rightly

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

https://www.rdoproject.org/Neutron_with_existing_external_network

At the point when I restart the network 'network' service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

unable to configure ovs bridge rightly

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

At the point when I restart the 'network' service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

unable to configure ovs bridge rightly

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

At the point when I restart the 'network' service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

UPDATE

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=br-ex
ONBOOT=yes
BOOTPROTO=none


unable to configure ovs bridge rightly

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

At the point when I restart the 'network' service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

UPDATE

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=br-ex
ONBOOT=yes
BOOTPROTO=none

[root@ip-10-3-3-219 ~(keystone_admin)]# ovs-vsctl show
0e11330a-f3de-4b8e-aa5d-01c1a4183d7c
Bridge br-int
fail_mode: secure
Port "tap9e51a51f-1f"
tag: 1
Interface "tap9e51a51f-1f"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port "qvo770ee127-d1"
tag: 1
Interface "qvo770ee127-d1"
Port br-int
Interface br-int
type: internal
Port "qr-c3690b5d-e9"
tag: 1
Interface "qr-c3690b5d-e9"
type: internal
Bridge br-ex
Port "qg-a83a7152-29"
Interface "qg-a83a7152-29"
type: internal
Port "eth0"
Interface "eth0"
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.3.1"

br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
inet6 fe80::4f3:38ff:fec7:be59  prefixlen 64  scopeid 0x20<link>
ether 06:f3:38:c7:be:59  txqueuelen 0  (Ethernet)
RX packets 84577  bytes 67169262 (64.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 56791  bytes 7209320 (6.8 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-int: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::808f:c1ff:fe56:2045  prefixlen 64  scopeid 0x20<link>
ether 82:8f:c1:56:20:45  txqueuelen 0  (Ethernet)
RX packets 200  bytes 23513 (22.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 8  bytes 648 (648.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
inet6 fe80::4f3:38ff:fec7:be59  prefixlen 64  scopeid 0x20<link>
ether 06:f3:38:c7:be:59  txqueuelen 1000  (Ethernet)
RX packets 266550  bytes 308743234 (294.4 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 125416  bytes 14093596 (13.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
ether 06:b3:b7:e3:e1:7d  txqueuelen 1000  (Ethernet)
RX packets 16265  bytes 966900 (944.2 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 6254  bytes 329676 (321.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10<host>
loop  txqueuelen 0  (Local Loopback)
RX packets 36964165  bytes 5455773323 (5.0 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 36964165  bytes 5455773323 (5.0 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qbr770ee127-d1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::d0df:57ff:fef4:5fe4  prefixlen 64  scopeid 0x20<link>
ether d2:df:57:f4:5f:e4  txqueuelen 0  (Ethernet)
RX packets 34  bytes 2024 (1.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 9  bytes 738 (738.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qvb770ee127-d1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
inet6 fe80::d0df:57ff:fef4:5fe4  prefixlen 64  scopeid 0x20<link>
ether d2:df:57:f4:5f:e4  txqueuelen 1000  (Ethernet)
RX packets 577  bytes 57419 (56.0 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 492  bytes 56290 (54.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qvo770ee127-d1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
inet6 fe80::684c:97ff:fea4:5317  prefixlen 64  scopeid 0x20<link>
ether 6a:4c:97:a4:53:17  txqueuelen 1000  (Ethernet)
RX packets 492  bytes 56290 (54.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 577  bytes 57419 (56.0 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap770ee127-d1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::fc16:3eff:fecd:e3c0  prefixlen 64  scopeid 0x20<link>
ether fe:16:3e:cd:e3:c0  txqueuelen 500  (Ethernet)
RX packets 476  bytes 54994 (53.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 587  bytes 58215 (56.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


unable Unable to configure ovs bridge rightlyping VM from an external host through its floating ip

Hello, I am trying to install Juno on an Amazon VM with RHEL 7. My installation goes perfectly without a hitch. I am also able to access the Dash board, create an external and internal network and start a VM. However, I am stuck at a point where I cannot access this VM that I create.

After reading up a lot I understood that an OVS bridge needs to be configured. I followed the instructions given at the link below point by point.

At the point when I restart the 'network' service my AWS instance loses connectivity with the network completely. I am left with no other alternative but to terminate this instance and start the RDO installation, over a new instance, all over again. Losing connectivity also means that I don't have the chance to get back to the machine and analyze the neutron or openvswitch logs to figure out what went wrong.

Here is what my cofigurations look like:

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.3.3.143 # Old eth0 IP that is assigned by AWS to eth0
GATEWAY=10.3.3.1  # your gateway
DNS1=10.3.2.234     # your nameserver
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=52:54:00:92:05:AE # This is the hwaddr of eth0 that is originally given by AWS
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes

/etc/neutron/plugin.ini

network_vlan_ranges = physnet1
bridge_mappings = physnet1:br-ex


neutron agent-list shows that all agents are running fine and dandy with :) against each.

I know that its not idea to install Openstack over a VM. However, I really don't have the resources to get a bare metal server and hence this is my only option.

Can anybody please guide me further to understand where things might be going wrong?

UPDATE

/etc/sysconfig/network-scripts/ifcfg-br-ex

DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=br-ex
ONBOOT=yes
BOOTPROTO=none

[root@ip-10-3-3-219 ~(keystone_admin)]# ovs-vsctl show
0e11330a-f3de-4b8e-aa5d-01c1a4183d7c
Bridge br-int
fail_mode: secure
Port "tap9e51a51f-1f"
tag: 1
Interface "tap9e51a51f-1f"
type: internal
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port "qvo770ee127-d1"
tag: 1
Interface "qvo770ee127-d1"
Port br-int
Interface br-int
type: internal
Port "qr-c3690b5d-e9"
tag: 1
Interface "qr-c3690b5d-e9"
type: internal
Bridge br-ex
Port "qg-a83a7152-29"
Interface "qg-a83a7152-29"
type: internal
Port "eth0"
Interface "eth0"
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.3.1"

br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
inet6 fe80::4f3:38ff:fec7:be59  prefixlen 64  scopeid 0x20<link>
ether 06:f3:38:c7:be:59  txqueuelen 0  (Ethernet)
RX packets 84577  bytes 67169262 (64.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 56791  bytes 7209320 (6.8 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-int: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::808f:c1ff:fe56:2045  prefixlen 64  scopeid 0x20<link>
ether 82:8f:c1:56:20:45  txqueuelen 0  (Ethernet)
RX packets 200  bytes 23513 (22.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 8  bytes 648 (648.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
inet6 fe80::4f3:38ff:fec7:be59  prefixlen 64  scopeid 0x20<link>
ether 06:f3:38:c7:be:59  txqueuelen 1000  (Ethernet)
RX packets 266550  bytes 308743234 (294.4 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 125416  bytes 14093596 (13.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9001
ether 06:b3:b7:e3:e1:7d  txqueuelen 1000  (Ethernet)
RX packets 16265  bytes 966900 (944.2 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 6254  bytes 329676 (321.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10<host>
loop  txqueuelen 0  (Local Loopback)
RX packets 36964165  bytes 5455773323 (5.0 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 36964165  bytes 5455773323 (5.0 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qbr770ee127-d1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::d0df:57ff:fef4:5fe4  prefixlen 64  scopeid 0x20<link>
ether d2:df:57:f4:5f:e4  txqueuelen 0  (Ethernet)
RX packets 34  bytes 2024 (1.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 9  bytes 738 (738.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qvb770ee127-d1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
inet6 fe80::d0df:57ff:fef4:5fe4  prefixlen 64  scopeid 0x20<link>
ether d2:df:57:f4:5f:e4  txqueuelen 1000  (Ethernet)
RX packets 577  bytes 57419 (56.0 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 492  bytes 56290 (54.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qvo770ee127-d1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
inet6 fe80::684c:97ff:fea4:5317  prefixlen 64  scopeid 0x20<link>
ether 6a:4c:97:a4:53:17  txqueuelen 1000  (Ethernet)
RX packets 492  bytes 56290 (54.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 577  bytes 57419 (56.0 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap770ee127-d1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::fc16:3eff:fecd:e3c0  prefixlen 64  scopeid 0x20<link>
ether fe:16:3e:cd:e3:c0  txqueuelen 500  (Ethernet)
RX packets 476  bytes 54994 (53.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 587  bytes 58215 (56.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0