-
Notifications
You must be signed in to change notification settings - Fork 9
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
RFC: Possibility to store operational issues to a machine #41
Comments
/cc @Gerrit91 @mwennrich @ulrichSchreiner WDYT ? |
Sorry, I do not really have a strong opinion about that. Only thing that comes to my mind is that there would be the opportunity to add this to |
i'm unsure about this feature. first it sounds good, but who creates this issues? and more important: how do you make sure that such issues are removed from the machine when it is resolved? does a machine with an issue mark this machine as defect or unusable? if this is not the case than after some time you will have machines with many issues and do not know if any of these issues is already fixed. |
Could potentially be done with a issue webhook in gitlab ?? |
Gitlab issues are freetext .... it will be hard to connect them to a specific machine-ID and do a specific REST-call when an issue event happens. |
@mwennrich have you some opinions here ? |
related: metal-stack/metal-hammer#17 |
During normal operations, it is sometimes the case that there are failures regarding a machine like:
It might be a good idea to track such issues by machine. To do so we could either:
open issues
field on the machineFor me it feels like add MachineIssue the right approach.
Then we can add the following
metalctl
command:And the other way round, machine listing will add a Sign to machines with issues:
The text was updated successfully, but these errors were encountered: