)]}'
{"specs/pike/messaging-config.rst":[{"author":{"_account_id":2813,"name":"Mehdi Abaakouk","email":"sileht@sileht.net","username":"sileht"},"change_message_id":"7611bf31023874f7c5330ce0f8cbf69e213efaf6","unresolved":false,"context_lines":[{"line_number":133,"context_line":"  | System(1) |     | System(2) |"},{"line_number":134,"context_line":"  +-----------+     +-----------+"},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Proposed change"},{"line_number":138,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":139,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df140735_162ff2a1","line":136,"updated":"2017-05-31 07:27:59.000000000","message":"I think I don\u0027t get something, All these scenarios are already possible and options can be defined as deployer wish, per backend, per transport and different transports can already be used for rpc or notification.\n\n* scenario1: deployer can just use:\n\n  [DEFAULT]/transport_url \u003d rabbit://user:pass@foobar/vhost?ssl\u003dTrue\u0026ssl_ca_file\u003d/etc/ssl/foobar.cert\n\n* scenario2: deployer can just use:\n\n  [DEFAULT]/transport_url \u003d rabbit://user:pass@foobar/vhost?heartbeat_timeout_threshold\u003d60\n  [notification]/transport_url \u003d rabbit://user:pass@foobar/vhost?heartbeat_timeout_threshold\u003d120\n\n* scenario3: deployer can just use:\n\n  [DEFAULT]/transport_url \u003d amqp://user:pass@foobar/vhost?connection_retry_backoff\u003d5\n  [notification]/transport_url \u003d kafka://user:pass@foobar/vhost?kafka_consumer_timeout\u003d5\n\n\nAlso changing the default of a driver can be done with:\n\n  [oslo_messaging_rabbit]/heartbeat_timeout_threshold \u003d 5\n\n\nIf no [notification]/transport_url is set, we fallback to the rpc one.\n\nI think we cover all use cases here. The only pain point is some options that does the same thing in different drivers don\u0027t have the same names. We recently fix that for ssl parameters to make deployer life easier, if some are remaining we can fix them too.\n\nIs this specs about moving common options to an other location ?","commit_id":"0b83577b2c37114c73a73fc12d5aaf446f09f06b"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c2c377296776eb302aeb9013ab6410f1329de11b","unresolved":false,"context_lines":[{"line_number":288,"context_line":"* override the default value as appropriate  "},{"line_number":289,"context_line":"* update the deprecate attributes to convey option mappings"},{"line_number":290,"context_line":"* validate the configuration option settings"},{"line_number":291,"context_line":"* generate an error/warning if values set for unused/ignored options"},{"line_number":292,"context_line":" "},{"line_number":293,"context_line":"Drivers should release note any condition where the update to RPC and"},{"line_number":294,"context_line":"Notification options will result in a functional change to the driver behavior."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_61a61a56","line":291,"updated":"2017-05-22 20:37:21.000000000","message":"If some of these options are not used by some of the drivers, that tells me we can\u0027t unify them all.\n\nWhich options are not used in all drivers?","commit_id":"0b83577b2c37114c73a73fc12d5aaf446f09f06b"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c2c377296776eb302aeb9013ab6410f1329de11b","unresolved":false,"context_lines":[{"line_number":298,"context_line":"The following additions will be included in this update:"},{"line_number":299,"context_line":""},{"line_number":300,"context_line":"new files:"},{"line_number":301,"context_line":"* rpc option file (such as oslo_messaging/rpc/rpcer.py)"},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"changed files:"},{"line_number":304,"context_line":"* oslo.messaging/oslo_messaging/opts.py"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_c18a86bd","line":301,"updated":"2017-05-22 20:37:21.000000000","message":"what is \"rpcer\" short for?","commit_id":"0b83577b2c37114c73a73fc12d5aaf446f09f06b"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c2c377296776eb302aeb9013ab6410f1329de11b","unresolved":false,"context_lines":[{"line_number":339,"context_line":"parameters for installation and deployments. Historically, these have"},{"line_number":340,"context_line":"had fixed configurations for a single driver such as rabbit and have"},{"line_number":341,"context_line":"recently been updated to utilize transport_urls for separated backend"},{"line_number":342,"context_line":"specifications."},{"line_number":343,"context_line":""},{"line_number":344,"context_line":"Developer Impact"},{"line_number":345,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff0f0b1f_c17846c5","line":342,"updated":"2017-05-22 20:37:21.000000000","message":"How will the new options be made backwards compatible with the existing options so that it is not necessary to update configuration files before upgrading the software?","commit_id":"0b83577b2c37114c73a73fc12d5aaf446f09f06b"}]}