Hi Salvatore,

Thanks for bringing this up. We do have plans for supporting L3 API
extensions in Grizzly. The blueprint was created earlier and work is
currently under way to submit a patch:
https://blueprints.launchpad.net/quantum/+spec/quantum-floodlight-bigswitch-l3

That said, I don't have any objections with your suggestion of
postponing moving L3 apis into Quantum core to the next release.

Thanks,
~Sumit.


On Mon, Jan 21, 2013 at 5:30 AM, Salvatore Orlando <sorla...@nicira.com> 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?
>
> Regards,
> Salvatore
>
> --
> Mailing list: https://launchpad.net/~quantum-core
> Post to     : quantum-core@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~quantum-core
> More help   : https://help.launchpad.net/ListHelp

-- 
Mailing list: https://launchpad.net/~quantum-core
Post to     : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to