Idea ID: 2685309

Population of VMware storage topology (mapping between Drive C: -> VMware Datastore)

Status : Accepted
over 2 years ago

Dear all,

We would like to see population of VMware storage topology that will include population of mapping between Drive C: down to VMware datastore. 

The change should most probably touch both VMware Topology by VIM as well as Resources by Shell/WMI.

Thanks,

Dmitry

Labels:

Discovery-Content
  •  thanks for the answer....as the vmdk is discovered by the OoB discovery, I understand that point won't be change with your improvement.


    As you said it's a bad pratice to switch disk from a VM to another and we do not implement that hopefully. So, i'm confident with that.

     

    Anyway I really hope your improvement will be add to OoB MF Discovery very soon

    Regards

    Erwan LE BARON

  •  We do not have clustered virtual servers sharing the same VMDK in our infrastructure, so I would not be able to tell the behavior. However, our add-on do not modify the out-of-the-box discovery of the VMware virtual disk. So, if the Vmware virtual disk discovered as "Logical volume" is currently merged into a single object in uCMDB, it will stay the same and we should see two Disk devices (\\PHYSICALDRIVEx) pointing to the same Logical volume (Hard disk x+1) . I am just unsure how our module "OS storage by Shell" would react if the VMware virtual disk is not at the same position on each virtual machine (ex: 3rd disk on the first VM and 4th disk on the second VM), but if I remember correctly, that kind of configuration is a bad practice for building a virtual cluster...

    FYI, we already had a few meetings with MF R&D about this idea. We have sent them our improved discovery code.

  • Great Job .

    It's exactly what we are looking for

     

    Just few questions

    How do you manage two server in cluster which have using the same VMDK (cf. Hard Disk <N>). Is theire a merge of the CIs or their is still one CIs by server ?
    Some user are looking to be able to get those information and we are not able to do that for the moment.

    , what is the roadmap for this feature ? Is it already at the a futur release ?

    Have a good days guys

    Erwan

  • Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

  • Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes.