Canonical naming for non-x86 architectures

Bug #1483159 reported by James Page
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
James Page
simplestreams
Fix Released
Undecided
James Page
nova (Ubuntu)
Won't Fix
High
James Page

Bug Description

Various non-x86 architectures (POWER and ARM) don't correctly canonicalize into things that libvirt natively understands.

The attached patches normalizes some alternative architecture strings into standardized ones for Nova/libvirt.

Tags: patch
Revision history for this message
James Page (james-page) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nova (Ubuntu):
status: New → Confirmed
Changed in nova:
assignee: nobody → James Page (james-page)
status: New → In Progress
tags: added: patch
Revision history for this message
James Page (james-page) wrote :
Changed in nova (Ubuntu):
status: Confirmed → Triaged
assignee: nobody → James Page (james-page)
milestone: none → ubuntu-15.09
James Page (james-page)
Changed in simplestreams:
status: New → In Progress
assignee: nobody → James Page (james-page)
Revision history for this message
James Page (james-page) wrote :

The original source of this bug is incorrect configuration of the 'architecture' property in a glance image; if the standard Ubuntu/Debian architecture names are used, then they don't match the architecture that nova-compute/libvirt detect on the hypervisors, and instances can't be scheduled appropriately.

I've proposed a fix to simplestreams (a distribution tool for images) but it would be nice if openstack could be a little friendlier in mapping the distro architecture names into canonical forms as well.

Changed in nova (Ubuntu):
importance: Undecided → High
Revision history for this message
Daniel Berrange (berrange) wrote :

This is simply user error - OpenStack has a documented list of required architecture values

http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html

Nova should not have to apply workarounds for every possible way the user can specify incorrect architecture names.

Revision history for this message
James Page (james-page) wrote :

I don't think its unreasonable to map well know architecture names used by distributions into something OpenStack understands - this is not 'every possible way' - its if the user makes and (somewhat understandable) choice of using the Ubuntu/Debian architecture name for their image.

Revision history for this message
Scott Moser (smoser) wrote :

Daniel,
Your suggestion that openstack should not be in charge of "fixing" strings does make sense, but it should at least be configurable to reject invalid strings for well known properties. That way the user fails the upload (or the property set) rather than arbitrary failure further down the line.

James Page (james-page)
Changed in simplestreams:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.openstack.org/211041

James Page (james-page)
Changed in nova:
status: In Progress → Invalid
James Page (james-page)
Changed in nova (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Scott Moser (smoser) wrote : Fixed in simplestreams version 0.1.0.

This bug is believed to be fixed in simplestreams in version 0.1.0. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in simplestreams:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.