From ac54793f1fbddf4e662ec5f8d35b598526a7ab7c Mon Sep 17 00:00:00 2001 From: Yikun Jiang Date: Mon, 10 Dec 2018 15:59:46 +0800 Subject: [PATCH] Appending change for improve-volume-transfer-records bp 1. Use source/destination instead of original/current, because "current" is misleading since it will no longer be accurate if two transfers have occurred for the same volume. 2. Change "accept" to " accepted". Part of blueprint: improve-volume-transfer-records Change-Id: I5d7c948ee51503e3a92543ba3855171f98a7ea81 --- .../stein/improve-volume-transfer-records.rst | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/specs/stein/improve-volume-transfer-records.rst b/specs/stein/improve-volume-transfer-records.rst index 3bd5e109..03c240a8 100644 --- a/specs/stein/improve-volume-transfer-records.rst +++ b/specs/stein/improve-volume-transfer-records.rst @@ -10,16 +10,16 @@ Improve volume transfer records https://blueprints.launchpad.net/cinder/+spec/improve-volume-transfer-records This blueprint proposes to improve volume transfer records by adding -``original_project_id`` and ``current_project_id``, ``accept`` fields to +``source_project_id`` and ``destination_project_id``, ``accepted`` fields to ``transfer`` table and related api responses, makes it easier for users to trace the volume transfer history. Problem description =================== -Currently, the volume transfer record does not include the current project_id -after transferring and the original project_id before transferring. These -fields are very useful for admins and operators to trace the transfer +Currently, the volume transfer record does not include the destination +project_id after transferring and the source project_id before transferring. +These fields are very useful for admins and operators to trace the transfer history. And also once the transfer is deleted, the user can't determine if this @@ -40,13 +40,13 @@ This spec proposes to do 1. Add three new fields to ``transfer`` table: - * ``original_project_id``, this field records the original project_id + * ``source_project_id``, this field records the source project_id before volume transferring. - * ``current_project_id``, this field records the current project_id after - volume transferring. + * ``destination_project_id``, this field records the destination project_id + after volume transferring. - * ``accept``, this field records if this transfer was accepted or not. + * ``accepted``, this field records if this transfer was accepted or not. 2. Add a new microverion API to add above fields to the response of follow API: @@ -121,10 +121,10 @@ Primary assignee: Work Items ---------- -* Add ``original_project_id`` and ``current_project_id``, ``accept`` fields to - ``transfer`` table -* Add ``original_project_id`` and ``current_project_id``, ``accept`` fields to - related API. +* Add ``source_project_id`` and ``destination_project_id``, ``accepted`` + fields to ``transfer`` table +* Add ``source_project_id`` and ``destination_project_id``, ``accepted`` + fields to related API. * Implement changes for python-cinderclient to support list transfer with ``--detail``. * Update related transfer api doc.