-
Notifications
You must be signed in to change notification settings - Fork 113
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
User-guide: add diagram to describe the baremetal inspection/provision workflow #258
Comments
/triage accepted The community has accepted the proposal for a sequence diagram related to inspection/provision workflow. |
@djfjeff we will just need to agree with the community on the common tool to draw diagrams, which hopefully will be decided by the next week's community meeting. And then I can submit a patch with the state diagram. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale This is something that would still be useful to have. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale This is something that would still be useful to have. Is there any progress made on this? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale This is something that would still be useful to have. Is there any progress made on this? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
@Rozzii: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Any additional documentation would be good, I will move this to frozen, no need to always remove the stale label. |
I've created a diagram proposal in #354 |
/lifecycle frozen |
/unassign |
Having a diagram to explain the inspection/provision workflow for Metal3 (similar to https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/bare_metal_provisioning/index#the-bare-metal-provisioning-service) would greatly help understand how it works.
Also, a diagram will help understand what part to troubleshoot when an issue arise in the workflow.
The text was updated successfully, but these errors were encountered: