hi,
On Wed, Aug 20, 2014 at 1:03 PM, Salvatore Orlando wrote:
> As the original thread had a completely different subject, I'm starting a
> new one here.
>
> More specifically the aim of this thread is about:
> 1) Define when a service is best implemented with a service plugin or with a
> ML2 dri
+1
The agent number should be limited restrictly.
On Thu, Aug 21, 2014 at 8:56 AM, loy wolfe wrote:
>
>
>
> On Wed, Aug 20, 2014 at 7:03 PM, Salvatore Orlando
> wrote:
>
>> As the original thread had a completely different subject, I'm starting a
>> new one here.
>>
>> More specifically the ai
On Wed, Aug 20, 2014 at 7:03 PM, Salvatore Orlando
wrote:
> As the original thread had a completely different subject, I'm starting a
> new one here.
>
> More specifically the aim of this thread is about:
> 1) Define when a service is best implemented with a service plugin or with
> a ML2 driver
I was merely suggesting that this is the approach that we've followed so
far.
The incubator is not even a real thing at the moment, so it's still too
early to make any statement as we do not even know if the stuff in the
incubator will use the same database or not. This is a necessary discussion
to
>From a data model perspective, I believe so if we follow the pattern we've
followed so far.
How will database setup work in this case? IIRC, the auto-generation of
schema was just disabled in a recent merge. Will we have a big pile of
various migration scripts that users will need to pick from de
As the original thread had a completely different subject, I'm starting a
new one here.
More specifically the aim of this thread is about:
1) Define when a service is best implemented with a service plugin or with
a ML2 driver
2) Discuss how bindings between a "core" resource and the one provided
