Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Operators

deprecated connection_type in nova.conf

 

 

OpenStack operators RSS feed   Index | Next | Previous | View Threaded


sdague at linux

Jul 17, 2012, 7:47 AM

Post #1 of 2 (191 views)
Permalink
deprecated connection_type in nova.conf

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
alt-email: sldague [at] us


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


anne at openstack

Jul 17, 2012, 12:11 PM

Post #2 of 2 (169 views)
Permalink
Re: deprecated connection_type in nova.conf [In reply to]

All,

Sean has done great work here by patching every bit of docs he could
find including a diagram's source file. Outstanding. I know many of us
who appreciate this level effort and wanted to recognize it as a great
bar to set. :)

Anne

On Tue, Jul 17, 2012 at 7:47 AM, Sean Dague <sdague [at] linux> wrote:
> 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
> alt-email: sldague [at] us
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

OpenStack operators RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.