)]}'
{"etc/metadefs/storage-volume-type.json":[{"author":{"_account_id":14676,"name":"Kairat Kushaev","email":"kkushaev@mirantis.com","username":"kairat_kushaev"},"change_message_id":"28fcfb7c9ed1024789921649afb613abd9ee37f6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{"},{"line_number":2,"context_line":"    \"namespace\": \"OS::Storage::Volumetype\","},{"line_number":3,"context_line":"    \"display_name\": \"Cinder Volume Type\","},{"line_number":4,"context_line":"    \"description\": \"The Cinder volume type configuration option.  \\n\\nVolume type assignment provides a mechanism not only to provide scheduling to a specific storage back-end, but also can be used to specify specific information for a back-end storage device to act upon.\","},{"line_number":5,"context_line":"    \"visibility\": \"public\","},{"line_number":6,"context_line":"    \"protected\": true,"},{"line_number":7,"context_line":"    \"resource_type_associations\": ["}],"source_content_type":"application/json","patch_set":2,"id":"da6ed579_8716d053","line":4,"range":{"start_line":4,"start_character":68,"end_line":4,"end_character":69},"updated":"2016-01-18 08:36:43.000000000","message":"Did you add an empty string intentionally here?","commit_id":"9c8b6dced8b93c38f7a657462fa5fc4ba61e76a4"},{"author":{"_account_id":10115,"name":"Mitsuhiro Tanino","email":"mitsuhiro.tanino@lycorp.co.jp","username":"mtanino"},"change_message_id":"f6f5f418135a1a2aaf75b984b2f06cc77752b2ef","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{"},{"line_number":2,"context_line":"    \"namespace\": \"OS::Storage::Volumetype\","},{"line_number":3,"context_line":"    \"display_name\": \"Cinder Volume Type\","},{"line_number":4,"context_line":"    \"description\": \"The Cinder volume type configuration option.  \\n\\nVolume type assignment provides a mechanism not only to provide scheduling to a specific storage back-end, but also can be used to specify specific information for a back-end storage device to act upon.\","},{"line_number":5,"context_line":"    \"visibility\": \"public\","},{"line_number":6,"context_line":"    \"protected\": true,"},{"line_number":7,"context_line":"    \"resource_type_associations\": ["}],"source_content_type":"application/json","patch_set":2,"id":"da6ed579_25aa601a","line":4,"range":{"start_line":4,"start_character":68,"end_line":4,"end_character":69},"in_reply_to":"da6ed579_8716d053","updated":"2016-01-18 16:46:29.000000000","message":"I saw compute-libvirt-flavor.json as a reference. But when I checked the description at the Horizon view, this \u0027\\n\\n\u0027 doesn\u0027t work. Should we remove the return code?","commit_id":"9c8b6dced8b93c38f7a657462fa5fc4ba61e76a4"},{"author":{"_account_id":14676,"name":"Kairat Kushaev","email":"kkushaev@mirantis.com","username":"kairat_kushaev"},"change_message_id":"28fcfb7c9ed1024789921649afb613abd9ee37f6","unresolved":false,"context_lines":[{"line_number":13,"context_line":"    \"properties\": {"},{"line_number":14,"context_line":"        \"img_volume_type\": {"},{"line_number":15,"context_line":"            \"title\": \"Image Volume Type\","},{"line_number":16,"context_line":"            \"description\": \"Specifies the volume type that should be applied during new volume creation with a image. This value is passed to Cinder when creating a new volume. Priority of volume type related parameters are 1.volume_type(via API or CLI), 2.cinder_img_volume_type, 3.default_volume_type(via cinder.conf). If not specified, volume_type or default_volume_type will be referred based on their priority.\","},{"line_number":17,"context_line":"            \"type\": \"string\""},{"line_number":18,"context_line":"        }"},{"line_number":19,"context_line":"    }"}],"source_content_type":"application/json","patch_set":2,"id":"da6ed579_02696e8b","line":16,"range":{"start_line":16,"start_character":28,"end_line":16,"end_character":37},"updated":"2016-01-18 08:36:43.000000000","message":"No new lines here. Is it intentional to have such long string in description?","commit_id":"9c8b6dced8b93c38f7a657462fa5fc4ba61e76a4"},{"author":{"_account_id":10115,"name":"Mitsuhiro Tanino","email":"mitsuhiro.tanino@lycorp.co.jp","username":"mtanino"},"change_message_id":"f6f5f418135a1a2aaf75b984b2f06cc77752b2ef","unresolved":false,"context_lines":[{"line_number":13,"context_line":"    \"properties\": {"},{"line_number":14,"context_line":"        \"img_volume_type\": {"},{"line_number":15,"context_line":"            \"title\": \"Image Volume Type\","},{"line_number":16,"context_line":"            \"description\": \"Specifies the volume type that should be applied during new volume creation with a image. This value is passed to Cinder when creating a new volume. Priority of volume type related parameters are 1.volume_type(via API or CLI), 2.cinder_img_volume_type, 3.default_volume_type(via cinder.conf). If not specified, volume_type or default_volume_type will be referred based on their priority.\","},{"line_number":17,"context_line":"            \"type\": \"string\""},{"line_number":18,"context_line":"        }"},{"line_number":19,"context_line":"    }"}],"source_content_type":"application/json","patch_set":2,"id":"da6ed579_65b0588c","line":16,"range":{"start_line":16,"start_character":28,"end_line":16,"end_character":37},"in_reply_to":"da6ed579_02696e8b","updated":"2016-01-18 16:46:29.000000000","message":"I checked this description at the Horizon view of master branch, and I think this is readable for user.","commit_id":"9c8b6dced8b93c38f7a657462fa5fc4ba61e76a4"},{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"d48ea9bb53d161778a62213c74365b8e4a054177","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{"},{"line_number":2,"context_line":"    \"namespace\": \"OS::Storage::Volumetype\","},{"line_number":3,"context_line":"    \"display_name\": \"Cinder Volume Type\","},{"line_number":4,"context_line":"    \"description\": \"The Cinder volume type configuration option. Volume type assignment provides a mechanism not only to provide scheduling to a specific storage back-end, but also can be used to specify specific information for a back-end storage device to act upon.\","},{"line_number":5,"context_line":"    \"visibility\": \"public\","}],"source_content_type":"application/json","patch_set":3,"id":"ba63e191_f972df7b","line":2,"range":{"start_line":2,"start_character":22,"end_line":2,"end_character":29},"updated":"2016-01-19 09:40:57.000000000","message":"The namespace names are generally derived from Heat Resources Types. It seems that for Cinder it should be OS::Cinder::VolumeType [1].\n\n[1] http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Cinder::VolumeType","commit_id":"a3f6fddcbdbaefe907f82c5517499968515b4b70"},{"author":{"_account_id":10115,"name":"Mitsuhiro Tanino","email":"mitsuhiro.tanino@lycorp.co.jp","username":"mtanino"},"change_message_id":"c739e62fd050f51dfc44c8658f014b0173556f5f","unresolved":false,"context_lines":[{"line_number":1,"context_line":"{"},{"line_number":2,"context_line":"    \"namespace\": \"OS::Storage::Volumetype\","},{"line_number":3,"context_line":"    \"display_name\": \"Cinder Volume Type\","},{"line_number":4,"context_line":"    \"description\": \"The Cinder volume type configuration option. Volume type assignment provides a mechanism not only to provide scheduling to a specific storage back-end, but also can be used to specify specific information for a back-end storage device to act upon.\","},{"line_number":5,"context_line":"    \"visibility\": \"public\","}],"source_content_type":"application/json","patch_set":3,"id":"ba63e191_22110953","line":2,"range":{"start_line":2,"start_character":22,"end_line":2,"end_character":29},"in_reply_to":"ba63e191_f972df7b","updated":"2016-01-19 16:38:08.000000000","message":"Thank you for the link.","commit_id":"a3f6fddcbdbaefe907f82c5517499968515b4b70"},{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"d48ea9bb53d161778a62213c74365b8e4a054177","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    \"resource_type_associations\": ["},{"line_number":8,"context_line":"        {"},{"line_number":9,"context_line":"            \"name\": \"OS::Glance::Image\","},{"line_number":10,"context_line":"            \"prefix\": \"cinder_\""},{"line_number":11,"context_line":"        }"},{"line_number":12,"context_line":"    ],"},{"line_number":13,"context_line":"    \"properties\": {"}],"source_content_type":"application/json","patch_set":3,"id":"ba63e191_79ffcf01","line":10,"range":{"start_line":10,"start_character":23,"end_line":10,"end_character":30},"updated":"2016-01-19 09:40:57.000000000","message":"It\u0027s worth thinking if \"cinder:\" isn\u0027t more appropriate. Right now we have mixed _ and : as separators. I don\u0027t have any opinion though.","commit_id":"a3f6fddcbdbaefe907f82c5517499968515b4b70"},{"author":{"_account_id":10115,"name":"Mitsuhiro Tanino","email":"mitsuhiro.tanino@lycorp.co.jp","username":"mtanino"},"change_message_id":"c739e62fd050f51dfc44c8658f014b0173556f5f","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    \"resource_type_associations\": ["},{"line_number":8,"context_line":"        {"},{"line_number":9,"context_line":"            \"name\": \"OS::Glance::Image\","},{"line_number":10,"context_line":"            \"prefix\": \"cinder_\""},{"line_number":11,"context_line":"        }"},{"line_number":12,"context_line":"    ],"},{"line_number":13,"context_line":"    \"properties\": {"}],"source_content_type":"application/json","patch_set":3,"id":"ba63e191_f3ae6297","line":10,"range":{"start_line":10,"start_character":23,"end_line":10,"end_character":30},"in_reply_to":"ba63e191_79ffcf01","updated":"2016-01-19 16:38:08.000000000","message":"I understand your consideration.\n\nI checked other properties for Glance image metadata, but all of them use underscore for the separator. Also I talked some persons from Glance community, they suggested \u0027cinder_\u0027 prefix.\n\nI don\u0027t have strong opinion here too.","commit_id":"a3f6fddcbdbaefe907f82c5517499968515b4b70"}]}