Please see one additional comment at the end... On Nov 6, 2013, at 2:53 AM, Michael MacFaden <[email protected]> wrote:
>>> Virtual Machine Processor >> >>> ProcessorUserTime CPU time spent on user processes (milliseconds) >>> ProcessorSysTime CPU time spent on system processes >>> (milliseconds) >> What's the difference between these two time metrics? > > Breakdown between apps and OS, can be code running in priviledged processor > mode vs non as well. Helps to know if a driver is going nuts or some web > service. > >> Are they user-time and system-time at a guest OS? > > Yes All of these items presented are about either the Virtual Machine or code > running in the > virtual machine. > > >>> Virtual Machine Processes >>> PID Process ID >>> ProcessName ProcessName >>> ProcessParam ProcessParameters >>> ProcessCPUUsage ProcessCPUUsage >>> ProcessMemoryUsed ProcessMemoryUsage > >> Do you mean they are processes on a guest OS? > > Yes, they want that. > >> If the objects above are those of a guest OS, they need a special tool such >> as vmware tools installed to the guest OS. So, MIB modules on guest OSes, >> such >> as HOST-RESOURCES-MIB, could be used. > > Yes, that's one way. There could be others. More typically there will be > SNMP agent running in the Guest OS that is polled separately and/or have an > entry in ENTITY-MIB with hypervisor is another way. > >> The following objects are also related to guest OSes. >>> Virtual Machine Partitions >>> PartitionLabel disk path (c:\, /boot, etc) >>> PartitionCapacity capacity of the disk in bytes >>> PartitionUsedSpace capacity minus freespace >>> PartitionUtilization used as a percentage of capacity >> >> Some of them might be recognizable from hypervisor. The partition format >> itself does not vary by guest OS (i.e., MBR or GPT partition), so some of >> these might be able to available from hypervisor. However, I still don't >> think >> VM-MIB is the appropriate place to contain these objects, and it is better >> to use >> MIB modules on guest OS (e.g., HOST-RESOURCES-MIB). Moreover, >> PartitionLabel, PartitionUsedSpace, and PartitionUtilization are information >> on file system, then a hypervisor cannot recognize them without any special >> tools such as vmware tools. > > Makes sense to me. In fact I'd prefer if there was prose in the MIB to > explain all how and where we recommend they look for these items. A good proposal. A number of earlier MIB Documents contained a section call "Relationship to other MIBs". That would be a good way to address this. > > Regards, > Mike MacFaden > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg Jon Saperia Enterprise Architect Harvard University Information Technology Innovation & Architecture (M) (617) 201-2655 (P) (617) 384-6683 1350 Mass Ave., room 758 Cambridge, MA 02138
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
