[openstack-dev] [neutron] Do we still support core plugin not based on the ML2 framework?
edouard.thuleau at gmail.com
Wed Jun 21 08:45:30 UTC 2017
Ok, we would like to help on that. How we can start?
I think the issue I raise in that thread must be the first point to
address and my second proposition seems to be the correct one. What do
But it will needs some time and not sure we'll be able to fix all
service plugins loaded by default before the next Pike release.
I like to propose a workaround until all default service plugins will
be compatible with non-DB core plugins. We can continue to load that
default service plugins list but authorizing a core plugin to disable
it completely with a private attribut on the core plugin class like
it's done for bulk/pagination/sorting operations.
Of course, we need to add the ability to report any regression on
that. I think unit tests will help and we can also work on a
functional test based on a fake non-DB core plugin.
On Tue, Jun 20, 2017 at 12:09 AM, Kevin Benton <kevin at benton.pub> wrote:
> The issue is mainly developer resources. Everyone currently working upstream
> doesn't have the bandwidth to keep adding/reviewing the layers of interfaces
> to make the DB optional that go untested. (None of the projects that would
> use them run a CI system that reports results on Neutron patches.)
> I think we can certainly accept patches to do the things you are proposing,
> but there is no guarantee that it won't regress to being DB-dependent until
> there is something reporting results back telling us when it breaks.
> So it's not that the community is against non-DB core plugins, it's just
> that the people developing those plugins don't participate in the community
> to ensure they work.
> On Mon, Jun 19, 2017 at 2:15 AM, Édouard Thuleau <edouard.thuleau at gmail.com>
>> Oops, sent too fast, sorry. I try again.
>> Since Mitaka release, a default service plugins list is loaded when
>> server starts . That list is not editable and was extended with few
>> . But all of them rely on the Neutron DB model.
>> If a core driver is not based on the ML2 core plugin framework or not
>> based on
>> the 'neutron.db.models_v2' class, all that service plugins will not work.
>> So my first question is Does Neutron still support core plugin not based
>> on ML2
>> or 'neutron.db.models_v2' class?
>> If yes, I would like to propose two solutions:
>> - permits core plugin to overload the service plugin class by it's own
>> implementation and continuing to use the actual Neutron db based services
>> - modifying all default plugin service to use service plugin driver
>> framework , and set the actual Neutron db based implementation as
>> default driver for services. That permits to core drivers not based on the
>> Neutron DB to specify a driver. We can see that solution was adopted in
>> networking-bgpvpn project, where can find two abstract driver classes, one
>> core driver based on Neutron DB model  and one used by core driver not
>> on the DB  as the Contrail driver .
>> On Mon, Jun 19, 2017 at 10:47 AM, Édouard Thuleau
>> <edouard.thuleau at gmail.com> wrote:
>> > Hi,
>> > Since Mitaka release , a default service plugins list is loaded
>> > when Neutron server starts. That list is not editable and was extended
>> > with few services . But none of th
>> > 
>> > https://github.com/openstack/neutron/commit/aadf2f30f84dff3d85f380a7ff4e16dbbb0c6bb0#diff-9169a6595980d19b2649d5bedfff05ce
>> > 
>> > https://github.com/openstack/neutron/blob/master/neutron/plugins/common/constants.py#L43
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev