From 4a4fbf6ca5d965eca8a857b3473e0799bca3c03d Mon Sep 17 00:00:00 2001 From: zhongjun Date: Mon, 11 Sep 2017 10:50:28 +0800 Subject: [PATCH] Retarget ensure share to Queens Move ensure share spec to Queens folder. Change-Id: I3dc9e960ce38b9124b942413a90d91568fd4082b --- specs/{pike => queens}/ensure-share.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) rename specs/{pike => queens}/ensure-share.rst (96%) diff --git a/specs/pike/ensure-share.rst b/specs/queens/ensure-share.rst similarity index 96% rename from specs/pike/ensure-share.rst rename to specs/queens/ensure-share.rst index 8e455ce..cf11ff3 100644 --- a/specs/pike/ensure-share.rst +++ b/specs/queens/ensure-share.rst @@ -71,8 +71,10 @@ called after driver initialization but before ensure_shares, that returns a dictionary. Drivers will have complete control of the contents of the dictionary to be hashed. Driver can include any of the following: -1. The ID of the most recent DB migration. Including this value guarantees - that ensure_shares will be called after DB schema changes. +1. The ID of the most recent DB migration. The manager will add new + ``get_recent_db_migration_id`` interface to supply this value to the + driver. Then this value guarantees that ensure_shares will be called + after DB schema changes. 2. Any of the keys and values in the oslo config object. Including these values guarantees that ensure_shares is called whenever the config file changes in a way that impacts the driver. @@ -224,8 +226,7 @@ Primary assignee: Work items ---------- -* Implement the core feature with functional tempest and scenario test - coverage +* Implement the core feature with unit tests * Convert all ensure_share() methods to ensure_shares() * Implement get_backend_info() in first party drivers. * Add documentation of this feature