Re: [Openstack] linuxbridge or open vswitch choice
On Sun, 2018-04-08 at 21:49 +0300, s serge wrote: > Hello, > > Could you please advice a technical decision how to made a choice > between linuxbridge and Open vSwitch for > an OpenStack deployment ? > > While Open vSwitch is more flexible and provides more features, it > also involves additional level of complexity. > > However, are there OpenStack features which can only be utilised > using Open vSwitch functionality or is it implemented > in OpenStack just as an option to choose? > > According to https://www.ibm.com/support/knowledgecenter/en/linuxonib > m/liaag/wkvm/wkvm_c_net_conbridge.htm, > there is no significant difference in the terms of performance, but > Open vSwitch implies more additional attendance to > understand and debug network level. > > I would appreciate a feedback based on real operation and maintenance > experience. In my experience, linuxbridge works very well and is a lot simpler to set up and configure in an environment where other software/hardware is handling the general network configuration (especially if you have experience with using network bridges on Linux KVM deployments). I would go with linuxbridge (especially in a straightfoward setup) unless the additional features of openvswitch are needed. > > Thanks, > Regards, > Serge. > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ope > nstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ope > nstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Neutron unable to create VLAN network
On May 2, 2017, at 2:53 PM, Kaustubh Kelkar mailto:kaustubh.kel...@casa-systems.com>> wrote: VLAN 1 might be treated as the “default” VLAN by your switch. -Kaustubh The issue turned out to be old configuration in the database..after stracing neutron-server, I saw that it was running “SELECT from ml2_vlan_allocations” just after I tried to create the network..after finding that table in the neutron database, it was incorrectly showing that VLANs 1 and 2 were allocated, so that was an easy fix with: mysql> update ml2_vlan_allocations set allocated = '0' where vlan_id = ‘1’; mysql> update ml2_vlan_allocations set allocated = '0' where vlan_id = ‘2'; And now I can create the networks as intended. From: Kevin Benton [mailto:ke...@benton.pub] Sent: Tuesday, May 2, 2017 3:19 PM To: Timothy Geier mailto:tge...@accertify.com>> Cc: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: Re: [Openstack] Neutron unable to create VLAN network That means vlan 1 is in use by one of the other networks. On May 2, 2017 14:59, "Timothy Geier" mailto:tge...@accertify.com>> wrote: I’m doing some testing/PoC on an RDO Ocata CentOS7 setup and everything has gone well with the exception of configuring multiple VLANs. After following the configuration detailed at https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/networking_guide/sec-connect-instance#Using-VLAN-Provider-Networks , neutron errors out with the following: $ neutron net-create 1_network \ --provider:network_type vlan \ --router:external true \ --provider:physical_network extnet \ --provider:segmentation_id 1 --shared Unable to create the network. The VLAN 1 on physical network extnet is in use. extnet is mapped to the OVSbridge br-ex, which has a physical interface that’s trunked to all of the available VLANs..trying this command on the other available VLANs works, but 1 and 2 (the ones I want to test on) always fails. Is there anything obvious to try on the system itself or is this more likely a network issue? Thanks much, ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Neutron unable to create VLAN network
I’m doing some testing/PoC on an RDO Ocata CentOS7 setup and everything has gone well with the exception of configuring multiple VLANs. After following the configuration detailed at https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/networking_guide/sec-connect-instance#Using-VLAN-Provider-Networks , neutron errors out with the following: $ neutron net-create 1_network \ --provider:network_type vlan \ --router:external true \ --provider:physical_network extnet \ --provider:segmentation_id 1 --shared Unable to create the network. The VLAN 1 on physical network extnet is in use. extnet is mapped to the OVSbridge br-ex, which has a physical interface that’s trunked to all of the available VLANs..trying this command on the other available VLANs works, but 1 and 2 (the ones I want to test on) always fails. Is there anything obvious to try on the system itself or is this more likely a network issue? Thanks much, ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
