Hi Ihar, While doing the integration for vlanallocation [1] I found that OVO associated with VlanAllocation throws “unhashable type” error with py35. The associated stack trace is here [2]. To resolve this issue I added an equality and hash method in the vlanallocation OVO [3]. My understanding is we will face the same problem with other OVO objects as well when we do similar operations on the object as in [1]. Should we make all the OVO objects hashable or deal it case by case? Thoughts? [1] https://review.openstack.org/#/c/367810/28/neutron/plugins/ml2/drivers/type_vlan.py@77 [2] http://paste.openstack.org/show/596281/ [3] https://review.openstack.org/#/c/367810/28/neutron/objects/plugins/ml2/vlanallocation.py@38-55 Thanks, Anindita (irc: dasanind) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170125/3ee4ae72/attachment.html>