Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
NICo currently operates under the assumption that it controls the full bare-metal provisioning lifecycle and can explicitly observe both host boot events and network configuration events.
When network provisioning and reboots happen via an external workflow, NICo does not observe the host boot completion. As a result:
a. Instances get stuck in a pending state indefinitely.
b. There is no mechanism to reconcile the state, transition the instance to ready, or recover gracefully from external orchestration workflows.
Feature Description
NICo should natively support external provisioning workflows. It must allow an instance to transition to a ready state even when NICo does not directly orchestrate or observe the physical host boot, ensuring state consistency based on alternative readiness signals.
This feature introduces a modular, decoupled lifecycle tracking mechanism within NICo. It allows the platform to accurately manage, transition, and reconcile instance states for bare-metal hosts where the provisioning, network configuration, and reboot sequences are orchestrated by external, third-party automation systems.
By removing the strict hard-dependency on NICo-observed boot events, this enhancement enables seamless compatibility with Zero-DPU (NIC-mode) architectures and Bring-Your-Own-SDN (BYO-SDN) infrastructure models without introducing state-machine deadlocks.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
NICo currently operates under the assumption that it controls the full bare-metal provisioning lifecycle and can explicitly observe both host boot events and network configuration events.
When network provisioning and reboots happen via an external workflow, NICo does not observe the host boot completion. As a result:
a. Instances get stuck in a pending state indefinitely.
b. There is no mechanism to reconcile the state, transition the instance to ready, or recover gracefully from external orchestration workflows.
Feature Description
NICo should natively support external provisioning workflows. It must allow an instance to transition to a ready state even when NICo does not directly orchestrate or observe the physical host boot, ensuring state consistency based on alternative readiness signals.
This feature introduces a modular, decoupled lifecycle tracking mechanism within NICo. It allows the platform to accurately manage, transition, and reconcile instance states for bare-metal hosts where the provisioning, network configuration, and reboot sequences are orchestrated by external, third-party automation systems.
By removing the strict hard-dependency on NICo-observed boot events, this enhancement enables seamless compatibility with Zero-DPU (NIC-mode) architectures and Bring-Your-Own-SDN (BYO-SDN) infrastructure models without introducing state-machine deadlocks.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct