On Mon, 2010-01-25 at 15:33 -0800, C.J. Adams-Collier wrote:

On Mon, 2010-01-18 at 13:46 -0800, C.J. Adams-Collier wrote:

...

Hey Dan, list,

It seems to me that virt-manager could do with more information about the virtual network devices, the DHCP leases on them, maybe a view of the arp table, etc.

To this end, I've abused Dan's .glade file a bit and put some stub code in virtManger/host.py

Could I get some comments and some recommendations for next steps? It's been a while since I've done any glade'ing...

Cheers,

C.J.

17:09 < cjac> danpb: what do you think about a new .glade file for network properties? 17:13 < danpb> you mean for virt-manager ? 17:14 < cjac> danpb: yeah, that. didn't you get my email? :) 17:16 < danpb> best to send those kind of ideas to the virt-tools mailing list 17:16 < danpb> i'm not really involved with virt-manager recently 17:16 < cjac> ah, virt-tools.

I asked the virt-tools folks, and they mentioned that they get their information exclusively from libvirt. If I want to show arp table info, I need to implement retrieval in libvirt.

Would any of you be able to help me sketch out some extensions to libvirt to give some feedback about the virtual network interface? It would also be nice to have a way to remotely manage the device. It might be a bit too far-reaching, but quagga might be a good way to provide such remote management.

Thoughts?

C.J.

It looks like quagga doesn't provide any switch management tools, only route management. I'm taking a sick day to take care of the family, so I may have some time to poke at this after I fix up the ironruby .debs Cheers, C.J.