Re: [Openstack] Specification of nova-diagnostics

2012-03-29 Thread Leander Bessa
Ok, so far i have been able to generate the following output: +---+-+ | Property |Value| +---+-+ | cpu0 | 0.0 | | cpu1 | 0.0 | | memory| Unavailable | | vda_bytes_read

Re: [Openstack] Specification of nova-diagnostics

2012-03-27 Thread Diego Parrilla SantamarĂ­a
I'm not familiar with nova-diagnostics, but we use collectd to gather information about each virtual machine running in KVM. We get information about cpu usage, memory, disk io, and network io per instance. Obviously it's not nicely integrated with nova commands, but it works in our deployments.

Re: [Openstack] Specification of nova-diagnostics

2012-03-27 Thread Leander Bessa
I was hopping to find out more as well, since the only information i currently have comes from nova help diagnostics. It would be interesting to work since this appears to be hypervisor agnostic and would allow for the development of a monitoring tool which fetches its information solely from the

[Openstack] Specification of nova-diagnostics

2012-03-26 Thread Leander Bessa
Hello, I've been trying to implement the nova-diagnostics command for libvirt. I'm using the devstack installation on ubuntu 12.04. So far i've managed to gather information regarding CPU, IO (network and disks). The memory reading only works with the virsh command and does not report the actual