)]}'
{"specs/newton/create_volume_from_source.rst":[{"author":{"_account_id":1207,"name":"Duncan Thomas","email":"duncan.thomas@gmail.com","username":"duncan-thomas"},"change_message_id":"a2b28fc598ac41a4d5689ab809126f6332528d8d","unresolved":false,"context_lines":[{"line_number":36,"context_line":"If no, it needs data migration. Use following steps to create the new volume."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Create a temporary cloned volume from source vol."},{"line_number":39,"context_line":"* RPC call to create destination volume with specified volume type."},{"line_number":40,"context_line":"* Set temp_volume_id in the new volume."},{"line_number":41,"context_line":"* Map both volume to volume host. If any volume is encrypted, it needs to"},{"line_number":42,"context_line":"  attach encryptors."},{"line_number":43,"context_line":"* Data migration."},{"line_number":44,"context_line":"* Delete temporary cloned volume and unset temp_volume_id."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"If error happens in above steps, the temporary cloned volume is deleted"},{"line_number":47,"context_line":"the field temp_volume_id is unset, and status of new volume is set"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aa78d24_8898ab1d","line":44,"range":{"start_line":39,"start_character":0,"end_line":44,"end_character":58},"updated":"2016-07-07 02:18:59.000000000","message":"Once you\u0027ve created the temporary volume, you can use all of the same code as retype/migrate, save on duplication. If you can clone and not clear the state to available, then it becomes completely transparent to the user, with very little extra code to write (I think)\n\n(This assumes the retype encrypted volume work is done first)","commit_id":"0f9f1cc2d88b7a9048be0f5a97ea5b9507c0c54a"},{"author":{"_account_id":1207,"name":"Duncan Thomas","email":"duncan.thomas@gmail.com","username":"duncan-thomas"},"change_message_id":"a2b28fc598ac41a4d5689ab809126f6332528d8d","unresolved":false,"context_lines":[{"line_number":64,"context_line":"REST API impact"},{"line_number":65,"context_line":"---------------"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"Change the existing create API to take a new parameter called"},{"line_number":68,"context_line":"allow_data_migration."},{"line_number":69,"context_line":"Only when this parameter is specified as True, it allows above enhanced"},{"line_number":70,"context_line":"operations."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"* Create volume"},{"line_number":73,"context_line":"  * /v3/{tenant_id}/volumes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aa78d24_8866eb27","line":70,"range":{"start_line":67,"start_character":0,"end_line":70,"end_character":11},"updated":"2016-07-07 02:18:59.000000000","message":"I\u0027d question the value of the flag. Why should the tenant care whether data migration happens or not? They just specify the type they want.","commit_id":"0f9f1cc2d88b7a9048be0f5a97ea5b9507c0c54a"}]}