Paul,
I'm not sure but I think there may be some mixing of ideas implicit
in your mail, but perhaps I'm just miss reading things.
On 10/19/2015 7:46 AM, Paul Jakma wrote:
> On Mon, 19 Oct 2015, Nicolas Dichtel wrote:
>
>> I think so.
> Ok, I'll queue that with an ACK from you, assuming it complemented the
> VRF_UNREGISTER Zserv message (I don't remember right now). :) If not, I'll
> resend you something.
>
>> I'm not sure that this part must be handled by quagga. Setting up
>> namespaces is part of the global configuration. You will have to put
>> some interfaces inside and maybe configure firewall or ipsec. It's like
>> interfaces: quagga is not in charge of creating them.
> If we want a cohesive UI or API around the running of daemons, and what is
> responsible for which VRFs, there's going have to be something that at
> least takes care of co-ordinating running the right daemons in the right
> VRFs with the right arguments and/or sending them the required initial
> information.
>
> Whether that something creates the namespace directly, or co-ordinates
> with something that does, or is run by something that did, or indeed runs
> the thing will (e.g. a script), it must be there.
>
> Is it satisfying if our answer to "does Quagga do VRFs?" is "yeah, if you
> write a shell-script to set them up, run the daemons in each, ignore the
> 'vrf' commands in zebra; or else do your own stuff and hack to suit"?
>
> regards,
What your describing here sounds like logical routers vs VRFs. Referring
back to
https://lists.quagga.net/pipermail/quagga-dev/2015-October/013382.html ,
I think/agree that both types are desirable and possible; with one
possible today and the other newly enabled in mainline. I also
completely agree that we'll need new CLI commands and conventions and am
happy to see you kicking off this discussion.
My hope is that the next release would provide support in at least zebra
and provide a platform of for those of us interested in doing multi-VRF
protocol work.
Cheers,
Lou
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
