On Thu, Sep 27, 2012 at 8:36 PM, Ben Pfaff <b...@nicira.com> wrote: > On Fri, Sep 28, 2012 at 11:56:47AM +0900, Tadaaki Nagao wrote: >> In "Re: [ovs-dev] "brctl show" doesn't list attached interfaces", >> Ben Pfaff <b...@nicira.com> wrote: >> > I see datapaths in brctl show output even without brcompat: >> > >> > oot@debian:~# rmmod brcompat >> > Error: Module brcompat is not currently loaded >> > root@debian:~# brctl show >> > bridge name bridge id STP enabled interfaces >> > root@debian:~# ovs-vsctl add-br br0 >> > root@debian:~# brctl show >> > bridge name bridge id STP enabled interfaces >> > br0 0000.d61b592dd94d no >> > root@debian:~# ovs-dpctl show >> > system@br0: >> > lookups: hit:0 missed:0 lost:0 >> > flows: 0 >> > port 0: br0 (internal) >> > root@debian:~# >> > >> > I assumed that was what Isaku meant. >> >> (Though I'm not Isaku ;-), > > Sorry about that. I apologize. > >> what I tried to meant was, as Jesse wrote, OVS ports aren't appearing >> in brctl output. I wasn't clear enough, sorry about it. >> >> Actually, we are trying OVS + KVM + LibVirt + CloudStack. From what I >> heard from my colleague, KVM support code in CloudStack uses "brctl show" >> to list the ports attached to a bridge. Simply changing them to use >> "ovs-dpctl show" would work for us, but I thought it would be better if >> compatibility to Linux bridge is also kept in brctl output. > > It would be better to use "ovs-vsctl list-ports". The output of > "ovs-dpctl show" is an implementation detail that is subject to change > and, in fact, we plan to change soon.
Regardless of the mechanism, it is better to build on the OVS native commands rather than relying on brctl since they are much more robust. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
