Open djfjeff opened 2 years ago
/triage accepted /assign @fmuyassarov /kind feature
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.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
This is something that would still be useful to have.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/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.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/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.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale /help /good first issue
@Rozzii: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Any additional documentation would be good, I will move this to frozen, no need to always remove the stale label. /lifecycle frozen
I've created a diagram proposal in https://github.com/metal3-io/metal3-docs/pull/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.