Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/add maintenance steps #398

Closed
wants to merge 4 commits into from

Conversation

jneo8
Copy link

@jneo8 jneo8 commented Jan 9, 2025

  • Add steps to enable/disable maintenance
  • EnableHypervisorStep, RunWatcherHostMaintenanceStep, and RunWatcherWorkloadBalancingStep

blocked by: #397

@jneo8 jneo8 mentioned this pull request Jan 9, 2025
@jneo8 jneo8 force-pushed the feat/add-maintenance-steps branch from 5d44997 to dd789b3 Compare January 10, 2025 08:45
jneo8 added 4 commits January 13, 2025 10:55
- Add core watcher module
- Refactor guests_on_hypervisor
- fix/Read watcher configuration from clusterdb to build watcher client
- doc/Update guests_on_hypervisor func docstring
- doc/Add comment for TIMEOUT and TIMEOUT_INTERVAL variables
…her action

- Refactor: Replace timeout decorator by tenacity
- Fix: Raise exception on failed watcher action
- Add EnableHypervisorStep, RunWatcherHostMaintenanceStep, and RunWatcherWorkloadBalancingStep
@jneo8 jneo8 force-pushed the feat/add-maintenance-steps branch from dd789b3 to 13e055a Compare January 14, 2025 10:13
run_sync(self.jhelper.run_action(self.unit, self.model, "enable"))
except ActionFailedException as e:
LOG.debug(str(e))
return Result(ResultType.FAILED, "Failed to enable hypervisor unit")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add unit name in error message. Helps user not to bother about mapping unit name to node name.

f" | parameters: {action.input_parameters}\n"
)
question = ConfirmQuestion(
("Confirm to run operations for cluster:\n" f"{action_operation_msg}"),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update in Github Conversation first commit message box with the UX along with output.

Is the user will be prompted to accept the actions for every Step that contains has_prompts as True? In other words, user accepts the actions for Hypervisor maintenance using watcher once and then after some time for Storage related?

Do you have plan to add maintenance commands that list all actions required across hypervisor/k8s/microceph?
Do you have plan to add flag to proceed with maintenance without prompts once user has reviewed the actionplan in total?

@jneo8
Copy link
Author

jneo8 commented Jan 20, 2025

Move to #409

@jneo8 jneo8 closed this Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants