openstack
/
placement
Code Issues Proposed changes
placement/placement/tests/functional/db
History
Tetsuro Nakamura c198326150 Set root_provider_id in the database 
When nested resource provider feature was added in Rocky,
root_provider_id column, which should be non-None value, is created in
the resource provider DB.

However, online data migration is only done implicitly via listing or
showing resource providers. With this patch, executing the cli command

    `placement-manage db online_data_migrations`

makes sure all the resource providers are ready for nested provider
feature, that is, all the root_provider_ids in the DB have non-None
value.

Change-Id: I42a1afa69f379b095417f5eb106fe52ebff15017
Related-Bug:#1803925
 		2019-01-18 15:39:36 -05:00
..
__init__.py Move the functional test directories 2018-09-04 10:31:24 -05:00
test_allocation_candidates.py Use os-resource-classes in placement 2018-12-19 10:43:18 +00:00
test_base.py Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00
test_consumer.py Use os-resource-classes in placement 2018-12-19 10:43:18 +00:00
test_migrations.py Use oslo_db fixtures 2018-12-03 18:31:27 +00:00
test_project.py Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00
test_reshape.py Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00
test_resource_class_cache.py Use os-resource-classes in placement 2018-12-19 10:43:18 +00:00
test_resource_provider.py Set root_provider_id in the database 2019-01-18 15:39:36 -05:00
test_user.py Use uuidsentinel from oslo.utils 2018-09-05 22:32:56 +00:00