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 <[email protected]> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Date: Tuesday, November 15, 2016 at 3:06 AM To: OpenStack List <[email protected]> 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 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
