[Openstack-operators] deprecated connection_type in nova.conf
Sean Dague
sdague at linux.vnet.ibm.com
Tue Jul 17 14:47:19 UTC 2012
As we've been talking about deprecation recently, I wanted to make sure
that folks were aware of a change in Folsom that they'll need to take
action in by Grizzly. This is cross posted to operators to make sure
users see this.
The connection_type parameter in nova.conf is deprecated for Folsom.
This means it will still work as it did in Essex, but you'll get a
warning log message about using it. It was the last module loader in
nova that wasn't dynamic.
This is replaced by compute_driver, which takes the class name of the
virt driver to load. It is using the new import_object_ns() function,
which means if the compute driver is in the nova.virt namespace you
don't need to include that part.
compute_driver=libvirt.LibvirtDriver
is completely valid.
All the code for this is in folsom already, devstack defaults to the
above on new installs (as of a week or so ago), and most of the docs
referencing connection_type have been changed (need a couple more
changes today).
connection_type support will be removed in master as soon as Folsom is
branched off, so it will be gone in Grizzly. So if you don't change your
configs for Folsom (which you don't need to do), you will need to change
them in Grizzly.
-Sean
--
Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com
More information about the Openstack-operators
mailing list