[quagga-dev 12597] Re: [PATCH v3 00/22] VRF support in quagga

Andrew Qu andrew.qu at mediatek.com
Mon Jun 1 18:51:41 BST 2015

Hi Paul,

Would be possible to hold a conference for this topic?



===================== ignore whatever attached after this line ========

-----Original Message-----
From: Paul Jakma [mailto:paul at jakma.org] 
Sent: Monday, June 01, 2015 8:59 AM
To: David Lamparter
Cc: Donald Sharp; quagga-dev at lists.quagga.net
Subject: [quagga-dev 12596] Re: [PATCH v3 00/22] VRF support in quagga

On Mon, 1 Jun 2015, Paul Jakma wrote:

> How, if you are required to be able to support *ONE* Zserv instance 
> for
> *ALL* VRFs (as we would be if we take this patch train as it stands), 
> would you implement that using a zebra process per VRF in a 
> non-horrific way?

I.e., in order to assauge my review comments, either:

Explain how the above will work to me.


Make the single-daemon approach use a separate ZServ instance per VRF (e.g. a different socket for each VRF on the zebra side, /var/run/quagga/zserv.$VRF.api for VRF>0 say, or whatever). This API it seems to me might be easier to implement by /either/ way.


Be up-front about the fact that the approach of this patch set may cause 
significant problems for anyone who later tries to implement 
multiple-daemons - potentially a blocker. (Because it was presented with 
claims that it doesn't stop the other way at all - though it seems to me 
it does, at least until someone answers the quoted question).

Paul Jakma	paul at jakma.org	@pjakma	Key ID: 64A2FF6A
More are taken in by hope than by cunning.
 		-- Vauvenargues

Quagga-dev mailing list
Quagga-dev at lists.quagga.net
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any 
attachments) may be confidential, proprietary, privileged, or otherwise
exempt from disclosure under applicable laws. It is intended to be 
conveyed only to the designated recipient(s). Any use, dissemination, 
distribution, printing, retaining or copying of this e-mail (including its 
attachments) by unintended recipient(s) is strictly prohibited and may 
be unlawful. If you are not an intended recipient of this e-mail, or believe 
that you have received this e-mail in error, please notify the sender 
immediately (by replying to this e-mail), delete any and all copies of 
this e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person. Thank you!

More information about the Quagga-dev mailing list