JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Information related to the non-differentiating parts of deploying of VSC defined functions/capabilities/services in containers.
Possible examples might include:
At the time of writing this could be considered an ancillary topic to 'VSC Core' which defines the core API model of those functions.
Discussion in the group lead to a request for Renesas/Epam to make a container deployment definition proposal as a starting point. A proposal based on the open definition of containers taking the OCI standards as a starting point was created, with an example of how it might be integrated into a production system. This proposal was presented in the 4/6/22 meeting covering four broad areas:
Meeting video:
Proposal slides:
As discussed in the scope there is a need for open standardisation of various aspects of deploying a VSC defined function. These can be tracked in more detail in this section.
Please add topics to the list below by adding a title and summary description. Topics can then be expanded upon in a sub-section or sub-page as needed.
Rather than repeat it for each topic there is a general working assumption that collaboration on non-differentiating parts is beneficial for interoperability, open marketplaces and avoidance of fragmentation.
The OCI container runtime specification has somewhat of a cloud focus, for example concentrating on network port connections, which lacks some controls typically required in embedded applications that has more diverse IP in h/w. Standardisation of the missing controls and their definition is therefore beneficial. Controls should be upstreamed where possible.
Examples can be found in VSC PR #39