)]}'
{"releasenotes/notes/pike-prelude-815f73ba4ad59f97.yaml":[{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"93f0588b09eea89d11942e144c697832df3db7ea","unresolved":false,"context_lines":[{"line_number":14,"context_line":"    - The long-awaited support to boot from volumes is here (TODO: mjturek is"},{"line_number":15,"context_line":"      going to propose a patch for admin doc, add link here)"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"    - Support for \"dynamic\" drivers is available. All \"classic\" drivers have"},{"line_number":18,"context_line":"      equivalent hardware types, and we encourage the use of the hardware"},{"line_number":19,"context_line":"      types instead of the \"classic\" drivers. The hardware types available are:"},{"line_number":20,"context_line":"      "}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_0c088b25","line":17,"range":{"start_line":17,"start_character":6,"end_line":17,"end_character":49},"updated":"2017-08-15 14:50:14.000000000","message":"This may be confusing, we actually introduced them in Ocata. I\u0027d also avoid creating a list of present hardware types, as it duplicates the existing release notes and the upgrade docs (which I have to finish, sigh).","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d3380e6b362ec4261b04996a6c80beeda20e5a9c","unresolved":false,"context_lines":[{"line_number":14,"context_line":"    - The long-awaited support to boot from volumes is here (TODO: mjturek is"},{"line_number":15,"context_line":"      going to propose a patch for admin doc, add link here)"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"    - Support for \"dynamic\" drivers is available. All \"classic\" drivers have"},{"line_number":18,"context_line":"      equivalent hardware types, and we encourage the use of the hardware"},{"line_number":19,"context_line":"      types instead of the \"classic\" drivers. The hardware types available are:"},{"line_number":20,"context_line":"      "}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_6034bbfc","line":17,"range":{"start_line":17,"start_character":6,"end_line":17,"end_character":49},"in_reply_to":"9f436f4f_0c088b25","updated":"2017-08-15 15:55:00.000000000","message":"I\"m find with deleting the list of hardware types. In Ocata, we said they were experimental...","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"93f0588b09eea89d11942e144c697832df3db7ea","unresolved":false,"context_lines":[{"line_number":17,"context_line":"    - Support for \"dynamic\" drivers is available. All \"classic\" drivers have"},{"line_number":18,"context_line":"      equivalent hardware types, and we encourage the use of the hardware"},{"line_number":19,"context_line":"      types instead of the \"classic\" drivers. The hardware types available are:"},{"line_number":20,"context_line":"      "},{"line_number":21,"context_line":"      - ``cisco-ucs-standalone`` and ``cisco-ucs-managed`` to support"},{"line_number":22,"context_line":"        Cisco UCS servers"},{"line_number":23,"context_line":"      - ``idrac`` to support DELL EMC integrated DELL remote access controllers"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_511d0c72","line":20,"range":{"start_line":20,"start_character":0,"end_line":20,"end_character":6},"updated":"2017-08-15 14:50:14.000000000","message":"trailing spaces","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"93f0588b09eea89d11942e144c697832df3db7ea","unresolved":false,"context_lines":[{"line_number":30,"context_line":"      - ``snmp`` to support SNMP powered systems"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"    - ``redfish`` is a new hardware type that supports the Redfish standard."},{"line_number":33,"context_line":"      (There is no equivalent \"classic\" driver for this.)"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    - The Compute service is changing the way bare metal nodes are scheduled,"},{"line_number":36,"context_line":"      and will be using the node\u0027s ``resource_class`` to do this."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_6c16f74b","line":33,"range":{"start_line":33,"start_character":6,"end_line":33,"end_character":57},"updated":"2017-08-15 14:50:14.000000000","message":"I\u0027d remove the last sentence. If you think it\u0027s valuable (and I tend to agree), please move it to the appropriate release note.","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d3380e6b362ec4261b04996a6c80beeda20e5a9c","unresolved":false,"context_lines":[{"line_number":30,"context_line":"      - ``snmp`` to support SNMP powered systems"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"    - ``redfish`` is a new hardware type that supports the Redfish standard."},{"line_number":33,"context_line":"      (There is no equivalent \"classic\" driver for this.)"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    - The Compute service is changing the way bare metal nodes are scheduled,"},{"line_number":36,"context_line":"      and will be using the node\u0027s ``resource_class`` to do this."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_00eccf8c","line":33,"range":{"start_line":33,"start_character":6,"end_line":33,"end_character":57},"in_reply_to":"9f436f4f_6c16f74b","updated":"2017-08-15 15:55:00.000000000","message":"Good suggestion.","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"93f0588b09eea89d11942e144c697832df3db7ea","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    - The Compute service is changing the way bare metal nodes are scheduled,"},{"line_number":36,"context_line":"      and will be using the node\u0027s ``resource_class`` to do this."},{"line_number":37,"context_line":"      (TODO: is there documentation on this?)"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"    - The Bare Metal service can now incorporate physical network information"},{"line_number":40,"context_line":"      when attaching virtual interfaces (VIFs) via the new ``physical_network``"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_ac397fd7","line":37,"range":{"start_line":37,"start_character":6,"end_line":37,"end_character":45},"updated":"2017-08-15 14:50:14.000000000","message":"https://docs.openstack.org/ironic/latest/install/configure-nova-flavors.html#scheduling-based-on-resource-classes","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d3380e6b362ec4261b04996a6c80beeda20e5a9c","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    - The Compute service is changing the way bare metal nodes are scheduled,"},{"line_number":36,"context_line":"      and will be using the node\u0027s ``resource_class`` to do this."},{"line_number":37,"context_line":"      (TODO: is there documentation on this?)"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"    - The Bare Metal service can now incorporate physical network information"},{"line_number":40,"context_line":"      when attaching virtual interfaces (VIFs) via the new ``physical_network``"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_807affb6","line":37,"range":{"start_line":37,"start_character":6,"end_line":37,"end_character":45},"in_reply_to":"9f436f4f_ac397fd7","updated":"2017-08-15 15:55:00.000000000","message":"Thx, that was on my list of things to read :)","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"93f0588b09eea89d11942e144c697832df3db7ea","unresolved":false,"context_lines":[{"line_number":41,"context_line":"      field to the port object. For details, see"},{"line_number":42,"context_line":"      https://docs.openstack.org/ironic/latest/admin/multitenancy.html#multitenancy-physnets."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"    - Port group information (``mode`` and ``properties`` fields) is now passed"},{"line_number":45,"context_line":"      to the Network service via the (network) port’s ``binding:profile`` field."},{"line_number":46,"context_line":"      This allows an ML2 driver to configure the port bonding automatically."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"    - The ssh-based drivers have been removed from ironic. Please see the"},{"line_number":49,"context_line":"      \"Upgrade Notes\" section for more information."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_ec58a731","line":46,"range":{"start_line":44,"start_character":0,"end_line":46,"end_character":76},"updated":"2017-08-15 14:50:14.000000000","message":"I\u0027d skip this one, unless at least one ML2 driver already implements it.","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d3380e6b362ec4261b04996a6c80beeda20e5a9c","unresolved":false,"context_lines":[{"line_number":41,"context_line":"      field to the port object. For details, see"},{"line_number":42,"context_line":"      https://docs.openstack.org/ironic/latest/admin/multitenancy.html#multitenancy-physnets."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"    - Port group information (``mode`` and ``properties`` fields) is now passed"},{"line_number":45,"context_line":"      to the Network service via the (network) port’s ``binding:profile`` field."},{"line_number":46,"context_line":"      This allows an ML2 driver to configure the port bonding automatically."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"    - The ssh-based drivers have been removed from ironic. Please see the"},{"line_number":49,"context_line":"      \"Upgrade Notes\" section for more information."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f436f4f_203a33e6","line":46,"range":{"start_line":44,"start_character":0,"end_line":46,"end_character":76},"in_reply_to":"9f436f4f_ec58a731","updated":"2017-08-15 15:55:00.000000000","message":"Done","commit_id":"18b9b06fb2f414344ddf6fdddbfc915d7632b181"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"b3a87748cf0951120a103bee9d6d31e472d4dcf6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 8.0.1 (Pike) release includes many new features and bug fixes."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"    Please review the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your installation from 7.0.x (Ocata) to 8.0.1 (Pike)."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_b6a092f5","line":3,"range":{"start_line":3,"start_character":8,"end_line":3,"end_character":13},"updated":"2017-08-16 11:56:40.000000000","message":"Dmitry feels like 9.0.0 is the appropriate next version given the major changes. I agree since many of the changes, if someone does not follow the upgrade steps, then their deployment may break in unexpected ways.","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d9e7f0deffb09cb2bfd8e8b5b0d001c62c2a5cec","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 8.0.1 (Pike) release includes many new features and bug fixes."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"    Please review the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your installation from 7.0.x (Ocata) to 8.0.1 (Pike)."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_2b22f0b9","line":3,"range":{"start_line":3,"start_character":8,"end_line":3,"end_character":13},"in_reply_to":"9f436f4f_56584686","updated":"2017-08-16 19:26:21.000000000","message":"Ok, 9.0.0 it is! (or will be)","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"3226250d73e532462552e293415c24fd84455239","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: |"},{"line_number":3,"context_line":"    The 8.0.1 (Pike) release includes many new features and bug fixes."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"    Please review the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your installation from 7.0.x (Ocata) to 8.0.1 (Pike)."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_56584686","line":3,"range":{"start_line":3,"start_character":8,"end_line":3,"end_character":13},"in_reply_to":"9f436f4f_b6a092f5","updated":"2017-08-16 12:26:25.000000000","message":"Oh, good catch. And 8.0.1 is something we would never end up anyway, it would mean a bugfix-only release.","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d9e7f0deffb09cb2bfd8e8b5b0d001c62c2a5cec","unresolved":false,"context_lines":[{"line_number":3,"context_line":"    The 8.0.1 (Pike) release includes many new features and bug fixes."},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"    Please review the upgrade section which describes the required actions to"},{"line_number":6,"context_line":"    upgrade your installation from 7.0.x (Ocata) to 8.0.1 (Pike)."},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"    A few major changes are worth mentioning. This is not an exhaustive list:"},{"line_number":9,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_0b2deca6","line":6,"updated":"2017-08-16 19:26:21.000000000","message":"s/8.0.1/9.0.0/","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"8938adfd15a00f4bd0e89999ff34351c3d5011da","unresolved":false,"context_lines":[{"line_number":12,"context_line":"      https://docs.openstack.org/ironic/latest/admin/upgrade-guide.html."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"    - The long-awaited support to boot from volumes is here (TODO: mjturek is"},{"line_number":15,"context_line":"      going to propose a patch for admin doc, add link here)"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"    - Full support for \"dynamic\" drivers is available. There are hardware types"},{"line_number":18,"context_line":"      for all \"classic\" drivers. The use of hardware types is preferred over"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_4b79b4c5","line":15,"updated":"2017-08-16 19:21:10.000000000","message":"https://docs.openstack.org/ironic/latest/admin/boot-from-volume.html ?","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d9e7f0deffb09cb2bfd8e8b5b0d001c62c2a5cec","unresolved":false,"context_lines":[{"line_number":12,"context_line":"      https://docs.openstack.org/ironic/latest/admin/upgrade-guide.html."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"    - The long-awaited support to boot from volumes is here (TODO: mjturek is"},{"line_number":15,"context_line":"      going to propose a patch for admin doc, add link here)"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"    - Full support for \"dynamic\" drivers is available. There are hardware types"},{"line_number":18,"context_line":"      for all \"classic\" drivers. The use of hardware types is preferred over"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_eb006804","line":15,"in_reply_to":"9f436f4f_4b79b4c5","updated":"2017-08-16 19:26:21.000000000","message":"Yup, waiting for it to land. \n\nIt\u0027ll be \u0027here. For details see https://docs.openstack.org/ironic/latest/admin/boot-from-volume.html.\u0027","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"d9e7f0deffb09cb2bfd8e8b5b0d001c62c2a5cec","unresolved":false,"context_lines":[{"line_number":18,"context_line":"      for all \"classic\" drivers. The use of hardware types is preferred over"},{"line_number":19,"context_line":"      the use of \"classic\" drivers, since \"classic\" drivers may be deprecated"},{"line_number":20,"context_line":"      in Queens."},{"line_number":21,"context_line":"      (TODO: if idrac doesn\u0027t make it, need to update this.)"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    - ``redfish`` is a new hardware type that supports the Redfish standard."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_a604d715","line":21,"updated":"2017-08-16 19:26:21.000000000","message":"Still hoping for this to land...","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"b9795a48e75e52b640c69a1dfce34159c2d76681","unresolved":false,"context_lines":[{"line_number":25,"context_line":"    - The Compute service is changing the way bare metal nodes are scheduled,"},{"line_number":26,"context_line":"      and will be using the node\u0027s ``resource_class`` to do this. For more"},{"line_number":27,"context_line":"      details, see"},{"line_number":28,"context_line":"      https://docs.openstack.org/ironic/latest/install/configure-nova-flavors.html#scheduling-based-on-resource-classes"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    - The Bare Metal service can now incorporate physical network information"},{"line_number":31,"context_line":"      when attaching virtual interfaces (VIFs) via the new ``physical_network``"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9f436f4f_d88fcf27","line":28,"updated":"2017-08-16 01:38:17.000000000","message":"nit, missing period at end","commit_id":"6bf428b01a234571f1ddf5d04e27e6c21e66dbd9"}]}