On 1/27/2016 11:22 AM, Avishay Traeger wrote:
On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann <mrie...@linux.vnet.ibm.com <mailto:mrie...@linux.vnet.ibm.com>> wrote: <snip> I've replied on https://review.openstack.org/#/c/266095/ and the related cinder change https://review.openstack.org/#/c/272899/ which are adding a new key to the volume connector dict being passed around between nova and cinder, which is not ideal. I'd really like to see us start modeling the volume connector with versioned objects so we can (1) tell what's actually in this mystery connector dict in the nova virt driver interface and (2) handle version compat with adding new keys to it. I agree with you. Actually, I think it would be more correct to have Cinder store it, and not pass it at all to terminate_connection(). -- *Avishay Traeger, PhD* /System Architect/ Mobile:+972 54 447 1475 E-mail: avis...@stratoscale.com <mailto:avis...@stratoscale.com> Web <http://www.stratoscale.com/> | Blog <http://www.stratoscale.com/blog/> | Twitter <https://twitter.com/Stratoscale> | Google+ <https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts> | Linkedin <https://www.linkedin.com/company/stratoscale> __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
That would be ideal but I don't know if cinder is storing this information in the database like nova is in the nova block_device_mappings.connection_info column.
-- Thanks, Matt Riedemann __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
