Skip to content

[Story: ] As a Margo Device Vendor and WFM Vendor, I would like to use the device constraints, labels and selectors to target specific runtimes #369

Description

@nilanjan-samajdar

Description

As a Margo WFM Vendor, the WFM needs to store the attributes defined in the Device Capabilities for each Device in the local database

As a Margo WFM Vendor, the WFM MAY interpret the constraints, selector properties and labels in the AppDescription to qualify the target devices

  • Design a module in the Sandbox WFM as a provider for device-selector
  • Interpret the constraints, selector properties and labels according to the rules provided in the specification
  • Filter the list of available devices and their capabilities, based on these properties

as a Margo device Vendor, the WFM Agent needs to send the resource constraints, labels and other capabilities.

  • These properties should be read from the WFM Agent configuration file, as JSON attributes
  • These values need to be reported in the Device Capabilities update API to the WFM

Raised by (email-id)

nilanjan.samajdar@capgemini.com

Type of Story

Implementation

Related product requirements

margo/specification#203

Definition of Done

The required technical documentation should be updated
In case of any prototyping activity, the evaluation, design and outcomes need to be documented
API updates need to be updated in swagger (or other) files
Test automation should be done to demonstrate the use-case
Code and documentation should be pulled into the release branch and the pull-request approved by the TWG

Estimated Story-points

15

Impacted artifacts

  • API Documentation (Swagger)
  • User Docmentation
  • Reference Implementation Code
  • Test Automation

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions