Bug 1044606 - Update configuration for nova in Icehouse
Summary: Update configuration for nova in Icehouse
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-puppet-modules
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: Icehouse
Assignee: Martin Magr
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 16:26 UTC by Xavier Queralt
Modified: 2014-06-18 07:00 UTC (History)
6 users (show)

Fixed In Version: openstack-puppet-modules-2014.1-3.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-29 14:16:16 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Xavier Queralt 2013-12-18 16:26:36 UTC 
Description of problem:

The values packstack sets for a couple of keys in nova.conf should be updated in Icehouse:

- libvirt_vif_driver should be set to nova.virt.libvirt.vif.LibvirtGenericVIFDriver even when using openvswitch (was LibvirtHybridOVSBridgeDriver)

- compute_driver should use the full path "nova.virt.libvirt.LibvirtDriver" (was libvirt.LibvirtDriver) otherwise the import fails.
Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Alvaro Lopez Ortega 2013-12-19 15:49:48 UTC 
I'm taking ownership of this bug. A new branch has to be created for Icehouse.
Comment 2 Matthias Runge 2014-03-17 14:22:02 UTC 
Sounds like this will show up on the upcoming test days, which will make this urgent.
Comment 3 Martin Magr 2014-03-17 14:38:50 UTC 
Parameter libvirt_vif_driver is already set currently in Icehouse branch, we need to only set compute_driver probably.
Comment 4 Matthias Runge 2014-03-17 20:39:46 UTC 
I tested this with
openstack-packstack-2013.2.1-0.34.dev989.fc20.noarch
and had to set both libvirt_vif_driver and compute_driver manually.
Note You need to log in before you can comment on or make changes to this bug.