yahoo-eng-team team mailing list archive

[Jeremy Stanley <fungi@xxxxxxxxxxx>]

Mis-filed. Switching from openstack-ci (developer tools, continuous
integration and service hosting) to nova (cloud computing fabric
controller).

** Project changed: openstack-ci => nova

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

Title:
  NOVA scheduler to properly launch a VM or BM instance based on
  selected flavor

Status in OpenStack Compute (Nova):
  New

Bug description:
  The NOVA infrastructure is allowing different flavors which can be either virtual machines, or baremetal machines. 
  Unfortunately the selection is being done at the nova.conf and hard set

  scheduler_host_manager =
  nova.scheduler.baremetal_host_manager.BaremetalHostManager

  As a consequence, when trying to launch a regular VM on the local
  host, the nova-scheduler attempts to launch a BM instance and is
  looking for BM related parameters unnecessary for the VM.

  For example, prior to launching the instance, the dashboard is asking for a network ID to be connected to
  Secondly, and after launched, the error message comes up:

  Error: Failed to launch instance "virtual_instance": Please try again
  later [Error: No valid host was found. ].

  I have attached the error log for more details, but this seems to
  indicate that the flavor does not seem to have an influence on the
  type of scheduler used.

  This seems to be a design error which prevents the support of an
  heterogeneous environment with a mix of different type of instances
  selected by the flavor and not from the configuration file.

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