Cleanup handling of SQLAlchemy session in DB access layer

Registered by Viktor Serhieiev on 2013-08-08

Bring the use of sessions and transactions in glance.db.sqlalchemy.api modules into a consistent state:
 - use explicit transactions only when necessary
 - don't pass session objects to public DB api methods
 - fix incorrect usage of sessions throughout the DB-related code

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Viktor Serhieiev
Direction:
Approved
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

These cleanups seem beneficial. What is the status here, has any of the work been started, if so can you provide links to the reviews? Sorry if this has been neglected by reviewers.
markwash more-info 2014-02-17

Unfortunately, work on this blueprint has not been started. Can we have this BP approved and targeted to Juno-(1 or 2)? Thanks.
viktors 2014-02-19

I think Juno is fine for this, however typically our process is to have the assignee do the targeting when they have started (and can commit to) working on a blueprint. Right now, I consider the direction approved, but would love a little bit more info (maybe just some examples from the code currently) about what will be cleaned up. Since the general idea / direction is approved, I'll put this on the wishlist. Please reassign yourself when you start working on it. Thanks!
markwash wishlist 2014-03-07

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.