[Ovirt-devel] Enumerating node information to the WUI

[Darryl L. Pierce]

Chris Lalancette wrote:
>> 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.
> 
> Well, this is kind of interesting.  After thinking about it some, having the
> additional CPU information would be worthwhile.  It won't necessarily help
> taskomatic make better decisions at this point, but if we add SLA's for "start
> on a Barcelona processor" or whatever in the future, this stuff could be useful.
>  A record-per-cpu might be overkill, though; one CPU record per host might be
> enough.

There's no chance that a single system might have two different (on some 
level) physical CPUs?

Something else that came to mind is monitoring CPU state. Probably 
outside of the identify stage, but would there be a benefit to being 
able to periodically ping the CPUs and check things like temperature and 
load? If one is running too hot or heavy, it would be a benefit to shut 
it down or spin up a separate instance or at least track that detail 
over time.

Thoughts?

<snip mem>

>> DISK: Returning the physical and logical partitions with free space 
>> available.
> 
> Hard to say.  We've been going with the idea of totally diskless machines until
> now, with totally remote storage.  That being said, if we are going to support
> other things in the future (like Xen), we will need some sort of stuff for
> disks.  This needs more thought; I would punt on this one for now until we
> better understand our requirements for local disks.

Okay, sounds good.

>> NETWORK: Iterating over the physical interface adaptors. Also returning 
>> any IP addresses already assigned and routing information.
> 
> Yes, definitely.  Along with this is a total DB schema redesign of the network
> parts, since it is pretty bad right now.  This also goes hand-in-hand with
> apevec's "boot-time" changes; basically, you start up, DHCP on one interface,
> fetch your network configuration information from the WUI, and then re-configure
> your interfaces based on the config info.  More thought needs to go into how
> this initial "auto-discovery" phase fits in with that plan.

Okay.

Is there a master backlog for the managed node where we can capture this 
stuff?

-- 
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?"