placement/nova
Chris Dent cc9f665f54 Use placement context in placement functional tests
A few placement functional tests were importing and using
nova.context for a RequestContext. Placement has its own
in nova.api.openstack.placement.context so use that instead.

In the process, stop using an 'admin' context. It is not
necessary in placement as we do not do any policy checking
at the database level.

Change-Id: I1f6e6db6aca7dd160d3e94bb0b6ebf9b4f8dfd7d
2018-07-24 20:54:26 +01:00
..
api/openstack Merge "Address nits from consumer generation" 2018-07-24 02:19:42 +00:00
conf z/VM Driver: Initial change set of z/VM driver 2018-07-16 11:35:10 +08:00
db Merge "Address nits in server group policy series" 2018-07-17 06:23:25 +00:00
notifications/objects Transform aggregate.update_prop notification 2018-07-15 23:36:31 +09:00
objects Transform aggregate.update_prop notification 2018-07-15 23:36:31 +09:00
policies Consistent policies 2017-07-17 16:45:41 -04:00
scheduler/filters Remove remaning log translation in scheduler 2018-05-09 18:43:11 -07:00
tests Use placement context in placement functional tests 2018-07-24 20:54:26 +01:00
virt/hyperv Remove baremetal virt driver 2014-10-08 13:41:37 +00:00
i18n.py correct referenced url in comments 2018-01-18 09:16:37 +08:00
rc_fields.py Make ResourceClass.normalize_name handle sharp S 2018-04-10 12:24:40 -05:00
test.py Use nova.db.api directly 2018-07-10 14:56:27 +00:00
utils.py Adapter raise_exc=False by default 2018-06-22 09:40:33 -05:00