[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] Re: [PATCH] Remove bond-slave filter from PIF.scan


  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: Ben Pfaff <blp@xxxxxxxxxx>
  • Date: Fri, 04 Jun 2010 09:51:22 -0700
  • Cancel-lock: sha1:RN6N3cL0Y1pNIgOCnE7JCB/c7PM=
  • Connect(): No such file or directory
  • Delivery-date: Fri, 04 Jun 2010 09:55:23 -0700
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Rob Hoes <rob.hoes@xxxxxxxxxx> writes:

> This filter uses sysfs to find out whether an interface is a
> bond slave. This does not work when the openvswitch backend is
> used. Besides, it does not seem to be necessary (anymore?)
> anyway.
>
> PIF.scan creates a new PIF for each interface it finds if this
> interface is physical and there is no PIF with the same
> MAC. The slave interfaces always have the same MAC as the bond
> master PIF (bridging backend) or their "real" MACs as stored in
> their PIFs (openvswitch backend). Therefore, when a bond is in
> effect, the MACs of all bond slaves have corresponding PIFs in
> the DB, so PIF.scan won't create new ones.

Makes sense to me.

Acked-by: Ben Pfaff <blp@xxxxxxxxxx>


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.