)]}'
{"specs/ussuri/support-transports-per-oslo-notifications.rst":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"6cc13a43334c2c5ea2d10b759ec7f50082467115","unresolved":false,"context_lines":[{"line_number":62,"context_line":"  [notifications]"},{"line_number":63,"context_line":"  transport_url \u003d rabbit://username:password@rabbit001.com:5672"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"  [notifications_designate]"},{"line_number":66,"context_line":"  transport_url \u003d rabbit://username:password@rabbit002.com:5672"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"As described in the above config section, ``[oslo_messaging_notifications]``"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_587f1fde","line":65,"range":{"start_line":65,"start_character":3,"end_line":65,"end_character":26},"updated":"2019-11-04 15:37:43.000000000","message":"What do you think about to prefix these config sub-sections with something like `oslo_messaging_topic__xxxxx` to avoid collisions between topics names and possibly other config sections names?\n\nWill give something like:\n\n- `oslo_messaging_topic__notifications`\n- `oslo_messaging_topic__notifications_designate`","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":20191,"name":"Dinesh Bhor","email":"bhordinesh07@gmail.com","username":"dineshbhor"},"change_message_id":"f4363571b9aa7d208c2451e94c902a98b8bc11ae","unresolved":false,"context_lines":[{"line_number":62,"context_line":"  [notifications]"},{"line_number":63,"context_line":"  transport_url \u003d rabbit://username:password@rabbit001.com:5672"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"  [notifications_designate]"},{"line_number":66,"context_line":"  transport_url \u003d rabbit://username:password@rabbit002.com:5672"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"As described in the above config section, ``[oslo_messaging_notifications]``"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_bcef20af","line":65,"range":{"start_line":65,"start_character":3,"end_line":65,"end_character":26},"in_reply_to":"3fa7e38b_587f1fde","updated":"2019-11-05 02:00:22.000000000","message":"Sounds good. Let me update the spec.","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"6cc13a43334c2c5ea2d10b759ec7f50082467115","unresolved":false,"context_lines":[{"line_number":77,"context_line":"``[oslo_messaging_rabbit]``."},{"line_number":78,"context_line":"In the above example ``notifications`` topic uses ``rabbit001.com`` rabbitmq"},{"line_number":79,"context_line":"cluster. ``notifications_designate`` uses ``rabbit002.com`` rabbitmq cluster"},{"line_number":80,"context_line":"and ``any_other_notification`` used ``rabbit002.com`` rabbitmq cluster."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The notifications will inherit all the other config option values like"},{"line_number":83,"context_line":"``driver`` etc."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_58807ff7","line":80,"range":{"start_line":80,"start_character":4,"end_line":80,"end_character":71},"updated":"2019-11-04 15:37:43.000000000","message":"Not sure to understand why we use the rabbitmq cluster`rabbit002.com` here.\n\nIf I correctly understand your proposal the topic `any_other_notification` should use `rabbit001.com`, I\u0027m right?","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":20191,"name":"Dinesh Bhor","email":"bhordinesh07@gmail.com","username":"dineshbhor"},"change_message_id":"f4363571b9aa7d208c2451e94c902a98b8bc11ae","unresolved":false,"context_lines":[{"line_number":77,"context_line":"``[oslo_messaging_rabbit]``."},{"line_number":78,"context_line":"In the above example ``notifications`` topic uses ``rabbit001.com`` rabbitmq"},{"line_number":79,"context_line":"cluster. ``notifications_designate`` uses ``rabbit002.com`` rabbitmq cluster"},{"line_number":80,"context_line":"and ``any_other_notification`` used ``rabbit002.com`` rabbitmq cluster."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The notifications will inherit all the other config option values like"},{"line_number":83,"context_line":"``driver`` etc."}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_dcea1c9e","line":80,"range":{"start_line":80,"start_character":4,"end_line":80,"end_character":71},"in_reply_to":"3fa7e38b_58807ff7","updated":"2019-11-05 02:00:22.000000000","message":"aah, Sorry its typo. Yes it should be `rabbit001.com`.","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"6cc13a43334c2c5ea2d10b759ec7f50082467115","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"One more alternative could be to use RabbitMQ Shovel plugin (in case if you are"},{"line_number":130,"context_line":"using rabbitmq as a messaging backend) to move messages from one cluster to"},{"line_number":131,"context_line":"other cluster. Shovel plugin also has limitations and RabbitMQ community does"},{"line_number":132,"context_line":"not allow to use multiple ``dest-uri`` in the shovel policy so that means you"},{"line_number":133,"context_line":"can not send the notifications to two different clusters at the same time in"},{"line_number":134,"context_line":"one policy. Offcourse you can define more than one policy per notification."},{"line_number":135,"context_line":"The other disadvantage of this approach is RabbitMQ shovel plugin actually"},{"line_number":136,"context_line":"creates a non-existent queue on the RabbitMQ node as a durable queues because"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_b87c13eb","line":133,"range":{"start_line":131,"start_character":15,"end_line":133,"end_character":56},"updated":"2019-11-04 15:37:43.000000000","message":"What\u0027s about `connects`?\n\nIf I\u0027m right you can specify many brokers as sources or destinations [1].\n\n[1] https://www.rabbitmq.com/shovel.html","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":20191,"name":"Dinesh Bhor","email":"bhordinesh07@gmail.com","username":"dineshbhor"},"change_message_id":"f4363571b9aa7d208c2451e94c902a98b8bc11ae","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"One more alternative could be to use RabbitMQ Shovel plugin (in case if you are"},{"line_number":130,"context_line":"using rabbitmq as a messaging backend) to move messages from one cluster to"},{"line_number":131,"context_line":"other cluster. Shovel plugin also has limitations and RabbitMQ community does"},{"line_number":132,"context_line":"not allow to use multiple ``dest-uri`` in the shovel policy so that means you"},{"line_number":133,"context_line":"can not send the notifications to two different clusters at the same time in"},{"line_number":134,"context_line":"one policy. Offcourse you can define more than one policy per notification."},{"line_number":135,"context_line":"The other disadvantage of this approach is RabbitMQ shovel plugin actually"},{"line_number":136,"context_line":"creates a non-existent queue on the RabbitMQ node as a durable queues because"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3fa7e38b_bc72c010","line":133,"range":{"start_line":131,"start_character":15,"end_line":133,"end_character":56},"in_reply_to":"3fa7e38b_b87c13eb","updated":"2019-11-05 02:00:22.000000000","message":"Oops sorry. Yes, you are right.\nWe can specify multiple `src-uri` and `dest-uri`. \nThanks for pointing out. \n\nLong back ago I checked:\n * If more than one string is provided, the shovel will randomly pick one URI from the list.  \n * It\u0027s probably not a great idea to use multiple URIs that do not point to the same cluster. \n\nBut this is not related to the use case we are trying to solve here.","commit_id":"f8c3eb9d4cd9ed02dce44d3700170fdc5a7c2e91"},{"author":{"_account_id":8770,"name":"Ken Giusti","email":"kgiusti@gmail.com","username":"kgiusti"},"change_message_id":"eb2d4d33f9734a350fa3f4e4ede0fa0e601c8f1d","unresolved":false,"context_lines":[{"line_number":74,"context_line":""},{"line_number":75,"context_line":"By default if the transport_url is not defined for any of the notification"},{"line_number":76,"context_line":"it will fall back to the main sections transport_url"},{"line_number":77,"context_line":"``[oslo_messaging_notifications]`` and if it is defined over there as well then"},{"line_number":78,"context_line":"it will finally fallback to the transport_url defined in the"},{"line_number":79,"context_line":"``[oslo_messaging_rabbit]``."},{"line_number":80,"context_line":"In the above example ``notifications`` topic uses ``rabbit001.com`` rabbitmq"}],"source_content_type":"text/x-rst","patch_set":10,"id":"df33271e_db04787e","line":77,"updated":"2020-03-23 14:50:27.000000000","message":"Just for clarity - oslo_messaging_rabbit configuration section no longer defines a transport_url.  If no url is supplied a default of \"localhost:5672\" is provided.","commit_id":"f454ec330e303cfd1a618a7b07600e843e1b8eb7"},{"author":{"_account_id":8770,"name":"Ken Giusti","email":"kgiusti@gmail.com","username":"kgiusti"},"change_message_id":"eb2d4d33f9734a350fa3f4e4ede0fa0e601c8f1d","unresolved":false,"context_lines":[{"line_number":147,"context_line":"Security impact"},{"line_number":148,"context_line":"---------------"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"No impact."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Performance Impact"},{"line_number":153,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"df33271e_ae27b0b6","line":150,"updated":"2020-03-23 14:50:27.000000000","message":"One potential issue here is that the [oslo_messaging_rabbit] section is a single instance that will apply to all transport_urls defined in the configuration.\n\nThis means all of the rabbitmq servers will need to use the same global configuration.  This includes SSL configuration.\n\nPersonally I think that should be ok for now - just something that needs to be pointed out in the related documentation.","commit_id":"f454ec330e303cfd1a618a7b07600e843e1b8eb7"}],"specs/victoria/support-transports-per-oslo-notifications.rst":[{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"bb40dc388c55fb5a0a36f7b9a751e4f712de4c97","unresolved":false,"context_lines":[{"line_number":152,"context_line":"Performance Impact"},{"line_number":153,"context_line":"------------------"},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"No impact."},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Configuration Impact"},{"line_number":158,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":11,"id":"bf51134e_5dd9fdf0","line":155,"updated":"2020-06-22 15:28:20.000000000","message":"Not sure I agree with this. It sounds like there would be an extra lookup per notification to see if there is a topic-specific transport url defined. I don\u0027t know if it would be significant, but when we\u0027re talking about a high volume thing like notifications it could be.","commit_id":"86f3f74920e8e7f5ae4d5561ce819ec569fde880"}]}