Hi, For 3.6.0, I'm working on improvements for the sampling/monitoring code in VDSM
The sampling/monitoring code is that part of VDSM which periodically checks the state of the VMs (and host also, but that part is out of scope for now), and collect data to be reported to Engine. The point here is "just" to minimize resource consumption and improve scalability, so it can be probabily bluntly summarized as "refactoring" Despite being utterly boring and not-sexy, this change has a quite relevant impact on the VDSM behaviour and architecture. I've collected a summary and some notes here: https://gist.github.com/mojaves/3a917f53cb3151be09da Please bear in mind that the notes are - very terse (and) - very developer-oriented (and) - probably not trivial to grok if one's not following the discussion since the beginning (thus) - these notes are *meant* to spark discussion and bring more interest on the topic So everyone's welcome to contribute! -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
