[one-users] V4.4: Bridge Configuration/physical device attach in VLAN driver on existing bridge
Jaime Melis
jmelis at opennebula.org
Wed Feb 5 05:35:19 PST 2014
Hi Michael,
I've closed the ticket I created for your contribution:
http://dev.opennebula.org/issues/2574
I've explained my reasoning there, I basically think there's something you
might be overlooking and that the patch is not required. Could you please
take a look and let me know what you think?
cheers,
Jaime
On Wed, Dec 18, 2013 at 4:14 PM, Jaime Melis <jmelis at c12g.com> wrote:
> Hi Michael,
>
> thanks for the contribution!
>
> I've just create a ticket to evaluate it for OpenNebula 4.6:
> http://dev.opennebula.org/issues/2574
>
> Cheers,
> Jaime
>
>
> On Fri, Dec 13, 2013 at 11:02 AM, Michael Kutzner <
> michael.kutzner at virtion.de> wrote:
>
>> Hello,
>>
>> we had some problems in the past deploying VMs when a bridge interface was
>> already existing (static configuration e.g.) using a different interface
>> as
>> physical than defined in the virtual network in ON.
>>
>> Example:
>> - A bridge br10 was existing with a local interface eth0 attached.
>> - The virtual network in opennebula was configured to use eth1.
>> (due to some historical or physical reasons eth0 was used on that host
>> and the bridge was "preconfigured")
>>
>> The ON driver (opennebula-4.4.0/src/vnm_mad/remotes/802.1Q/HostManaged.rb)
>> now checks the following:
>> - bridge exists: no, create bridge
>> This works fine as the bridge is already existing
>> - device is attached?
>> No, attach it (so we have eth0 and eth1 attached to the bridge
>> interface afterwards)
>> This leads to some small (or bigger) problems (e.g. creating a loop on
>> the switches and making
>> the network practically unusable).
>>
>> Attached you find a small patch which does the following:
>> - bridge exists?
>> Yes, do nothing
>> - no: create bridge, add interface
>>
>> This will also cover the scenario that you can change the physical device
>> in the virtual
>> network definition after having deployed certain VMs.
>>
>> Hopefully I did it right and made the changes in the right place.
>>
>> I dont know, if anybody else had that problem, but I wanted to share this
>> information.
>>
>> Best, Michael
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> Jaime Melis
> C12G Labs - Flexible Enterprise Cloud Made Simple
> http://www.c12g.com | jmelis at c12g.com
>
> --
>
> Confidentiality Warning: The information contained in this e-mail and
> any accompanying documents, unless otherwise expressly indicated, is
> confidential and privileged, and is intended solely for the person
> and/or entity to whom it is addressed (i.e. those identified in the
> "To" and "cc" box). They are the property of C12G Labs S.L..
> Unauthorized distribution, review, use, disclosure, or copying of this
> communication, or any part thereof, is strictly prohibited and may be
> unlawful. If you have received this e-mail in error, please notify us
> immediately by e-mail at abuse at c12g.com and delete the e-mail and
> attachments and any copy from your system. C12G's thanks you for your
> cooperation.
>
--
Jaime Melis
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | jmelis at opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140205/a5bffa8e/attachment.htm>
More information about the Users
mailing list