yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1384546@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
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/1384546

Title:
  Disk filter is not worked correct when the instance directory are
  shared

Status in OpenStack Compute (Nova):
  Expired

Bug description:
  - Abstraction
  When you assign an launch request of instance, disk filter to a decision by looking at the free disk space on the target nova-compute.
  Here, since the calculation of the free space is not performed correctly if you are sharing a disk with multiple nova-compute, it would allow instance start up in nova-compute no free disk

  - Situation
  If the instance directory is shared, the launch request of the instance that more than the actual disk size can not be blocked.
  For example, if you had to share the disc with nova-compute between the two, it is assumed that you start the instance at the same time multiple units.
  Free space of the shared disk is 15G, if the instance to start was a disk of 10G, respectively, as Quota, the instance of the two or to start?
  When's current situation, it starts normally both.
  However, since disk space is 15G in fact, it is not possible to use the disk of 15G or more in both instance.

  - How to reproduce
  0. Append disk filter on nova-scheduler
  1. Prepare two nova-compute with share the instance directory as NFS.
  2. NFS disk has 15G free space.
  3. Boot two instance at the same time with 10G disk
  4. Both instance can boot normally

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