)]}'
{"specs/liberty/brick-fetch-paths.rst":[{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"d864e25e80a44f5bb69de99f2252bb9cd82da085","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to "},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a50d1a3_243ea4b8","line":57,"updated":"2015-07-21 17:55:24.000000000","message":"Most of this makes sense, but I\u0027m not quite sure I understand the Flask based API script statements here.\n\nAre you intending Brick to become a service, or is it still a library?  What I mean is wouldn\u0027t you just make the API pieces in Cinder and/or Nova and have them call Brick methods?  Or am I reading this correctly that you want to put a Flask framework in Brick so it has it\u0027s own stand-alone API service capabilities?","commit_id":"ba7359aececf2fd3a79fef95422b34ef35a6a65e"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"266667e64e6cc017f3cc32f5e9250f47529cd9bf","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to "},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a50d1a3_bfab9d1c","line":57,"in_reply_to":"3a50d1a3_243ea4b8","updated":"2015-07-21 18:25:34.000000000","message":"I\u0027m not intending on making Brick a service at all.  I described the purpose of the flask script below your comment in the spec itself.\n\nThis flask script is intended to be used in check and gate and tempest testing.....somehow.  Basically during live migration tests we need a way of verifying on the remote compute host that when a volume has been detached that all of it\u0027s paths are now gone.  Since this is a test tool only, I didn\u0027t think it warranted adding new Nova/Cinder APIs to do this.   \n\nAnyway, that\u0027s what the intention of the flask script is, if we have a better way to do this, I\u0027m all ears.","commit_id":"ba7359aececf2fd3a79fef95422b34ef35a6a65e"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"b5ebedc96088b84c51383203dc102efd9492bfe3","unresolved":false,"context_lines":[{"line_number":33,"context_line":"volumes.  I define orphaned volumes as volume paths on a system"},{"line_number":34,"context_line":"that were associated with a volume, that has been detached.  In"},{"line_number":35,"context_line":"testing Nova live migration, there has been many times where after"},{"line_number":36,"context_line":"the nova VM was migrated, volume paths had been left behind on the"},{"line_number":37,"context_line":"originating compute host after the volume was detached.   This can"},{"line_number":38,"context_line":"cause problems later on when volumes are attached to that host."},{"line_number":39,"context_line":"Some SAN arrays reuse iqn\u0027s and or LUN ids for volumes.  This can"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_f2043719","line":36,"updated":"2015-07-31 02:14:21.000000000","message":"Why can\u0027t we fix that problem instead of introducing this? I\u0027m mainly asking because that spec leaves things open for this question.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"f1568e33bf66802d6afccd6c4d9edf1c9fd21df9","unresolved":false,"context_lines":[{"line_number":33,"context_line":"volumes.  I define orphaned volumes as volume paths on a system"},{"line_number":34,"context_line":"that were associated with a volume, that has been detached.  In"},{"line_number":35,"context_line":"testing Nova live migration, there has been many times where after"},{"line_number":36,"context_line":"the nova VM was migrated, volume paths had been left behind on the"},{"line_number":37,"context_line":"originating compute host after the volume was detached.   This can"},{"line_number":38,"context_line":"cause problems later on when volumes are attached to that host."},{"line_number":39,"context_line":"Some SAN arrays reuse iqn\u0027s and or LUN ids for volumes.  This can"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_f6e355d7","line":36,"in_reply_to":"3a50d1a3_f2043719","updated":"2015-09-29 18:34:51.000000000","message":"Good point.  The issues we discovered, that lead to writing this sec and code, have since been fixed.  This spec talks about how we can add APIs into brick to ensure that this problem isn\u0027t introduced again.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":7173,"name":"Scott DAngelo","email":"scott.dangelo@gmail.com","username":"scottda"},"change_message_id":"3484397ca59a2612f5a81b7354317ab51a0c342a","unresolved":false,"context_lines":[{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The primary use case is for fetching the list of existing paths for a volume"},{"line_number":48,"context_line":"on a system after attach and detach."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Proposed change"},{"line_number":51,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a2ca52d_4e02090d","line":48,"updated":"2015-10-14 18:15:39.000000000","message":"I think that this could be expanded in the future to improvements in the way that Nova does volume attach/detach. Currently, these are asynchronous with no check in Nova to verify that the attach/detach has actually occurred. Adding a Brick API would allow a future version of Nova to perform these checks, which would help prevent the situation where state in Cinder does not match state in Nova.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"b5ebedc96088b84c51383203dc102efd9492bfe3","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_ed321cf2","line":57,"updated":"2015-07-31 02:14:21.000000000","message":"I\u0027m also asking the question above because it seems odd we\u0027re introducing flask to solve a problem live migrations not being cleaned up properly.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"c51dcb808433400558343a7704a724214fef1a31","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a26ad4f_79f6ffd8","line":57,"in_reply_to":"3a29b11f_97da22e7","updated":"2015-10-27 07:36:47.000000000","message":"will do.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"f1568e33bf66802d6afccd6c4d9edf1c9fd21df9","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_d67ad1f0","line":57,"in_reply_to":"3a50d1a3_ed321cf2","updated":"2015-09-29 18:34:51.000000000","message":"This spec and patch isn\u0027t about solving the live migration problems.  This spec outlays an API into brick that allows us a mechanism for verification.   If future patches land that cause volumes to be left behind, we can detect it if we get this API in and a way to remotely call it (via a running flask), to check for those paths being left behind.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":1736,"name":"Ivan Kolodyazhny","email":"e0ne@e0ne.info","username":"e0ne"},"change_message_id":"71c2e6050da0e17ab3ae9859e8acd8e428359fcc","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_f5284be4","line":57,"in_reply_to":"3a50d1a3_ed321cf2","updated":"2015-09-29 07:36:39.000000000","message":"Why do we need Flask app instead of CLI tool?","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"d06a3f578937af360838c92fd00acd38037c8528","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_9776a2d5","line":57,"in_reply_to":"9a1a9d01_1675a9f8","updated":"2015-10-21 14:37:16.000000000","message":"I\u0027ve been asking this as well.  The statement below \"Add a flask script to expose these API calls\" does NOT explain why we need a flask script at all!  It just restates that you\u0027re implementing a flask script.\n\nThe question a number of us have is \"why\"?  What\u0027s the point of this?  How will it work?  Why is it the right option?  What is it\u0027s real purpose in life?  Why flask and not shell calls?  What is it exactly that\u0027s being done here and what problem is being solved with it?\n\nIs it possible that perhaps this should be follow up work?","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"d06a3f578937af360838c92fd00acd38037c8528","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_97da22e7","line":57,"in_reply_to":"9a1a9d01_d67ad1f0","updated":"2015-10-21 14:37:16.000000000","message":"Then you should remove your statement using live-migration as an example use case probably don\u0027t you think?","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"f1568e33bf66802d6afccd6c4d9edf1c9fd21df9","unresolved":false,"context_lines":[{"line_number":54,"context_line":"1) fetch the existing paths on the system for a given volume."},{"line_number":55,"context_line":"2) fetch all of the volume paths for a connector."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Flask based API script."},{"line_number":58,"context_line":"Add a new flask script that exposes these API calls that can be run"},{"line_number":59,"context_line":"in a test environment.  This flask script is needed in order to"},{"line_number":60,"context_line":"automatically verify the success of detach during nova live migration"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_1675a9f8","line":57,"in_reply_to":"9a1a9d01_f5284be4","updated":"2015-09-29 18:34:51.000000000","message":"It\u0027s explained in here below.","commit_id":"c1e65a513fff528de5d2e6c017cd1bfee6a4a136"}]}
