)]}'
{"specs/liberty/clone-cg.rst":[{"author":{"_account_id":12924,"name":"Patrick East","email":"east.patrick@gmail.com","username":"patrick.east"},"change_message_id":"f9cb8db410c89b3b6467f4365985675e69b03a15","unresolved":false,"context_lines":[{"line_number":21,"context_line":"until all volumes are cloned and added to the CG."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"The proposal wants to enhance the existing create CG from source API"},{"line_number":24,"context_line":"and make this a one step rather than multi-step process."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Use Cases"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_5b7606d8","line":24,"updated":"2015-06-23 22:51:08.000000000","message":"Would these cloned volumes be consistent? Or are they equivalent to if you just cloned each member of the source group one at a time?\n\nI\u0027m not sure how these work for other vendors, but for us we could just iterate through each volume, clone them, add the new clone to the new group, and thats it. This would mimic the behavior described here. They would not however be \u0027consistent\u0027 in the sense that any io would be essentially be frozen to the group while cloning each volume. \n\nAlternatively we could take a group snapshot (so the volumes in the group are all at the exact same point) and clone new volumes from the snapshot. I\u0027m assuming other vendors maybe can consistently clone a group of volumes, or do other things to make this work, so we should probably be sure to specify how it is supposed to behave so that an end user cloning a cg gets the same behavior from different backends.","commit_id":"181ff4709ef654b63753e20e4c81683ec070d8e5"},{"author":{"_account_id":6491,"name":"xing-yang","email":"xingyang105@gmail.com","username":"xing-yang"},"change_message_id":"f905b11b83f249192bd02774fd9a4dab125d8513","unresolved":false,"context_lines":[{"line_number":21,"context_line":"until all volumes are cloned and added to the CG."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"The proposal wants to enhance the existing create CG from source API"},{"line_number":24,"context_line":"and make this a one step rather than multi-step process."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Use Cases"},{"line_number":27,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_ec4b9eaf","line":24,"in_reply_to":"fa32b979_5b7606d8","updated":"2015-06-24 01:00:21.000000000","message":"The cloned volumes are not consistent.  From the consistency point of view, it\u0027s no different from creating a empty CG first and then creating volume one after another and adding to the CG.\n\nThe existing Create CG from source API already create a CG from the group snapshot, which should be consistent. I believe Pure has already implemented this API.\n\nI\u0027ll clarify this.","commit_id":"181ff4709ef654b63753e20e4c81683ec070d8e5"}]}