On 01/21/2013 03:30 PM, Salvatore Orlando wrote:
Hi guys,
while I am doing progress on the implementation of this blueprint, I
realized something which might be a blocker for it.
It seems indeed that the bigswitch and cisco plugins do not support
the L3 APIs; moving them into core will therefore violate one of
Quantum principles, ie: the core API should be the smallest set of
APIs supported by all the plugins.
The NVP plugin has the same issue, but this is currently being
addressed by another blueprint targeting Grizzly-3.
I think Sumit and Edgar are respectively the maintainers for these
plugins; at a first glance I do not see plans for adding Layer-3
support in the Grizzly release.
If that is the case, I suggest postponing moving l3 apis into Quantum
core to the next release, just as we did for the provider networks
API.
What are your thoughts?
I think that we are between a rock and a hard place. It would be great
if the aforementioned could be moved into the core API. I think that
there are a number of areas that we need to address:
1. timing
2. plugin support
Regarding the timing the sooner in a series that this is done the
better. If we decide to go ahead with this in this cycle then we will
need to make sure that we have the resources allocated to review and test.
The plugin support is interesting and challenging. An alternative that
may be worth considering is moving it to the core and return
"NotSupported" if the plugin does not support the API (this can be done
via a configuration variable).
Thanks
Gary
Regards,
Salvatore
--
Mailing list: https://launchpad.net/~quantum-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp
