You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Define the device requirements for multi-node clusters #71
As a device vendor, I want the Margo to define the required functions devices must provide to fulfill Margo roles related to multi-node clusters. These roles include...
Cluster lead
Cluster worker
This release only includes same vendor lead and worker with compatible kubernetes versions.
Deliverables impacted (not required)
Open specification
Milestone (Not Required)
Add details - Desired milestone/snap-shot PMG wants to include.
The Margo community needs first to well define the Device management scope and priorities before assigning this requirement to a release. In this activity, a clear definition is required to highlight what Margo will care about and what not, in the context of cluster environment (suggestion to use terminology like "resiliency" , "high availability", instead of K8S specific terms like clusters)
After the scope being defined:
Define the device requirements (what functionality must exist on the device) for multi-node clusters (current one)
an new requirement is needed to describe the app requirements related cluster deployment. (app package)
an additional requirement is needed to describe the device capabilities related to clusters
suggestion : add agenda topic to SB workshop asking opinion on importance of support for "resiliency" , "high availability" deployment targets (aka clusters in K8S or "Docker Swarm" Mesos...)
Activity
ajcraig commentedon Jun 19, 2025
This was targeted to for PR2 to expand the device roles beyond the PR1 Standalone Cluster and Standalone Device.
Further clarification is needed:
bnieuwborg commentedon Aug 14, 2025
The Margo community needs first to well define the Device management scope and priorities before assigning this requirement to a release. In this activity, a clear definition is required to highlight what Margo will care about and what not, in the context of cluster environment (suggestion to use terminology like "resiliency" , "high availability", instead of K8S specific terms like clusters)
After the scope being defined:
suggestion : add agenda topic to SB workshop asking opinion on importance of support for "resiliency" , "high availability" deployment targets (aka clusters in K8S or "Docker Swarm" Mesos...)