)]}'
{"doc/source/devref/replication.rst":[{"author":{"_account_id":16793,"name":"Liucheng Jiang","email":"jiangliucheng@huawei.com","username":"Jiangliucheng"},"change_message_id":"9d6a31d88395805fab81b3770b11c1b9a1c004d5","unresolved":false,"context_lines":[{"line_number":49,"context_line":"    [driver-foo]"},{"line_number":50,"context_line":"    volume_driver\u003dxxxx"},{"line_number":51,"context_line":"    volume_backend_name\u003dfoo"},{"line_number":52,"context_line":"    replication_device \u003d target_device_id:vendor-id-info,managed_backend_name:biz,unique_key:val...."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The use of multiopt will result in self.configuration.get(\u0027replication_device\u0027)"},{"line_number":55,"context_line":"returning a list of properly formed python dictionaries that can"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa69d971_79a2fafd","line":52,"range":{"start_line":52,"start_character":25,"end_line":52,"end_character":41},"updated":"2016-01-11 10:02:06.000000000","message":"I find the last commit change target_device_id to device_target_id by @John Griffith. I don\u0027t know what the reason is. Using target_device_id is pretty good.","commit_id":"e704230279e47a522897dc697ab19066148b8c02"},{"author":{"_account_id":16917,"name":"Alex O\u0027Rourke","email":"alex.orourke@hpe.com","username":"aorourke"},"change_message_id":"e64c4ba39ab5c7fc18a99e0788fddee9af7e1671","unresolved":false,"context_lines":[{"line_number":119,"context_line":""},{"line_number":120,"context_line":"**WARNING**"},{"line_number":121,"context_line":"The building of the host string for a driver is not always"},{"line_number":122,"context_line":"very straight forward.  The enabled back ends names which"},{"line_number":123,"context_line":"correspond to the driver-section are what actually get used"},{"line_number":124,"context_line":"to form the host string for the volume service."},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_afd32603","line":122,"range":{"start_line":122,"start_character":28,"end_line":122,"end_character":45},"updated":"2016-01-14 17:31:57.000000000","message":"This should be changed back. enabled_backends is a cinder.conf entry.","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":10628,"name":"Peter Wang","email":"peter.wang13@emc.com","username":"peter_wang"},"change_message_id":"902ef8ff30da91b628826c75c0687a72307a8cc9","unresolved":false,"context_lines":[{"line_number":119,"context_line":""},{"line_number":120,"context_line":"**WARNING**"},{"line_number":121,"context_line":"The building of the host string for a driver is not always"},{"line_number":122,"context_line":"very straight forward.  The enabled back ends names which"},{"line_number":123,"context_line":"correspond to the driver-section are what actually get used"},{"line_number":124,"context_line":"to form the host string for the volume service."},{"line_number":125,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_4f2293a4","line":122,"range":{"start_line":122,"start_character":28,"end_line":122,"end_character":45},"in_reply_to":"da6ed579_afd32603","updated":"2016-01-15 02:59:24.000000000","message":"my fault, thanks","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":16917,"name":"Alex O\u0027Rourke","email":"alex.orourke@hpe.com","username":"aorourke"},"change_message_id":"e64c4ba39ab5c7fc18a99e0788fddee9af7e1671","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"There\u0027s a good deal of flexibility by using volume types.  The scheduler can"},{"line_number":150,"context_line":"send the create request to a backend that provides replication by simply"},{"line_number":151,"context_line":"providing the replication\u003denabled key to the extra-specs of the volume type."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"For example, if the type was set to simply create the volume on any (or if you only had one)"},{"line_number":154,"context_line":"backend that supports replication, the extra-specs entry would be::"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_0f86f2da","line":151,"range":{"start_line":151,"start_character":14,"end_line":151,"end_character":33},"updated":"2016-01-14 17:31:57.000000000","message":"This is out of date. It is replication_enabled\u003d\u003cis\u003e True","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":10628,"name":"Peter Wang","email":"peter.wang13@emc.com","username":"peter_wang"},"change_message_id":"902ef8ff30da91b628826c75c0687a72307a8cc9","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"There\u0027s a good deal of flexibility by using volume types.  The scheduler can"},{"line_number":150,"context_line":"send the create request to a backend that provides replication by simply"},{"line_number":151,"context_line":"providing the replication\u003denabled key to the extra-specs of the volume type."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"For example, if the type was set to simply create the volume on any (or if you only had one)"},{"line_number":154,"context_line":"backend that supports replication, the extra-specs entry would be::"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_af8f8f73","line":151,"range":{"start_line":151,"start_character":14,"end_line":151,"end_character":33},"in_reply_to":"da6ed579_0f86f2da","updated":"2016-01-15 02:59:24.000000000","message":"Done, I missed it.","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":16917,"name":"Alex O\u0027Rourke","email":"alex.orourke@hpe.com","username":"aorourke"},"change_message_id":"e64c4ba39ab5c7fc18a99e0788fddee9af7e1671","unresolved":false,"context_lines":[{"line_number":195,"context_line":"replication on a volume for maintenance or whatever reason to signify that they\u0027d like to \"resume\""},{"line_number":196,"context_line":"replication on the given volume."},{"line_number":197,"context_line":""},{"line_number":198,"context_line":"Note that this method could be as well performed on volume whose replication state falls into *error*. "},{"line_number":199,"context_line":"Ideally drivers will now how to resume the state to *enabled* state."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"**replication_disable**"},{"line_number":202,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_6249c55f","line":199,"range":{"start_line":198,"start_character":0,"end_line":199,"end_character":68},"updated":"2016-01-14 17:31:57.000000000","message":"NOTE that this method can also be performed on a volume whose replication state is in *error*. \nIdeally drivers will know how to resume replication in this case.","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":10628,"name":"Peter Wang","email":"peter.wang13@emc.com","username":"peter_wang"},"change_message_id":"902ef8ff30da91b628826c75c0687a72307a8cc9","unresolved":false,"context_lines":[{"line_number":195,"context_line":"replication on a volume for maintenance or whatever reason to signify that they\u0027d like to \"resume\""},{"line_number":196,"context_line":"replication on the given volume."},{"line_number":197,"context_line":""},{"line_number":198,"context_line":"Note that this method could be as well performed on volume whose replication state falls into *error*. "},{"line_number":199,"context_line":"Ideally drivers will now how to resume the state to *enabled* state."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"**replication_disable**"},{"line_number":202,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_afbd4f03","line":199,"range":{"start_line":198,"start_character":0,"end_line":199,"end_character":68},"in_reply_to":"da6ed579_6249c55f","updated":"2016-01-15 02:59:24.000000000","message":"Done","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":16917,"name":"Alex O\u0027Rourke","email":"alex.orourke@hpe.com","username":"aorourke"},"change_message_id":"e64c4ba39ab5c7fc18a99e0788fddee9af7e1671","unresolved":false,"context_lines":[{"line_number":209,"context_line":"This may be used for triggering a fail-over manually or for testing purposes."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Note that ideally drivers will know how to update the volume reference properly so that Cinder is now"},{"line_number":212,"context_line":"pointing to the secondary.  Also, while it\u0027s not required, at this time; ideally the command would"},{"line_number":213,"context_line":"act as a toggle, allowing to switch back and forth between primary and secondary and back to primary."},{"line_number":214,"context_line":""},{"line_number":215,"context_line":"**list_replication_targets**"},{"line_number":216,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_e23e158a","line":213,"range":{"start_line":212,"start_character":73,"end_line":213,"end_character":101},"updated":"2016-01-14 17:31:57.000000000","message":"This is something we need to discuss. How do we want to proceed here. Should replication_failover be used to as the toggle for fail-back, or should replication_enable?\n\nPersonally, I think replication_enable makes more sense. Essentially you are reenabling replication on a volume. Probably something to bring up with the community.","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"},{"author":{"_account_id":10628,"name":"Peter Wang","email":"peter.wang13@emc.com","username":"peter_wang"},"change_message_id":"902ef8ff30da91b628826c75c0687a72307a8cc9","unresolved":false,"context_lines":[{"line_number":209,"context_line":"This may be used for triggering a fail-over manually or for testing purposes."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Note that ideally drivers will know how to update the volume reference properly so that Cinder is now"},{"line_number":212,"context_line":"pointing to the secondary.  Also, while it\u0027s not required, at this time; ideally the command would"},{"line_number":213,"context_line":"act as a toggle, allowing to switch back and forth between primary and secondary and back to primary."},{"line_number":214,"context_line":""},{"line_number":215,"context_line":"**list_replication_targets**"},{"line_number":216,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da6ed579_cf99a37a","line":213,"range":{"start_line":212,"start_character":73,"end_line":213,"end_character":101},"in_reply_to":"da6ed579_e23e158a","updated":"2016-01-15 02:59:24.000000000","message":"Agree with you that we need to bring it up.\nThat\u0027s why did not touch this section.\n\nfrom implementation perspective, above 2 approaches don\u0027t have much differences.\nbut from user/admin perspective, they do have.\n\nso here we need to have a more clearly definition for replication_enable, or user must get confused.\n\nThanks\nPeter","commit_id":"7baeae427a1bfb9ab6e8ea8c71e1ce9901275315"}]}