8000 Define standard format and content to describe a Margo device's capabilities · Issue #97 · margo/specification · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Define standard format and content to describe a Margo device's capabilities #97
Open
0 of 1 issue completed
Open
@ajcraig

Description

@ajcraig

Provide feature description below:

Goal: Device owners within Margo produce unique devices that need to be matched with compatible applications within the Workload Fleet Manager. To accomplish this, Margo needs to standardize on how the device owner provides information regarding it's capabilities.

Provide adequate technical acceptance criteria(s) associated with this feature below:

  • Defined format, schema, and content to describe the capabilities
  • Must be compatible with the Management Interface between WFM and Device
    • Transported securely over technology choice for that feature(needs linked / associated with)
  • Must utilize similar formats to the Application description file and it's required edge device resources.
    • This enables the WFM to quickly compare the two and provide user with a list of compatible edge applications.
  • MUST include the following information regarding the device:
    • resources (RAM / CPU / CPU Arch / Storage / Interface details / Peripheral details
  • It is up to the Device Owner to maintain the device capabilities information and inform the associated WFM of any changes that impact the current or future Applications from running on the device.
  • Example reference device and it's capabilities. Shall be included in the reference device and edge to cloud interface.

Although not required, it is highly encouraged to provide feature use-cases below:

  • Describe the device's capabilities
  • Inform the WFM of any changes if they occur to ensure no interruptions in operations
  • Ability to enable filtering within the WFM for compatible applications the user can deploy to the edge device.

Additional information

No response

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0