Comment 4 for bug 1517146
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The way I understand this, is that you'd want the linuxbridge agent to supported a custom environment where you run proprietary technology. There can be similarities where, right now, you are making small changes to the upstream LB agent to allow your solution to work with the upstream tools (without forking). But this strategy is a slippery slope and it gives you the least flexibility because later on you might realize that more is needed and more changes have to go upstream...when is this going to end, or where do we draw the line?
For this reason, I think is dangerous contemplating the idea that an open source tool designed with certain assumptions in mind (stock upstream vanilla components) can work with proprietary (accelerated) components.
Right now, I believe this is a distraction to all the other initiatives that revolve around LB and OVS, and for this reason I am against it.