Open Stack

Hi,

I'm not sure I need it. :-)

My first idea was, that if two plugins implement an extension together
(neither the new first class resource, nor the new port attributes is
a usable feature in themselves in my case), then it would be nice to
express this.

However thinking a bit more, I believe the only practical difference
between your solution in the qos patches and my first idea is that we
could catch some bad neutron configurations (ie. loading only one of
the two plugins). Which is probably really rare, so it does not seem
to justify the extra complexity. So I will just go with your stuff.
Thanks.

Cheers,
Bence

On Tue, Aug 18, 2015 at 4:02 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 08/18/2015 03:11 PM, Bence Romsics wrote:
>> Hi Ihar,
>>
>> Thank you. Just rebased my patch and following the example of the
>> qos feature now I can start neutron-server with both the service
>> plugin and the ml2 extension driver loaded. However I have noticed
>> that I can no longer mark the extension driver as implementing the
>> extension alias (the 'extension_alias' property seems to be better
>> not used, or I still have the same error). Is that intentional?
>>
>
> I think the assumption is that only one plugin is capable of
> implementing an extension. We only allowed to implement no extensions
> at all. If you think we should allow multiple plugins to claim support
> for the same extension, then it's an additional use case on top of
> what we needed in qos. Why do you need it?
>
> BTW feature/qos was merged in master yesterday, so it's now available
> for all patches.
>
> Ihar
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJV0zrZAAoJEC5aWaUY1u57DIAIAJG+U3sVI/ejvEmETEtbINH+
> mm8IFhpwoSzMNcRKfrlobgmu4R/+saGfQsUaQHjh4ko7PVq2eDH9sMPlHjVZXUGi
> x5Rt7gKuFCXsPLyXybjAaaWQjI/hO65/V7D1xwQceRl9FL6kSjgxoasu5ufGUR4j
> ZMmp0f9nN8v7VVHynhLq0FEYMqMs0fylO2hnyJKyJUk26Xd1GZqv/58jAl6RaB3Z
> LzE6Qd6yO0R4ekEhL4DhBbf3+J59ljDhgCbCvScKiL83IZb0FT4vcYMvuHIKezHt
> c23ImDJjz9ZCCld0ah39/jEcqOWj8IM41L/1Qjwdk/Fn/s1CUtFY1vJ28z8IOgg=
> =rMZ7
> -----END PGP SIGNATURE-----
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev