)]}'
{"/PATCHSET_LEVEL":[{"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":"65d4a328b44a38d6d3421bab4117c691aa914628","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"374eea87_64ff2f60","updated":"2026-02-08 21:16:43.000000000","message":"I\u0027d really love to see Dmitry\u0027s suggestion re: value prefixing implemented.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"19b803af519edf5286c705a6174f0490987e1a75","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"db320b9b_1c00368d","updated":"2026-02-06 12:59:52.000000000","message":"I\u0027m wondering if we should just switch everything to using serial numbers (falling back to ID\u0027s) just for consistency.\n\nAnother thought: maybe prefix the value with something to give it context? E.g. instead of `nic:ABCD` you get `nic:sn:ABCD`, where \"sn\" hints at a serial number?\n\nBoth could be topics for the next Ironic meeting. Consider me +2 if the community is ambivalent about these issues or disagrees with me.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"85399c74ebd8762c3032563232c79597e11bdf3c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"00e19f96_20e9c8e6","updated":"2026-02-06 16:40:52.000000000","message":"This falls under that same case of needing quirks.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":15519,"name":"Iury Gregory Melo Ferreira","display_name":"Iury Gregory","email":"iurygregory@gmail.com","username":"iurygregory"},"change_message_id":"9211aeafd722d816b1e8c8413091c818b915e6b2","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"514713ee_1c7d4ffb","in_reply_to":"374eea87_64ff2f60","updated":"2026-02-09 15:35:40.000000000","message":"We could implement, but like mentioned in the weekly meeting, this would not fix our problem.\nCurrently we have `nic:\u003cID\u003e` and \u003cID\u003e is something that changes after an update, if we go down `nic:\u003cSN\u003e:\u003cID\u003e` we will still hit the same problem, unless we store `nic:\u003cSN\u003e` and \u003cID\u003e in a separate field and let it visible for the end user, but this would change our current DB Model.\n\nThe question we have open is, do we change to `nic:\u003cSN\u003e` to all vendors? Or only for HPE that has this problem?","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"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":"0408448adfa839b084b519a1e596a086df6fd968","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4a8b751c_57dbe6c5","in_reply_to":"3c745912_6023ea04","updated":"2026-02-09 16:30:40.000000000","message":"I don\u0027t have an opinion strong enough to pend a +2 on it; so either way works for me; but I wonder if we\u0027re going to be creating a differently-shaped edge case around BMCs that don\u0027t reliably have accurate serials :).","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":15519,"name":"Iury Gregory Melo Ferreira","display_name":"Iury Gregory","email":"iurygregory@gmail.com","username":"iurygregory"},"change_message_id":"9bb35598b3e70848202c5b24f25ce298df269a84","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"9316243f_ec1b6259","in_reply_to":"4a8b751c_57dbe6c5","updated":"2026-02-10 02:17:42.000000000","message":"Done","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":23851,"name":"Riccardo Pittau","email":"elfosardo@gmail.com","username":"elfosardo"},"change_message_id":"8575a8266eaaa939cfd9c26c51feda96db155ad8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"be9c06c8_a4fe5b32","in_reply_to":"514713ee_1c7d4ffb","updated":"2026-02-09 16:22:13.000000000","message":"I vote for changing it for all vendors.\nUsing SN is objectively more robust because it’s tied to the physical hardware rather than a software-defined index. While only HPE is causing headaches today, Dell or Cisco could easily change their API response structure in a future firmware release. Standardizing on the Serial Number now prevents from having to do this exact same thing in the future.\nAlso what if we track both ID and SN?\nWe gain the ability to track the hardware consistently while still knowing its current logical position in the OS/Firmware.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":15519,"name":"Iury Gregory Melo Ferreira","display_name":"Iury Gregory","email":"iurygregory@gmail.com","username":"iurygregory"},"change_message_id":"cb7c810d9e4dde9c933fdbc77e1d50cbbe5849c8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"3c745912_6023ea04","in_reply_to":"be9c06c8_a4fe5b32","updated":"2026-02-09 16:26:13.000000000","message":"Thanks Riccardo! I will update the patch to address this.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":15519,"name":"Iury Gregory Melo Ferreira","display_name":"Iury Gregory","email":"iurygregory@gmail.com","username":"iurygregory"},"change_message_id":"c77ca01bfdbc0e5d63c6767c76046258a859c29e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e46cec5c_6c67dac8","in_reply_to":"db320b9b_1c00368d","updated":"2026-02-06 13:18:22.000000000","message":"\u003eI\u0027m wondering if we should just switch everything to using serial numbers (falling back to ID\u0027s) just for consistency.\nThis sounds reasonable to me, I will bring up the topic in the upstream meeting on monday. \n\n\u003e Another thought: maybe prefix the value with something to give it context? E.g. instead of nic:ABCD you get nic:sn:ABCD, where \"sn\" hints at a serial number?\nIn case ABCD is the Id, we would hit the same problem.This would generate \n`nic:\u003cSN\u003e:DE080000` and after uprade it would be `nic:\u003cSN\u003e:DE090000. \n\nThank you!","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"774c1119ea6e2ed702487b236ffe2b69581b1e02","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"9660e5a5_38e79858","in_reply_to":"e46cec5c_6c67dac8","updated":"2026-02-06 14:49:42.000000000","message":"\u003e In case ABCD is the Id, we would hit the same problem.This would generate\nnic:\u003cSN\u003e:DE080000 and after uprade it would be `nic:\u003cSN\u003e:DE090000. \n\nYeah, I did not mean this suggestion as an alternative to your approach, but rather as an improvement for consumers. Especially if we end up using both IDs and SNs, it\u0027s useful to distinguish them somehow. Maybe.","commit_id":"0f05266083a187d62281e21c2e7851b992d3929e"}]}