)]}'
{"releasenotes/notes/bp-nova-support-instance-power-update-49c531ef13982e62.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds power state change callbacks of an instance to the Compute service by"},{"line_number":5,"context_line":"    performing API notifications. This feature is enabled by default and can be"},{"line_number":6,"context_line":"    disabled via the new ``nova.send_power_notifications`` configuration option."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    Whenever there is a change in the power state of a physical instance,"},{"line_number":9,"context_line":"    the Bare Metal service will send a ``power-update`` external event to"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_351dacbd","line":6,"updated":"2019-09-04 20:21:54.000000000","message":"oh, are we using a new syntax for config options? I thought the group was always in square brackets, [nova].\n\nAs long as we\u0027re consistent...","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds power state change callbacks of an instance to the Compute service by"},{"line_number":5,"context_line":"    performing API notifications. This feature is enabled by default and can be"},{"line_number":6,"context_line":"    disabled via the new ``nova.send_power_notifications`` configuration option."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    Whenever there is a change in the power state of a physical instance,"},{"line_number":9,"context_line":"    the Bare Metal service will send a ``power-update`` external event to"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_7c2b9d2f","line":6,"in_reply_to":"7faddb67_351dacbd","updated":"2019-09-10 09:04:21.000000000","message":"Done","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":15,"context_line":"  - |"},{"line_number":16,"context_line":"    By immediately conveying power state changes of a node through"},{"line_number":17,"context_line":"    external events to the Compute service, the Bare Metal service becomes the"},{"line_number":18,"context_line":"    source of truth on the node\u0027s power state, preventing the Compute service"},{"line_number":19,"context_line":"    from forcing wrong power states on instances during the periodic power"},{"line_number":20,"context_line":"    state synchronization between the Compute and Bare Metal services."},{"line_number":21,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_f561543a","line":18,"updated":"2019-09-04 20:21:54.000000000","message":"maybe s/on/about/ (I\u0027m not sure which is better grammatically)","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":15,"context_line":"  - |"},{"line_number":16,"context_line":"    By immediately conveying power state changes of a node through"},{"line_number":17,"context_line":"    external events to the Compute service, the Bare Metal service becomes the"},{"line_number":18,"context_line":"    source of truth on the node\u0027s power state, preventing the Compute service"},{"line_number":19,"context_line":"    from forcing wrong power states on instances during the periodic power"},{"line_number":20,"context_line":"    state synchronization between the Compute and Bare Metal services."},{"line_number":21,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_1c22a953","line":18,"in_reply_to":"5faad753_e177e639","updated":"2019-09-10 09:04:21.000000000","message":"Done","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"4fdf510f4448aa84b70216ee24abd03de8fdaf8f","unresolved":false,"context_lines":[{"line_number":15,"context_line":"  - |"},{"line_number":16,"context_line":"    By immediately conveying power state changes of a node through"},{"line_number":17,"context_line":"    external events to the Compute service, the Bare Metal service becomes the"},{"line_number":18,"context_line":"    source of truth on the node\u0027s power state, preventing the Compute service"},{"line_number":19,"context_line":"    from forcing wrong power states on instances during the periodic power"},{"line_number":20,"context_line":"    state synchronization between the Compute and Bare Metal services."},{"line_number":21,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_e177e639","line":18,"in_reply_to":"7faddb67_f561543a","updated":"2019-09-10 08:20:18.000000000","message":"probably \"for the node\u0027s power state\"","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":27,"context_line":"upgrade:"},{"line_number":28,"context_line":"  - |"},{"line_number":29,"context_line":"    In order to support power state change call backs to nova, the ``[nova]``"},{"line_number":30,"context_line":"    section must be configured in the Bare Metal service configuration."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_75032443","line":30,"updated":"2019-09-04 20:21:54.000000000","message":"I could be wrong, I thought that for upgrades, we normally upgrade ironic first, then nova. For this to work though, I think the process is what... change [nova]send_power_notifications config to false, upgrade ironic, upgrade nova, modify ironic config option to true, restart ironic? Or is it ok for a new ironic to emit notifications to an old nova (and nova just ignores them?)\n\nI wasn\u0027t involved in this feature so just ignore me if none of this makes sense :)","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":27,"context_line":"upgrade:"},{"line_number":28,"context_line":"  - |"},{"line_number":29,"context_line":"    In order to support power state change call backs to nova, the ``[nova]``"},{"line_number":30,"context_line":"    section must be configured in the Bare Metal service configuration."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_dc1bb118","line":30,"in_reply_to":"7faddb67_75032443","updated":"2019-09-10 09:04:21.000000000","message":"An update to this note has landed that clarifies this aspect.","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"}],"releasenotes/notes/drac-fix-power-on-reboot-race-condition-fe712aa9c79ee252.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds a new configuration option ``boot_device_job_status_timeout`` that"},{"line_number":5,"context_line":"    specifies the maximum amount of time (in seconds) to wait for the boot"},{"line_number":6,"context_line":"    device configuration job to transition to the scheduled state to allow a"},{"line_number":7,"context_line":"    reboot or power on action to complete."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_15099093","line":4,"updated":"2019-09-04 20:21:54.000000000","message":"this is for drac, so s/boot_/[drac]boot_/","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds a new configuration option ``boot_device_job_status_timeout`` that"},{"line_number":5,"context_line":"    specifies the maximum amount of time (in seconds) to wait for the boot"},{"line_number":6,"context_line":"    device configuration job to transition to the scheduled state to allow a"},{"line_number":7,"context_line":"    reboot or power on action to complete."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_7ce07dfb","line":4,"in_reply_to":"7faddb67_15099093","updated":"2019-09-10 09:04:21.000000000","message":"Done","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"}],"releasenotes/notes/intel-ipmi-hardware-30aaa65cdbcb779a.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds support for the Intel IPMI Hardware with a new hardware type"},{"line_number":5,"context_line":"    ``intel-ipmitool``. This hardware type is same as ``ipmi`` hardware type"},{"line_number":6,"context_line":"    with additional support of `Intel Speed Select Performance Profile"},{"line_number":7,"context_line":"    Technology"},{"line_number":8,"context_line":"    \u003chttps://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-article.html\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_15bbd0c3","line":5,"updated":"2019-09-04 20:21:54.000000000","message":"nit s/is same as/is the same as the/","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds support for the Intel IPMI Hardware with a new hardware type"},{"line_number":5,"context_line":"    ``intel-ipmitool``. This hardware type is same as ``ipmi`` hardware type"},{"line_number":6,"context_line":"    with additional support of `Intel Speed Select Performance Profile"},{"line_number":7,"context_line":"    Technology"},{"line_number":8,"context_line":"    \u003chttps://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-article.html\u003e`_."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_3ce20503","line":5,"in_reply_to":"7faddb67_15bbd0c3","updated":"2019-09-10 09:04:21.000000000","message":"Done","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"}],"releasenotes/notes/irmc-dealing-with-ipxe-boot-interface-incompatibility-7d0b2bdb8f9deb46.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds the missing ``ipxe`` boot interface to the ``iRMC`` hardware type."},{"line_number":5,"context_line":"    It is supposed to be used instead of the deprecated ``ipxe_enabled``"},{"line_number":6,"context_line":"    configuration option."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_15bf50d0","line":5,"updated":"2019-09-04 20:21:54.000000000","message":"nit s/ipxe_enabled/[pxe]ipxe_enabled/","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds the missing ``ipxe`` boot interface to the ``iRMC`` hardware type."},{"line_number":5,"context_line":"    It is supposed to be used instead of the deprecated ``ipxe_enabled``"},{"line_number":6,"context_line":"    configuration option."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_3ccbe572","line":5,"in_reply_to":"7faddb67_15bf50d0","updated":"2019-09-10 09:04:21.000000000","message":"Done","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"84be3a2b4881cec2b76710e8538b755d307b1f76","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds the missing ``ipxe`` boot interface to the ``iRMC`` hardware type."},{"line_number":5,"context_line":"    It is supposed to be used instead of the deprecated ``ipxe_enabled``"},{"line_number":6,"context_line":"    configuration option."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7faddb67_d5977838","line":6,"updated":"2019-09-04 20:21:54.000000000","message":"wonder if you want to ask an iRMC person to ack this. The original is hard to understand, but maybe we might want to put back the upgrade section, because we want people to make the config change to enabled_boot_interfaces \u0026 not use ipx_enabled, right?","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9565be99b4bd10af83599b06936b7b27df1a024a","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds the missing ``ipxe`` boot interface to the ``iRMC`` hardware type."},{"line_number":5,"context_line":"    It is supposed to be used instead of the deprecated ``ipxe_enabled``"},{"line_number":6,"context_line":"    configuration option."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5faad753_9ca1b9ac","line":6,"in_reply_to":"7faddb67_d5977838","updated":"2019-09-10 09:04:21.000000000","message":"This change does not have a direct upgrade impact, I think","commit_id":"1c8e80fd10a69c915c020ec92ce03f9ec21d2691"}]}