From 4ac7ef26ce4d23fa3589289fbac2c8b327e7860c Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Sun, 4 Feb 2018 12:03:27 -0500 Subject: [PATCH] Update cells v2 layout doc caveats for Queens The instance list performance and reschedules issues have been fixed in Queens so this updates the caveats section of the cells v2 layout doc to point out those changes since Pike. Change-Id: I882f185554b6d2781534fa93e41e5010ea3a641d --- doc/source/user/cellsv2-layout.rst | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/doc/source/user/cellsv2-layout.rst b/doc/source/user/cellsv2-layout.rst index 1346ed0b7c..be0e869e27 100644 --- a/doc/source/user/cellsv2-layout.rst +++ b/doc/source/user/cellsv2-layout.rst @@ -245,7 +245,9 @@ this limitation. Caveats of a Multi-Cell deployment ---------------------------------- -.. note: This information is correct as of the Pike release. +.. note:: This information is correct as of the Pike release. Where + improvements have been made or issues fixed, they are noted per + item. Cross-cell instance migrations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -271,6 +273,8 @@ independent of the actual cell being reachable. Performance of listing instances ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. note:: This has been resolved in the Queens release [#]_. + With multiple cells, the instance list operation may not sort and paginate results properly when crossing multiple cell boundaries. Further, the performance of a sorted list operation will @@ -317,7 +321,10 @@ implement some features without such connectivity. Thus, anything that requires a so-called "upcall" will not function. This impacts the following: -#. Instance reschedules during boot +#. Instance reschedules during boot and resize + + .. note:: This has been resolved in the Queens release [#]_. + #. Instance affinity reporting from the compute nodes to scheduler #. The late anti-affinity check #. Querying host aggregates from the cell @@ -359,3 +366,6 @@ case of boot from volume where the *nova-compute* service itself creates the volume and must tell Cinder in which availability zone to create the volume. Long-term, volume creation during boot from volume should be moved to the top-level superconductor which would eliminate this AZ up-call check problem. + +.. [#] https://blueprints.launchpad.net/nova/+spec/efficient-multi-cell-instance-list-and-sort +.. [#] https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/return-alternate-hosts.html