Hi Nikolay, The memory and cpu are numeric attributes managed by the core, initialized to 0. If the driver doesn't report them, they are not updated.
The way I see it, the drivers didn't know how to populate the values, rather than encounter an error monitoring them. We could modify the core to initialize them with -1, and make the CLI show 'unk' or '-'. But to me it makes more sense to report always a positive value, since the data can be consumed by other applications, and dealing with the special case of -1 (or 'err' if the data is read from the onevm output) can introduce bugs. Regards. -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org <http://www.opennebula.org/> | cmar...@opennebula.org ---------- Forwarded message ---------- From: <kna...@gmail.com> Date: Wed, May 11, 2011 at 6:19 PM Subject: [one-users] '-' or 'err' (instead of 0) as a value for parameters which ONE fails to get To: users <users@lists.opennebula.org> Hi! ONE shows 0 (zero) as a value for those parameters which it fails to retrieve. For example, $ onevm list ID USER NAME STAT CPU MEM HOSTNAME TIME 39 oneadmin one-39 runn 0 0K <host1> 01 04:02:29 40 oneadmin vps145 runn 0 0K <host2> 00 08:23:28 I wonder if it wouldn't be more reasonable to show '-' or 'err' instead of 0? Sorry if that question has been already asked before (I couldn't found anything similar). Regards, Nikolay. _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org