yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1201656] Re: nova baremetal ties nova-compute to one architecture

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: OpenStack Hudson <1201656@xxxxxxxxxxxxxxxxxx>
Date: Tue, 16 Jul 2013 02:46:10 -0000
Reply-to: Bug 1201656 <1201656@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Reviewed:  https://review.openstack.org/37162
Committed: http://github.com/stackforge/tripleo-image-elements/commit/2282340a32f3dc57da58e4840b95398b3afae232
Submitter: Jenkins
Branch:    master

commit 2282340a32f3dc57da58e4840b95398b3afae232
Author: Robert Collins <rbtcollins@xxxxxx>
Date:   Tue Jul 16 14:25:30 2013 +1200

    Reinstate architecture binding for nova-bm.
    
    Per bug 1201656 (which this doesn't fix) nova is constrained to run
    one architecture per nova-compute host.
    
    Change-Id: I352f219f3ebb05705adf4bc6815ab738a0599c6b


** Changed in: tripleo
       Status: In Progress => Fix Released

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

Title:
  nova baremetal ties nova-compute to one architecture

Status in OpenStack Compute (Nova):
  Triaged
Status in tripleo - openstack on openstack:
  Fix Released

Bug description:
  This is configured via the baremetal_extra_specs setting, but it
  should be a per-node attribute, as nothing in the nova-compute process
  is actually architecture specific.

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