Hi! This fully belongs in Nova, so moving it back. I don't have a
precise answer to your question, but nova-scheduler's do not depend on
the exact compute backends. It is nova-compute instances that are

I guess your problem is with choosing between BM and VM nodes. You can
use, for example, host aggregates to distinguish between these. I
suggest you reach out to the Nova team for better explanation.

** Project changed: ironic => nova

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  Multiple nova schedulers for Ironic and nova conflict when they  work
  together in one Region

Status in OpenStack Compute (nova):

Bug description:
  When Ironic and nova work in one region。we should deploy multiple
  nova-scheduler process,some for Ironic node scheduling and others for
  virtual machines scheduling。 Then we call rest API to boot an ironic
  node, nova-conductor polls the message to multiple nova-scheduler,and
  not distinguish nova-schedulers for ironic from nova-schedulers for
  virtual machines。 so it will cause an exception for not selecting a
  valid host to boot。

  I eager to solving this question because this scenario happened in our
  deploying project。

  Anyone has good ideas?

To manage notifications about this bug go to:

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

Reply via email to