)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":10250,"name":"Christopher Dearborn","email":"Christopher.Dearborn@dell.com","username":"cdearbor"},"change_message_id":"c647adfc6bfd9f998a109249b774676be4cb3b20","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Richard Pioso \u003crichard.pioso@dell.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-06-16 23:40:57 -0400"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add spec for defining idrac support of Redfish"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This adds a specification for defining idrac hardware type support of"},{"line_number":10,"context_line":"Redfish interface implementations."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"9fb8cfa7_e16b601c","line":7,"updated":"2019-06-20 20:45:06.000000000","message":"Please change \"idrac\" to \"iDRAC\" on the line above since this is not referring to the hardware type.","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"bdcc11194e86b34cc4420085d340141ca3299933","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Richard Pioso \u003crichard.pioso@dell.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2019-06-16 23:40:57 -0400"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add spec for defining idrac support of Redfish"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This adds a specification for defining idrac hardware type support of"},{"line_number":10,"context_line":"Redfish interface implementations."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"9fb8cfa7_8d271c13","line":7,"in_reply_to":"9fb8cfa7_e16b601c","updated":"2019-06-21 22:08:53.000000000","message":"The intent is to refer to the hardware type. That line has been modified to be more explicit.","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"}],"specs/approved/idrac-support-of-redfish-interfaces.rst":[{"author":{"_account_id":10250,"name":"Christopher Dearborn","email":"Christopher.Dearborn@dell.com","username":"cdearbor"},"change_message_id":"c647adfc6bfd9f998a109249b774676be4cb3b20","unresolved":false,"context_lines":[{"line_number":118,"context_line":"  Redfish interface implementations during node registration, including"},{"line_number":119,"context_line":"  ``redfish_address``, ``redfish_system_id``, ``redfish_username``, and"},{"line_number":120,"context_line":"  ``redfish_password``. See the `Redfish driver`_ documentation. This will be"},{"line_number":121,"context_line":"  addressed by a TripleO project blueprint."},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"* Define ``idrac`` hardware type support of IPMI interface implementations."},{"line_number":124,"context_line":"  That could be done as a follow-on to this."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fb8cfa7_e4492e32","line":121,"updated":"2019-06-20 20:45:06.000000000","message":"Does the above mean that setting the credentials for both the Redfish interface and the WS-Man interface via TripleO is a non-goal?  If so, can you clarify that above?","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"bdcc11194e86b34cc4420085d340141ca3299933","unresolved":false,"context_lines":[{"line_number":118,"context_line":"  Redfish interface implementations during node registration, including"},{"line_number":119,"context_line":"  ``redfish_address``, ``redfish_system_id``, ``redfish_username``, and"},{"line_number":120,"context_line":"  ``redfish_password``. See the `Redfish driver`_ documentation. This will be"},{"line_number":121,"context_line":"  addressed by a TripleO project blueprint."},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"* Define ``idrac`` hardware type support of IPMI interface implementations."},{"line_number":124,"context_line":"  That could be done as a follow-on to this."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fb8cfa7_0d79ecfa","line":121,"in_reply_to":"9fb8cfa7_e4492e32","updated":"2019-06-21 22:08:53.000000000","message":"Exactly! And it\u0027s been modified.","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"},{"author":{"_account_id":10250,"name":"Christopher Dearborn","email":"Christopher.Dearborn@dell.com","username":"cdearbor"},"change_message_id":"c647adfc6bfd9f998a109249b774676be4cb3b20","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"This specification proposes to change the ``idrac`` hardware type to solve the"},{"line_number":130,"context_line":"problem it describes. The ``idrac`` hardware type is where operators expect it,"},{"line_number":131,"context_line":"as intended by the Ironic `Driver composition reform`_."},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"* Define two new groups of interface implementations with entrypoints named"},{"line_number":134,"context_line":"  ``idrac-redfish`` and ``idrac-wsman``. The ``idrac-redfish`` entrypoints"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fb8cfa7_d0d940f4","line":131,"updated":"2019-06-20 20:45:06.000000000","message":"Not exactly sure what the sentence above means.  Can you clarify?","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"bdcc11194e86b34cc4420085d340141ca3299933","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"This specification proposes to change the ``idrac`` hardware type to solve the"},{"line_number":130,"context_line":"problem it describes. The ``idrac`` hardware type is where operators expect it,"},{"line_number":131,"context_line":"as intended by the Ironic `Driver composition reform`_."},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"* Define two new groups of interface implementations with entrypoints named"},{"line_number":134,"context_line":"  ``idrac-redfish`` and ``idrac-wsman``. The ``idrac-redfish`` entrypoints"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9fb8cfa7_4d2124fb","line":131,"in_reply_to":"9fb8cfa7_d0d940f4","updated":"2019-06-21 22:08:53.000000000","message":"I extensively changed this paragraph. Hopefully, it\u0027s clearer :)","commit_id":"f745830dc27216e2bd7d0df0987ff4c0892838bd"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  it."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":42,"context_line":"  WS-Man to manage it. When both offer the needed functionality, WS-Man is"},{"line_number":43,"context_line":"  used."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":46,"context_line":"  WS-Man to manage it. When both offer the needed functionality, Redfish is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_ad08e02c","line":43,"range":{"start_line":42,"start_character":23,"end_line":43,"end_character":7},"updated":"2019-06-21 23:01:08.000000000","message":"Why?\nIs this temporary for initial implementation?\nI would expect that going forward Redfish is used unless behavior between two implementations are different.\n\nNot understanding this use case.","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"039d8db1586fc91ab842492e6bad339194af3242","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  it."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":42,"context_line":"  WS-Man to manage it. When both offer the needed functionality, WS-Man is"},{"line_number":43,"context_line":"  used."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":46,"context_line":"  WS-Man to manage it. When both offer the needed functionality, Redfish is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_0b0be67c","line":43,"range":{"start_line":42,"start_character":23,"end_line":43,"end_character":7},"in_reply_to":"9fb8cfa7_174564b4","updated":"2019-06-25 23:36:11.000000000","message":"Done","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"b2a08a8026d3483da888e405e3ebc0eef9028ef4","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  it."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":42,"context_line":"  WS-Man to manage it. When both offer the needed functionality, WS-Man is"},{"line_number":43,"context_line":"  used."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":46,"context_line":"  WS-Man to manage it. When both offer the needed functionality, Redfish is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_7155da4f","line":43,"range":{"start_line":42,"start_character":23,"end_line":43,"end_character":7},"in_reply_to":"9fb8cfa7_686df696","updated":"2019-06-24 03:00:29.000000000","message":"If you believe that there is a use case and that somebody will use it then add these level of details for business case. Suggest to add the same level of details for the next case.","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"e17c3639c095d8554c10f2285ac8b3c24ba8e5fe","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  it."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":42,"context_line":"  WS-Man to manage it. When both offer the needed functionality, WS-Man is"},{"line_number":43,"context_line":"  used."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":46,"context_line":"  WS-Man to manage it. When both offer the needed functionality, Redfish is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_174564b4","line":43,"range":{"start_line":42,"start_character":23,"end_line":43,"end_character":7},"in_reply_to":"9fb8cfa7_7155da4f","updated":"2019-06-24 17:10:22.000000000","message":"I could do that, but it would essentially repeat what\u0027s already described in the introduction paragraph above.\n\nIn my earlier reply, 1) is covered by \u0027* offers a means of incrementally increasing the use of Redfish as Ironic\u0027s support, the standard, and Dell EMC service implementations evolve\" and 2) is covered by \"* delivers management protocol choice among those supported by Dell EMC -- Intelligent Platform Management Interface (IPMI_), Redfish, and Web Services Management (WS-Man_)\".","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"c69e3e9608a13feff9e88d647c61679c341e427c","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  it."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":42,"context_line":"  WS-Man to manage it. When both offer the needed functionality, WS-Man is"},{"line_number":43,"context_line":"  used."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* An Admin User has a Dell EMC baremetal server and uses both Redfish and"},{"line_number":46,"context_line":"  WS-Man to manage it. When both offer the needed functionality, Redfish is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_686df696","line":43,"range":{"start_line":42,"start_character":23,"end_line":43,"end_character":7},"in_reply_to":"9fb8cfa7_ad08e02c","updated":"2019-06-22 00:05:21.000000000","message":"It\u0027s simply an option offered to an Admin User. Perhaps it will turn out most or all Admin Users elect not to do this.\n\nHowever, notice the first use case above currently can be an instance of this one. Both Redfish and WS-Man offer minimum viable product (MVP) management and power. Redfish\u0027s management actually has more functionality than WS-Man\u0027s.\n\nTherefore, if we believe the first use case is possible, then this one is, too. This use case covers variations which _could_ appear in the future.\n\nSituations to which this use case could apply include:\n\n1) An operator has a fleet of baremetal servers configured to use the idrac hardware type already in production, upgrades OpenStack, and wants to gradually transition them to Redfish over a period of time.\n2) An Admin User may have a greater comfort level with WS-Man, because it\u0027s been available longer than Redfish. S/he decides to transition at a future date.","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":75,"context_line":"the BMC. Those implement the ``bios``, ``inspect``, ``management``, and"},{"line_number":76,"context_line":"``power`` hardware interfaces. Again, like the hardware type, they are named"},{"line_number":77,"context_line":"``redfish``. They rely on ``sushy``\u0027s Redfish client. Importantly, while some"},{"line_number":78,"context_line":"of those work with the iDRAC, including ``management`` and ``power``, not all"},{"line_number":79,"context_line":"of them do."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The ``redfish`` hardware type enables managing servers compliant with the"},{"line_number":82,"context_line":"Redfish protocol. However, the hardware type is relatively new and the protocol"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_28285e84","line":79,"range":{"start_line":78,"start_character":70,"end_line":79,"end_character":11},"updated":"2019-06-21 23:01:08.000000000","message":"Is this correct statement. Or not all of them have been validated, or tested or have 3rd party CI for it?","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"c69e3e9608a13feff9e88d647c61679c341e427c","unresolved":false,"context_lines":[{"line_number":75,"context_line":"the BMC. Those implement the ``bios``, ``inspect``, ``management``, and"},{"line_number":76,"context_line":"``power`` hardware interfaces. Again, like the hardware type, they are named"},{"line_number":77,"context_line":"``redfish``. They rely on ``sushy``\u0027s Redfish client. Importantly, while some"},{"line_number":78,"context_line":"of those work with the iDRAC, including ``management`` and ``power``, not all"},{"line_number":79,"context_line":"of them do."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The ``redfish`` hardware type enables managing servers compliant with the"},{"line_number":82,"context_line":"Redfish protocol. However, the hardware type is relatively new and the protocol"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_6802d6b6","line":79,"range":{"start_line":78,"start_character":70,"end_line":79,"end_character":11},"in_reply_to":"9fb8cfa7_28285e84","updated":"2019-06-22 00:05:21.000000000","message":"Yes, this statement is accurate. The Redfish bios interface implementation presently doesn\u0027t work with the iDRAC. That\u0027s mentioned in the next paragraph.\n\nAs far as I understand, not all of them are exercised by 3rd party CI. I believe only management and power are.","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"b2a08a8026d3483da888e405e3ebc0eef9028ef4","unresolved":false,"context_lines":[{"line_number":75,"context_line":"the BMC. Those implement the ``bios``, ``inspect``, ``management``, and"},{"line_number":76,"context_line":"``power`` hardware interfaces. Again, like the hardware type, they are named"},{"line_number":77,"context_line":"``redfish``. They rely on ``sushy``\u0027s Redfish client. Importantly, while some"},{"line_number":78,"context_line":"of those work with the iDRAC, including ``management`` and ``power``, not all"},{"line_number":79,"context_line":"of them do."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The ``redfish`` hardware type enables managing servers compliant with the"},{"line_number":82,"context_line":"Redfish protocol. However, the hardware type is relatively new and the protocol"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_31768208","line":79,"range":{"start_line":78,"start_character":70,"end_line":79,"end_character":11},"in_reply_to":"9fb8cfa7_6802d6b6","updated":"2019-06-24 03:00:29.000000000","message":"OK","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":131,"context_line":"  ``redfish_system_id``, ``redfish_username``, and ``redfish_password``. See"},{"line_number":132,"context_line":"  the `Redfish driver`_ documentation."},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"  Changing that TripleO command to set both the Redfish and WS-Man properties"},{"line_number":135,"context_line":"  in a node\u0027s ``driver_info`` field when its ``driver`` is ``idrac`` is beyond"},{"line_number":136,"context_line":"  the scope of this specification. That will be addressed by a TripleO project"},{"line_number":137,"context_line":"  blueprint."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"* Define ``idrac`` hardware type support of IPMI interface implementations."},{"line_number":140,"context_line":"  That could be done as a follow-on to this."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_6835f6d9","line":137,"range":{"start_line":134,"start_character":2,"end_line":137,"end_character":12},"updated":"2019-06-21 23:01:08.000000000","message":"good","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":227,"context_line":"  specific incompatibilities with the generic, vendor-independent ``redfish``"},{"line_number":228,"context_line":"  hardware type nor using Redfish to introduce vendor value added."},{"line_number":229,"context_line":""},{"line_number":230,"context_line":"* We could let the ``redfish`` interface implementations use Redfish OEM"},{"line_number":231,"context_line":"  extensions to address vendor-specific incompatibilities and introduce vendor"},{"line_number":232,"context_line":"  value added. However, that seems inconsistent with the intent that they be"},{"line_number":233,"context_line":"  generic and vendor-independent."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"Data model impact"},{"line_number":236,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_a869aebe","line":233,"range":{"start_line":230,"start_character":1,"end_line":233,"end_character":33},"updated":"2019-06-21 23:01:08.000000000","message":"I think this will can considered as future work outside this spec, especially for customer needed functionality that cannot be delivered by base redfish implementation.","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":385,"context_line":"Upgrades and Backwards Compatibility"},{"line_number":386,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":387,"context_line":""},{"line_number":388,"context_line":"This change is designed to be backwards compatible. The legacy ``idrac``"},{"line_number":389,"context_line":"interface implementation entrypoints will be supported for at least some time."},{"line_number":390,"context_line":"A separate story will cover their deprecation."},{"line_number":391,"context_line":""},{"line_number":392,"context_line":"We will recommend switching to the appropriate new ``idrac-redfish`` and"},{"line_number":393,"context_line":"``idrac-wsman`` interface implementation entrypoints as soon as it is possible."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_885e2a10","line":390,"range":{"start_line":388,"start_character":0,"end_line":390,"end_character":46},"updated":"2019-06-21 23:01:08.000000000","message":"good","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":7160,"name":"arkady kanevsky","email":"akanevsk@redhat.com","username":"arkady"},"change_message_id":"5265e5ebb0951ae13dbe9b64142af00ae89689c7","unresolved":false,"context_lines":[{"line_number":396,"context_line":"Documentation Impact"},{"line_number":397,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":398,"context_line":""},{"line_number":399,"context_line":"The `iDRAC driver`_ documentation is updated to:"},{"line_number":400,"context_line":""},{"line_number":401,"context_line":"* describe switching from the legacy ``idrac`` interface implementation"},{"line_number":402,"context_line":"  entrypoints to the new ``idrac-redfish`` and ``idrac-wsman`` entrypoints,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fb8cfa7_489ef2b8","line":399,"range":{"start_line":399,"start_character":0,"end_line":399,"end_character":48},"updated":"2019-06-21 23:01:08.000000000","message":"good","commit_id":"83e55c92d1513f1cb542da014d15a883bfbd64b1"},{"author":{"_account_id":11076,"name":"Shivanand Tendulker","email":"stendulker@gmail.com","username":"stendulker"},"change_message_id":"a99486d39bdf4c89e465b22eb88589d4601130df","unresolved":false,"context_lines":[{"line_number":181,"context_line":"  refer to Redfish interface implementations which are compatible with the"},{"line_number":182,"context_line":"  iDRAC, presently those of the ``management`` and ``power`` hardware"},{"line_number":183,"context_line":"  interfaces. The ``idrac-wsman`` entrypoints are new names for the legacy"},{"line_number":184,"context_line":"  ``idrac`` entrypoints. The legacy ``idrac`` entrypoints are left unchanged."},{"line_number":185,"context_line":"  For example::"},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"    ironic.hardware.interfaces.management \u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9fb8cfa7_396ecd96","line":184,"range":{"start_line":184,"start_character":25,"end_line":184,"end_character":76},"updated":"2019-07-03 09:43:00.000000000","message":"Will the new features be available through ``idrac`` power and management interfaces or one would have to change it to ``idrac-wsman`` or ``idrac-redfish`` based on that feature? I suppose it would support would have behavior similar to idrac-wsman inetrface.","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":11076,"name":"Shivanand Tendulker","email":"stendulker@gmail.com","username":"stendulker"},"change_message_id":"e4259144e4647be618308dda5b4c28870b7f2fc1","unresolved":false,"context_lines":[{"line_number":181,"context_line":"  refer to Redfish interface implementations which are compatible with the"},{"line_number":182,"context_line":"  iDRAC, presently those of the ``management`` and ``power`` hardware"},{"line_number":183,"context_line":"  interfaces. The ``idrac-wsman`` entrypoints are new names for the legacy"},{"line_number":184,"context_line":"  ``idrac`` entrypoints. The legacy ``idrac`` entrypoints are left unchanged."},{"line_number":185,"context_line":"  For example::"},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"    ironic.hardware.interfaces.management \u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_d0bbd10b","line":184,"range":{"start_line":184,"start_character":25,"end_line":184,"end_character":76},"in_reply_to":"7faddb67_b555ea1f","updated":"2019-07-04 09:19:44.000000000","message":"Thanks, this makes sense.","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"28a65e30e2ae507b913603ef3edbbeefabbb66df","unresolved":false,"context_lines":[{"line_number":181,"context_line":"  refer to Redfish interface implementations which are compatible with the"},{"line_number":182,"context_line":"  iDRAC, presently those of the ``management`` and ``power`` hardware"},{"line_number":183,"context_line":"  interfaces. The ``idrac-wsman`` entrypoints are new names for the legacy"},{"line_number":184,"context_line":"  ``idrac`` entrypoints. The legacy ``idrac`` entrypoints are left unchanged."},{"line_number":185,"context_line":"  For example::"},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"    ironic.hardware.interfaces.management \u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_b555ea1f","line":184,"range":{"start_line":184,"start_character":25,"end_line":184,"end_character":76},"in_reply_to":"9fb8cfa7_396ecd96","updated":"2019-07-03 22:44:52.000000000","message":"New features may be added to both the WS-Man and Redfish interface implementations or only one or the other.\n\n``idrac`` becomes a synonym for ``idrac-wsman``. Bug fixes and new features added to the WS-Man interface implementations are available from both entrypoints. Please see the new content added by patch set five (5) on lines 224-242 -- https://review.opendev.org/#/c/665576/5/specs/approved/idrac-support-of-redfish-interfaces.rst@224","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"bb2ec042d123897cbee6de6794d9650a50eb30b3","unresolved":false,"context_lines":[{"line_number":188,"context_line":"        ..."},{"line_number":189,"context_line":"        idrac \u003d ironic.drivers.modules.drac.management:DracManagement"},{"line_number":190,"context_line":"        idrac-redfish \u003d ironic.drivers.modules.drac.management:DracRedfishManagement"},{"line_number":191,"context_line":"        idrac-wsman \u003d ironic.drivers.modules.drac.management:DracWSManManagement"},{"line_number":192,"context_line":"        ..."},{"line_number":193,"context_line":"        redfish \u003d ironic.drivers.modules.redfish.management:RedfishManagement"},{"line_number":194,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9fb8cfa7_f9fddf6d","line":191,"updated":"2019-06-27 19:18:37.000000000","message":"Is DracWSManManagement just an alias of DracManagement? (and same for power)","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"28a65e30e2ae507b913603ef3edbbeefabbb66df","unresolved":false,"context_lines":[{"line_number":188,"context_line":"        ..."},{"line_number":189,"context_line":"        idrac \u003d ironic.drivers.modules.drac.management:DracManagement"},{"line_number":190,"context_line":"        idrac-redfish \u003d ironic.drivers.modules.drac.management:DracRedfishManagement"},{"line_number":191,"context_line":"        idrac-wsman \u003d ironic.drivers.modules.drac.management:DracWSManManagement"},{"line_number":192,"context_line":"        ..."},{"line_number":193,"context_line":"        redfish \u003d ironic.drivers.modules.redfish.management:RedfishManagement"},{"line_number":194,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_003d9aba","line":191,"in_reply_to":"9fb8cfa7_f9fddf6d","updated":"2019-07-03 22:44:52.000000000","message":"The proposed change makes it the other way around. DracManagement becomes an alias of DracWSManManagement. That is done by changing the class name from DracManagement to DracWSManManagement and creating a new definition of class DracManagement which is entirely derived from DracWSManManagement.\n\nNew content added by patch set five (5) covers this on lines 224-242 -- https://review.opendev.org/#/c/665576/5/specs/approved/idrac-support-of-redfish-interfaces.rst@224","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"bb2ec042d123897cbee6de6794d9650a50eb30b3","unresolved":false,"context_lines":[{"line_number":219,"context_line":"  Dell EMC-specific incompatibility or introduce vendor value added, which"},{"line_number":220,"context_line":"  would eliminate support for ``redfish``, could be a breaking change. The new"},{"line_number":221,"context_line":"  Python classes are derived from the generic, vendor-independent Redfish"},{"line_number":222,"context_line":"  classes."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"  Analogously, the same applies to the new ``idrac-wsman`` entry points."},{"line_number":225,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9fb8cfa7_39085790","line":222,"updated":"2019-06-27 19:18:37.000000000","message":"Redfish makes my ideal world sad, but this paragraph makes sense in reality.","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"28a65e30e2ae507b913603ef3edbbeefabbb66df","unresolved":false,"context_lines":[{"line_number":219,"context_line":"  Dell EMC-specific incompatibility or introduce vendor value added, which"},{"line_number":220,"context_line":"  would eliminate support for ``redfish``, could be a breaking change. The new"},{"line_number":221,"context_line":"  Python classes are derived from the generic, vendor-independent Redfish"},{"line_number":222,"context_line":"  classes."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"  Analogously, the same applies to the new ``idrac-wsman`` entry points."},{"line_number":225,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_c0e22230","line":222,"in_reply_to":"9fb8cfa7_39085790","updated":"2019-07-03 22:44:52.000000000","message":"I fully empathize with your ideal world view :)\n\nI like to think of it as enabling vendors to innovate and deliver new functionality before being covered by the standard. Also, it supports an evolutionary approach to offering Redfish from non-greenfield BMC codebases which must continue to support legacy client workflows.","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"bb2ec042d123897cbee6de6794d9650a50eb30b3","unresolved":false,"context_lines":[{"line_number":320,"context_line":"  and ``enabled_power_interfaces`` options to enable those new interface"},{"line_number":321,"context_line":"  implementations."},{"line_number":322,"context_line":""},{"line_number":323,"context_line":"* A deployer can add ``idrac-wsman`` to the ``enabled_inspect_intefaces``,"},{"line_number":324,"context_line":"  ``enabled_management_interfaces``, ``enabled_power_interfaces``,"},{"line_number":325,"context_line":"  ``enabled_raid_interfaces``, and ``enabled_vendor_interfaces`` to enable"},{"line_number":326,"context_line":"  those new interface implementations."}],"source_content_type":"text/x-rst","patch_set":4,"id":"9fb8cfa7_b9fbe776","line":323,"updated":"2019-06-27 19:18:37.000000000","message":"nit: s/intefaces/interfaces/","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"441440b313a7edc1bc76dc7e9b45cb3783e798b8","unresolved":false,"context_lines":[{"line_number":320,"context_line":"  and ``enabled_power_interfaces`` options to enable those new interface"},{"line_number":321,"context_line":"  implementations."},{"line_number":322,"context_line":""},{"line_number":323,"context_line":"* A deployer can add ``idrac-wsman`` to the ``enabled_inspect_intefaces``,"},{"line_number":324,"context_line":"  ``enabled_management_interfaces``, ``enabled_power_interfaces``,"},{"line_number":325,"context_line":"  ``enabled_raid_interfaces``, and ``enabled_vendor_interfaces`` to enable"},{"line_number":326,"context_line":"  those new interface implementations."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_405e32e7","line":323,"in_reply_to":"9fb8cfa7_b9fbe776","updated":"2019-07-03 22:54:02.000000000","message":"Done\n\nI overlooked this in patch set five (5) :-( However, patch set six (6) corrects it.","commit_id":"a403604fbdd9b1bbd0fd461457359dee122653ec"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"e093db86af0c59a49e0ccdda3363be308b233f2f","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Use cases"},{"line_number":33,"context_line":"---------"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Expanding on what the introductory paragraph describes above, several use cases"},{"line_number":36,"context_line":"can be envisioned. While this specification enables them, it may turn out only"},{"line_number":37,"context_line":"some will find practical use among operators. That could be driven by many"},{"line_number":38,"context_line":"factors, including an existing versus greenfield deployment, operator comfort"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7faddb67_b5e08a98","line":35,"range":{"start_line":35,"start_character":0,"end_line":35,"end_character":12},"updated":"2019-07-03 22:06:30.000000000","message":"good change!","commit_id":"2ac92455a7f608ed1edb4d2f75cb5e2cdc92ccca"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"e093db86af0c59a49e0ccdda3363be308b233f2f","unresolved":false,"context_lines":[{"line_number":239,"context_line":"  ``idrac-wsman`` entrypoints. Having separate classes for the two groups of"},{"line_number":240,"context_line":"  entrypoints makes it possible to subsequently add logic that implements"},{"line_number":241,"context_line":"  deprecation of the legacy ``idrac`` entrypoints by emitting a log message and"},{"line_number":242,"context_line":"  similar."},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"Alternatives"},{"line_number":245,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7faddb67_55efd686","line":242,"updated":"2019-07-03 22:06:30.000000000","message":"I suspected this would be the case. Okay!","commit_id":"2ac92455a7f608ed1edb4d2f75cb5e2cdc92ccca"},{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"c3e56754228ca4851f626afa9129bca783bc261d","unresolved":false,"context_lines":[{"line_number":23,"context_line":"* is supported by the vendor and community, and"},{"line_number":24,"context_line":"* can offer Dell EMC value added."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"This specification suggests the ``idrac`` hardware type provide that."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7faddb67_6126cdba","line":26,"range":{"start_line":26,"start_character":56,"end_line":26,"end_character":63},"updated":"2019-07-04 08:54:49.000000000","message":"nit: provides","commit_id":"91c60b298eba5edf7373a161c0c6ab88d64fe59f"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"352c19952acb958721ad3adf015ac5e1e8431d19","unresolved":false,"context_lines":[{"line_number":23,"context_line":"* is supported by the vendor and community, and"},{"line_number":24,"context_line":"* can offer Dell EMC value added."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"This specification suggests the ``idrac`` hardware type provide that."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":6,"id":"7faddb67_db6446bc","line":26,"range":{"start_line":26,"start_character":56,"end_line":26,"end_character":63},"in_reply_to":"7faddb67_6126cdba","updated":"2019-07-04 21:44:28.000000000","message":"Done\n\nGood find. This is addressed by patch set seven (7).\n\nI had noticed this previously, but couldn\u0027t find it again. I suppose I had gotten spec editing fatigue ;-) Thank you for saving me from racking my brain!","commit_id":"91c60b298eba5edf7373a161c0c6ab88d64fe59f"},{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"c3e56754228ca4851f626afa9129bca783bc261d","unresolved":false,"context_lines":[{"line_number":88,"context_line":"The ``redfish`` hardware type enables managing servers compliant with the"},{"line_number":89,"context_line":"Redfish protocol. However, it is relatively new, and the protocol standard has"},{"line_number":90,"context_line":"been evolving, along with its implementations by hardware vendors such as Dell"},{"line_number":91,"context_line":"EMC. As is common with standards, there is a difference between compliance and"},{"line_number":92,"context_line":"interoperability. For example, the Redfish ``bios`` interface implementation"},{"line_number":93,"context_line":"has not worked with the iDRAC because of client and server protocol"},{"line_number":94,"context_line":"implementation incompatibility."}],"source_content_type":"text/x-rst","patch_set":6,"id":"7faddb67_216695ef","line":91,"range":{"start_line":91,"start_character":8,"end_line":91,"end_character":10},"updated":"2019-07-04 08:54:49.000000000","message":"nit: it\u0027s","commit_id":"91c60b298eba5edf7373a161c0c6ab88d64fe59f"},{"author":{"_account_id":23847,"name":"Richard G. Pioso","email":"richard.pioso@gmail.com","username":"richard.pioso"},"change_message_id":"352c19952acb958721ad3adf015ac5e1e8431d19","unresolved":false,"context_lines":[{"line_number":88,"context_line":"The ``redfish`` hardware type enables managing servers compliant with the"},{"line_number":89,"context_line":"Redfish protocol. However, it is relatively new, and the protocol standard has"},{"line_number":90,"context_line":"been evolving, along with its implementations by hardware vendors such as Dell"},{"line_number":91,"context_line":"EMC. As is common with standards, there is a difference between compliance and"},{"line_number":92,"context_line":"interoperability. For example, the Redfish ``bios`` interface implementation"},{"line_number":93,"context_line":"has not worked with the iDRAC because of client and server protocol"},{"line_number":94,"context_line":"implementation incompatibility."}],"source_content_type":"text/x-rst","patch_set":6,"id":"7faddb67_3b21da4e","line":91,"range":{"start_line":91,"start_character":8,"end_line":91,"end_character":10},"in_reply_to":"7faddb67_216695ef","updated":"2019-07-04 21:44:28.000000000","message":"\"As is\" versus \"As it is\" seems debatable to me. I\u0027m going to stick with \"As is\", because it is defined \"Just the way it is\" [1] and \"In the existing circumstances\" [2]. I replaced \"with standards\" with \"among standards\".\n\nPlease see patch set seven (7).\n\n[1] https://www.dictionary.com/browse/as--is?s\u003dts, at the end of the page\n[2] https://www.lexico.com/en/definition/as_(it)_is","commit_id":"91c60b298eba5edf7373a161c0c6ab88d64fe59f"}]}