On 15 June 2015 at 19:34, Sam Su <[email protected]> wrote: > Hi stackers, > > > > I am going to implement a Neutron plugin, however when I checked the > current Neutron code(master) structure, I found there are two way to > organize a Neutron plugin: > > 1. The first one is implement all L2 and L3 functions under the > folder ../neutron/plugins/xxx, e.g. vmware, plumgrid, and ibm… > > 2. The second way is put L2 functions on the folder > ../neutron/plugins/ml2/drivers/xxx and put L3 funtions on the folder > ../neutron/services/l3_router/xxx, e.g. brocade, cisco. > > > > If my understanding is correct, which way is more desirable for a neutron > plugin? If I am wrong, what is a neutron plugin code structure? > > > > Any help will be much appreciated! >
These requests are better directed to the -dev ML. Anyway, both structures are perfectly fine, and they both have pros and cons. Check out these resources that might help you decide: [1] https://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-videos/presentation/how-to-write-a-neutron-plugin-if-you-really-need-to [2] https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst HTH Armando > > > Thanks, > > Sam > > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
