)]}'
{"specs/backlog/standalone-networking.rst":[{"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":"bafb9f010f1a1d505423cc74151bc63c0f98a561","unresolved":true,"context_lines":[{"line_number":166,"context_line":""},{"line_number":167,"context_line":"  2. Inspection Network Configuration"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"  A new configuration option inspector.dhcp_all_interfaces modifies the"},{"line_number":170,"context_line":"  inspection process behavior:"},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffb2bcda_759660f4","line":169,"updated":"2025-09-15 17:59:30.000000000","message":"I\u0027d prefer a different name than this. It\u0027s weird that it influences LLDP as well. Maybe there\u0027s a better name? I\u0027ve been thinking and I don\u0027t have one right now (inspect_all_interfaces (?))","commit_id":"2589cd369b5be0a55ebb7a2debf55a9d44dfab61"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"eec2b20b8aa604670e64007c7c426252d4714d15","unresolved":false,"context_lines":[{"line_number":166,"context_line":""},{"line_number":167,"context_line":"  2. Inspection Network Configuration"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"  A new configuration option inspector.dhcp_all_interfaces modifies the"},{"line_number":170,"context_line":"  inspection process behavior:"},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"}],"source_content_type":"text/x-rst","patch_set":2,"id":"63f1ffaf_fa75cdec","line":169,"in_reply_to":"ffb2bcda_759660f4","updated":"2025-09-15 18:23:36.000000000","message":"Agreed.  I kicked this around for a while too and no spectacular choices were coming to mind.   I do like \"inspect_all_interfaces\"... generic enough.  I\u0027ll revise it.","commit_id":"2589cd369b5be0a55ebb7a2debf55a9d44dfab61"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"b8c60c2b5e2359c6ad485cbaa5bba36d3f6ff98d","unresolved":true,"context_lines":[{"line_number":147,"context_line":"To address these concerns two changes to the node state machine should be"},{"line_number":148,"context_line":"considered for which two additional configuration options are proposed:"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"  1. Restoration of Inspection Network"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"  A new configuration option conductor.restore_inspection_network_on_deletion"},{"line_number":153,"context_line":"  enables automatic restoration of inspection network configuration during key"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9ce8bc02_53f1354e","line":150,"updated":"2025-09-23 16:45:42.000000000","message":"FWIW, I\u0027m not really a fan of kicking nodes back to the introspection network, but I\u0027ve *long* advocated folks consider vlan1 by default for hardware introspection, which can then be mapped in and used.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"87e6beb20de9196bf5b7ac4d75ccf464883cceef","unresolved":true,"context_lines":[{"line_number":147,"context_line":"To address these concerns two changes to the node state machine should be"},{"line_number":148,"context_line":"considered for which two additional configuration options are proposed:"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"  1. Restoration of Inspection Network"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"  A new configuration option conductor.restore_inspection_network_on_deletion"},{"line_number":153,"context_line":"  enables automatic restoration of inspection network configuration during key"}],"source_content_type":"text/x-rst","patch_set":3,"id":"be8e3703_888e79bb","line":150,"in_reply_to":"9ce8bc02_53f1354e","updated":"2025-09-23 17:46:56.000000000","message":"I think what you are suggesting is similar to what I\u0027ve noted here.  In your case, vlan 1 would still have to have all of the capabilities of the inspection vlan -- it would need to respond to DHCP and it would need to be routable back to the API.  At that point, what would be the difference between that and the inspection vlan?  They might as well be the same thing... whether that\u0027s vlan 1 or vlan X does it really matter?\n\nThe issue that needs to be addressed is that when a node gets deleted its switch ports need to be put back in a state for a subsequent first inspection to work when the node is re-enrolled; otherwise, we won\u0027t be able to get the LLDP information and therefore won\u0027t know which switch ports to configure.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"47a903d2bfa47e265da8e227606c4acc84ab2b64","unresolved":false,"context_lines":[{"line_number":147,"context_line":"To address these concerns two changes to the node state machine should be"},{"line_number":148,"context_line":"considered for which two additional configuration options are proposed:"},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"  1. Restoration of Inspection Network"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"  A new configuration option conductor.restore_inspection_network_on_deletion"},{"line_number":153,"context_line":"  enables automatic restoration of inspection network configuration during key"}],"source_content_type":"text/x-rst","patch_set":3,"id":"92d07d12_729a9ff4","line":150,"in_reply_to":"be8e3703_888e79bb","updated":"2025-10-02 00:24:04.000000000","message":"As discussed, will use a different approach.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"83997d1348b0cdcc5efbd29cd3ef02a8c329b525","unresolved":true,"context_lines":[{"line_number":156,"context_line":"  - Available State Transition: After automated cleaning completion, nodes"},{"line_number":157,"context_line":"    transitioning to the available state will have their inspection network"},{"line_number":158,"context_line":"    configuration restored"},{"line_number":159,"context_line":"  - Node Deletion: Before node deletion (when not in maintenance mode), the"},{"line_number":160,"context_line":"    inspection network configuration is restored to ensure physical switch"},{"line_number":161,"context_line":"    ports remain properly configured for LLDP discovery during re-enrollment."},{"line_number":162,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"596d9e1b_87f481b5","line":159,"updated":"2025-09-24 12:24:37.000000000","message":"This is probably not doable. Deletion in Ironic is a short synchronous API, we cannot make full-blown calls to the switch in it.\n\nThere is also a very popular (at least in our world) pattern of \"disowning\" nodes by deleting them while in the \"active\" state. I don\u0027t think we should touch networking this case.\n\nI think it\u0027s fine if you only do the first bullet point and restore networking on deprovisioning.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"603ef5d70d22ae3cb6eed12540d5ba28ec23273c","unresolved":true,"context_lines":[{"line_number":156,"context_line":"  - Available State Transition: After automated cleaning completion, nodes"},{"line_number":157,"context_line":"    transitioning to the available state will have their inspection network"},{"line_number":158,"context_line":"    configuration restored"},{"line_number":159,"context_line":"  - Node Deletion: Before node deletion (when not in maintenance mode), the"},{"line_number":160,"context_line":"    inspection network configuration is restored to ensure physical switch"},{"line_number":161,"context_line":"    ports remain properly configured for LLDP discovery during re-enrollment."},{"line_number":162,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"a4cb6887_d7ec0874","line":159,"in_reply_to":"596d9e1b_87f481b5","updated":"2025-09-24 18:11:19.000000000","message":"Ok, I\u0027ll test it out with just the change to deprovisioning.  Thanks.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"47a903d2bfa47e265da8e227606c4acc84ab2b64","unresolved":false,"context_lines":[{"line_number":156,"context_line":"  - Available State Transition: After automated cleaning completion, nodes"},{"line_number":157,"context_line":"    transitioning to the available state will have their inspection network"},{"line_number":158,"context_line":"    configuration restored"},{"line_number":159,"context_line":"  - Node Deletion: Before node deletion (when not in maintenance mode), the"},{"line_number":160,"context_line":"    inspection network configuration is restored to ensure physical switch"},{"line_number":161,"context_line":"    ports remain properly configured for LLDP discovery during re-enrollment."},{"line_number":162,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"c08147a8_1e95d0c1","line":159,"in_reply_to":"8e24218d_e5b07861","updated":"2025-10-02 00:24:04.000000000","message":"Discussed with Julia... going with a different approach of always restoring the network whenever any of the remove_*_network interfaces are called.  This will avoid any changes to the state machine directly.  Logic will be in the standalone experimental network driver.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"737a03ae244ef8c813df7b0d1c303c18617cc5d5","unresolved":true,"context_lines":[{"line_number":156,"context_line":"  - Available State Transition: After automated cleaning completion, nodes"},{"line_number":157,"context_line":"    transitioning to the available state will have their inspection network"},{"line_number":158,"context_line":"    configuration restored"},{"line_number":159,"context_line":"  - Node Deletion: Before node deletion (when not in maintenance mode), the"},{"line_number":160,"context_line":"    inspection network configuration is restored to ensure physical switch"},{"line_number":161,"context_line":"    ports remain properly configured for LLDP discovery during re-enrollment."},{"line_number":162,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"8e24218d_e5b07861","line":159,"in_reply_to":"a4cb6887_d7ec0874","updated":"2025-10-01 13:06:16.000000000","message":"Actually... thinking about this some more.  The deprovisioning part would handle an active node being recycled, but not a node that just got added and never deployed ...and then was deleted and re-added again.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"83997d1348b0cdcc5efbd29cd3ef02a8c329b525","unresolved":true,"context_lines":[{"line_number":171,"context_line":""},{"line_number":172,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"},{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"920323d5_9f9a1b26","line":174,"updated":"2025-09-24 12:24:37.000000000","message":"Cannot this be solved with just a kernel parameter?","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"603ef5d70d22ae3cb6eed12540d5ba28ec23273c","unresolved":true,"context_lines":[{"line_number":171,"context_line":""},{"line_number":172,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"},{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"eaf96670_d96c9f18","line":174,"in_reply_to":"920323d5_9f9a1b26","updated":"2025-09-24 18:11:19.000000000","message":"Yes, but I think we have to ensure that we don\u0027t include the static data.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"47a903d2bfa47e265da8e227606c4acc84ab2b64","unresolved":false,"context_lines":[{"line_number":171,"context_line":""},{"line_number":172,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"},{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"b9a8fed0_469a5293","line":174,"in_reply_to":"eaf96670_d96c9f18","updated":"2025-10-02 00:24:04.000000000","message":"Yes, Julia pointed out my error here.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"83997d1348b0cdcc5efbd29cd3ef02a8c329b525","unresolved":true,"context_lines":[{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"}],"source_content_type":"text/x-rst","patch_set":3,"id":"166c6d79_7b380115","line":176,"updated":"2025-09-24 12:24:37.000000000","message":"This is already enabled by a kernel parameter.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"47a903d2bfa47e265da8e227606c4acc84ab2b64","unresolved":false,"context_lines":[{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"}],"source_content_type":"text/x-rst","patch_set":3,"id":"42dc9120_3af69e7d","line":176,"in_reply_to":"0e04d1c6_9bd8baa1","updated":"2025-10-02 00:24:04.000000000","message":"Thanks, Julia pointed out the error of my ways...","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"603ef5d70d22ae3cb6eed12540d5ba28ec23273c","unresolved":true,"context_lines":[{"line_number":173,"context_line":"    forces the inspection ramdisk to use DHCP on all available network"},{"line_number":174,"context_line":"    interfaces instead of injecting static network configuration"},{"line_number":175,"context_line":"  - Network Discovery: Automatically enables LLDP collection across all"},{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0e04d1c6_9bd8baa1","line":176,"in_reply_to":"166c6d79_7b380115","updated":"2025-09-24 18:11:19.000000000","message":"Yes, but unless I\u0027m mistaken I\u0027m not sure that parameter is actually enabled by default... maybe I missed something?   Take a look over at the https://review.opendev.org/c/openstack/ironic/+/960824?usp\u003ddashboard and see if maybe I\u0027ve done it incorrectly.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"83997d1348b0cdcc5efbd29cd3ef02a8c329b525","unresolved":true,"context_lines":[{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"These changes do not introduce new provisioning states but enhance the"},{"line_number":182,"context_line":"existing state transitions to better support standalone networking scenarios"}],"source_content_type":"text/x-rst","patch_set":3,"id":"e1351a2e_7503735c","line":179,"updated":"2025-09-24 12:24:37.000000000","message":"Please elaborate, what does it do exactly?","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"3bc7585a035148314b3535fc868be46254cf74fd","unresolved":true,"context_lines":[{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"These changes do not introduce new provisioning states but enhance the"},{"line_number":182,"context_line":"existing state transitions to better support standalone networking scenarios"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0df5089e_01ebfb50","line":179,"in_reply_to":"0961d9a0_5b2b64dc","updated":"2025-10-02 13:11:11.000000000","message":"I don\u0027t think having the user set different network configs for different parts of the process is feasible since the state machine goes thru different phases autonomously without the possibility to override the network data each time the network changes.\n\nWhy would this be useless in OpenShift?  We do provide static network data and we do need that to be ignored when using a dedicated vlan for inspection.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"44f12779d5c0a442d3b134edc8a2e003a18dbb23","unresolved":true,"context_lines":[{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"These changes do not introduce new provisioning states but enhance the"},{"line_number":182,"context_line":"existing state transitions to better support standalone networking scenarios"}],"source_content_type":"text/x-rst","patch_set":3,"id":"79022a90_1472143e","line":179,"in_reply_to":"0df5089e_01ebfb50","updated":"2025-10-02 13:46:38.000000000","message":"\u003e state machine goes thru different phases autonomously\n\nIt is not the case for pure Ironic, and in fact not the case for pure Metal3 too (you can inspect with deploying).\n\nOpenShift has an entirely different ramdisk format that is opaque for Ironic. Ironic can neither modify its kernel parameters, nor edit its networking configuration. Happy to talk you through it on the downstream slack.","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"cecb0d0d69a0b17d6be5d50b6324f1fbfd8330db","unresolved":true,"context_lines":[{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"These changes do not introduce new provisioning states but enhance the"},{"line_number":182,"context_line":"existing state transitions to better support standalone networking scenarios"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0961d9a0_5b2b64dc","line":179,"in_reply_to":"c2289bf8_61319dfa","updated":"2025-10-02 13:06:54.000000000","message":"Cannot users just set different NetworkData for different parts of the process?\n\nThis option won\u0027t work well with fast track (and, as an aside, will be useless in OpenShift).","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"603ef5d70d22ae3cb6eed12540d5ba28ec23273c","unresolved":true,"context_lines":[{"line_number":176,"context_line":"    interfaces to ensure comprehensive network topology discovery"},{"line_number":177,"context_line":"  - Multi-Network Support: Addresses scenarios where inspection and"},{"line_number":178,"context_line":"    provisioning networks are separate, avoiding conflicts from provisioning"},{"line_number":179,"context_line":"    network static configuration being applied to inspection networks"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"These changes do not introduce new provisioning states but enhance the"},{"line_number":182,"context_line":"existing state transitions to better support standalone networking scenarios"}],"source_content_type":"text/x-rst","patch_set":3,"id":"c2289bf8_61319dfa","line":179,"in_reply_to":"e1351a2e_7503735c","updated":"2025-09-24 18:11:19.000000000","message":"Sorry, maybe this isn\u0027t clear enough.  I was simply trying to capture the scenario that this is trying to protect against... that is, the static network configuration is only good on the provisioning network and potentially not good on the inspection network.   Here I\u0027m sort of assuming that the static network config provided for the node is only good on the final network (i.e., the tenant network).","commit_id":"c914511db399ee1c0efa2d02d322722558375852"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"cecb0d0d69a0b17d6be5d50b6324f1fbfd8330db","unresolved":true,"context_lines":[{"line_number":159,"context_line":""},{"line_number":160,"context_line":"  1. Restoration of Idle Network"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"  A new configuration option networking.restore_idle_network used by the"},{"line_number":163,"context_line":"  standalone experimental network driver ensures that the \"idle\" network VLAN"},{"line_number":164,"context_line":"  is always set on the port configuration whenever a network is removed from"},{"line_number":165,"context_line":"  the port."}],"source_content_type":"text/x-rst","patch_set":4,"id":"2a8c5826_047b01cf","line":162,"updated":"2025-10-02 13:06:54.000000000","message":"Do you need a new option or can you just rely on networking.idle_network being not empty?","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"3bc7585a035148314b3535fc868be46254cf74fd","unresolved":true,"context_lines":[{"line_number":159,"context_line":""},{"line_number":160,"context_line":"  1. Restoration of Idle Network"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"  A new configuration option networking.restore_idle_network used by the"},{"line_number":163,"context_line":"  standalone experimental network driver ensures that the \"idle\" network VLAN"},{"line_number":164,"context_line":"  is always set on the port configuration whenever a network is removed from"},{"line_number":165,"context_line":"  the port."}],"source_content_type":"text/x-rst","patch_set":4,"id":"3554af31_ba255e0c","line":162,"in_reply_to":"2a8c5826_047b01cf","updated":"2025-10-02 13:11:11.000000000","message":"Yes, good point.  The option is probably overkill.","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"f1560abc6e923e890a6a834590230fdecac981db","unresolved":true,"context_lines":[{"line_number":159,"context_line":""},{"line_number":160,"context_line":"  1. Restoration of Idle Network"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"  A new configuration option networking.restore_idle_network used by the"},{"line_number":163,"context_line":"  standalone experimental network driver ensures that the \"idle\" network VLAN"},{"line_number":164,"context_line":"  is always set on the port configuration whenever a network is removed from"},{"line_number":165,"context_line":"  the port."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7ce55829_8ed88ea7","line":162,"in_reply_to":"3554af31_ba255e0c","updated":"2025-10-02 20:38:59.000000000","message":"removed","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"28dd9a7852525ef913ff3936b005d8a8f7e91238","unresolved":false,"context_lines":[{"line_number":159,"context_line":""},{"line_number":160,"context_line":"  1. Restoration of Idle Network"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"  A new configuration option networking.restore_idle_network used by the"},{"line_number":163,"context_line":"  standalone experimental network driver ensures that the \"idle\" network VLAN"},{"line_number":164,"context_line":"  is always set on the port configuration whenever a network is removed from"},{"line_number":165,"context_line":"  the port."}],"source_content_type":"text/x-rst","patch_set":4,"id":"26fcffdb_24d07c58","line":162,"in_reply_to":"7ce55829_8ed88ea7","updated":"2025-10-02 20:39:34.000000000","message":"removed","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"cecb0d0d69a0b17d6be5d50b6324f1fbfd8330db","unresolved":true,"context_lines":[{"line_number":170,"context_line":""},{"line_number":171,"context_line":"  2. Inspection Network Configuration"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"  A new configuration option inspector.force_inspection_dhcp modifies the"},{"line_number":174,"context_line":"  inspection process behavior:"},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"}],"source_content_type":"text/x-rst","patch_set":4,"id":"035f12cb_a84002e5","line":173,"updated":"2025-10-02 13:06:54.000000000","message":"nit: s/inspection_// (already in the group name)","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"3bc7585a035148314b3535fc868be46254cf74fd","unresolved":true,"context_lines":[{"line_number":170,"context_line":""},{"line_number":171,"context_line":"  2. Inspection Network Configuration"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"  A new configuration option inspector.force_inspection_dhcp modifies the"},{"line_number":174,"context_line":"  inspection process behavior:"},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"}],"source_content_type":"text/x-rst","patch_set":4,"id":"a141804e_c361918d","line":173,"in_reply_to":"035f12cb_a84002e5","updated":"2025-10-02 13:11:11.000000000","message":"ok, will change.","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":25437,"name":"Allain Legacy","email":"alegacy@redhat.com","username":"alegacy"},"change_message_id":"f1560abc6e923e890a6a834590230fdecac981db","unresolved":false,"context_lines":[{"line_number":170,"context_line":""},{"line_number":171,"context_line":"  2. Inspection Network Configuration"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"  A new configuration option inspector.force_inspection_dhcp modifies the"},{"line_number":174,"context_line":"  inspection process behavior:"},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"  - Inspection State: During managed inspection, when enabled, this option"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5cc3c4ae_6d247def","line":173,"in_reply_to":"a141804e_c361918d","updated":"2025-10-02 20:38:59.000000000","message":"renamed","commit_id":"8527d63663abe63239df31ac8d9e475f1724d5c1"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"047e4251d16bcf46e69b2a3b0cfea699bce24fab","unresolved":true,"context_lines":[{"line_number":140,"context_line":"1. The switch ports must be enabled prior to the initial enrollment of the node"},{"line_number":141,"context_line":"and must be configured on a VLAN that is capable of running the initial"},{"line_number":142,"context_line":"inspection for the node.  That is, the VLAN must be routable back to the API"},{"line_number":143,"context_line":"endpoint."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. To ensure that the enrollment process is repeatable for nodes that are"},{"line_number":146,"context_line":"deprovisioned and later re-enrolled we must ensure that switch ports are"}],"source_content_type":"text/x-rst","patch_set":5,"id":"870c9908_ec3ad2dc","line":143,"updated":"2025-10-03 16:20:02.000000000","message":"For reviewers: In classical ironic context, we expect ports to be present, and we expect operators to ensure that they are inspecting with ports enabled. The idea here makes it a bit more explicit.\n\nTo reiterate the basic idea, in a neutron context with an ml2 driver, this is vlan1, where the port is still likely enabled for line carrier so LLDP will work as desired. That way when a single network attachment gets made for introspection, or the ports change, then all of the ports get discovered as active via LLDP.\n\nWe also, really, don\u0027t handle the unprovision flow in ironic very well, in the event ports are disabled or not. Also operators may do things like set a node to maintenance and force delete which can leave an inconsistent state.","commit_id":"f3fd4d7e87bad6cbef1b9960b453c45bd94c2b9d"}]}