-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/19/2015 10:54 AM, Bence Romsics wrote:
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
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
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
-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
Hi All,
How do I implement one extension by two plugins?
If I extend the API by:
* a first class resource, and
* attributes to an already existing resource (the port resource in my case).
These two parts don't make sense without each other, so I'd like to
keep this as one extension, not two.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/17/2015 04:35 PM, Bence Romsics wrote:
Hi All,
How do I implement one extension by two plugins?
If I extend the API by: * a first class resource, and * attributes
to an already existing resource (the port resource in my case).
These
