-
Notifications
You must be signed in to change notification settings - Fork 8
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
Margo Management Interface - Initial Construction/Proposal #19
Conversation
Signed-off-by: Armand Craig <[email protected]>
Signed-off-by: Armand Craig <[email protected]>
system-design/orchestration/workload/device-capability-reporting.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/device-capability-reporting.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/device-capability-reporting.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/device-capability-reporting.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/device-capability-reporting.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-management-interface-breakdown.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-management-interface-breakdown.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Philip Presson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many Thanks for this very good contribution, Armand.
I only had a bit of difficulty reading, as the reading order is not quite clear yet.
Following todays call's discussion, I think the abstraction of the API definition could be possible: (1) defining all messages (YAMLs) in a separate spec section, and (2) defining how the messages are exchanged in specific "protocol bindings" sections (e.g., for HTTP REST or WASM or CoAP or ...).
system-design/margo-api-reference/workload-api/desired-state-api/desired-state.md
Outdated
Show resolved
Hide resolved
system-design/margo-api-reference/workload-api/desired-state-api/desired-state.md
Outdated
Show resolved
Hide resolved
system-design/margo-api-reference/workload-api/device-api/device-capabilities.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Outdated
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Show resolved
Hide resolved
system-design/margo-api-reference/workload-api/desired-state-api/desired-state.md
Show resolved
Hide resolved
system-design/orchestration/workload/workload-management-interface-breakdown.md
Show resolved
Hide resolved
system-design/margo-api-reference/workload-api/onboarding-api/rootca-download.md
Show resolved
Hide resolved
system-design/margo-api-reference/workload-api/onboarding-api/device-onboarding.md
Show resolved
Hide resolved
system-design/orchestration/workload/workload-orchestration-edge-onboarding.md
Show resolved
Hide resolved
Signed-off-by: Armand Craig <[email protected]>
Signed-off-by: Armand Craig <[email protected]>
Description
Initial Contribution towards defining the Margo Management Interface.
Issues Addressed
List and link all the issues addressed by this PR.
Change Type
Please select the relevant options:
Checklist