[libvirt] [PATCHv2 0/9] Let libvirt manage a bridge's FDB

[Laine Stump]

On 12/04/2014 04:56 AM, Daniel P. Berrange wrote:
> On Thu, Dec 04, 2014 at 03:56:53AM -0500, Laine Stump wrote:
>> Maybe the problem is that you're providing a good name based entirely on
>> the differences in behavior the guests can see, but what I'm looking for
>> is a way to control how that behavior is provided, so more of a backend
>> thing. (Note that if the "backend" is the bridge module, "static" isn't
>> possible now and never will be, while if the backend is explicit
>> management by libvirt, then "dynamic" isn't currently available, but
>> will be in the future).
> So perhaps more along the lines of  macTableManager="kernel|libvirt"

As long as there are no issues with using the name of libvirt as the
value of an XML attribute, then that sounds good to me! (For some reason
I'd been consciously avoiding doing that, maybe some misguided attempt
to follow the "names should be generic" guideline. But in this case I
think that really is the most accurate description of what is being done.)

Thanks for your voice of reason! (there is no place that I second guess
myself more than the *name* of new features.)

Unless there are objections, I will respin with that naming (with
default being "kernel", subject to change sometime in the future when
the functionality of the two is deemed equivalent).