)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"2242c8127347386b3b511ad6886428b5c12b1bb9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4a2c8518_33b31de5","updated":"2023-09-08 10:03:48.000000000","message":"Addressing Jay\u0027s points + the issue on the doc job (twice using the \u0027nova-manage\u0027 target)","commit_id":"f4b0d6e877eb6e53ce26a3ab07b5c353c0b6e5f4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f585189a_baec6c8d","updated":"2023-09-11 16:33:14.000000000","message":"-1 mainly for dans nits although i have one inlien too","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"05312fbeb5a5e4f1af13f82f86b62075ceea37d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"19fec6f0_e9d7de88","updated":"2023-09-12 13:47:18.000000000","message":"FWIW, this looks good to me, as do all the good sugestions for tweaking the wording here.","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"8e284fa137428dab3cdc5060ee76bbed78c7cc9b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e8b76ec1_240924e7","updated":"2023-09-11 08:42:46.000000000","message":"LGTM: https://f2603edc7c975e6924b6-f9c86595ee722ed5765b04c30efd2d71.ssl.cf2.rackcdn.com/894213/2/check/openstack-tox-docs/c1ae153/docs/bobcat/highlights.html#nova","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"e1fe12a10ed505b8a5d3b6d2fa489de7d8539b34","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"9cd380bc_6288233c","updated":"2023-09-13 09:50:12.000000000","message":"LGTM: https://e8eb6bd6a42fb4653326-40441ca3a8251a37f4dc83d2dcff4685.ssl.cf2.rackcdn.com/894213/3/check/openstack-tox-docs/38d67f0/docs/bobcat/highlights.html#nova","commit_id":"36d635e0a19d99525afbbe51a7f170445f35a5d6"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"1dd0bf34559036a9d2c246857d39a3dddca9d875","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"864dc39b_be29cac7","updated":"2023-09-13 16:47:42.000000000","message":"Please await before approving this patch, we just discovered that the new Ironic shards feature isn\u0027t working appropriatly, so we may remove it from the highlights if no quick and valuable solution is found before RC1.","commit_id":"36d635e0a19d99525afbbe51a7f170445f35a5d6"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"c767e72a6bfa0e004b98c7bdb86891899501d72c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"0eb25f55_7ed5e252","updated":"2023-09-13 07:27:09.000000000","message":"Seems most of the cores reviewed it, release cores, you can accept this one.","commit_id":"36d635e0a19d99525afbbe51a7f170445f35a5d6"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"9da885f1b812425d9b5a7e2972844cee3d8d21d7","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"11bf2517_7236461a","in_reply_to":"864dc39b_be29cac7","updated":"2023-09-13 17:20:03.000000000","message":"ACK","commit_id":"36d635e0a19d99525afbbe51a7f170445f35a5d6"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"7f4b9925c712c0ac6fcbb4ac68c25be6b912fa48","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"447a67bc_c4e8b525","updated":"2023-09-13 17:37:58.000000000","message":"Yep, looks right now.","commit_id":"3ce63f458818f2860b015ee67100d92dd0925a63"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"40e1a6925920bb8fe90c642621786873de4c4e69","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"bbb221b0_d019a627","updated":"2023-09-22 12:52:21.000000000","message":"let\u0027s add back Sylvain\u0027s PTL-Approved as the content is the same as before the merge conflict was resolved.","commit_id":"be13f6de98b0ba38239783b3c2cedf9620635806"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"1de8d2e3b116faed77a5e8aaf88effe6ea329142","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"18ebe156_80a871c6","updated":"2023-09-21 14:45:17.000000000","message":"rebased \u0026 resolved the merge conflict. otherwise looks good to me.","commit_id":"be13f6de98b0ba38239783b3c2cedf9620635806"}],"deliverables/bobcat/nova.yaml":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"f110fbe694b223501b4187317eda1be324843111","unresolved":true,"context_lines":[{"line_number":9,"context_line":"  - |"},{"line_number":10,"context_line":"    The Ironic driver now supports a new way of sharding your nodes between"},{"line_number":11,"context_line":"    compute services by supporting a new configuration option named"},{"line_number":12,"context_line":"    ``[ironic]/shard_key`` per compute that will limit the number of nodes the"},{"line_number":13,"context_line":"    compute service supports by this sharding key. "},{"line_number":14,"context_line":"    This will help large Ironic deployments by providing an easier way to scale up your cloud. "},{"line_number":15,"context_line":"    A `nova-manage command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#db-ironic-compute-node-move\u003e`_"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"56178866_eef12f9c","line":12,"updated":"2023-09-07 17:36:17.000000000","message":"There are two things I\u0027d suggest mentioning here:\n\n- The HA model for the Ironic drive has changed, with the deprecation of peer_list. Operators using the new model are now required to use active/passive for compute service HA instead of being able to treat compute services as a horizontally-scalable cluster. This is an important item which impacts *all* Ironic deployers, not just those scaled up high enough to care about sharding. In fact, I would not even refer to the old method as sharding at all (it was sorta horizontally scaling done badly mixed with an abuse of Ironic conductor groups to get a sharding-like behavior).\n\n- Node sharding, as part of the configuration, requires some Ironic-side configuration as well (setting node.shard on the nodes you want managed by the given compute service).\n\n\nFor sharding, I\u0027d suggest text something like this:\n\"The Ironic driver now supports node sharding to allow splitting a large pool of Ironic nodes across multiple compute services. Operators implementing this feature should set ``[ironic]/shard_key`` to the same value as the ``node.shard`` value in Ironic for nodes they wish to manage. This will help large Ironic deployments maintain compute service performance while scaling up node counts. A `nova-manage command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#db-ironic-compute-node-move\u003e`_ is added to ease the transition.\".\n\nFor peer_list, I\u0027d suggest text something like this:\n\"The Ironic driver ``[ironic]/peer_list`` configuration has been deprecated. The Ironic driver now more closely models other Nova drivers by having a single compute have exclusive control over assigned nodes. Operators currently using multiple nova-computes for scaling should switch to Ironic node sharding for scaling. If high availability of a single compute service is required, operators should use active/passive failover.\"\n\nFor partition_key -\u003e conductor_group, I\u0027d suggest something like this:\n\"The Ironic driver ``[ironic]/partition_key`` configuration has been renamed to ``[ironic]/conductor_group``. Operators currently using Ironic conductor groups only for compute service scaling should migrate to ``node.shard`` and ``[ironic]/shard_key``.\"\n\n\nThis may be more than you want to put in cycle highlights, if so, I\u0027d recommend editing it down with a focus on:\n- HA model for compute services with Ironic driver has changed (this is the peer_list change which impacts all Nova+Ironic operators)\n- Introduction of node sharding (impacts Nova+Ironic operators at hundreds-of-nodes+ scale)","commit_id":"f4b0d6e877eb6e53ce26a3ab07b5c353c0b6e5f4"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"05312fbeb5a5e4f1af13f82f86b62075ceea37d0","unresolved":true,"context_lines":[{"line_number":22,"context_line":"    Operators currently using multiple nova-computes for scaling should switch"},{"line_number":23,"context_line":"    to Ironic node sharding for scaling. If high availability of a single"},{"line_number":24,"context_line":"    compute service is required, operators should use active/passive failover."},{"line_number":25,"context_line":"    More details can be found in the `specification \u003chttps://specs.openstack.org/openstack/nova-specs/specs/2023.2/approved/ironic-shards.html\u003e`_."},{"line_number":26,"context_line":"  - |"},{"line_number":27,"context_line":"    The legacy quota driver is now deprecated and a"},{"line_number":28,"context_line":"    `nova-manage limits command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits\u003e`_"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7ef8b51f_a0716d6c","line":25,"updated":"2023-09-12 13:47:18.000000000","message":"Nice, thank you!","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":22,"context_line":"    Operators currently using multiple nova-computes for scaling should switch"},{"line_number":23,"context_line":"    to Ironic node sharding for scaling. If high availability of a single"},{"line_number":24,"context_line":"    compute service is required, operators should use active/passive failover."},{"line_number":25,"context_line":"    More details can be found in the `specification \u003chttps://specs.openstack.org/openstack/nova-specs/specs/2023.2/approved/ironic-shards.html\u003e`_."},{"line_number":26,"context_line":"  - |"},{"line_number":27,"context_line":"    The legacy quota driver is now deprecated and a"},{"line_number":28,"context_line":"    `nova-manage limits command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits\u003e`_"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"a279fcfc_b7cbb2d2","line":25,"in_reply_to":"7ef8b51f_a0716d6c","updated":"2023-09-12 14:19:43.000000000","message":"Ack","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"ef7f861d23862d3cecaa4d92a05a41dd1382d2db","unresolved":true,"context_lines":[{"line_number":27,"context_line":"    The legacy quota driver is now deprecated and a"},{"line_number":28,"context_line":"    `nova-manage limits command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits\u003e`_"},{"line_number":29,"context_line":"    is provided in order to migrate the orginal limits into Keystone. Next cycle,"},{"line_number":30,"context_line":"    we plan to change the default quota driver to be using unified limits that"},{"line_number":31,"context_line":"    are set in Keystone, so it is recommended to anticipate this change by"},{"line_number":32,"context_line":"    already setting those limits into Keystone during this release."},{"line_number":33,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5fafc2a6_69301f09","line":30,"updated":"2023-09-11 16:06:49.000000000","message":"This sounds a bit awkward to me. Maybe something like \"we plan to change the default quota driver to be the unified limits one in an upcoming release. It is recommended that you begin planning and executing a migration to unified limits as soon as possible.\"","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":27,"context_line":"    The legacy quota driver is now deprecated and a"},{"line_number":28,"context_line":"    `nova-manage limits command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits\u003e`_"},{"line_number":29,"context_line":"    is provided in order to migrate the orginal limits into Keystone. Next cycle,"},{"line_number":30,"context_line":"    we plan to change the default quota driver to be using unified limits that"},{"line_number":31,"context_line":"    are set in Keystone, so it is recommended to anticipate this change by"},{"line_number":32,"context_line":"    already setting those limits into Keystone during this release."},{"line_number":33,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"8293a24b_c1e3ef0f","line":30,"in_reply_to":"2cd01795_481796dd","updated":"2023-09-12 14:19:43.000000000","message":"Ack","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":true,"context_lines":[{"line_number":27,"context_line":"    The legacy quota driver is now deprecated and a"},{"line_number":28,"context_line":"    `nova-manage limits command \u003chttps://docs.openstack.org/nova/latest/cli/nova-manage.html#limits-migrate-to-unified-limits\u003e`_"},{"line_number":29,"context_line":"    is provided in order to migrate the orginal limits into Keystone. Next cycle,"},{"line_number":30,"context_line":"    we plan to change the default quota driver to be using unified limits that"},{"line_number":31,"context_line":"    are set in Keystone, so it is recommended to anticipate this change by"},{"line_number":32,"context_line":"    already setting those limits into Keystone during this release."},{"line_number":33,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"2cd01795_481796dd","line":30,"in_reply_to":"5fafc2a6_69301f09","updated":"2023-09-11 16:33:14.000000000","message":"minor tweak but i agree with dan\n\n\"we plan to change the default quota driver to the unified limits driver in an upcoming release. It is recommended that you begin planning and executing a migration to unified limits as soon as possible.\"","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":true,"context_lines":[{"line_number":31,"context_line":"    are set in Keystone, so it is recommended to anticipate this change by"},{"line_number":32,"context_line":"    already setting those limits into Keystone during this release."},{"line_number":33,"context_line":"  - |"},{"line_number":34,"context_line":"    The libvirt driver can now configure the TB cache size per instance if the "},{"line_number":35,"context_line":"    virt type is ``qemu``. This helps running VMs with small memory size."},{"line_number":36,"context_line":"    In order to use this feature, a configuration option ``[libvirt]/tb_cache_size``"},{"line_number":37,"context_line":"    has been introduced."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7f21c5c3_c024f4d0","line":34,"range":{"start_line":34,"start_character":44,"end_line":34,"end_character":58},"updated":"2023-09-11 16:33:14.000000000","message":"you might want to expleing what this is\n\ni.e.\n\nQEMU in its TCG mode (i.e. full system emulation) uses a translation\nblock (TB) cache as an optimization during dynamic code translation.\nThe libvirt driver can now configure the tb-cache size when the virt type is ``qemu``. This helps running VMs with small memory size.\n    In order to use this feature, a configuration option ``[libvirt]/tb_cache_size``\n    has been introduced.","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    are set in Keystone, so it is recommended to anticipate this change by"},{"line_number":32,"context_line":"    already setting those limits into Keystone during this release."},{"line_number":33,"context_line":"  - |"},{"line_number":34,"context_line":"    The libvirt driver can now configure the TB cache size per instance if the "},{"line_number":35,"context_line":"    virt type is ``qemu``. This helps running VMs with small memory size."},{"line_number":36,"context_line":"    In order to use this feature, a configuration option ``[libvirt]/tb_cache_size``"},{"line_number":37,"context_line":"    has been introduced."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"beb32208_1f9e028e","line":34,"range":{"start_line":34,"start_character":44,"end_line":34,"end_character":58},"in_reply_to":"7f21c5c3_c024f4d0","updated":"2023-09-12 14:19:43.000000000","message":"Ack","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"ef7f861d23862d3cecaa4d92a05a41dd1382d2db","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    Two new scheduler weighers have been introduced. One helps sorting the nodes"},{"line_number":40,"context_line":"    by the number of active instances they run, the other helps sorting by"},{"line_number":41,"context_line":"    the hypervisor version each compute runs. Accordingly, you can place your"},{"line_number":42,"context_line":"    instances on different scenarios, eg. by allocating them to more recent"},{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"4666d4df_153695d8","line":42,"updated":"2023-09-11 16:06:49.000000000","message":"I think \"on different scenarios\" doesn\u0027t work well here. \"place instances with different strategies\" would sound better to me.","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    Two new scheduler weighers have been introduced. One helps sorting the nodes"},{"line_number":40,"context_line":"    by the number of active instances they run, the other helps sorting by"},{"line_number":41,"context_line":"    the hypervisor version each compute runs. Accordingly, you can place your"},{"line_number":42,"context_line":"    instances on different scenarios, eg. by allocating them to more recent"},{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"cd31ce43_f96357d3","line":42,"in_reply_to":"4666d4df_153695d8","updated":"2023-09-11 16:33:14.000000000","message":"+1","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":39,"context_line":"    Two new scheduler weighers have been introduced. One helps sorting the nodes"},{"line_number":40,"context_line":"    by the number of active instances they run, the other helps sorting by"},{"line_number":41,"context_line":"    the hypervisor version each compute runs. Accordingly, you can place your"},{"line_number":42,"context_line":"    instances on different scenarios, eg. by allocating them to more recent"},{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"b53f9c89_a853df9d","line":42,"in_reply_to":"cd31ce43_f96357d3","updated":"2023-09-12 14:19:43.000000000","message":"Ack","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"ef7f861d23862d3cecaa4d92a05a41dd1382d2db","unresolved":true,"context_lines":[{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"},{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"a4a1ca9f_f62e20c1","line":46,"updated":"2023-09-11 16:06:49.000000000","message":"the repetition of \"policy...policies\" here sounds awkward as well. Perhaps \"it is now possible to define different authorization policies for migration with and without a target host.\"","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"},{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"91e11b83_0ad349db","line":46,"in_reply_to":"250cc3d5_a02e1da0","updated":"2023-09-12 14:19:43.000000000","message":"Ack","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":true,"context_lines":[{"line_number":43,"context_line":"    nodes or by reducing the number of noisy instance neighbors."},{"line_number":44,"context_line":"  - |"},{"line_number":45,"context_line":"    A new policy has been defined that will give operators the ability to define"},{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"250cc3d5_a02e1da0","line":46,"in_reply_to":"a4a1ca9f_f62e20c1","updated":"2023-09-11 16:33:14.000000000","message":"+1","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"ef7f861d23862d3cecaa4d92a05a41dd1382d2db","unresolved":true,"context_lines":[{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"},{"line_number":50,"context_line":"    one ensuring a strict linkage between a compute, a service and the instances"},{"line_number":51,"context_line":"    it runs."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"828f2c1d_97f012c5","line":49,"updated":"2023-09-11 16:06:49.000000000","message":"... \"and another one\" I think? They\u0027re not mutually exclusive :)","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bb5b226931f69cf66a1e77820fbb01f39d6c6e15","unresolved":true,"context_lines":[{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"},{"line_number":50,"context_line":"    one ensuring a strict linkage between a compute, a service and the instances"},{"line_number":51,"context_line":"    it runs."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"c08ce923_37e9fd08","line":49,"in_reply_to":"828f2c1d_97f012c5","updated":"2023-09-11 16:33:14.000000000","message":"honestly i woudl remove this form the highlights\n\nyes we have bug fixes but i think the fixes releaes notes are enough to cover that.\n\nnone of these ar ereally useful for margeting reasons or critical form a security point of view.\n\ni think the highlight are lon enough with that so i would vote for droping this.","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"28638b8630d01df1a869c9f1ebb60225516e91c6","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    different policies for migrate, whether a target is specified or not."},{"line_number":47,"context_line":"  - |"},{"line_number":48,"context_line":"    A couple of other improvements target reducing the number of bugs we have,"},{"line_number":49,"context_line":"    one checking at reboot if stale volume attachments still reside or another"},{"line_number":50,"context_line":"    one ensuring a strict linkage between a compute, a service and the instances"},{"line_number":51,"context_line":"    it runs."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"8239403e_235a94a6","line":49,"in_reply_to":"c08ce923_37e9fd08","updated":"2023-09-12 14:19:43.000000000","message":"I still want to note that we worked on a better Nova support with those.\n\nDone.","commit_id":"dfaa4745cb23190448cc0f81e1217424174fc8de"}]}