)]}'
{"etc/keystone.conf.sample":[{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"1224812f45b941035de2ce83d0c58014b7276cd9","unresolved":false,"context_lines":[{"line_number":119,"context_line":"# template_file \u003d default_catalog.templates"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"[token]"},{"line_number":122,"context_line":"# driver \u003d keystone.token.backends.sql.Token"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"# Amount of time a token should remain valid (in seconds)"},{"line_number":125,"context_line":"# expiration \u003d 86400"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAPX%2F%2Fz%2FI%3D","line":122,"updated":"2013-06-09 17:50:36.000000000","message":"I absolutely agree that kvs is the wrong answer.  The question is, should the default be sql or memcache?  The problem with sql is that the DB grows very fast....and we don\u0027t have any (by default) mechanism that cull it.  Memcache will expire the tokens and avoid this (although of course, will not be permanent if you need audit capability).  Personally, I\u0027d vote for memcache.  Probably just worth canvassing the other core\u0027s on this.","commit_id":"0b242217113025084838f4bda9dc53b243276bf7"},{"author":{"_account_id":6282,"name":"Wu Wenxiang","email":"wu.wenxiang@algoblu.com","username":"wu-wenxiang"},"change_message_id":"124eddb905988faa2f381e7e380ba4a45cb2b893","unresolved":false,"context_lines":[{"line_number":119,"context_line":"# template_file \u003d default_catalog.templates"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"[token]"},{"line_number":122,"context_line":"# driver \u003d keystone.token.backends.sql.Token"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"# Amount of time a token should remain valid (in seconds)"},{"line_number":125,"context_line":"# expiration \u003d 86400"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAPX%2F%2Fz1s%3D","line":122,"in_reply_to":"AAAAPX%2F%2Fz%2FI%3D","updated":"2013-06-11 09:37:40.000000000","message":"Thanks for your advice. I had also thinked about Memcache \u0026 SQL, which one is better? In my opinion: 1. SQL is more popular used than memcache because DB is required while memcache is optional. 2. DB has enough capability to handle token grow fast. Actually, we use DB in a public cloud deployment. ^_^","commit_id":"0b242217113025084838f4bda9dc53b243276bf7"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"7258bd03dc8bcf580d42390cec571d920ac2ebb9","unresolved":false,"context_lines":[{"line_number":119,"context_line":"# template_file \u003d default_catalog.templates"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"[token]"},{"line_number":122,"context_line":"# driver \u003d keystone.token.backends.sql.Token"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"# Amount of time a token should remain valid (in seconds)"},{"line_number":125,"context_line":"# expiration \u003d 86400"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAPX%2F%2FvD4%3D","line":122,"in_reply_to":"AAAAPX%2F%2Fz1s%3D","updated":"2013-06-11 18:00:22.000000000","message":"I\u0027d rather limit external dependencies out of the box, so I vote for SQL, although I would lean toward memcache for production as well","commit_id":"0b242217113025084838f4bda9dc53b243276bf7"}]}