XenAPI questions & bugs & missing festures

* VDI uuid is always recreated when creating. (XendLocalStorageRepo.py,
  XendQCoWStorageRepo.py). Is it designed like that or a bug?

* twisted is ever used in xen-2.0, but striped. As twisted is getting mature,
  do we have the plan to use it again?

* libvirt project is meant to support multiple virtualization products. XenAPI
  is also well designed and can easily ported to support other hypervisors.
  (In my opinion, I think XenAPI is a far better design than libvirt ;-).)
  How about rename XenAPI to VirtAPI and start sub-projects against kvm, qemu,
  OpenVZ, etc?

* I think XenAPI development should be separated form hypervisor. But the
  detailed steps to get it are still in testing and thinking.

* I noticed some differences between the Citrix XenServer XenAPI implement and
  the open source one:

  * the object reference: XenServer XenAPI is prefixed by 'OpaqueRef'. This
    can prevent the user from mixing the 'ref' and 'uuid'.
  * the citrix xenapi implement should be ready for for user in a cluster
    environment. Eg. vm-migrate accept a host ref rather than a uri.

  ...

  Any plan to add all these things to open source XenAPI?

* the xm command line interface has too much history burden. can we just leave
  it for the legacyXMLRPC interface and rewrite a small XenAPI only client?
  Does citrix has the plan to rewrite and open the xe tool for open source
  XenAPI?

* As many users asking about Java binding, does citrix developers have a plan
  to maintain a Java binding for the open source XenAPI?