)]}'
{"reference/tags/assert_supports-upgrade.rst":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"3ad3ad6a18982c53cc53149c3d9222d1a98ba4d7","unresolved":false,"context_lines":[{"line_number":47,"context_line":"  database (with actual data in it) from release N-1 to N is possible"},{"line_number":48,"context_line":"  without data loss. This must be actively tested full-stack on every"},{"line_number":49,"context_line":"  proposed commit in the gate, with resources present and working"},{"line_number":50,"context_line":"  before and after the upgrade step."},{"line_number":51,"context_line":"* A procedure for general upgrades of the project is defined and does"},{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da85f559_952b3f94","line":50,"updated":"2015-11-09 20:10:15.000000000","message":"I have a question on the requirement: it suggests that we should validate migration with data pre-populated into db, right? If so, do we even have projects in openstack that validate it with enough data pushed into old side of db?","commit_id":"0d1e71ce97707060b35689394f82009ef57b592d"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"331e7f9d1a4462522dcf36f22d46100cf58feb07","unresolved":false,"context_lines":[{"line_number":47,"context_line":"  database (with actual data in it) from release N-1 to N is possible"},{"line_number":48,"context_line":"  without data loss. This must be actively tested full-stack on every"},{"line_number":49,"context_line":"  proposed commit in the gate, with resources present and working"},{"line_number":50,"context_line":"  before and after the upgrade step."},{"line_number":51,"context_line":"* A procedure for general upgrades of the project is defined and does"},{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da85f559_4be1b4cf","line":50,"in_reply_to":"da85f559_0b45ec15","updated":"2015-11-09 20:42:49.000000000","message":"I am actually in support of how it\u0027s defined here. We will need to revisit grenade coverage in M for neutron in any case. Just wanted to clarify something unclear for me (f.e. I did not know that grenade has its own resource creation steps apart from devstack ones).","commit_id":"0d1e71ce97707060b35689394f82009ef57b592d"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"dd48fe21991dbc27255c9ce21d66dd99177eac9e","unresolved":false,"context_lines":[{"line_number":47,"context_line":"  database (with actual data in it) from release N-1 to N is possible"},{"line_number":48,"context_line":"  without data loss. This must be actively tested full-stack on every"},{"line_number":49,"context_line":"  proposed commit in the gate, with resources present and working"},{"line_number":50,"context_line":"  before and after the upgrade step."},{"line_number":51,"context_line":"* A procedure for general upgrades of the project is defined and does"},{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da85f559_0b45ec15","line":50,"in_reply_to":"da85f559_0b5bac2f","updated":"2015-11-09 20:36:39.000000000","message":"Neutron doesn\u0027t do this kind of testing at all yet (I tried to start, but that\u0027s another story).\n\nIhar, it may be that the initial Neutron test covers some subset of resources and the test is updated over time to cover more and more stuff.  Baby steps!  I wouldn\u0027t be surprised if we need to have documentation around this that says \"it\u0027s supported, but see this document for the details.\"  The details will have to include info on what exactly we test, as well as what backend configurations are expected to be supported, as this is complicated, and different depending on what backend you use.  I just didn\u0027t want to derail the initial tag definition with those details when we can just cover it in some project docs.","commit_id":"0d1e71ce97707060b35689394f82009ef57b592d"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"d77a1ac01b8cb117820069c01be42f502c253d62","unresolved":false,"context_lines":[{"line_number":47,"context_line":"  database (with actual data in it) from release N-1 to N is possible"},{"line_number":48,"context_line":"  without data loss. This must be actively tested full-stack on every"},{"line_number":49,"context_line":"  proposed commit in the gate, with resources present and working"},{"line_number":50,"context_line":"  before and after the upgrade step."},{"line_number":51,"context_line":"* A procedure for general upgrades of the project is defined and does"},{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da85f559_0b5bac2f","line":50,"in_reply_to":"da85f559_2b00f000","updated":"2015-11-09 20:33:21.000000000","message":"Yeah, surely default resources are upgraded. But I believe it\u0027s very incomplete. In Neutron case, we have lots of resources that are not part of default devstack setup (f.e. floating IPs, or QoS policies, or load balancers, etc.) so it would be misleading to claim we cover most resources.","commit_id":"0d1e71ce97707060b35689394f82009ef57b592d"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"7956b94835d3453a3e87c6a4fba471baca4c81ac","unresolved":false,"context_lines":[{"line_number":47,"context_line":"  database (with actual data in it) from release N-1 to N is possible"},{"line_number":48,"context_line":"  without data loss. This must be actively tested full-stack on every"},{"line_number":49,"context_line":"  proposed commit in the gate, with resources present and working"},{"line_number":50,"context_line":"  before and after the upgrade step."},{"line_number":51,"context_line":"* A procedure for general upgrades of the project is defined and does"},{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da85f559_2b00f000","line":50,"in_reply_to":"da85f559_952b3f94","updated":"2015-11-09 20:30:43.000000000","message":"Yes we should and yes we do. Grenade starts the old side cloud, creates resources, does the upgrade, verifies those resources, and then runs tempest.\n\nFor nova, it\u0027s two instances. For cinder, it\u0027s at least one volume. Not sure on the details for Neutron.","commit_id":"0d1e71ce97707060b35689394f82009ef57b592d"}],"reference/tags/can-upgrade.rst":[{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"fc5d584a1b5f8efbf46e0ca97cf6e7afd0bedb3c","unresolved":false,"context_lines":[{"line_number":7,"context_line":".. _`tag-can-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"},{"line_number":10,"context_line":"assert: can-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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag is part of the assert category of tags, which are assertions"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_b9afa07c","line":10,"updated":"2015-11-03 13:34:47.000000000","message":"extraneous space","commit_id":"285303d46dd10b48ab83464c5f1629a6b830e813"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"fc5d584a1b5f8efbf46e0ca97cf6e7afd0bedb3c","unresolved":false,"context_lines":[{"line_number":25,"context_line":"the proposed tag to at least some subset of the current project list. This"},{"line_number":26,"context_line":"will serve as an example of how the tag should be applied in the real world."},{"line_number":27,"context_line":"You may also submit (as a subsequent change) the corresponding governance"},{"line_number":28,"context_line":"change to immediately apply the proposed tag to projects."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":".. tagged-projects:: can-upgrade"},{"line_number":31,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_d9eb84af","line":28,"updated":"2015-11-03 13:34:47.000000000","message":"This is boilerplate and should be removed. Assert tags are proposed by projects themselves, so no need to propose a list of projects it would likely apply to.","commit_id":"285303d46dd10b48ab83464c5f1629a6b830e813"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"fc5d584a1b5f8efbf46e0ca97cf6e7afd0bedb3c","unresolved":false,"context_lines":[{"line_number":42,"context_line":"danger that operators should be aware of."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Requirements"},{"line_number":45,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"* Configuration from release N-1 is supported in release N. Sane"},{"line_number":48,"context_line":"  defaults for new configuration variables are provided in such a way"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa80f949_39817090","line":45,"updated":"2015-11-03 13:34:47.000000000","message":"Should we limit that tag to type:service projects ? Or dos it make sense for libraries too ?","commit_id":"285303d46dd10b48ab83464c5f1629a6b830e813"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"8d76f5a2a6ac2f26f7e2c168575b870cbfe89728","unresolved":false,"context_lines":[{"line_number":4,"context_line":"  Unported License."},{"line_number":5,"context_line":"  http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":".. _`tag-can-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"},{"line_number":10,"context_line":"assert:can-upgrade"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa80f949_20e27d04","line":7,"updated":"2015-11-03 19:19:59.000000000","message":".. `tag-assert:can-upgrade`:","commit_id":"fac5e823f646a500fcec320dc1d972bc49c3cd0f"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"8d76f5a2a6ac2f26f7e2c168575b870cbfe89728","unresolved":false,"context_lines":[{"line_number":21,"context_line":"Application to current projects"},{"line_number":22,"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"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":".. tagged-projects:: can-upgrade"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Rationale"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa80f949_a052eddb","line":24,"updated":"2015-11-03 19:19:59.000000000","message":"should be tagged-projects:: assert:can-upgrade","commit_id":"fac5e823f646a500fcec320dc1d972bc49c3cd0f"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"8d76f5a2a6ac2f26f7e2c168575b870cbfe89728","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  not change substantially from cycle to cycle."},{"line_number":53,"context_line":"* The project provides an upgrade impact section on the release notes"},{"line_number":54,"context_line":"  page that highlights anything that must be done by operators for"},{"line_number":55,"context_line":"  each cycle outside the normal upgrade procedures."},{"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":2,"id":"fa80f949_c0ce1183","line":55,"updated":"2015-11-03 19:19:59.000000000","message":"Fantastic description of requirements. ++","commit_id":"fac5e823f646a500fcec320dc1d972bc49c3cd0f"}]}