deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Peterson <>
Subject vSphere and RHEV-M Design Questions
Date Sun, 28 Jul 2013 21:43:01 GMT
I'm currently evaluating Deltacloud to serve as a common bridge between
some vSphere and RHEV-M clusters. So far it's been great to not have to
deal with VMWare's APIs! I do have some questions with the implementations
of the vSphere and RHEV-M drivers.

The vSphere driver currently enumerates machines be scanning through the
observable data stores. Each datastore volume is considered to be a
separate realm. Why does the vSphere driver go with this instead of
mirroring the RHEV-M driver in using datacenters as providers and clusters
as realms?

For the RHEV-M driver, why does the storage_volumes method return the
storage domains instead of the individual disks? Would it be possible to
extend the RHEV-M driver to list individual disks per instance?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message