To enable existing solution providers to implement Margo constructs.
Margo Conformance Profiles
Feature description
The goal is to introduce a set of Conformance Profiles into the specification that will allow a larger portion of the industry adopt Margo concepts and take advantage of the Margo developer ecosystem. This would make it so a device or workload fleet manager could choose to implement the application conformance profile (where it makes use of the Margo application and packaging sheme) but not the management interface profile (where it implements the REST interfaces to support state seeking and capability reporting). This means that margo developers could still write and package the solution in a common way and allow the application conformance profile implementing device to use another control plane
Category
Provide adequate technical acceptance criteria(s) associated with this feature below:
The conformance profiles must enable implementation of "segments" of the Margo specification (such as applications) so they can be used independently or multiple conformance profiles can be implemented. When all available conformance profiles are completed it is a fully Margo compliant implementation.
Although not required, it is highly encouraged to provide feature use-cases below:
A company has an existing solution that uses a non REST based control plane to manage the device and applications on it. Providing an Applications Profile allows the application descriptions and packages built for Margo to be deployed onto these devices even though the control plane is not capable of REST.
Additional information
Create a set of Conformance Profiles allowing devices and Workload Fleet Managers to have different levels of Margo compliance. These levels are not mutually exclusive and can enable more platforms to take part in the Margo ecosystem while declaring the compliance profiles they implement. This list should remain small but may expand over time. Initially we should start with the following levels.
1.) Margo Applications: A WFM or device that implements this conformance profile indicates they use Margo's application packaging scheme
2.) Margo Management Interface: A WFM or device uses the Margo management interface (REST APIs) to enable capability and resource reporting, state seeking etc.
3.) Margo Identity: A WFM or device uses the Margo identity
What this enables is a platform (potentially device and WFM that are tightly integrated) that cannot make use of the Margo Management Interface to declare themselves as Conforming to Margo Applications so they can gain advantage from the Margo developer ecosystem and the Margo developer ecosystem can gain the ability to operate on their devices, but allow them to maintain their tightly integrated stance.
It is also possible that a WFM or device may not have the capabilities to leverage the Margo Identity services but can work with the applications and management interface. if this is the case they could choose implement the Margo Application and Margo Management Interface Conformance profiles.
Implementing these more flexible profiles is in line with many specification practices and opens up the ecosystem to a wider range of WFM and devices.
In future efforts there may be a desire to also have targeting in the application to say that it requires the identity conformance profile to be available, but at this point it is recommended to postpone that.
Notes from minimum scope definition exercise:
The minimum scope is support of the Application descriptors, manifest and packaging.
To enable existing solution providers to implement Margo constructs.
Margo Conformance Profiles
Feature description
The goal is to introduce a set of Conformance Profiles into the specification that will allow a larger portion of the industry adopt Margo concepts and take advantage of the Margo developer ecosystem. This would make it so a device or workload fleet manager could choose to implement the application conformance profile (where it makes use of the Margo application and packaging sheme) but not the management interface profile (where it implements the REST interfaces to support state seeking and capability reporting). This means that margo developers could still write and package the solution in a common way and allow the application conformance profile implementing device to use another control plane
Category
Provide adequate technical acceptance criteria(s) associated with this feature below:
The conformance profiles must enable implementation of "segments" of the Margo specification (such as applications) so they can be used independently or multiple conformance profiles can be implemented. When all available conformance profiles are completed it is a fully Margo compliant implementation.
Although not required, it is highly encouraged to provide feature use-cases below:
A company has an existing solution that uses a non REST based control plane to manage the device and applications on it. Providing an Applications Profile allows the application descriptions and packages built for Margo to be deployed onto these devices even though the control plane is not capable of REST.
Additional information
Create a set of Conformance Profiles allowing devices and Workload Fleet Managers to have different levels of Margo compliance. These levels are not mutually exclusive and can enable more platforms to take part in the Margo ecosystem while declaring the compliance profiles they implement. This list should remain small but may expand over time. Initially we should start with the following levels.
1.) Margo Applications: A WFM or device that implements this conformance profile indicates they use Margo's application packaging scheme
2.) Margo Management Interface: A WFM or device uses the Margo management interface (REST APIs) to enable capability and resource reporting, state seeking etc.
3.) Margo Identity: A WFM or device uses the Margo identity
What this enables is a platform (potentially device and WFM that are tightly integrated) that cannot make use of the Margo Management Interface to declare themselves as Conforming to Margo Applications so they can gain advantage from the Margo developer ecosystem and the Margo developer ecosystem can gain the ability to operate on their devices, but allow them to maintain their tightly integrated stance.
It is also possible that a WFM or device may not have the capabilities to leverage the Margo Identity services but can work with the applications and management interface. if this is the case they could choose implement the Margo Application and Margo Management Interface Conformance profiles.
Implementing these more flexible profiles is in line with many specification practices and opens up the ecosystem to a wider range of WFM and devices.
In future efforts there may be a desire to also have targeting in the application to say that it requires the identity conformance profile to be available, but at this point it is recommended to postpone that.
Notes from minimum scope definition exercise:
The minimum scope is support of the Application descriptors, manifest and packaging.