On 3/2/2011 2:26 PM, Aaron Dummer wrote:
Do you already handle the other end of the nesting scenario: VMs hosted on a blade in a chassis?Yes, that is doable right now. An object may have both 'children' and 'parents', creating a hierarchy. Blade server chassis -> blade server -> VM Also, an object may have multiple parents. In the case of a blade server which is in a clustered VM environment, the blade would have two parents - 1) the server chassis, 2) the VM cluster.
Interesting... Can it handle virtualized things that move around like VMs that migrate to different hosts or floating failover IP addresses? Is there still some way to map them to a physical representation of location or port?
-- Les Mikesell lesmikesell@xxxxxxxxx