yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

This is the basic issue with volumes not being scheduler aware. The
placement api in Nova is the path to solving this. Please get involved
there if you can.

** Changed in: nova
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1613706

Title:
  VMware VMDK : In multi hypervisor environment, a volume will be
  created in vCenter if an attempt to attach it a KVM instance

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Description
  ===========
  In a multi hypervisor environment containing esx computes and KVM computes, and cinder VMDK backend configured,
  When attaching a volume to a KVM INSTANCE, A volume is created in the vCenter if a volume of type VMDK.

  The volume VM is created in the cluster not part of the OpenStack plane. In other words, the volume can be created anywhere.
  Though there is a failure, which is expected, the concern is with the creation of volume VM. 

  Check in manger for the volume type and the driver type before
  delegating it to cinder would be ideal.

  Steps to reproduce
  ==================
  1. Create a VM in KVM region.
  2. Register cinder VMDK driver and create a volume.
  3. Attach the cinder volume to a KVM instance.

  Expected result
  ===============
  After the execution of the steps above, Either volume in vCenter shouldn't be created or it should be deleted.

  Actual result
  =============
  But the volume remains there in the vCenter.

  Environment
  ===========
  1. Devstack, stable/mitaka

  2. Which hypervisor did you use?
     libivrt  + vmware

  2. Which storage type did you use?
     VMDK

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1613706/+subscriptions