HI Armando,
I opened a launchpad bug [1]. I'll try to propose a patch on one of
the service plugin to enable plugable backend driver.
I'll look how we can add tests to check service plugin works with a
dummy core plugin not based on the Neutron model.
[1]
On 22 June 2017 at 17:24, Édouard Thuleau wrote:
> Hi Armando,
>
> I did not opened any bug report. But if a core plugin implements only
> the NeutronPluginBaseV2 interface [1] and not the NeutronDbPluginV2
> interface [2], most of the service plugins of that list will
Hi Armando,
I did not opened any bug report. But if a core plugin implements only
the NeutronPluginBaseV2 interface [1] and not the NeutronDbPluginV2
interface [2], most of the service plugins of that list will be
initialized without any errors (only the timestamp plugin fails to
initialize
On 21 June 2017 at 17:40, Édouard Thuleau wrote:
> Hi,
>
> @Chaoyi,
> I don't want to change the core plugin interface. But I'm not sure we
> are talking about the same interface. I had a very quick look into the
> tricycle code and I think it uses the
On 20 June 2017 at 00:09, Kevin Benton 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
Hi,
@Chaoyi,
I don't want to change the core plugin interface. But I'm not sure we
are talking about the same interface. I had a very quick look into the
tricycle code and I think it uses the NeutronDbPluginV2 interface [1]
which implements the Neutron DB model. Our Contrail Neutron plugin
Why not just delete the service plugins you don't support from the default
plugins dict?
On Wed, Jun 21, 2017 at 1:45 AM, Édouard Thuleau
wrote:
> 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
] [neutron] Do we still support core plugin not
based on the ML2 framework?
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
you think?
But it will needs some
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
you think?
But it will needs some time and not sure we'll be able to fix all
service plugins loaded by
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
Oops, sent too fast, sorry. I try again.
Hi,
Since Mitaka release, a default service plugins list is loaded when Neutron
server starts [1]. That list is not editable and was extended with few services
[2]. But all of them rely on the Neutron DB model.
If a core driver is not based on the ML2
Hi,
Since Mitaka release [1], a default service plugins list is loaded
when Neutron server starts. That list is not editable and was extended
with few services [2]. But none of th
[1]
12 matches
Mail list logo