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. BIG TIME DISCLAIMER ABOUT WHAT IS MARGO SPECIFIED AND WHAT IS OUTSIDE SCOPE. THERE TO DEMO WHAT MARGO CAN DO, NOT DICTATE IMPLEMENTATION.

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. Description of the demo + links to associated specification sections related to the demo.
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.
   • Demo Video showing the architecture of the demonstration components.
   • REQ: Components to create the demonstration should be packages to be installed on an insfrastructure of choice. if the components that mimic Margo can be containerized it would be beneficial to do so. WOA for example.
   • High level overview videos describing the Margo concepts(A-Fair type Armand + Pragya) Maybe animated with spongebob.
   • Quick start guide and steps to enable quick construction on how to replicate Margo Ecosystem/Infrastructure locally
     • Mimicked Workload Orchestration Software
     • Local registries(includes config of platform to reach out ot local + configure a "remote" repository to test additional workloads through the flow)
     • How to produce a device that complies with a Margo Device Role.
       • Standalone Cluster role
         • Kubernetes
       • Standalone device role
         • Docker
     • Includes OTEL integration to show progress on that configuration. (land on a local collector could get a feel for pulling and utilizing. Fleet manager integration to collect from the device's.
   • 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:
  • Margo Release 1 Roadmap(WIP)
• 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

[stormc]

Seconding @abbottjd's comments, the vote is: Approval.

Additional note: This is a preview / pre-alpha / snapshot (*) release to gather early feedback from the margo adopter community to (re)align margo's direction with the community's vision of margo.

(*) naming is framing so we need to come to a naming consensus for the official release.

[hsinghcg]

• Approve Proposal

[pauldbrooks]

Rockwell Automation approves with comment:
While Kubernetes and Docker should be the short term focus, the architecture must be extensible to support many other workload approaches. This scope should not be interpreted to exclude other open or proprietary workloads.

[jjaswanson4]

Red Hat approves with comment:

We think the scope is very solid, and is focused enough on "let's ensure we can start deploying apps", which is necessary to show viability in the short term. Longer term, more clarity is desired.

[adamqiu-emerson]

Emerson approves with the following comment:
Margo's initial scope should continue to focus on core functionality, emphasizing a code-first approach and end-to-end deployment. This will accelerate feedback loops and enable rapid iteration.