)]}'
{"specs/kilo/associate-flavors-datastores.rst":[{"author":{"_account_id":8214,"name":"Auston McReynolds","email":"amcreynolds@ebaysf.com","username":"amcreynolds"},"change_message_id":"b84809d783d275d96783683ad21ed208469fc5e6","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- The trove-manage utility will provide the ability:"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":" - to add and delete the datastore version-flavor associations."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- There will be an additional API call in order to get a list of flavors for the specified datastore version id."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a890539_a27a6885","line":40,"updated":"2014-11-18 00:04:34.000000000","message":"is the desired behavior:\n\n(1) all nova flavors are permitted for a datastore-version unless one or more entries are found in datastore_version_metadata, in which case only those are permitted.\n\nor\n\n(2) no flavors are permitted for a datastore unless they are explicitly listed in datastore_version_metadata.","commit_id":"dc490bd66782587e24774fafd3b7ff03485b7584"},{"author":{"_account_id":7796,"name":"Riddhi Shah","email":"ridhi.j.shah@gmail.com","username":"ridhi-j-shah"},"change_message_id":"e5b1399bdf3dba70fa647e7cfd80ed42b815c035","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- The trove-manage utility will provide the ability:"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":" - to add and delete the datastore version-flavor associations."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- There will be an additional API call in order to get a list of flavors for the specified datastore version id."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a890539_5a40b206","line":40,"in_reply_to":"5a890539_3fc2f8e8","updated":"2014-11-18 16:11:03.000000000","message":"Also, Auston, forgot to also add in my previous reply: basically I thought of implementing your option 1 - \u0027all nova flavors are permitted for a datastore-version unless one or more entries are found in datastore_version_metadata, in which case only those are permitted.\u0027","commit_id":"dc490bd66782587e24774fafd3b7ff03485b7584"},{"author":{"_account_id":8214,"name":"Auston McReynolds","email":"amcreynolds@ebaysf.com","username":"amcreynolds"},"change_message_id":"c4d97226cc6d3e1d58644779061d60a5c8471aae","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- The trove-manage utility will provide the ability:"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":" - to add and delete the datastore version-flavor associations."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- There will be an additional API call in order to get a list of flavors for the specified datastore version id."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a890539_81b46ad2","line":40,"in_reply_to":"5a890539_5a40b206","updated":"2014-11-18 18:47:44.000000000","message":"it seems to me that the following behavior likely makes the most sense:\n\nall nova flavors are permitted for a datastore-version unless one or more entries are found in datastore_version_metadata, in which case only those are permitted. The new route (/\u003cdatastore-version\u003e/flavors) will return all nova flavors if no entries are found for said datastore-version in datastore_version_metadata, otherwise only the entries found are returned. the existing route (/flavors) behaves exactly as it does today.\n\nthoughts?","commit_id":"dc490bd66782587e24774fafd3b7ff03485b7584"},{"author":{"_account_id":7796,"name":"Riddhi Shah","email":"ridhi.j.shah@gmail.com","username":"ridhi-j-shah"},"change_message_id":"0476ba860461a441e1a0d8055e27ef86bb6032d1","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- The trove-manage utility will provide the ability:"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":" - to add and delete the datastore version-flavor associations."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- There will be an additional API call in order to get a list of flavors for the specified datastore version id."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5a890539_3fc2f8e8","line":40,"in_reply_to":"5a890539_a27a6885","updated":"2014-11-18 16:00:07.000000000","message":"Auston: \nI was thinking of implementing the following behavior:\n\nWhen we try to provision an instance of a particular datastore version, we check if the flavor is:\n\n1. present as a mapping with the ds_version in the datastore_version_metadata table. \n\n2. If 1 not True, check if the flavor is a valid nova flavor (this assures backwards compatibility - things would not break if the metadata mapping is not present. )\n\nI would like more feedback on this.","commit_id":"dc490bd66782587e24774fafd3b7ff03485b7584"}]}