Shubhendu Tripathi has posted comments on this change.

Change subject: restapi: Migrates the brick data and mark it for deletion
......................................................................


Patch Set 8:

(1 comment)

....................................................
Commit Message
Line 12: 
Line 13: Its different from the normal brick deletion in the sense that normal
Line 14: delete works as force delete and removes the bricks from the volume
Line 15: without any data migration. Whereas this option would migrate the data
Line 16: first and then by using the commit deletes the brick from volume.
In gluster, remove brick with force option is normal delete and the same is 
implemented as is DELETE on bricks.

This migrate is a variation of remove brick where user can migrate the data 
available on the said brick to rest of the bricks in the volume and then opt to 
delete/retain the brick for future use.

If user opts to COMMIT, it means user does not need the brick anymore and wants 
to delete it permanently.

User can also opt to retain the brick (even after migration) by selecting the 
STOP MIGRATE option. The brick becomes usable from that point of time and data 
would start coming to this brick as well.

STOP MIGRATE options plays two fold action -
1. Stop an on going migration of a brick data - this would stop the migration 
of data from the brick on the way and later the same can be resumed for 
migration again.
2. Retain a brick on which data migration has completed successfully - this 
would make sure brick is usable after this action

Hope this clarifies the existence of separate COMMIT option and the same not 
happening as part of migrate.

Sahina any comments ?
Line 17: 
Line 18: Usage:
Line 19:     - 
api/clusters/<cluster-Id>/glustervolumes/<volume-id>/bricks/migrate
Line 20: 


-- 
To view, visit http://gerrit.ovirt.org/19400
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Iaa88f3402a25316d1717ee914aa77856fbe802db
Gerrit-PatchSet: 8
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Shubhendu Tripathi <[email protected]>
Gerrit-Reviewer: Kanagaraj M <[email protected]>
Gerrit-Reviewer: Michael Pasternak <[email protected]>
Gerrit-Reviewer: Ori Liel <[email protected]>
Gerrit-Reviewer: Sahina Bose <[email protected]>
Gerrit-Reviewer: Shubhendu Tripathi <[email protected]>
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: Yes
_______________________________________________
Engine-patches mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-patches

Reply via email to