libvirt can pull hard cpu stats. which can be useful. for instance it can pick out the cpu generation names.
-matt On Tue, May 22, 2012 at 2:32 PM, Doug Hellmann <[email protected]>wrote: > > > On Tue, May 22, 2012 at 4:35 PM, James R Penick <[email protected]>wrote: > >> >>-> In addition to a signature, I think we would need a sequence number >> >>to be embedded by the agent for each message sent, so that loss of >> >>messages, or forgery of messages, can be detected by the collector and >> >>further audit process. >> >> >OK. We have a message id, but I assumed those would be used to eliminate >> >duplicates so this sounds like something different or new. It implies >> >that the agent knows its own id (not hard) and keeps up >with a sequence >> >counter (more difficult, though not impossible). >> >Did you have something in mind for how to implement that? >> >> >> If we're submitting messages every given node with a predictable >> frequency, we should be able to determine that a message was lost simply >> by noting a gap in the timestamps. Also, if we're sending cumulative >> statistics then the loss of a single message (or even a fair number of >> them) shouldn't impact our ability to meter too much. >> > > I don't know if we have cumulative statistics. What does libvirt actually > give us? > > >> >> -James >> >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
