The driver.virt.active and driver.virt.inactive attributes reflect the number of VMs running. But this data is already available to the Nomad servers via Node.UpdateStatus RPCs. Sending it as part of a periodic fingerprint will cause Nomad client nodes to update their fingerprints regularly, kicking off new evaluations for all the jobs on the node.
Note to reviewers: this PR originally had this description:
The driver.virt.inactive attribute was being incorrectly suffixed with "bytes". The names of the fingerprinted fields for the number of active and inactive domains are potentially confusing, as they don't refer to what about the driver is active or inactive. Adjust the name to include domains in such a way that active and inactive domains will sort together.
But then I realized the extra evals we'd be creating. If I'm misunderstanding the purpose of these attributes then I'd suggest we at least take the first commit in this PR.
The
driver.virt.activeanddriver.virt.inactiveattributes reflect the number of VMs running. But this data is already available to the Nomad servers viaNode.UpdateStatusRPCs. Sending it as part of a periodic fingerprint will cause Nomad client nodes to update their fingerprints regularly, kicking off new evaluations for all the jobs on the node.Note to reviewers: this PR originally had this description:
But then I realized the extra evals we'd be creating. If I'm misunderstanding the purpose of these attributes then I'd suggest we at least take the first commit in this PR.