Hello. I'm looking for the way of LinuxBridge setup for openstack neutron networking instead of ML2 VLAN/VXLAN/GRE like your reason, and you seems successfully deployed the environment.
Could you give me any advice for the deployment? I'm now deploying openstack 3 nodes (actually, I attached another compute, so my current deployment setup is 4nodes, i.e., 1 controller, 1 network, and 2 computes) by following the openstack installation guide, http://docs.openstack.org/kilo/install-guide/install/yum/content/neutron-controller-node.html. I think several options in /etc/nova/nova.conf, /etc/neutron/plugins/ml2/ml2_conf.ini and /etc/neutron/neutron.conf should be modifed properly in order to use LinuxBridge instead of OVS. Here are the lists what I know to modify: 1. /etc/neutron/neutron.conf on controller core_plugin = ml2 (I think this should be modified but I don't know what parameter indicates Linux Bridge Agent Plugin) 2. /etc/neutron/plugins/ml2/ml2_conf.ini on controller Do I still need to modify this file? I'm confused, because the file name is 'ml2', which is for ml2 plugin not for 'linux bridge'... And, I wonder the lists should be modified. Thank you in advance! Regards Byeong-Gi KIM 2015-04-21 7:19 GMT+09:00 Martinx - ジェームズ <thiagocmarti...@gmail.com>: > Hi James! > > On 20 April 2015 at 18:16, James Denton <james.den...@rackspace.com> > wrote: > >> Hi Thiago, >> >> VXLAN requires an IP address on each host from which to build the overlay >> mesh between hosts. Some choose to use a dedicated interface/IP/VLAN for >> this, but its not required. >> > > Sure, I'm aware of that. > > What is new for me, is that when using "VXLAN + OpenvSwitch", plains VLANs > are not required but, when using "VXLAN + LinuxBridges", then, you'll need > plain VLANs as well (and this is new for me). > > >> >> As for ‘vconfig’ missing - It appears that the 'ip link’ command >> (iproute2) is being used instead to create vlan interfaces. >> > > Okay, cool! I'll take a look on that. > > Thank you! > > >> >> James >> > > Thiago > > >> >> On Apr 17, 2015, at 10:26 PM, Martinx - ジェームズ <thiagocmarti...@gmail.com> >> wrote: >> >> Perfect! I followed the Juno documentation here: >> >> >> http://docs.openstack.org/juno/install-guide/install/apt/content/ch_preface.html >> >> But I have "VXLAN + LinuxBridges", instead of "GRE + OVS", pretty cool! >> >> I was doing it wrong (of course), I did not realized that VXLAN with >> LinuxBridges, required plain VLANs to work (Is that right?)... >> >> Nevertheless, I still do not fully understand this setup, since the >> "vlan" package and its "vconfig" binary, is not even installed at my >> Network Node, also, there is nothing at my "/proc/net/vlan...". >> >> So, how it is working? lol >> >> Good challenge for the weekend to figure this out! ^_^ >> >> Cheers! >> Thiago >> >> On 17 April 2015 at 23:30, Martinx - ジェームズ <thiagocmarti...@gmail.com> >> wrote: >> >>> BTW, I just found this: >>> >>> https://github.com/madorn/vagrant-juno-linuxbridge-vxlan-vlan >>> >>> The problem is that it is for VirtualBox or VMWare, and I'm using >>> exclusively KVM these days... :-/ >>> >>> But, I believe it will help me anyway... =P >>> >>> On 17 April 2015 at 22:01, Martinx - ジェームズ <thiagocmarti...@gmail.com> >>> wrote: >>> >>>> Hey guys, >>>> >>>> Where can I find a complete documentation to make use of LinuxBridges, >>>> instead of OpenvSwitch, when using it with VXLAN? >>>> >>>> I faced too many problems with OVS in the past (also these days) and >>>> now, even Rackspace deploys their RPC v9 and v10 with LinuxBridges but, >>>> where are the documents? >>>> >>>> I'm reading now, the following Ansible files, to try to figure this >>>> out: >>>> >>>> https://github.com/stackforge/os-ansible-deployment >>>> >>>> But, this isn't a documentation... :-P >>>> >>>> The current Juno documents only explain GRE + OVS but, this setup is >>>> unstable and slow. >>>> >>>> Cheers! >>>> Thiago >>>> >>> >>> >> _______________________________________________ >> 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 >> >> >> > > _______________________________________________ > 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 > >
_______________________________________________ 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