[openstack-dev] [neutron] OVO support
Morales, Victor
victor.morales at intel.com
Tue Nov 15 14:15:34 UTC 2016
My two cents on this.
OVO is going to be the new layer to access to DB model classes, therefore all the calls to the database(ensuring that there is an opened session) and the process to receive(validating fields) and/or return data(determining if a specific column exists) should be managed by OVO classes internally, so that’s also my understanding.
Regards,
Victor Morales
From: Gary Kotton <gkotton at vmware.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Tuesday, November 15, 2016 at 3:06 AM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [neutron] OVO support
Hi,
It seems like a lot of the object work is being done under database transactions. My understanding is that the objects should take care of this internally.
Any thoughts?
Thanks
Gary
More information about the OpenStack-dev
mailing list