I can't wait to see how it end up working. In the example I showed it has partitioned hardware along with virtualization with solaris zones. You could really use it to represent any way of carving up a physical server, including grouping or clustering. With a simple VMware server you'd only have two layers, the outer shell would be the server running ESX with guests where my lz (local zones) are. Or maybe you have a cluster of hosts, in that case the outer layer would be the Group name with the next layer in the physical server, like the dom layer in my example. Just bouncing ideas around. On Jan 14, 2011, at 1:51 PM, Mills, Matt wrote: > From what I've seen of Aarons code I believe it will be applied more > generically then just Virtualization (I plan on using it for Blade servers / > switches). An interface designed on the parent/child relationship would > probably be best. We would probably be able to apply at least parts of such > an interface to the Location parenting patch that I am working on as well > (Site -> Room -> Row -> etc) > > Thanks, > Matt. > > -----Original Message----- > From: Ernest Shaffer > > Also the first column with phy, dom, gz, lz, is the object type, so phy real > should just be server. But the other types would represent the type of > virtualization used. >