Margo Preview Release 1 Scope: Intent/Deliverables/Future Scope

[ajcraig]

Purpose

The goal of this Issue is to establish the Margo Preview Release 1 scope. The scope snippet below covers the intent of the release, major deliverables, and future scope items. The goal of this issue is to gain approval on the proposed Preview Release 1 scope. Additional issues will be released for approval regarding the full scope.

Margo Preview Release 1 Intent

Margo Preview Release 1 (PR1) is a precursor release focusing on margo’s founding core concerns being interoperable application definition and deployment plus workload management. Preview Release 1 allows vendors to work with the Margo specification to start prototyping and exploring solutions. It is deliberately intended as a technical sneak preview release.

With Preview Release 1:

• Application vendors can start to see how to define and package their applications for deployment to Margo-compliant devices using either Helm or Docker Compose to cater for different Edge application scenarios.
• Device vendors can start to see what makes a device Margo-compliant and how to communicate with a Margo-compliant workload orchestration platform.
• Workload orchestration platform vendors can start to see how to manage, and monitor, workload application lifecycles.
  • This release will include Margo specification communication patterns for defining and deploying containerized workloads.
• Elicit feedback from the broader community by showing progress within the current community.

Focus Group Deliverables

Items below are set to be deliverables for the following focus groups: App Package Definition, Device Requirements, Observability, and Workload Management Interface.

1. Specification Document Snapshot Release supporting/augmenting the preview reference implementation
2. Preview/Beta Reference Implementation built for each major scope category
   • The intent is to gather feedback from the broader community with this preview to (re-)align the project’s direction to community needs.
   • Quick start guide on how to replicate Margo Ecosystem/Infrastructure locally
     • Mimicked Workload Orchestration Software
     • Local registries
     • How to produce a device that complies with a Margo Device Role.
       • Standalone Cluster role
         • Kubernetes
       • Standalone device role
         • Docker
   • Cohesive examples throughout specification
     • Applications / etc.

Note: Test and Compliance suite has been moved out of scope for this preview release. Intent is to include once we get close to the official release.

Future scope items can be found in the following location:

• Release 1 Project to see current backlog:
  • https://github.com/orgs/margo/projects/7
• Device Orchestration Topics:
  • Onboarding/Enrollment
  • Device Update Mechanism
  • Device Management Interface
    • Onboarding
  • Device Observability

Review/Approval Options:

@margo/approvers Please respond below and consolidate your company's response to a single reply. If additional information is needed to provide your response, please reach out.

Response Options:

• Approve Proposal
• Reject Proposal - Provide reasoning for rejection
• Abstain from Vote - No strong opinion either way

[effndc]

On behalf of Intel I am submitting an approval.

[abbottjd]

Some may be misunderstanding that agreeing to this scope definition in turn solidifies the documented decisions into the Margo spec and reference implementation. This is not how I have interpreted the intent, but may be useful to stress that the decisions within the PR1 scope are intended to solicit feedback from the community as soon as possible.

[abbottjd]

From ABB's perspective I approve this proposal to move forward with a preview release. It makes sense to use this as a first iteration to get more direct feedback and allow vendors to "try out" the Margo approach before we finalize in a specification release.

[tomcounihan]

Approve