)]}'
{"releasenotes/notes/add_keystone_option-138dff5efb9a53aa.yaml":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"08e8d59e3504aac1f9b38fd210021dafd2f09175","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    A new ``keystone`` config section is added so that you can"},{"line_number":5,"context_line":"    set session link attributes for communicating with keystone. This"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"bf57530f_26f55dcc","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":7},"updated":"2017-09-20 16:45:25.000000000","message":"This is a bit hairy when it comes to backports. Is there any actual upgrade impact here? In other words, doesn\u0027t the operator have to opt in to using this configuration, otherwise they are just getting what we were using before?\n\nOr does this mean the operator actually has to now configure a [keystone] section in nova.conf to use these APIs otherwise they will fail with some kind of endpoint/ksa error?","commit_id":"c0ff5b33ca42a417a5fa08e5133a27397af08c3d"},{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"5f902f31354cbb1b2f4fb82aa598d9723322f0bb","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    A new ``keystone`` config section is added so that you can"},{"line_number":5,"context_line":"    set session link attributes for communicating with keystone. This"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"bf57530f_86e649e8","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":7},"in_reply_to":"bf57530f_26f55dcc","updated":"2017-09-20 16:50:02.000000000","message":"if the operator changes nothing, things will work exactly as they did before, so there should be no issue there. Backporting this just provides a solution for operators who are hitting the referenced bug.","commit_id":"c0ff5b33ca42a417a5fa08e5133a27397af08c3d"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"a6a4cc982bf21ae10340c907898b676fcf276f23","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    A new ``keystone`` config section is added so that you can"},{"line_number":5,"context_line":"    set session link attributes for communicating with keystone. This"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f5c4f37_46aaa785","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":7},"in_reply_to":"bf57530f_64ab4ed6","updated":"2017-09-21 05:40:55.000000000","message":"yes, it\u0027s cert option, we backport so operator with older version can fix the problem as Matthew mentioned","commit_id":"c0ff5b33ca42a417a5fa08e5133a27397af08c3d"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"6db3754563495cd63a2d5e47baf409a53de9d42e","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    A new ``keystone`` config section is added so that you can"},{"line_number":5,"context_line":"    set session link attributes for communicating with keystone. This"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"bf57530f_c6bd6169","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":7},"in_reply_to":"bf57530f_86e649e8","updated":"2017-09-20 16:58:11.000000000","message":"Is that because it comes out of the [keystone_authtoken] section if [keystone] isn\u0027t configured?","commit_id":"c0ff5b33ca42a417a5fa08e5133a27397af08c3d"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"36eb170d66f43a8ba1915691a960bcc8741a48b6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    A new ``keystone`` config section is added so that you can"},{"line_number":5,"context_line":"    set session link attributes for communicating with keystone. This"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"bf57530f_64ab4ed6","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":7},"in_reply_to":"bf57530f_c6bd6169","updated":"2017-09-20 17:06:40.000000000","message":"I see this came up here too:\n\nhttps://review.openstack.org/#/c/485121/12/releasenotes/notes/add_keystone_option-138dff5efb9a53aa.yaml@11\n\nAnd looking at the generated sample config:\n\nhttp://docs-draft.openstack.org/46/505546/1/check/gate-nova-docs-ubuntu-xenial/33238f0//doc/build/html/configuration/sample-config.html\n\nIt\u0027s not the auth/credentials in this group, it\u0027s the cert options:\n\n[keystone]\n# Configuration options for the identity service\n\n#\n# From nova.conf\n#\n\n# PEM encoded Certificate Authority to use when verifying HTTPs connections.\n# (string value)\n#cafile \u003d \u003cNone\u003e\n\n# PEM encoded client certificate cert file (string value)\n#certfile \u003d \u003cNone\u003e\n\n# PEM encoded client certificate key file (string value)\n#keyfile \u003d \u003cNone\u003e\n\n# Verify HTTPS connections. (boolean value)\n#insecure \u003d false\n\n# Timeout value for http requests (integer value)\n#timeout \u003d \u003cNone\u003e\n\nSo yeah I guess this seems fine.","commit_id":"c0ff5b33ca42a417a5fa08e5133a27397af08c3d"}]}