-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: properly handle powered off machines in the UI and machine classes
Introduce the new label `omni.sidero.dev/ready-to-use`, which is now used in the UI when creating/scaling a cluster and in the machine set scaling controller instead of `omni.sidero.dev/connected`. The machine status controller was changed to add the ready to use label when the machine is created by the bare metal infra provider. Then the controller looks on the state of the `InfraMachineStatus` resource and sets `omni.sidero.dev/ready-to-use` label when the `ReadyToUse` flag is true in the `InfraMachineStatus`. If the machine is managed by the bare metal infra provider and is not a part of a cluster we no longer set `omni.sidero.dev/disconnected` label. It is used only in the UI. We still remove `connected` label when the machine gets disconnected from Omni. Update the `MachineStatus` resource to also include power state of the machine. Then display it in the UI for the machines list. Introduce `POWERING_ON` stage in the cluster machine status. Although it doesn't cover the power on stage fully. It will show powering on only for a short period until the bare metal provider issues the power on. We can improve that in the follow-up PR when we start tracking powering on stage more precisely. Fixes: #774 Signed-off-by: Artem Chernyshev <[email protected]>
- Loading branch information
Showing
19 changed files
with
1,727 additions
and
1,457 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.