Mark Doffman 9cfd6fc760 Aggregate create and destroy work against API db ... Make aggregate.create() and destroy() use the API rather than cell database. Also block aggregate creation until main database empty. This makes Aggregate.create() fail until the main database has had all of its aggreagtes migrated. Since we want to avoid any overlap or clashes in integer ids we need to enforce this. Note that this includes a change to a notification sample, which encodes the function and module of a sample exception (which happens to be during an aggregate operation). Since the notifications are encoding internal function names, which can and will change over time, this is an expected change. blueprint cells-aggregate-api-db Co-Authored-By: Dan Smith <dansmith@redhat.com> Change-Id: Ida70e3c05f93d6044ddef4fcbc1af999ac1b1944		2016-08-01 08:22:08 -07:00
..
functional	Aggregate create and destroy work against API db	2016-08-01 08:22:08 -07:00
unit	Aggregate create and destroy work against API db	2016-08-01 08:22:08 -07:00
__init__.py	move all tests to nova/tests/unit	2014-11-12 15:31:08 -05:00
fixtures.py	Add metadata server fixture	2016-07-26 08:14:55 -04:00
uuidsentinel.py	Add uuidsentinel test module	2015-12-14 11:28:55 +01:00