)]}'
{"deliverables/stein/python-novaclient.yaml":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"300f47893ba1b87867475bd9448a433af6a02f12","unresolved":false,"context_lines":[{"line_number":18,"context_line":"  - projects:"},{"line_number":19,"context_line":"      - hash: 62bf8809c660ed0675f301c235b1d434caeaf580"},{"line_number":20,"context_line":"        repo: openstack/python-novaclient"},{"line_number":21,"context_line":"    version: 12.1.0"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_2ee97119","line":21,"range":{"start_line":21,"start_character":13,"end_line":21,"end_character":19},"updated":"2019-03-07 15:23:20.000000000","message":"We may want to consider a major version bump because of the 2.68 change:\n\nhttps://docs.openstack.org/releasenotes/python-novaclient/unreleased.html#upgrade-notes\n\n\"Added support for microversion 2.68, which removes the --force option from the nova evacuate, nova live-migration, nova host-evacuate and nova host-evacuate-live commands.\"\n\nSince the nova CLI negotiates the max microversion to use between the client and server, if this is running against a Stein nova-api it will remove the --force option from those commands, so someone whose script is not pinned to a particular microversion and is using the --force option would break. Granted, they can simply pass --os-compute-api-version\u003d2.67 to work around that, and probably should have been pinning the requested version in scripts anyway to avoid backward incompatible API changes on the CLI, i.e. the CLI behavior is akin to passing microversion 2.latest which you shouldn\u0027t really do if you\u0027re going for stability, and we have said in the past that the nova CLI is not a bash SDK, so I\u0027m a bit torn here. 13.0.0 would be safe, but maybe unnecessary.","commit_id":"650733afcc88bbdb87a24534a8969a431cb2f508"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"cc20ddf7c3cdad202297434daf6e9fb97dce93d3","unresolved":false,"context_lines":[{"line_number":18,"context_line":"  - projects:"},{"line_number":19,"context_line":"      - hash: 62bf8809c660ed0675f301c235b1d434caeaf580"},{"line_number":20,"context_line":"        repo: openstack/python-novaclient"},{"line_number":21,"context_line":"    version: 12.1.0"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_8e6ae57d","line":21,"range":{"start_line":21,"start_character":13,"end_line":21,"end_character":19},"in_reply_to":"5fc1f717_2ee97119","updated":"2019-03-07 15:28:08.000000000","message":"\u003e We may want to consider a major version bump because of the 2.68\n \u003e change:\n \u003e \n \u003e https://docs.openstack.org/releasenotes/python-novaclient/unreleased.html#upgrade-notes\n \u003e \n \u003e \"Added support for microversion 2.68, which removes the --force\n \u003e option from the nova evacuate, nova live-migration, nova\n \u003e host-evacuate and nova host-evacuate-live commands.\"\n \u003e \n \u003e Since the nova CLI negotiates the max microversion to use between\n \u003e the client and server, if this is running against a Stein nova-api\n \u003e it will remove the --force option from those commands, so someone\n \u003e whose script is not pinned to a particular microversion and is\n \u003e using the --force option would break. Granted, they can simply pass\n \u003e --os-compute-api-version\u003d2.67 to work around that, and probably\n \u003e should have been pinning the requested version in scripts anyway to\n \u003e avoid backward incompatible API changes on the CLI, i.e. the CLI\n \u003e behavior is akin to passing microversion 2.latest which you\n \u003e shouldn\u0027t really do if you\u0027re going for stability, and we have said\n \u003e in the past that the nova CLI is not a bash SDK, so I\u0027m a bit torn\n \u003e here. 13.0.0 would be safe, but maybe unnecessary.\n\n\nWell, I think we need a major release even if we say that end-users shouldn\u0027t directly use Nova CLI (at least without asking for a specific API like you said) for the point you said.\n\nExcellent comment, btw!","commit_id":"650733afcc88bbdb87a24534a8969a431cb2f508"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"09948c007bacd0f317007c3880181bb7683cb53f","unresolved":false,"context_lines":[{"line_number":18,"context_line":"  - projects:"},{"line_number":19,"context_line":"      - hash: 62bf8809c660ed0675f301c235b1d434caeaf580"},{"line_number":20,"context_line":"        repo: openstack/python-novaclient"},{"line_number":21,"context_line":"    version: 12.1.0"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5fc1f717_d96679ee","line":21,"range":{"start_line":21,"start_character":13,"end_line":21,"end_character":19},"in_reply_to":"5fc1f717_8e6ae57d","updated":"2019-03-07 15:56:58.000000000","message":"Done. Safe and harmless \u003d\u003d better.","commit_id":"650733afcc88bbdb87a24534a8969a431cb2f508"}]}