Ovirt devel - Jun 2008 - Enumerating node information to the WUI

I've been working on the enumeration piece (ovirt-identify-node) to 
submit node information to the aggregator service on the server.

Currently the system works as follows:

1. managed node starts
2. when /etc/init.d/ovirt runs the managed node runs ovirt-awake to 
announce that the node is now awake and fetches the keytab from the server.
3. next the node runs ovirt-identify-node, which submits the hardware 
information. Currently the pieces are UUID, ARCH, MEMSIZE, NUMCPUS and 
CPUSPEED, all collected from libvirt APIs.

My question to the project is what details does the WUI need beyond the 
above when the managed node identifies itself?

-- 
Darryl L. Pierce, Sr. Software Engineer
Red Hat, Inc. - http://www.redhat.com/
oVirt - Virtual Machine Management - http://www.ovirt.org/
"What do you care what other people think, Mr. Feynman?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dpierce.vcf
Type: text/x-vcard
Size: 319 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20080617/927ae638/attachment.vcf>

Darryl L. Pierce wrote:
> My question to the project is what details does the WUI need beyond the 
> above when the managed node identifies itself?
I've been looking at some system details that might be of interest to 
the WUI/admin when deploying virtual machines.  Particularly, I've been 
looking at CPU, memory, disk and network details, though there may be 
other elements that we'd want to pull from the managed node as it's 
coming up. At any rate, what would seem to be of interest are:

CPU: the family, model, cpuid level, cache size, number of cores and the 
set of CPU flags. This would give us a nice idea of the individual CPU's 
capabilities.

As a result, we'd want to refactor the hosts table a bit. Rather than 
capturing as a column the number of CPUs, we could get that implicitly 
by having a record-per-cpu for the host. Then each row would capture the 
important details from above.

MEM: We currently return the total system memory reported but should 
probably also grab the free memory after the managed node image is loaded.

DISK: Returning the physical and logical partitions with free space 
available.

NETWORK: Iterating over the physical interface adaptors. Also returning 
any IP addresses already assigned and routing information.

Questions? Comments?

-- 
Darryl L. Pierce, Sr. Software Engineer
Red Hat, Inc. - http://www.redhat.com/
oVirt - Virtual Machine Management - http://www.ovirt.org/
"What do you care what other people think, Mr. Feynman?"