)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"46239aaa0a548231161711435f3f67fd11ede05c","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Related-Bug: 1576000"},{"line_number":14,"context_line":"Change-Id: Ibf7d60dfc57bec090f16d909c050c09e7cfd9352"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"1a122d0e_99d57b1d","line":13,"updated":"2016-04-29 23:24:56.000000000","message":"how do you intend to close the bug? Can you elaborate so that we don\u0027t leave this bug hanging for ever? Also, do we assume that DocImpact is not necessary for these sort of changes anymore (as the releasenote suffices)?","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"5dbac8bdcb7c7727520c4fa778a775ff287054d5","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Related-Bug: 1576000"},{"line_number":14,"context_line":"Change-Id: Ibf7d60dfc57bec090f16d909c050c09e7cfd9352"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"dab17558_71fab4be","line":13,"in_reply_to":"1a122d0e_99d57b1d","updated":"2016-05-16 14:39:48.000000000","message":"I thought that deprecation bugs are closed when options are actually removed. Is it different?\n\nActually, DocImpact may make sense to remove the notion of the option from networking guide.","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ed7819218ce332aa8d6b3f1fec1d9e1aed18530d","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"DocImpact: remove references to advertise_mtu from user visible"},{"line_number":14,"context_line":"           documentation."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: 1576000"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"bab6814e_ad2b8f2f","line":13,"updated":"2016-05-18 18:47:40.000000000","message":"rather than remove these should be advertised as deprecated, no?","commit_id":"ac54f0712d32a73c3d4fcf545d41325c9d0eba9a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"82558f67b48cda4ea88453db6f98d3ed2a2b4f91","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"DocImpact: remove references to advertise_mtu from user visible"},{"line_number":14,"context_line":"           documentation."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: 1576000"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"bab6814e_c6430641","line":13,"in_reply_to":"bab6814e_1d3ba69d","updated":"2016-05-19 23:30:19.000000000","message":"Yes we do, for instance:\n\nhttp://docs.openstack.org/mitaka/config-reference/networking/networking_options_reference.html#agent","commit_id":"ac54f0712d32a73c3d4fcf545d41325c9d0eba9a"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"246a5208728d5a8eca3e93caacb895cd1b8f8836","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"DocImpact: remove references to advertise_mtu from user visible"},{"line_number":14,"context_line":"           documentation."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: 1576000"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"bab6814e_1d3ba69d","line":13,"in_reply_to":"bab6814e_ad2b8f2f","updated":"2016-05-19 19:50:48.000000000","message":"Do we document deprecated options in networking-guide? I think better not, if we don\u0027t see a reason to disable it.","commit_id":"ac54f0712d32a73c3d4fcf545d41325c9d0eba9a"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"821b33416c64d5a30ab5dcac924dcf442fec23a2","unresolved":false,"context_lines":[{"line_number":10,"context_line":"to keep the option available for configuration. Other agents/plugins are"},{"line_number":11,"context_line":"also encouraged to advertise MTU values to instances by their own means."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"DocImpact: remove references to advertise_mtu from user visible"},{"line_number":14,"context_line":"           documentation."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Closes-Bug: 1576000"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"bab6814e_c69826c3","line":13,"updated":"2016-05-19 23:31:10.000000000","message":"see my comment on previous PS. I am not sure this is the right way to DocImpact this one.","commit_id":"154e3176e349802c6540f600ec852ccf8c1ad4c5"}],"releasenotes/notes/deprecate-advertise-mtu-51e3f78475a14efc.yaml":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5077b0d493954eda789637aba51501386c094ab9","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - The \u0027advertise_mtu\u0027 option is deprecated and will be removed in next"},{"line_number":4,"context_line":"    releases. DHCP and L3 agents will continue advertising MTU values to"},{"line_number":5,"context_line":"    instances by their own means. Plugins are also encouraged to advertise to"},{"line_number":6,"context_line":"    instances."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1a122d0e_b97f9768","line":4,"updated":"2016-04-29 23:21:54.000000000","message":"which release (not releases)? Can you be more specific on the timeline?","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"c50ff1ace4c1b0a95e7c76db00df3f2975e2ea14","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - The \u0027advertise_mtu\u0027 option is deprecated and will be removed in next"},{"line_number":4,"context_line":"    releases. DHCP and L3 agents will continue advertising MTU values to"},{"line_number":5,"context_line":"    instances by their own means. Plugins are also encouraged to advertise to"},{"line_number":6,"context_line":"    instances."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"bab6814e_5d461824","line":4,"in_reply_to":"1a122d0e_b97f9768","updated":"2016-05-18 16:33:43.000000000","message":"Done","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"5077b0d493954eda789637aba51501386c094ab9","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - The \u0027advertise_mtu\u0027 option is deprecated and will be removed in next"},{"line_number":4,"context_line":"    releases. DHCP and L3 agents will continue advertising MTU values to"},{"line_number":5,"context_line":"    instances by their own means. Plugins are also encouraged to advertise to"},{"line_number":6,"context_line":"    instances."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"1a122d0e_796a1f83","line":6,"updated":"2016-04-29 23:21:54.000000000","message":"Can you elaborate why this is deprecated for removal? And what is supposed to happen in its absence? Also, what is a user supposed to expect if a plugin implementing both L3 and DHCP hasn\u0027t caught up yet?","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"5dbac8bdcb7c7727520c4fa778a775ff287054d5","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - The \u0027advertise_mtu\u0027 option is deprecated and will be removed in next"},{"line_number":4,"context_line":"    releases. DHCP and L3 agents will continue advertising MTU values to"},{"line_number":5,"context_line":"    instances by their own means. Plugins are also encouraged to advertise to"},{"line_number":6,"context_line":"    instances."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"dab17558_d1ee0021","line":6,"in_reply_to":"1a122d0e_796a1f83","updated":"2016-05-16 14:39:48.000000000","message":"\u003e why this is deprecated for removal?\nBecause there is no valid use case to disable the feature.\n\n\u003e what is supposed to happen in its absence?\nThe current default behaviour: neutron attempts to advertise MTU by means implemented by the plugin enabled (DHCP, RA, anything else?)\n\n\u003e what is a user supposed to expect if a plugin implementing both L3 and DHCP hasn\u0027t caught up yet?\nSame as now with default True: the feature is not working because the plugin has not implemented this part of the MTU story.","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"c50ff1ace4c1b0a95e7c76db00df3f2975e2ea14","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - The \u0027advertise_mtu\u0027 option is deprecated and will be removed in next"},{"line_number":4,"context_line":"    releases. DHCP and L3 agents will continue advertising MTU values to"},{"line_number":5,"context_line":"    instances by their own means. Plugins are also encouraged to advertise to"},{"line_number":6,"context_line":"    instances."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"bab6814e_ddefa8ae","line":6,"in_reply_to":"dab17558_d1ee0021","updated":"2016-05-18 16:33:43.000000000","message":"I added some more details that hopefully answer the questions.","commit_id":"e1d774735a9ba5cdcc844b060d0b5949ec58faee"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"ed7819218ce332aa8d6b3f1fec1d9e1aed18530d","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    encouraged to advertise MTU to instances. Note: the actual implementation"},{"line_number":8,"context_line":"    of MTU advertisement depends on the plugin in use, but it\u0027s assumed that"},{"line_number":9,"context_line":"    at least DHCP option for IPv4 clients and Router Advertisements for IPv6"},{"line_number":10,"context_line":"    clients is supported."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"bab6814e_8d2b2beb","line":10,"updated":"2016-05-18 18:47:40.000000000","message":"so in other words: after the config removal, there is no way to disable the MTU advertisement, and configuration for plugins that do not rely on these agents must have their own mechanism to control how MTU is advertised.\n\nDid I get it right?","commit_id":"ac54f0712d32a73c3d4fcf545d41325c9d0eba9a"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"246a5208728d5a8eca3e93caacb895cd1b8f8836","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    encouraged to advertise MTU to instances. Note: the actual implementation"},{"line_number":8,"context_line":"    of MTU advertisement depends on the plugin in use, but it\u0027s assumed that"},{"line_number":9,"context_line":"    at least DHCP option for IPv4 clients and Router Advertisements for IPv6"},{"line_number":10,"context_line":"    clients is supported."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"bab6814e_5dceceb4","line":10,"in_reply_to":"bab6814e_8d2b2beb","updated":"2016-05-19 19:50:48.000000000","message":"Other plugins should implement MTU advertisements (DHCP, RA). If they don\u0027t... well, they don\u0027t.","commit_id":"ac54f0712d32a73c3d4fcf545d41325c9d0eba9a"}]}