yahoo-eng-team team mailing list archive

[Raul Moldovan <2033434@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently host resources are updated in the DB on the following occasions:
- periodic task runs `update_available_resources`
- spawn a VM on a host (update based on falvor)
- pre/post live migration on source host

As we can see at no point the resources for the destination host are updated
in the interval set by the configuration value `update_resources_interval`.
This means that even after subsequent live-migrations to the same host,
important resources like used vCPUs, memory, disk will still look empty.

As the scheduler makes decisions based on the weights assigned to these metrics,
the same hosts are chosen over and over. The state of the hosts will remain
unbalanced until the next update periodic task executes.

Reproduce bug:

For the following values configured:
host_subset_size = 3 (on the head node)
update_resources_interval = 3600 (on every compute node)

In the span of an hour of migrations we can see that only the top 3 hosts
considered initially 'the best' are targeted until the next periodic task
runs the `update_available_resources` function.

Just like the function is called in the next stack trace executed on the
source host:

live_migration
_do_live_migration
_post_live_migration_update_host
_post_live_migration
update_available_resource

It should be executed at some point on the next path:

live_migration
_do_live_migration
_post_live_migration_update_host
_post_live_migration
compute_rpcapi.post_live_migration_at_destination
post_live_migration_at_destination

** 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/2033434

Title:
  Destination host resources not updated post live-migration

Status in OpenStack Compute (nova):
  New

Bug description:
  Currently host resources are updated in the DB on the following occasions:
  - periodic task runs `update_available_resources`
  - spawn a VM on a host (update based on falvor)
  - pre/post live migration on source host

  As we can see at no point the resources for the destination host are updated
  in the interval set by the configuration value `update_resources_interval`.
  This means that even after subsequent live-migrations to the same host,
  important resources like used vCPUs, memory, disk will still look empty.

  As the scheduler makes decisions based on the weights assigned to these metrics,
  the same hosts are chosen over and over. The state of the hosts will remain
  unbalanced until the next update periodic task executes.

  Reproduce bug:

  For the following values configured:
  host_subset_size = 3 (on the head node)
  update_resources_interval = 3600 (on every compute node)

  In the span of an hour of migrations we can see that only the top 3 hosts
  considered initially 'the best' are targeted until the next periodic task
  runs the `update_available_resources` function.

  Just like the function is called in the next stack trace executed on the
  source host:

  live_migration
  _do_live_migration
  _post_live_migration_update_host
  _post_live_migration
  update_available_resource

  It should be executed at some point on the next path:

  live_migration
  _do_live_migration
  _post_live_migration_update_host
  _post_live_migration
  compute_rpcapi.post_live_migration_at_destination
  post_live_migration_at_destination

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