)]}'
{"releasenotes/notes/stein-prelude-b5fe92310e1e725e.yaml":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"672c2d11da51498fd8940aa04079f4bfceb7018a","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 19.0.0 release includes many new features and bug fixes. It is"},{"line_number":4,"context_line":"    difficult to cover all the changes that have been introduced. Please at"},{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_056b5d1f","line":4,"range":{"start_line":3,"start_character":65,"end_line":4,"end_character":65},"updated":"2019-03-19 14:02:56.000000000","message":"I can see you\u0027re following the template from earlier releases, but this sentence seems unnecessary.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e76dca66bfece3a95d9c0326bb184dd0b0ac359c","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 19.0.0 release includes many new features and bug fixes. It is"},{"line_number":4,"context_line":"    difficult to cover all the changes that have been introduced. Please at"},{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_10495431","line":4,"range":{"start_line":3,"start_character":65,"end_line":4,"end_character":65},"in_reply_to":"5fc1f717_056b5d1f","updated":"2019-03-19 20:13:20.000000000","message":"Ack, can remove. I\u0027m not creative, so I tend to start by copying things.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"672c2d11da51498fd8940aa04079f4bfceb7018a","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 19.0.0 release includes many new features and bug fixes. It is"},{"line_number":4,"context_line":"    difficult to cover all the changes that have been introduced. Please at"},{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    That said, a few major changes are worth mentioning. This is not an"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_c5747501","line":5,"range":{"start_line":4,"start_character":73,"end_line":5,"end_character":9},"updated":"2019-03-19 14:02:56.000000000","message":"likewise. Perhaps \"be sure to\"","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e76dca66bfece3a95d9c0326bb184dd0b0ac359c","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 19.0.0 release includes many new features and bug fixes. It is"},{"line_number":4,"context_line":"    difficult to cover all the changes that have been introduced. Please at"},{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    That said, a few major changes are worth mentioning. This is not an"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_d052ecde","line":5,"range":{"start_line":4,"start_character":73,"end_line":5,"end_character":9},"in_reply_to":"5fc1f717_c5747501","updated":"2019-03-19 20:13:20.000000000","message":"Can do.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"672c2d11da51498fd8940aa04079f4bfceb7018a","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    That said, a few major changes are worth mentioning. This is not an"},{"line_number":9,"context_line":"    exhaustive list:"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    - The latest Compute API microversion supported for Stein is v2.72. Details"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_8560ad37","line":8,"range":{"start_line":8,"start_character":4,"end_line":8,"end_character":15},"updated":"2019-03-19 14:02:56.000000000","message":"x","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e76dca66bfece3a95d9c0326bb184dd0b0ac359c","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    least read the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your cloud from 18.0.0 (Rocky) to 19.0.0 (Stein)."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    That said, a few major changes are worth mentioning. This is not an"},{"line_number":9,"context_line":"    exhaustive list:"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"    - The latest Compute API microversion supported for Stein is v2.72. Details"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_905ea4e7","line":8,"range":{"start_line":8,"start_character":4,"end_line":8,"end_character":15},"in_reply_to":"5fc1f717_8560ad37","updated":"2019-03-19 20:13:20.000000000","message":"Ack, can remove.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"672c2d11da51498fd8940aa04079f4bfceb7018a","unresolved":false,"context_lines":[{"line_number":12,"context_line":"      on REST API microversions added since the 18.0.0 Rocky release can be"},{"line_number":13,"context_line":"      found in the `REST API Version History`_ page."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - The 2.69 compute API microversion adds handling of server details in the"},{"line_number":16,"context_line":"      presence of down or poor-performing cells in a multi-cell environment for"},{"line_number":17,"context_line":"      the ``GET /servers``, ``GET /servers/detail``,"},{"line_number":18,"context_line":"      ``GET /servers/{server_id}``, ``GET /os-services`` REST APIs. See the"},{"line_number":19,"context_line":"      `handling down cells`_ documentation for more details."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"    - Users can now specify a volume type when creating servers when using the"},{"line_number":22,"context_line":"      2.67 compute API microversion. See the `block device mapping`_"},{"line_number":23,"context_line":"      documentation for more details."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    - Users are now able to create servers with Neutron ports that have QoS"},{"line_number":26,"context_line":"      minimum bandwidth rules when using the 2.72 compute API microversion. See"},{"line_number":27,"context_line":"      the `using ports with resource request`_ documentation for more details."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    - Operators can now set overcommit allocation ratios using Nova"},{"line_number":30,"context_line":"      configuration files or the placement API, by making use of the initial"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_a0ecb729","line":27,"range":{"start_line":15,"start_character":0,"end_line":27,"end_character":78},"updated":"2019-03-19 14:02:56.000000000","message":"Are these in any intentional order? At a glance it\u0027s jarring that they\u0027re not sorted by ascending or descending microversion. But if they\u0027re, like, in order of \"importance\" or something, that\u0027s fine.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e76dca66bfece3a95d9c0326bb184dd0b0ac359c","unresolved":false,"context_lines":[{"line_number":12,"context_line":"      on REST API microversions added since the 18.0.0 Rocky release can be"},{"line_number":13,"context_line":"      found in the `REST API Version History`_ page."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"    - The 2.69 compute API microversion adds handling of server details in the"},{"line_number":16,"context_line":"      presence of down or poor-performing cells in a multi-cell environment for"},{"line_number":17,"context_line":"      the ``GET /servers``, ``GET /servers/detail``,"},{"line_number":18,"context_line":"      ``GET /servers/{server_id}``, ``GET /os-services`` REST APIs. See the"},{"line_number":19,"context_line":"      `handling down cells`_ documentation for more details."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"    - Users can now specify a volume type when creating servers when using the"},{"line_number":22,"context_line":"      2.67 compute API microversion. See the `block device mapping`_"},{"line_number":23,"context_line":"      documentation for more details."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    - Users are now able to create servers with Neutron ports that have QoS"},{"line_number":26,"context_line":"      minimum bandwidth rules when using the 2.72 compute API microversion. See"},{"line_number":27,"context_line":"      the `using ports with resource request`_ documentation for more details."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"    - Operators can now set overcommit allocation ratios using Nova"},{"line_number":30,"context_line":"      configuration files or the placement API, by making use of the initial"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_f0ba8808","line":27,"range":{"start_line":15,"start_character":0,"end_line":27,"end_character":78},"in_reply_to":"5fc1f717_a0ecb729","updated":"2019-03-19 20:13:20.000000000","message":"No, I added them initially as a rough draft and added the microversions later without thinking about it. I could see sorting them by microversion would look more intuitive.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"df7564c02211eb6de01154163cae748795318db7","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_a1192623","line":42,"updated":"2019-03-19 07:00:38.000000000","message":"Note: I removed from PS1 the mention of extracted placement because we don\u0027t yet have test coverage of an upgrade to extracted placement. I was thinking maybe too early to mention it in the prelude. I also removed mention of the reshaper because IIUC it doesn\u0027t provide any user-facing utility [yet].\n\n\nNote: possible additions? Opinions welcome.\n\n- os_compute_api:servers:allow_all_filters policy rule\n- [api]/instance_list_cells_batch_strategy config option","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"18270858eda76515163a3e77872043b0afc7db41","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_5beaa6ac","line":42,"in_reply_to":"5fc1f717_200e8732","updated":"2019-03-19 14:51:30.000000000","message":"I\u0027m confused. grenade has been upgrading to extracted placement since very early in the Stein. Perhaps you mean something different with \"test coverage for upgrade to extracted placement\"?\n\nI would think that placement being extracted would be near the top of the list. It\u0027s a major and real change that will impact every installation at some point in their Stein lifecycle.\n\nIt\u0027s possible to get away with not paying attention to it initially, but at some point, either during their Stein upgrade, or before upgrading to Train, a deployment will need to upgrade to extracted placement, so we have to highlight its existence and the release notes is one of the best places for that, and the prelude is the one place we can be relatively sure people will actually read.\n\nSo it needs to be mentioned, in some form.\n\nFor reference the placement\u0027s prelude is at https://review.openstack.org/#/c/644567/\n\nAlso agree that some mention of nested-ness is probably a good idea, even if the reshaper is left out of it (which I think is right, mentioning it probably confuses the picture).","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"1efaefcb05c8ff8a1bf328f871840d7ae729682f","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_67c7bb47","line":42,"in_reply_to":"5fc1f717_2431b1ed","updated":"2019-03-19 21:41:45.000000000","message":"This doc is for operators and/or users, right? So they\u0027re not going to care about update_provider_tree. I think the first bit is good, but the second bit would probably be better off mentioning VGPUs.\n\n\"It is now possible for virt drivers to report resources with nested topology to the placement service. In Stein this becomes visible when using `VGPUs with libvirt`_.\"","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"7dd47c766f9a33ac1294e889d622c8dda93decb5","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_2431b1ed","line":42,"in_reply_to":"5fc1f717_5beaa6ac","updated":"2019-03-19 20:23:05.000000000","message":"\u003e Also agree that some mention of nested-ness is probably a good\n \u003e idea, even if the reshaper is left out of it (which I think is\n \u003e right, mentioning it probably confuses the picture).\n\nDo you have a suggestion about how to mention nested-ness? \"It is now possible for virt drivers to report resources with nested topology to the placement service. Please see the `update_provider_tree`_ documentation for more details.\" Does that sound OK?","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e76dca66bfece3a95d9c0326bb184dd0b0ac359c","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_b0d64027","line":42,"in_reply_to":"5fc1f717_5beaa6ac","updated":"2019-03-19 20:13:20.000000000","message":"Apologies, what I meant was that upgrade is not implemented in any deployment tool yet. I definitely wanted to give an announcement to folks about extracted placement but was worried about stating, \"nova can now run with an extracted placement service\" when upgrade isn\u0027t implemented yet in deployment tools. Scenario: someone out there is a user of OSA for deploying openstack and sees \"extracted placement available\" and then goes to upgrade to Stein only to find upgrade to extracted placement is unavailable in OSA.\n\nBut, now I realize the release note doesn\u0027t have to be all or nothing. I could add it, link to install/upgrade docs, and then add a note/warning that install/upgrade is not implemented yet, depending on the deployment tool. And to check with their particular deployment tool before proceeding. That way, anyone reading it will understand the current limitations in deployment tools.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"4731b36f366a06379ebe74abc2f7a952fc49e9a5","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_875ae780","line":42,"in_reply_to":"5fc1f717_67c7bb47","updated":"2019-03-19 21:54:10.000000000","message":"\u003e This doc is for operators and/or users, right? So they\u0027re not going\n \u003e to care about update_provider_tree. I think the first bit is good,\n \u003e but the second bit would probably be better off mentioning VGPUs.\n \u003e \n \u003e \"It is now possible for virt drivers to report resources with\n \u003e nested topology to the placement service. In Stein this becomes\n \u003e visible when using `VGPUs with libvirt`_.\"\n\nYeah... that\u0027s true. I had been thinking virt driver maintainers are the folks who\u0027d be interested to know they can nest. I\u0027m not sure what to put here. The release note that went along with reshaper [1] itself says, \"There is no end-user visible impact for this; it is for internal resource tracking purposes.\" It will be end-user visible once we have multiple vGPU types. Hm.\n\n[1] https://docs.openstack.org/releasenotes/nova/unreleased.html#upgrade-notes","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"cead1046d1609d34f514432608a2cb606ba92712","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_07aa7718","line":42,"in_reply_to":"5fc1f717_67ffbb34","updated":"2019-03-19 22:02:52.000000000","message":"I guess, in what way can end users \"see\" the result of the reshaping that was done? I could use that in the bullet point.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"78860d9e3acf374e4294063b1827cca1f4bdd04c","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_67ffbb34","line":42,"in_reply_to":"5fc1f717_875ae780","updated":"2019-03-19 21:59:01.000000000","message":"Right, reshaper *itself* didn\u0027t have any visible impact until somebody was using it. VGPU is using it, so now there\u0027s visible impact. And \"multiple\" turned out to be slightly ambitious because we only got around to reshaping a single VGPU provider in Stein.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"672c2d11da51498fd8940aa04079f4bfceb7018a","unresolved":false,"context_lines":[{"line_number":39,"context_line":"      ``[compute]resource_provider_association_refresh`` can now be set to zero"},{"line_number":40,"context_line":"      to disable refresh entirely. This should be useful for large-scale"},{"line_number":41,"context_line":"      deployments."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_200e8732","line":42,"in_reply_to":"5fc1f717_a1192623","updated":"2019-03-19 14:02:56.000000000","message":"\u003e Note: I removed from PS1 the mention of extracted placement because\n \u003e we don\u0027t yet have test coverage of an upgrade to extracted\n \u003e placement.\n\nWe don\u0027t?\n\nBut we at least have coverage of using extracted placement in a fresh install. IMO it should be mentioned. It\u0027s pretty major.\n\nCan link to some of the docs being worked in the placement repo right now:\n\nFresh install: https://review.openstack.org/643938\nUpgrade: https://review.openstack.org/644396\n\nChris should weigh in here.\n\n \u003e I also removed mention of the reshaper because IIUC it\n \u003e doesn\u0027t provide any user-facing utility [yet].\n\nI agree it probably doesn\u0027t make sense to mention the reshaper itself, but it does have a major operator-facing manifestation that I think we should include here: for the first time ever, a single host\u0027s resources may be represented by multiple providers. Operators will see that (and potentially be confused) if they start poking around osc-placement etc.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"ecd7cfbb1555d9e0c61755d0136a640cdc668aeb","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":44,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":45,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":46,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":47,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":48,"context_line":"    .. _compute capabilities as traits:"},{"line_number":49,"context_line":"https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_e1f64ed9","line":46,"updated":"2019-03-19 06:55:17.000000000","message":"Note: this link will be broken until https://review.openstack.org/642064 merges.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"ecd7cfbb1555d9e0c61755d0136a640cdc668aeb","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":47,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":48,"context_line":"    .. _compute capabilities as traits:"},{"line_number":49,"context_line":"https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_8108aad9","line":49,"updated":"2019-03-19 06:55:17.000000000","message":"Note: this link will be broken until https://review.openstack.org/644293 merges.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"9e2232eae0351a345df7d7877ca3d77b779c7098","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":47,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":48,"context_line":"    .. _compute capabilities as traits:"},{"line_number":49,"context_line":"https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fc1f717_9c0011ae","line":49,"in_reply_to":"5fc1f717_8108aad9","updated":"2019-03-19 08:21:06.000000000","message":"This is also failing CI, for being on the next line. Will wait for review feedback and fix when I respin.","commit_id":"99ae068fb78860288d169382e0497bec31199dce"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"51eabeff8c68f21243844fdc5c7b458427e9f08d","unresolved":false,"context_lines":[{"line_number":20,"context_line":"      In Stein, operators may choose to continue to run with the integrated"},{"line_number":21,"context_line":"      placement service from the Nova repository, but should begin planning a"},{"line_number":22,"context_line":"      migration to the extracted placement service by Train, as the removal of"},{"line_number":23,"context_line":"      the integrated placement code from Nova is planned for the Train release."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    - Users can now specify a volume type when creating servers when using the"},{"line_number":26,"context_line":"      2.67 compute API microversion. See the `block device mapping`_"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_879d070c","line":23,"updated":"2019-03-19 22:02:28.000000000","message":"Nice.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"b414c29b1ccebb525837307b6af89c404dc89ead","unresolved":false,"context_lines":[{"line_number":20,"context_line":"      In Stein, operators may choose to continue to run with the integrated"},{"line_number":21,"context_line":"      placement service from the Nova repository, but should begin planning a"},{"line_number":22,"context_line":"      migration to the extracted placement service by Train, as the removal of"},{"line_number":23,"context_line":"      the integrated placement code from Nova is planned for the Train release."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"    - Users can now specify a volume type when creating servers when using the"},{"line_number":26,"context_line":"      2.67 compute API microversion. See the `block device mapping`_"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_1a316eed","line":23,"in_reply_to":"5fc1f717_879d070c","updated":"2019-03-19 22:19:26.000000000","message":"Yeah, this is good. Clear without being too much info.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"8c6965d9775e351dd755d8eca0aab212fd7995e5","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_278e93d0","line":56,"updated":"2019-03-19 22:00:39.000000000","message":"I\u0027m aware this might not be appropriate for the prelude because it\u0027s relevant to developers, not operators and users. The nested-ness of vGPU resources in the libvirt driver is not yet end-user visible (but will be once we have multiple vGPU types on a single compute host). What else could I put here? Should I remove it?","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"51eabeff8c68f21243844fdc5c7b458427e9f08d","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_47b07f8c","line":56,"updated":"2019-03-19 22:02:28.000000000","message":"Still think this should mention VGPU rather than upt. (Not to derail the first sentence, but) technically it has been *possible* for virt drivers to report resources with nested topology since Rocky. Just this is the first time a virt driver is doing it. And that\u0027s the only thing the reader of this doc is likely to care about.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4b3e6108fdadf79061bca7021ccced585fb03ad4","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_9a5a3e28","line":56,"in_reply_to":"5fc1f717_077fd7ab","updated":"2019-03-19 22:19:39.000000000","message":"Definitely agree this should be re-written based on audience. This isn\u0027t about what developers can do now or later, it\u0027s about what is coming out in Stein, and from an end-user (operator perspective) it\u0027s that VGPU resource inventory and allocations, at least for the libvirt driver, are nested under the compute node resource provider. The end user should have no idea nor care that this happened.\n\nHonestly since this doesn\u0027t even expose a feature for end users I\u0027m not sure it\u0027s worth mentioning in here. It\u0027s definitely an upgrade impact for operators though since the data gets migrated online when you upgrade to Stein and restart libvirt compute nodes with VGPU inventory, so if that\u0027s what you want to convey, just say that. If you want to soften that by saying, \"to enable supporting multiple VGPU types on the same compute host in a future release\" then you could add that I guess.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"b414c29b1ccebb525837307b6af89c404dc89ead","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_da50c60d","line":56,"in_reply_to":"5fc1f717_077fd7ab","updated":"2019-03-19 22:19:26.000000000","message":"I agree that talking about VGPU rather than upt is more useful to most uses of the release notes","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"b2297d50c403a948fe7719135bab157c75552122","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_077fd7ab","line":56,"in_reply_to":"5fc1f717_47b07f8c","updated":"2019-03-19 22:04:27.000000000","message":"comment race condition fail.\n\nThe nested-ness is end-user visible in the sense that, if you ask placement for the resource providers associated with a host, you\u0027ll now get two (on libvirt-VGPU hosts) instead of one. When we have N types, it\u0027ll be N+1 (unless at that time we also have numa, and last-level cache, and memory bandwidth, and accelerators, and...).","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f7c73beaea3fca0e05ebc43f8caf3e030c8950fc","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    - It is now possible for compute virt drivers to report resources with"},{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_bad05a55","line":56,"in_reply_to":"5fc1f717_9a5a3e28","updated":"2019-03-19 22:26:35.000000000","message":"My suggested alternative:\n\n\"Upon restarting nova-compute services using the libvirt driver which expose VGPU inventory, the inventory will be moved from the root compute node resource provider to a child resource provider. As a result, when listing resource providers, you may see two for the same compute node where there was one before. See the upgrade notes for details.\"","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"d5b7d4f8c92fc4a31ae44bc11eb155c2c97a7ac9","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      nested topology to the placement service. Compute virt driver developers"},{"line_number":55,"context_line":"      should consult the `update_provider_tree`_ documentation for more"},{"line_number":56,"context_line":"      details."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"},{"line_number":60,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_fab6e23e","line":57,"updated":"2019-03-19 22:22:56.000000000","message":"It might be worth mentioning that VMwareVCDriver now supports live migration, which is a rock they\u0027ve been pushing for years.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4b3e6108fdadf79061bca7021ccced585fb03ad4","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":59,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"},{"line_number":60,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":61,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":62,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":63,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_470cff41","line":60,"updated":"2019-03-19 22:19:39.000000000","message":"Would normally ask for a depends-on to https://review.openstack.org/#/c/644396/ but it\u0027s already approved so shouldn\u0027t be an issue.","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4b3e6108fdadf79061bca7021ccced585fb03ad4","unresolved":false,"context_lines":[{"line_number":60,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":61,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":62,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":63,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":64,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":65,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":66,"context_line":"    .. _update_provider_tree: https://docs.openstack.org/nova/latest/reference/update-provider-tree.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_e71deb73","line":63,"updated":"2019-03-19 22:19:39.000000000","message":"OK I guess you need a depends-on for this: https://review.openstack.org/#/c/642064/","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4b3e6108fdadf79061bca7021ccced585fb03ad4","unresolved":false,"context_lines":[{"line_number":61,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":62,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":63,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":64,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":65,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":66,"context_line":"    .. _update_provider_tree: https://docs.openstack.org/nova/latest/reference/update-provider-tree.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_6709fb2f","line":64,"range":{"start_line":64,"start_character":35,"end_line":64,"end_character":109},"updated":"2019-03-19 22:19:39.000000000","message":"This could be more targeted:\n\nhttps://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#allocation-ratios","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4b3e6108fdadf79061bca7021ccced585fb03ad4","unresolved":false,"context_lines":[{"line_number":62,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":63,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":64,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html"},{"line_number":65,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":66,"context_line":"    .. _update_provider_tree: https://docs.openstack.org/nova/latest/reference/update-provider-tree.html"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5fc1f717_bafdba09","line":65,"updated":"2019-03-19 22:19:39.000000000","message":"Should probably depends-on or rebase on top of https://review.openstack.org/#/c/644293/","commit_id":"2dca30f50a1eb5e22a00bdec0fb644091bee41c1"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"180286d14a7639b2b51368fb4a6004eba6354456","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_3de21631","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"updated":"2019-03-20 13:55:14.000000000","message":"Actually, you\u0027ll also see multiple providers when bandwidth QoS is in play. The child providers are owned by Neutron, but they\u0027ll still show up in your deployment. We should rework this accordingly.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"565641ccd960808343a87fd9beac7ca6c11642c9","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_5320334a","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"in_reply_to":"5fc1f717_10ab8175","updated":"2019-03-20 14:52:15.000000000","message":"Done","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0757f289888975a3c59d288e8b3bf3462054335d","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_10ab8175","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"in_reply_to":"5fc1f717_1daaba18","updated":"2019-03-20 14:24:04.000000000","message":"OK this is what I suggested in IRC:\n\n\"Nova now supports nested resource providers in two cases: 1. QoS-enabled ports will have resource allocates created on a nested resource provider from the start. 2. Libvirt compute nodes reporting VGPU inventory will have that VGPU inventory and corresponding allocations moved to a child resource provider on restart of the nova-compute service after upgrading to Stein. - In both cases this means when looking at resource providers, depending on scenario, you can see more than one provider where there was initially just a root compute node provider per compute service.\"\n\nI\u0027ve also reported bug 1821015 to flesh out the VGPU docs about what someone should expect to see with the libvirt driver if they have correctly set this all up and reshaping is working.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"4c65e4cf4a1ee5d04e4afb091af1d552ce885187","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_d09f3963","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"in_reply_to":"5fc1f717_1daaba18","updated":"2019-03-20 14:21:48.000000000","message":"mriedem proposed the following:\n\nNova now supports nested resource providers in two cases: 1. QoS-enabled ports will have inventories and allocations created on nested resource providers from the start. 2. Libvirt compute nodes reporting VGPU inventory will have that VGPU inventory and corresponding allocations moved to a child resource provider on restart of the nova-compute service after upgrading to Stein. In both cases this means when looking at resource providers, depending on the scenario, you can see more than one provider where there was initially just a root compute node provider per compute service.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"c1daab07a159ff6c5b3b6f325fe0a4bd94736986","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_7d689e20","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"in_reply_to":"5fc1f717_3de21631","updated":"2019-03-20 14:02:07.000000000","message":"That\u0027s a different scenario though and we also mention QoS ports above.\n\nWhat are we really trying to tell the user here? That inventory is going to move to a child provider for VGPU, and in the case of QoS it\u0027s going to start on a child provider? And what does that mean to them?\n\nI think what we have here is likely good enough since it\u0027s an upgrade thing. QoS is not an upgrade change where the format of the tree changes, since QoS ports are going to start on nested providers, and that is well documented in the nova and neutron docs for that feature. So I think it was worth calling out the 1-\u003e2 provider thing in the VGPU case specifically because of the reshape nature of the upgrade.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"19aad270367a06eca2612271166499788842b1f5","unresolved":false,"context_lines":[{"line_number":54,"context_line":"      enable it."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_1daaba18","line":57,"range":{"start_line":57,"start_character":6,"end_line":57,"end_character":27},"in_reply_to":"5fc1f717_7d689e20","updated":"2019-03-20 14:06:37.000000000","message":"\u003e What are we really trying to tell the user here?\n\nThe message I thought was worth conveying was, \"You\u0027re used to seeing one resource provider per host when you poke placement. Now you\u0027re going to see more than one, if you use a) VGPU, or b) QoS. Don\u0027t be scared, it\u0027s all part of the plan.\"","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"5e823345480e6f3cbc470ede4804469437197220","unresolved":false,"context_lines":[{"line_number":56,"context_line":"    - Upon restarting nova-compute services using the libvirt driver which"},{"line_number":57,"context_line":"      expose VGPU inventory, the inventory will be moved from the root compute"},{"line_number":58,"context_line":"      node resource provider to a child resource provider. As a result, when"},{"line_number":59,"context_line":"      listing resource providers, you may see two for the same compute node"},{"line_number":60,"context_line":"      where there was one before. See the upgrade notes for details."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_1a1ba073","line":59,"range":{"start_line":59,"start_character":46,"end_line":59,"end_character":49},"updated":"2019-03-20 13:16:58.000000000","message":"s/.*/more than one if you use the ``[devices]/vgpu_enabled_types`` option/","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"fa1fb8a71b8a0387c497017895b079cce28ac6c1","unresolved":false,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":63,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"},{"line_number":64,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":65,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_9da8f8db","line":64,"updated":"2019-03-19 23:41:14.000000000","message":"This upgrade document is now \u0027404 Not Found\u0027","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"75ab5c235ce07de9850afe781ad63865ff33409f","unresolved":false,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":63,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"},{"line_number":64,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":65,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_fdc7bc63","line":64,"in_reply_to":"5fc1f717_9da8f8db","updated":"2019-03-19 23:49:44.000000000","message":"Sorry, I didn\u0027t use a Depends-On and it\u0027s this approved patch that contains the doc:\n\nhttps://review.openstack.org/644396","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"8234d252b2d2de7b2425a132245fecb795bcea47","unresolved":false,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":"    .. _REST API Version History: https://docs.openstack.org/nova/latest/reference/api-microversion-history.html"},{"line_number":63,"context_line":"    .. _install: https://docs.openstack.org/placement/latest/install/index.html"},{"line_number":64,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":65,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_9d38f83d","line":64,"in_reply_to":"5fc1f717_fdc7bc63","updated":"2019-03-19 23:59:30.000000000","message":"Thanks for your explanation, I see.\nMost patches have been approved, so LGTM now.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"75ab5c235ce07de9850afe781ad63865ff33409f","unresolved":false,"context_lines":[{"line_number":64,"context_line":"    .. _upgrade: https://docs.openstack.org/placement/latest/upgrade/to-stein.html"},{"line_number":65,"context_line":"    .. _handling down cells: https://developer.openstack.org/api-guide/compute/down_cells.html"},{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":68,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#allocation-ratios"},{"line_number":69,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":70,"context_line":"    .. _live migration configuration: https://docs.openstack.org/nova/latest/admin/configuring-migrations.html#vmware"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_5d90504f","line":67,"updated":"2019-03-19 23:49:44.000000000","message":"This one is also a Depends-On: https://review.openstack.org/642064","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"fa1fb8a71b8a0387c497017895b079cce28ac6c1","unresolved":false,"context_lines":[{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":68,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#allocation-ratios"},{"line_number":69,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":70,"context_line":"    .. _live migration configuration: https://docs.openstack.org/nova/latest/admin/configuring-migrations.html#vmware"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_bd35b4aa","line":69,"range":{"start_line":69,"start_character":114,"end_line":69,"end_character":145},"updated":"2019-03-19 23:41:14.000000000","message":"This link doesn\u0027t seem to exist.\nMaybe is that https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#computecapabilitiesfilter which mentions traits?","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"75ab5c235ce07de9850afe781ad63865ff33409f","unresolved":false,"context_lines":[{"line_number":66,"context_line":"    .. _block device mapping: https://docs.openstack.org/nova/latest/user/block-device-mapping.html"},{"line_number":67,"context_line":"    .. _using ports with resource request: https://developer.openstack.org/api-guide/compute/port_with_resource_request.html"},{"line_number":68,"context_line":"    .. _initial allocation ratios: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#allocation-ratios"},{"line_number":69,"context_line":"    .. _compute capabilities as traits: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#compute-capabilities-as-traits"},{"line_number":70,"context_line":"    .. _live migration configuration: https://docs.openstack.org/nova/latest/admin/configuring-migrations.html#vmware"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"5fc1f717_dda440bc","line":69,"range":{"start_line":69,"start_character":114,"end_line":69,"end_character":145},"in_reply_to":"5fc1f717_bd35b4aa","updated":"2019-03-19 23:49:44.000000000","message":"This is the Depends-On: https://review.openstack.org/644293 from the commit message.","commit_id":"c54adc671940ac3c3a79445ee4624cf365cb90f5"}]}