Public bug reported:
When 10 user starts to provision VMs to a VCenter, OpenStack chooses one same
datastore for everyone.
After the first clone task is complete, OpenStack recognizes that datastore
space usage is increased, and will choose another datastore. However, all the
next 9 provision tasks are still performed on the same datastore. If no
provision task on one datastore completes, OpenStack will persist to choose
that datastore to spawn next VMs.
This bug has significant performance impact, because it slows down
performance of all the provisioning tasks greatly. VCenter driver should
choose a not busy datastore for the provisioning tasks.
** Affects: nova
Importance: Undecided
Status: New
** Tags: vmware
--
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/1340564
Title:
Very bad performance of concurrent spawning VMs to VCenter
Status in OpenStack Compute (Nova):
New
Bug description:
When 10 user starts to provision VMs to a VCenter, OpenStack chooses one same
datastore for everyone.
After the first clone task is complete, OpenStack recognizes that datastore
space usage is increased, and will choose another datastore. However, all the
next 9 provision tasks are still performed on the same datastore. If no
provision task on one datastore completes, OpenStack will persist to choose
that datastore to spawn next VMs.
This bug has significant performance impact, because it slows down
performance of all the provisioning tasks greatly. VCenter driver
should choose a not busy datastore for the provisioning tasks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1340564/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
