first stab at a design where each incoming API call has its own dbsession
authorThierry Parmentelat <thierry.parmentelat@inria.fr>
Thu, 7 Nov 2013 21:00:58 +0000 (22:00 +0100)
committerThierry Parmentelat <thierry.parmentelat@inria.fr>
Thu, 7 Nov 2013 21:00:58 +0000 (22:00 +0100)
commitf42832ac5338cb900a7d297cf6cdbe63bace6009
treea619310a627a0fa903ad16657cdbff1054dc242f
parentb1f27f83087c333cbcb80c63b5d0e7b9a9f9d1ed
first stab at a design where each incoming API call has its own dbsession
very incomplete (focusing on PL for now) also needs work for the v2/v3 adapter
probably impovable on many respects
seems to pass the PL tests though
21 files changed:
sfa/client/sfaadmin.py
sfa/dummy/dummyslices.py
sfa/generic/__init__.py
sfa/generic/architecture.txt
sfa/importer/__init__.py
sfa/importer/dummyimporter.py
sfa/importer/iotlabimporter.py
sfa/importer/nitosimporter.py
sfa/importer/openstackimporter.py
sfa/importer/plimporter.py
sfa/managers/driver.py
sfa/managers/registry_manager.py
sfa/managers/v2_to_v3_adapter.py
sfa/methods/GetSelfCredential.py
sfa/planetlab/plaggregate.py
sfa/planetlab/pldriver.py
sfa/planetlab/plslices.py
sfa/server/sfaapi.py
sfa/server/threadedserver.py
sfa/storage/alchemy.py
sfa/storage/model.py