flavor details should include arch

I believe your use case is already covered using the filter scheduler. A good thread to read would be:

http://lists.openstack.org/pipermail/openstack-dev/2012-August/000691.html

Is there something missing here that you need?

Afaik the scheduler is pretty opaque to an api user. I'm looking for a
mechanism to discover what architecture a given openstack instance supports
using its api. While i agree with the comments in that thread that a
compatible flavor and image combination are required to make it work, i
disagree that this is soley the property of the image, as that leaves zero
ability to introspect the system capabilities as an api user. ie its
 possible to have an arm compatible image with no applicable hardware. The
flavor/instance-type level introspection seems the most appropriate to
allow for an api user to distinguish hardware.

On Fri, Aug 17, 2012 at 2:43 PM, Russell Bryant
<email address hidden>wrote:

> I believe your use case is already covered using the filter scheduler.
> A good thread to read would be:
>
> http://lists.openstack.org/pipermail/openstack-
> dev/2012-August/000691.html
>
> Is there something missing here that you need?
>
> ** Changed in: nova
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1028688
>
> Title:
> flavor details should include arch
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1028688/+subscriptions
>

This is sooooo old now. While it's probably worth thinking about this in the current nova arch, we should do so with fresh eyes if it's important.