)]}'
{"devstack/plugin.sh":[{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"8537ee38010836111498d777352e0008ee9d7aa8","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    iniset $SEARCHLIGHT_CONF DEFAULT public_endpoint $SEARCHLIGHT_SERVICE_PROTOCOL://$SEARCHLIGHT_SERVICE_HOST:$SEARCHLIGHT_SERVICE_PORT/"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"    # OpenStack users"},{"line_number":100,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_username admin "},{"line_number":101,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_tenant_name admin"},{"line_number":102,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_password $ADMIN_PASSWORD"},{"line_number":103,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_auth_url $KEYSTONE_AUTH_URI/v2.0"}],"source_content_type":"text/x-sh","patch_set":7,"id":"fa1b9901_ac2fb73d","line":100,"updated":"2015-08-20 17:23:50.000000000","message":"I\u0027m not sure using admin/admin is the right path here. Although effective, the same should be able to be accomplished with an admin role assignment.","commit_id":"daaa9e24aeb8c54bc7b2989fa256cee23ffa5190"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"57b82938d48f7ec64f5088e7bb6ab243ab7ebf3f","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    iniset $SEARCHLIGHT_CONF DEFAULT public_endpoint $SEARCHLIGHT_SERVICE_PROTOCOL://$SEARCHLIGHT_SERVICE_HOST:$SEARCHLIGHT_SERVICE_PORT/"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"    # OpenStack users"},{"line_number":100,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_username admin "},{"line_number":101,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_tenant_name admin"},{"line_number":102,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_password $ADMIN_PASSWORD"},{"line_number":103,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_auth_url $KEYSTONE_AUTH_URI/v2.0"}],"source_content_type":"text/x-sh","patch_set":7,"id":"fa1b9901_e084d90b","line":100,"updated":"2015-08-20 15:36:43.000000000","message":"ws","commit_id":"daaa9e24aeb8c54bc7b2989fa256cee23ffa5190"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"adcb7bc8a43811a38b113bac53b98b8eaaff192c","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    iniset $SEARCHLIGHT_CONF DEFAULT public_endpoint $SEARCHLIGHT_SERVICE_PROTOCOL://$SEARCHLIGHT_SERVICE_HOST:$SEARCHLIGHT_SERVICE_PORT/"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"    # OpenStack users"},{"line_number":100,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_username admin "},{"line_number":101,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_tenant_name admin"},{"line_number":102,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_password $ADMIN_PASSWORD"},{"line_number":103,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_auth_url $KEYSTONE_AUTH_URI/v2.0"}],"source_content_type":"text/x-sh","patch_set":7,"id":"fa1b9901_9237694c","line":100,"in_reply_to":"fa1b9901_ac2fb73d","updated":"2015-08-20 19:10:33.000000000","message":"yeah, assigning the searchlight user the admin role on the services tenant is probably a better solution.","commit_id":"daaa9e24aeb8c54bc7b2989fa256cee23ffa5190"},{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"15cb2898a5090307e68f160f26f0524d62039653","unresolved":false,"context_lines":[{"line_number":99,"context_line":"    # OpenStack users"},{"line_number":100,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_username searchlight"},{"line_number":101,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_tenant_name $SERVICE_TENANT_NAME"},{"line_number":102,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_password $ADMIN_PASSWORD"},{"line_number":103,"context_line":"    iniset $SEARCHLIGHT_CONF service_credentials os_auth_url $KEYSTONE_AUTH_URI/v2.0"},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"    # Keystone Middleware"}],"source_content_type":"text/x-sh","patch_set":10,"id":"fa1b9901_6dd964f2","line":102,"updated":"2015-08-21 15:20:38.000000000","message":"I actually don\u0027t think this should have changed. They happen to be the same by default. But this is fragile.","commit_id":"3efabce9e8f9ca53a2bd5ac16c8effe217cbcca1"}],"doc/source/dev-environment.rst":[{"author":{"_account_id":7665,"name":"Travis Tripp","email":"os.travis.tripp@gmail.com","username":"travis.tripp"},"change_message_id":"b012a57ae05c549ef8ba453164e2d19125c0ab77","unresolved":false,"context_lines":[{"line_number":164,"context_line":"    policy_file \u003d ~/openstack/searchlight/etc/policy.json"},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"    [paste_deploy]"},{"line_number":167,"context_line":"    flavor \u003d keystone"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"Setup credentials to either use existing credentials or create a new keystone"},{"line_number":170,"context_line":"user with the defaults that searchlight uses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_62c4d03f","line":167,"updated":"2015-08-10 14:31:18.000000000","message":"Lakshmi,\n\nI\u0027m thinking that we should actually create a section above \"Suggested changes\" and say Important Changes::\n\nI\u0027d put the policy_file setting and this in that section.\n\nI know this isn\u0027t really required for it to function, but it should be more strongly worded.","commit_id":"4530760cfb17a1c4f17de65fe45b3c30c22afd64"},{"author":{"_account_id":8959,"name":"Lakshmi N Sampath","email":"lakshmi.sampath@hp.com","username":"lakshmi"},"change_message_id":"901fd807927bfe357cee7a15221857686fb0b4d9","unresolved":false,"context_lines":[{"line_number":164,"context_line":"    policy_file \u003d ~/openstack/searchlight/etc/policy.json"},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"    [paste_deploy]"},{"line_number":167,"context_line":"    flavor \u003d keystone"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"Setup credentials to either use existing credentials or create a new keystone"},{"line_number":170,"context_line":"user with the defaults that searchlight uses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_bdee5b89","line":167,"in_reply_to":"1a4dcd0f_62c4d03f","updated":"2015-08-11 04:16:57.000000000","message":"ok. will do a final check to see if there are any other fields worth mentioning.","commit_id":"4530760cfb17a1c4f17de65fe45b3c30c22afd64"},{"author":{"_account_id":7665,"name":"Travis Tripp","email":"os.travis.tripp@gmail.com","username":"travis.tripp"},"change_message_id":"eef477c7b61d2c0720984eecf61bf05bcbfec350","unresolved":false,"context_lines":[{"line_number":162,"context_line":"    policy_file \u003d ~/openstack/searchlight/etc/policy.json"},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"    [paste_deploy]"},{"line_number":165,"context_line":"    flavor \u003d keystone"},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"Suggested changes::"},{"line_number":168,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a4dcd0f_0804c647","line":165,"updated":"2015-08-11 16:28:53.000000000","message":"I\u0027ve made these changes in a local devstack env and in my \"manually setup env.  This definitely prevents the case of not allowing it through, but I can\u0027t ever get through now.  I tried using the same admin token to query nova and searchlight.  Nova responds, but searchlight always responds with a 401.  Commenting out the above line (flavor \u003d keystone) and it always works (no authentication). Is there something else missing?\n\npython ./scripts/get_token.py\n\ntoken\u003d\u003ctoken\u003e\n\ncurl -X POST http://localhost:9393/v1/search -H \"X-Auth-Token:$token\" -d @search.json -H \"Content-Type: application/json\"\n\nReturns 401 Unauthorized\n\nLog message: 2015-08-11 09:53:08.149 WARNING keystonemiddleware.auth_token [-] Authorization failed for token\n\n\nBut, making the following call to Nova, succeeds:\n\ncurl -X GET  http://127.0.0.1:8774/v2.1/$tenant_id/servers/detail -H \"X-Auth-Token:$token\" | python -mjson.tool","commit_id":"3618cd9051c8e3404d745782ea2bcc662a129a5d"},{"author":{"_account_id":10063,"name":"Steve McLellan","email":"steven.j.mclellan@gmail.com","username":"sjmc7"},"change_message_id":"7a8fd9d15e4e40022e3df2792640c6771360bf25","unresolved":false,"context_lines":[{"line_number":168,"context_line":""},{"line_number":169,"context_line":"    debug \u003d true"},{"line_number":170,"context_line":"    verbose \u003d true"},{"line_number":171,"context_line":"    log_file \u003d /var/log/searchlight/api.log"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"Setup credentials to either use existing credentials or create a new keystone"},{"line_number":174,"context_line":"user with the defaults that searchlight uses."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a4dcd0f_146aaaed","line":171,"updated":"2015-08-11 14:21:51.000000000","message":"Though not because of this patch, this is actually a bit of a problem at the moment; the listener and api will write to the same log. This must be a solved problem (maybe searchlight.conf, searchlight-api.conf?)","commit_id":"3618cd9051c8e3404d745782ea2bcc662a129a5d"},{"author":{"_account_id":7665,"name":"Travis Tripp","email":"os.travis.tripp@gmail.com","username":"travis.tripp"},"change_message_id":"d4f3322a2e6cd6e1998cf7d757241be138872304","unresolved":false,"context_lines":[{"line_number":168,"context_line":""},{"line_number":169,"context_line":"    debug \u003d true"},{"line_number":170,"context_line":"    verbose \u003d true"},{"line_number":171,"context_line":"    log_file \u003d /var/log/searchlight/api.log"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"Setup credentials to either use existing credentials or create a new keystone"},{"line_number":174,"context_line":"user with the defaults that searchlight uses."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a4dcd0f_3979d282","line":171,"in_reply_to":"1a4dcd0f_146aaaed","updated":"2015-08-11 22:36:21.000000000","message":"Also, this is inconsistent with the directions above.  the directions above say to create a log dir in \u003cgit-dir\u003e/log.  So, if this is the instruction then above instructions should go away.  Or this should be set to log in the created log dir.","commit_id":"3618cd9051c8e3404d745782ea2bcc662a129a5d"}]}