← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1519745] [NEW] Default Image Architecture Attribute

 

Public bug reported:

Analog to https://bugs.launchpad.net/horizon/+bug/1519720

In heterogeneous compute environments an operator may require images to
have the architecture attribute set in order to schedule the image onto
a hypervisor of the correct architecture.  Glance (afaict) doesn't
provide a method to enforce this attribute to be supplied.

Change https://review.openstack.org/#/c/242458/ proposes to optionally
mutate a creation request to include a default architecture (typically
x86_64) which allows correct operation for 99% of cases in the
deployment described above.  Additionally if you so wish it is also
flexible enough to add other attributes e.g. set the disk bus to virtio-
scsi etc.

Feel free to debate my choice of tactics but I'm of the opinion that for
now it is a good enough solution that allows users to get on with their
work without having to rework their provisioning solutions.

** Affects: glance
     Importance: Undecided
     Assignee: Simon Murray (spjmurray)
         Status: In Progress

** Changed in: glance
     Assignee: (unassigned) => Simon Murray (spjmurray)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1519745

Title:
  Default Image Architecture Attribute

Status in Glance:
  In Progress

Bug description:
  Analog to https://bugs.launchpad.net/horizon/+bug/1519720

  In heterogeneous compute environments an operator may require images
  to have the architecture attribute set in order to schedule the image
  onto a hypervisor of the correct architecture.  Glance (afaict)
  doesn't provide a method to enforce this attribute to be supplied.

  Change https://review.openstack.org/#/c/242458/ proposes to optionally
  mutate a creation request to include a default architecture (typically
  x86_64) which allows correct operation for 99% of cases in the
  deployment described above.  Additionally if you so wish it is also
  flexible enough to add other attributes e.g. set the disk bus to
  virtio-scsi etc.

  Feel free to debate my choice of tactics but I'm of the opinion that
  for now it is a good enough solution that allows users to get on with
  their work without having to rework their provisioning solutions.

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