yahoo-eng-team team mailing list archive

[Christian Berendt <1643569@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

At the moment the _select_datastore method in the VMware driver chooses
the in dependence of the free space. The datastore with the most free
space will be chosen for a new instance.

On of our customers want to place new instances on the datastore with
the less provisioned space and not the one with the most free space.

The amount of provisioned space is not directly provided by the VMware
API and has to be calculated by using the capacity, the free space and
the uncommitted bytes of the datastore. provisionedSpace = Capacity -
freeSpace - uncommitted.

Following changes are necessary to support the selection of a datastore
in dependence of the provisioned space:

* The uncommitted property is not requested by the get_datastore method.
The get_datastore method hast to request the uncommitted property.

* The Datastore class does not provide a keyword argument for the amount
of provisioned space. A provisioned space keyword argument has to be
added to the Datastore class.

* The _select_datastore method has to calculate the provisioned space of
a datastore.

* A new configuration parameter datastore_allocation_type with
'provisionedSpace' and 'freeSpace' as choices has to be introduced. The
default value should be 'freeSpace' to not change the default behaviour
of the _select_datastore method.

* When  datastore_allocation_type is set to 'provisionedSpace' then the
provisionedSpace will be compared instead of the freeSpace and the
datastore with the lowest value for provisionedSpace will be chosen.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Choose VMware datastore in dependence of the provisioned space

Status in OpenStack Compute (nova):
  New

Bug description:
  At the moment the _select_datastore method in the VMware driver
  chooses the in dependence of the free space. The datastore with the
  most free space will be chosen for a new instance.

  On of our customers want to place new instances on the datastore with
  the less provisioned space and not the one with the most free space.

  The amount of provisioned space is not directly provided by the VMware
  API and has to be calculated by using the capacity, the free space and
  the uncommitted bytes of the datastore. provisionedSpace = Capacity -
  freeSpace - uncommitted.

  Following changes are necessary to support the selection of a
  datastore in dependence of the provisioned space:

  * The uncommitted property is not requested by the get_datastore
  method. The get_datastore method hast to request the uncommitted
  property.

  * The Datastore class does not provide a keyword argument for the
  amount of provisioned space. A provisioned space keyword argument has
  to be added to the Datastore class.

  * The _select_datastore method has to calculate the provisioned space
  of a datastore.

  * A new configuration parameter datastore_allocation_type with
  'provisionedSpace' and 'freeSpace' as choices has to be introduced.
  The default value should be 'freeSpace' to not change the default
  behaviour of the _select_datastore method.

  * When  datastore_allocation_type is set to 'provisionedSpace' then
  the provisionedSpace will be compared instead of the freeSpace and the
  datastore with the lowest value for provisionedSpace will be chosen.

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