← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1769283] [NEW] ImagePropertiesFilter has no default value resulting in unpredictable scheduling

 

Public bug reported:

When using ImagePropertiesFilter for something like hardware
architecture, it can cause very unpredictable behaviour because of the
lack of default value.

In our case, a public cloud user will most likely upload an image
without `hw_architecture` defined anywhere (as most instruction and
general OpenStack documentation refers to).

However, in a case where there are multiple architectures available, the
images tagged with a specific architecture will go towards hypervisors
with that specific architecture.  However, those which are not tagged
will go to *any* hypervisor.

Because of how popular certain architectures are, it should be possible
to be able to set a 'default' value for the architecture as it is the
implied one, with the ability to override it if a user wants a specific
one.

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

Title:
  ImagePropertiesFilter has no default value resulting in unpredictable
  scheduling

Status in OpenStack Compute (nova):
  New

Bug description:
  When using ImagePropertiesFilter for something like hardware
  architecture, it can cause very unpredictable behaviour because of the
  lack of default value.

  In our case, a public cloud user will most likely upload an image
  without `hw_architecture` defined anywhere (as most instruction and
  general OpenStack documentation refers to).

  However, in a case where there are multiple architectures available,
  the images tagged with a specific architecture will go towards
  hypervisors with that specific architecture.  However, those which are
  not tagged will go to *any* hypervisor.

  Because of how popular certain architectures are, it should be
  possible to be able to set a 'default' value for the architecture as
  it is the implied one, with the ability to override it if a user wants
  a specific one.

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


Follow ups