On May 3, 2013, at 1:27 PM, yulin...@dell.com wrote: > Hi All, > > I was wondering if anyone could help me with a question related to the > guideline of Quantum plugin development. > > Let's say if we need to develop a quantum plugin and we would need to use OVS > plugin in our plugin. Is it a good practice to change the code of OVS plugin > when we need to, or we should preserve the OVS plugin and only add code on > top of it? > > Or in another word, if we would need to contribute back our quantum plugin to > OpenStack, will there be any issue if we changed OVS plugin in our solution? > Bob Kakura is developing something called the Module Layer2 Plugin (https://blueprints.launchpad.net/quantum/+spec/modular-l2) which may be what you want to use here. In general, if you're adding functionality to the OVS plugin, that would likely be ok. But if you're attaching anything vendor specific to it, I would expect some pushback from the community, given the OVS plugin is the default plugin most people use. Perhaps knowing a bit more about what you're doing would help in answering this with more certainty.
Thanks, Kyle > Thanks, > > YuLing > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
