)]}'
{"reference/tags/assert_supports-accessible-upgrade.rst":[{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f7fb59c80218ba8c78f6772c8f6111d53a67b4e3","unresolved":false,"context_lines":[{"line_number":7,"context_line":".. _`tag-assert:supports-zero-downtime-upgrade`:"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":"assert:supports-zero-downtime-upgrade"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag is part of the assert category of tags, which are assertions made by"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_fe07d57e","line":10,"updated":"2016-12-13 17:44:08.000000000","message":"nit: should be supports-accessible-upgrade","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"9c28e78bcc4165243e3e83c2bcec6d713dcf3bf8","unresolved":false,"context_lines":[{"line_number":7,"context_line":".. _`tag-assert:supports-zero-downtime-upgrade`:"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":"assert:supports-zero-downtime-upgrade"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag is part of the assert category of tags, which are assertions made by"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_d0ee82b3","line":10,"in_reply_to":"1a6eadb0_fe07d57e","updated":"2016-12-13 20:05:11.000000000","message":"Bah, thanks. Will fix.","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f7fb59c80218ba8c78f6772c8f6111d53a67b4e3","unresolved":false,"context_lines":[{"line_number":45,"context_line":"* In addition to the plan required by the :ref:`tag-assert:supports-upgrade`"},{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any disruption"},{"line_number":48,"context_line":"  of accessibility to controlled resources during the upgrade process."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":51,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_1eff3168","line":48,"updated":"2016-12-13 17:44:08.000000000","message":"Would this rule out nova migrations? Or some dropped packets in neutron (depending on what backend was used)\n\nOr, for example - when you reboot neutron agent, it can reboot the dnsmasq process - doing this could cause servers on that network to loose DNS resolution while it is being restarted. would this count as a distruption?","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"9c28e78bcc4165243e3e83c2bcec6d713dcf3bf8","unresolved":false,"context_lines":[{"line_number":45,"context_line":"* In addition to the plan required by the :ref:`tag-assert:supports-upgrade`"},{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any disruption"},{"line_number":48,"context_line":"  of accessibility to controlled resources during the upgrade process."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":51,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_70276e12","line":48,"in_reply_to":"1a6eadb0_1eff3168","updated":"2016-12-13 20:05:11.000000000","message":"Which nova migrations do you mean? But yes, this is targeting the dropped packets example from previous discussions (and I agree, it\u0027s dependent on the backend ... but as long as there is *a* happy path that is supported and tested, I believe a project should be able to successfully apply for this tag).\n\nThat is absolutely the type of disruption I\u0027m looking to disallow with this tag.","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f7fb59c80218ba8c78f6772c8f6111d53a67b4e3","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":53,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":54,"context_line":"  job wherein accessibility of a controlled resource is continuously maintained"},{"line_number":55,"context_line":"  throughout the upgrade process."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Tag application process"},{"line_number":58,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_3e022d70","line":55,"updated":"2016-12-13 17:44:08.000000000","message":"so, as part of grenade, we should have a new test that runs while the \"upgrade\" phase is running, and have it validate that the resource is availible?","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"9c28e78bcc4165243e3e83c2bcec6d713dcf3bf8","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":53,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":54,"context_line":"  job wherein accessibility of a controlled resource is continuously maintained"},{"line_number":55,"context_line":"  throughout the upgrade process."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Tag application process"},{"line_number":58,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_f0ee1e8a","line":55,"in_reply_to":"1a6eadb0_3e022d70","updated":"2016-12-13 20:05:11.000000000","message":"That is my thinking, yes.","commit_id":"a8974607d384cfdf39d6bf49cfc9c6b08f1ced98"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"eeebd109582eca124e1a35502eef9b11f032f9d7","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* In addition to the plan required by the :ref:`tag-assert:supports-upgrade`"},{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any disruption"},{"line_number":48,"context_line":"  of accessibility to controlled resources during the upgrade process when"},{"line_number":49,"context_line":"  using at least one documented configuration."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_e19e6655","line":47,"updated":"2017-01-02 15:24:15.000000000","message":"I keep coming back to the wording of \"any disruption\" and worrying that someone is going to interpret it as meaning \"100% uptime\" which, AFAIK, isn\u0027t even promised when upgrades aren\u0027t happening (dropping packets under load is a feature of TCP, right?). Can we qualify the requirement somehow to avoid that connotation? Maybe something like \"upgrades should not introduce access disruptions\" or more explicitly \"upgrades should not take the managed resources offline or otherwise make them inaccessible\" instead of saying that services have to \"eliminate any\" disruption?","commit_id":"2d1bb91e12c45550d1a82326cc81157a2962841d"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"f89d1aa3000f263381fd85380589fff4558bef27","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* In addition to the plan required by the :ref:`tag-assert:supports-upgrade`"},{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any disruption"},{"line_number":48,"context_line":"  of accessibility to controlled resources during the upgrade process when"},{"line_number":49,"context_line":"  using at least one documented configuration."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_60a090a0","line":47,"in_reply_to":"ba5201f7_779222a1","updated":"2017-01-03 19:01:38.000000000","message":"I like the simplicity of paraphrasing it as \"abnormal disruption,\" but I think using Doug\u0027s suggestion of an explicit example to help clarify the intent further.","commit_id":"2d1bb91e12c45550d1a82326cc81157a2962841d"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"9e042db22e4d77489138bcaa0e8807ef57be863b","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* In addition to the plan required by the :ref:`tag-assert:supports-upgrade`"},{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any disruption"},{"line_number":48,"context_line":"  of accessibility to controlled resources during the upgrade process when"},{"line_number":49,"context_line":"  using at least one documented configuration."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_779222a1","line":47,"in_reply_to":"ba5201f7_e19e6655","updated":"2017-01-03 13:20:54.000000000","message":"maybe changing it to \"any abnormal disruption\" ?","commit_id":"2d1bb91e12c45550d1a82326cc81157a2962841d"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"9e042db22e4d77489138bcaa0e8807ef57be863b","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":53,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":54,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":55,"context_line":"  job wherein accessibility of a controlled resource is continuously maintained"},{"line_number":56,"context_line":"  throughout the upgrade process."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Tag application process"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_97ba2622","line":55,"range":{"start_line":55,"start_character":69,"end_line":55,"end_character":79},"updated":"2017-01-03 13:20:54.000000000","message":"maybe \"validated\" might be better here.","commit_id":"2d1bb91e12c45550d1a82326cc81157a2962841d"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"f89d1aa3000f263381fd85380589fff4558bef27","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":53,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":54,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":55,"context_line":"  job wherein accessibility of a controlled resource is continuously maintained"},{"line_number":56,"context_line":"  throughout the upgrade process."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Tag application process"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_e082c0ff","line":55,"in_reply_to":"ba5201f7_97ba2622","updated":"2017-01-03 19:01:38.000000000","message":"++ I was struggling with wording on that one. Thanks!","commit_id":"2d1bb91e12c45550d1a82326cc81157a2962841d"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"372a31d003162562e3f071462c5f58b5b28dcb05","unresolved":false,"context_lines":[{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any abnormal"},{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_1a31d605","line":49,"range":{"start_line":49,"start_character":15,"end_line":49,"end_character":58},"updated":"2017-01-04 10:49:52.000000000","message":"I was just thinking about this bit.\n\nTotally agreed with it, but I wonder if we should also mandate that any limitations to the ability upgrade without affecting the accessibility of resources be well documented?\n\nI think its obvious that its required, but probably good to make that explicit.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"5b058ed8a323f2bed60c787c9479aae97f9a18be","unresolved":false,"context_lines":[{"line_number":46,"context_line":"  tag, which allows for upgrades to disrupt end user accessibility of"},{"line_number":47,"context_line":"  controlled resources, this tag requires services to eliminate any abnormal"},{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a461143_01902394","line":49,"in_reply_to":"ba5201f7_1a31d605","updated":"2017-01-31 16:14:21.000000000","message":"Adding \"Conversely, configurations that may result in abnormal disruption, and any limitations of the upgrade process that may affect accessibility, must be explicitly documented as such.\"","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"6fc74d8fdc8273c204692cf98af523645e727159","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_894aff81","line":51,"range":{"start_line":51,"start_character":2,"end_line":51,"end_character":14},"updated":"2017-01-03 20:50:10.000000000","message":"So we don\u0027t want users to \"notice\" an outage.\n\nSo maybe dropping the odd packet is fine, assuming a TCP stream is not interrupted? Too bad for UDP, it will always see the odd problem.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"5b058ed8a323f2bed60c787c9479aae97f9a18be","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a461143_c14e1b3a","line":51,"in_reply_to":"ba5201f7_3a905aec","updated":"2017-01-31 16:14:21.000000000","message":"I don\u0027t think that\u0027s a specific theme of this tag alone, though. That would be the best way to summarize the net affect of all four of these tags applied at once. Users don\u0027t notice upgrades at all when their resources are always accessible, the control plane is always up, and there\u0027s no perceivable performance impact incurred from the upgrade process itself. Perhaps I\u0027ll propose something for the index page to describe that as the end goal?","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"0493ca00aafb40c405309d09e931682f1eecba03","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_a93423fb","line":51,"in_reply_to":"ba5201f7_894aff81","updated":"2017-01-03 20:52:14.000000000","message":"+1","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"372a31d003162562e3f071462c5f58b5b28dcb05","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  disruption of accessibility to controlled resources during the upgrade"},{"line_number":49,"context_line":"  process when using at least one documented configuration. For example,"},{"line_number":50,"context_line":"  upgrades should not take managed resources offline or otherwise make them"},{"line_number":51,"context_line":"  inaccessible."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* In addition to the full stack integration testing required by the"},{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_3a905aec","line":51,"in_reply_to":"ba5201f7_a93423fb","updated":"2017-01-04 10:49:52.000000000","message":"Not sure what words to put here to get that across. I like that \"users don\u0027t notice\" phrase, its says what we need in a general way. Its vague, but I think it has to be, as the answer to that question is clearly different for each project.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"0493ca00aafb40c405309d09e931682f1eecba03","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":55,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":56,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":57,"context_line":"  job wherein accessibility of a controlled resource is continuously validated"},{"line_number":58,"context_line":"  throughout the upgrade process."}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_a94d039b","line":57,"updated":"2017-01-03 20:52:14.000000000","message":"\"continuously\" could be further strengthened with \"continually\" (e.g. an SSH session) or loosened with \"periodically\". However, \"continuously\" seems to strike the right balance for difference types of resources and test methodologies, which I think the tag should be flexible enough to accept.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"9cfc2e6eb411a76bd67dbe7eacbf45d520386bfb","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":55,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":56,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":57,"context_line":"  job wherein accessibility of a controlled resource is continuously validated"},{"line_number":58,"context_line":"  throughout the upgrade process."}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_09f9af80","line":57,"updated":"2017-01-03 20:38:04.000000000","message":"Agree with John, \"continuously\" validating is probably infeasible depending on how you interpret the term. We could poll at variouskey  points but proving there was no downtime between samples is probably not going to be possible.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"ddd023e7a72110918d977d5f0dcd7dea6eba4770","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":55,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":56,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":57,"context_line":"  job wherein accessibility of a controlled resource is continuously validated"},{"line_number":58,"context_line":"  throughout the upgrade process."}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_a9926349","line":57,"range":{"start_line":57,"start_character":56,"end_line":57,"end_character":68},"updated":"2017-01-03 20:34:36.000000000","message":"Something tells me this will be hard, but I agree with the intent here.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"372a31d003162562e3f071462c5f58b5b28dcb05","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":55,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":56,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":57,"context_line":"  job wherein accessibility of a controlled resource is continuously validated"},{"line_number":58,"context_line":"  throughout the upgrade process."}],"source_content_type":"text/x-rst","patch_set":6,"id":"ba5201f7_fa5a524f","line":57,"in_reply_to":"ba5201f7_a94d039b","updated":"2017-01-04 10:49:52.000000000","message":"How about just \"is validated throughout the upgrade process\"?\n\nSomehow I read continuously and continually as the same thing. Thats probably bad.\n\nIts a total nit pick, its just when I read \"continuously validated\" I just think, wow thats hard to do properly, how can I do that? If we are all trying to say the same thing, I don\u0027t want to block on the specific wording.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"5b058ed8a323f2bed60c787c9479aae97f9a18be","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  :ref:`tag-assert:supports-upgrade` tag, the accessibility of controlled"},{"line_number":55,"context_line":"  resources should be maintained throughout the upgrade process. In order to"},{"line_number":56,"context_line":"  assert this tag, services should prevent regression by implementing a gate"},{"line_number":57,"context_line":"  job wherein accessibility of a controlled resource is continuously validated"},{"line_number":58,"context_line":"  throughout the upgrade process."}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a461143_8125f35c","line":57,"in_reply_to":"ba5201f7_fa5a524f","updated":"2017-01-31 16:14:21.000000000","message":"I like that as a simplification.","commit_id":"9ca9773289da4e504faa71e1b3aadc2beace3029"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"253090197a27b0cba78de42cbae3d1daf4a35f2b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"the project team themselves about their maturity."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The ``assert:supports-accessible-upgrade`` tag asserts that in addition to a"},{"line_number":17,"context_line":"project supporting basic `upgrade capabilities"},{"line_number":18,"context_line":"\u003chttps://governance.openstack.org/reference/tags/assert_supports-upgrade.html\u003e`_,"},{"line_number":19,"context_line":"it does so *without disrupting the accessibility of controlled resources.*."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"1a430d35_bb27f362","line":17,"updated":"2017-02-06 15:23:00.000000000","message":"Please change the link format to use an internal cross reference instead of a full URL. The current link is incorrect, since we have added the extra hierarchy level to the governance site, and using this syntax will fix the link in a forward-compatible way.\n\n  :ref:`upgrade capabilities \u003ctag-assert:supports-upgrade\u003e`","commit_id":"c21d24f616d939878eda10f019a4fb97cdfb89a1"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"a5cfbba21738ad95cd8b00a873e2c71c1e3bba32","unresolved":false,"context_lines":[{"line_number":14,"context_line":"the project team themselves about their maturity."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The ``assert:supports-accessible-upgrade`` tag asserts that in addition to a"},{"line_number":17,"context_line":"project supporting basic `upgrade capabilities"},{"line_number":18,"context_line":"\u003chttps://governance.openstack.org/reference/tags/assert_supports-upgrade.html\u003e`_,"},{"line_number":19,"context_line":"it does so *without disrupting the accessibility of controlled resources.*."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"1a430d35_ce383fa3","line":17,"in_reply_to":"1a430d35_bb27f362","updated":"2017-02-07 19:35:13.000000000","message":"Cool!","commit_id":"c21d24f616d939878eda10f019a4fb97cdfb89a1"}],"reference/tags/assert_supports-upgrade.rst":[{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"157d26a63bd5aec253cb41fbe795bacc5c21c5ec","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"line_number":56,"context_line":"* The upgrade procedure does not result in downtime of the data plane."},{"line_number":57,"context_line":"  In other words, cloud workloads should not be affected by an upgrade"},{"line_number":58,"context_line":"  of the control plane."},{"line_number":59,"context_line":"* Full stack integration testing is performed on every proposed commit"},{"line_number":60,"context_line":"  to validate that cold upgrades from the previous stable release are"},{"line_number":61,"context_line":"  not broken. Any upgrade tasks that would be documented as above are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_628826c6","line":58,"updated":"2016-12-05 18:17:11.000000000","message":"Data plane has a very specific meaning in networking, but I think the intention here is more broad than that.  It might be helpful to clarify.\n\nDo you literally mean not a single packet should be allowed to be dropped?","commit_id":"581afe47fee691b7b94ba899790d82be85c614a0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"2ec5c4afeb25c96c442ccbd506089266c7b15256","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"line_number":56,"context_line":"* The upgrade procedure does not result in downtime of the data plane."},{"line_number":57,"context_line":"  In other words, cloud workloads should not be affected by an upgrade"},{"line_number":58,"context_line":"  of the control plane."},{"line_number":59,"context_line":"* Full stack integration testing is performed on every proposed commit"},{"line_number":60,"context_line":"  to validate that cold upgrades from the previous stable release are"},{"line_number":61,"context_line":"  not broken. Any upgrade tasks that would be documented as above are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_f2b6c1f7","line":58,"in_reply_to":"3a71b18c_628826c6","updated":"2016-12-05 19:18:52.000000000","message":"Yes, I think this statement is sufficiently strict that we need to be more detailed about what it means. It\u0027s one thing to say a VM won\u0027t be turned off. It\u0027s quite another to say it won\u0027t be \"affected\".","commit_id":"581afe47fee691b7b94ba899790d82be85c614a0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"291841a76724dbed805eb71d8407ee7123f93463","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"line_number":56,"context_line":"* The upgrade procedure does not result in downtime of the data plane."},{"line_number":57,"context_line":"  In other words, cloud workloads should not be affected by an upgrade"},{"line_number":58,"context_line":"  of the control plane."},{"line_number":59,"context_line":"* Full stack integration testing is performed on every proposed commit"},{"line_number":60,"context_line":"  to validate that cold upgrades from the previous stable release are"},{"line_number":61,"context_line":"  not broken. Any upgrade tasks that would be documented as above are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_d79525e4","line":58,"in_reply_to":"3a71b18c_97b64d3c","updated":"2016-12-12 14:50:45.000000000","message":"Is it always possible to upgrade Neutron without having any impact on the networks? I don\u0027t know enough about the implementation details there.","commit_id":"581afe47fee691b7b94ba899790d82be85c614a0"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"843a3a4a5278806df651ae08eafdd273c3ebd464","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"line_number":56,"context_line":"* The upgrade procedure does not result in downtime of the data plane."},{"line_number":57,"context_line":"  In other words, cloud workloads should not be affected by an upgrade"},{"line_number":58,"context_line":"  of the control plane."},{"line_number":59,"context_line":"* Full stack integration testing is performed on every proposed commit"},{"line_number":60,"context_line":"  to validate that cold upgrades from the previous stable release are"},{"line_number":61,"context_line":"  not broken. Any upgrade tasks that would be documented as above are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a6eadb0_118f4d24","line":58,"in_reply_to":"3a71b18c_d79525e4","updated":"2016-12-13 02:15:56.000000000","message":"It\u0027s going to be backend specific.  That\u0027s actually one of the problems I have with tags like this.  There hasn\u0027t been any effort to clarify which configurations it applies to.\n\nThinking about Neutron ML2+OVS, the agent most directly involved with processing network traffic would be the metadata API proxy, so restarting that presumably does have some effect.  There\u0027s another agent that manages dnsmasq processes (the DHCP agent).  I\u0027m not sure if restarting the agent also restarts the dnsmasq processes.","commit_id":"581afe47fee691b7b94ba899790d82be85c614a0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"c3f5ed78550686c70ef914333c70d4947aadcb85","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"line_number":56,"context_line":"* The upgrade procedure does not result in downtime of the data plane."},{"line_number":57,"context_line":"  In other words, cloud workloads should not be affected by an upgrade"},{"line_number":58,"context_line":"  of the control plane."},{"line_number":59,"context_line":"* Full stack integration testing is performed on every proposed commit"},{"line_number":60,"context_line":"  to validate that cold upgrades from the previous stable release are"},{"line_number":61,"context_line":"  not broken. Any upgrade tasks that would be documented as above are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_97b64d3c","line":58,"in_reply_to":"3a71b18c_f2b6c1f7","updated":"2016-12-12 14:42:14.000000000","message":"In my head, the intent was that not a single packet would be dropped.\n\nBut in my head, I am basing things on Nova\u0027s idea of the workload always continuing to run even when Nova is dead (includes nova-network, in theory). Other projects are way more involved in the dataplane, so its maybe not a practical base line.\n\nThat or we have different views of \"control plane\"?","commit_id":"581afe47fee691b7b94ba899790d82be85c614a0"}]}
