yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Public bug reported:

ChanceScheduler was implemented before multiple nodes were possible for the same nova-compute service.
As a result, it returns a tuple (host, node, limits) where node is None but that's then not possible to know which ComputeNode object was provided. Instead, we should choose between all the related nodes so that ChanceScheduler could be used for Ironic driver.

** Affects: nova
     Importance: Low
     Assignee: Sylvain Bauza (sylvain-bauza)
         Status: Confirmed


** Tags: ironic scheduler

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => Low

** Changed in: nova
     Assignee: (unassigned) => Sylvain Bauza (sylvain-bauza)

** Tags added: ironic scheduler

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

Title:
  ChanceScheduler doesn't return properly the nodename attribute

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  ChanceScheduler was implemented before multiple nodes were possible for the same nova-compute service.
  As a result, it returns a tuple (host, node, limits) where node is None but that's then not possible to know which ComputeNode object was provided. Instead, we should choose between all the related nodes so that ChanceScheduler could be used for Ironic driver.

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