)]}'
{"cinder/volume/flows/manager/create_volume.py":[{"author":{"_account_id":1297,"name":"Joshua Harlow","email":"jxharlow@godaddy.com","username":"harlowja"},"change_message_id":"a658810dbe4d2887a3133d62a36e8a49093579cf","unresolved":false,"context_lines":[{"line_number":45,"context_line":")"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"AVAILABLE_TASKS \u003d ("},{"line_number":49,"context_line":"    \u0027entry_create\u0027,"},{"line_number":50,"context_line":"    \u0027extract-volume-ref-task\u0027,"},{"line_number":51,"context_line":"    \u0027extract-volume-spec-task\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"da86d52c_9503c772","line":48,"updated":"2015-01-31 01:39:37.000000000","message":"So this is slightly weird in that u could infer this information from the code itself right? Doesn\u0027t the \u0027get_flow\u0027 routine has this same information?\n\nU could create the \u0027full\u0027 \u0027volume_flow\u0027 workflow object there and then iterate over it and then create a secondary \u0027volume_flow\u0027 workflow object that has just the stuff u want to run; both of these approaches could avoid yet another name/ordering mapping...\n\nExample that could do just this:\n\nhttp://paste.ubuntu.com/9967086/\n\nNeeds a small change (but you would likely do this in the get_flow routine directly without this change...)\n\nhttp://paste.ubuntu.com/9967074/\n\nThat will then output the following (which u can introspect and then create a new flow that has just the leftover stuff...)\n\nhttp://paste.ubuntu.com/9967106/\n\nTLDR; instead of coding the AVAILABLE_TASKS in a static list; the get_flow routine would seem to have the same info in a structure u can already use?","commit_id":"3250dadd9b7aa0b5c49a4af2d7913454fd825ab8"},{"author":{"_account_id":1297,"name":"Joshua Harlow","email":"jxharlow@godaddy.com","username":"harlowja"},"change_message_id":"a658810dbe4d2887a3133d62a36e8a49093579cf","unresolved":false,"context_lines":[{"line_number":203,"context_line":"            return"},{"line_number":204,"context_line":"        micro_states_properties \u003d {"},{"line_number":205,"context_line":"            \u0027volume_id\u0027: volume_id,"},{"line_number":206,"context_line":"            \u0027state\u0027: \u0027entry_create\u0027,"},{"line_number":207,"context_line":"        }"},{"line_number":208,"context_line":"        self.db.volume_micro_state_update("},{"line_number":209,"context_line":"            context, volume_id, micro_states_properties)"}],"source_content_type":"text/x-python","patch_set":1,"id":"da86d52c_55094f94","line":206,"updated":"2015-01-31 01:39:37.000000000","message":"Seems like these state constants should almost be constants that are on these classes; and then referred to in the class itself.","commit_id":"3250dadd9b7aa0b5c49a4af2d7913454fd825ab8"}]}