)]}'
{"specs/proposed/refstack-client-cloudid.rst":[{"author":{"_account_id":9377,"name":"Sergey Slipushenko","email":"slipushenko@gmail.com","username":"sslypushenko"},"change_message_id":"c53606ea721f11ff929b4800b43bcc2741033d82","unresolved":false,"context_lines":[{"line_number":26,"context_line":"cloud ID when the Keystone Service ID is not available. When"},{"line_number":27,"context_line":"the Keystone Service ID is not available, refstack-client will"},{"line_number":28,"context_line":"instead generate an md5 hash of the active tempest.conf file"},{"line_number":29,"context_line":"and use that is the CPID."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Although this ID generation scheme is stable across multiple"},{"line_number":32,"context_line":"runs, it is not stable across Tempest configuration. In effect,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_36d29635","line":29,"updated":"2015-09-09 16:37:18.000000000","message":"This proposition looks really weird to me. IMO, we should ask user to provide CloudID by your own. It will make CloudID just a some soft of metadata tag. In addition, such kind of CloudID will be a human readable and carry some information for user.","commit_id":"996a3d58dde87ce32af609a16399c95e17def7bb"},{"author":{"_account_id":7822,"name":"Chris Hoge (not involved in upstream development)","email":"chris@hogepodge.com","username":"hogepodge"},"change_message_id":"0a928cc11c487b7162c093dc4885216eadf8e2ff","unresolved":false,"context_lines":[{"line_number":26,"context_line":"cloud ID when the Keystone Service ID is not available. When"},{"line_number":27,"context_line":"the Keystone Service ID is not available, refstack-client will"},{"line_number":28,"context_line":"instead generate an md5 hash of the active tempest.conf file"},{"line_number":29,"context_line":"and use that is the CPID."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Although this ID generation scheme is stable across multiple"},{"line_number":32,"context_line":"runs, it is not stable across Tempest configuration. In effect,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_a045f743","line":29,"in_reply_to":"da20952f_36d29635","updated":"2015-09-09 17:38:56.000000000","message":"What do we do when a user doesn\u0027t have access to admin interface? We need a way to test public clouds.","commit_id":"996a3d58dde87ce32af609a16399c95e17def7bb"},{"author":{"_account_id":9377,"name":"Sergey Slipushenko","email":"slipushenko@gmail.com","username":"sslypushenko"},"change_message_id":"339889789c18ef2417080c5c00fc432658e922f4","unresolved":false,"context_lines":[{"line_number":26,"context_line":"cloud ID when the Keystone Service ID is not available. When"},{"line_number":27,"context_line":"the Keystone Service ID is not available, refstack-client will"},{"line_number":28,"context_line":"instead generate an md5 hash of the active tempest.conf file"},{"line_number":29,"context_line":"and use that is the CPID."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Although this ID generation scheme is stable across multiple"},{"line_number":32,"context_line":"runs, it is not stable across Tempest configuration. In effect,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_a9e86417","line":29,"in_reply_to":"da20952f_a045f743","updated":"2015-09-10 11:37:37.000000000","message":"My suggestion here is asking user to provide cloud id manually. As far as I understand, it fits to RefStack goals with 100%. \n\nRight now we should trust to user in terms of test results authenticity\njust because we don\u0027t have another options here. So, I don\u0027t see any reason why we can\u0027t  trust to user in terms of cloud id. And anyway it is better than random ID.","commit_id":"996a3d58dde87ce32af609a16399c95e17def7bb"}]}