Page History

...

• A neutral playground to investigate internals of such data services. In the context of data-centric architectures for example.
• A neutral playground to investigate, illustrate and disseminate combining data services and the Covesa eco-system with other parts of the vehicle and off-board. To For example, to demonstrate how VSS data can be used with VISS for newcomers for example.
• Repeated use of shared terminology, patterns and tools leads to quicker understanding in discussions, shared costs in development and can lead to quicker outcomes.
  • Jump from 'what is the box' to 'how are we using the box' for example.

Success Factors

1. Newcomers to Covesa technology use the playground to accelerate their understanding of how the technology can be used. That could be a looking at a simple instance of how a VSS data server is combined with a VSS data store and queried using VISS. It could also be a more complex instance that combines components to illustrate a longer specific end to end use case, e.g. mobile to vehicle connection.
2. Internal groups within Covesa naturally use the logical concepts and the playground implementation in combination with other components to develop and disseminate ideas. This especially applies to the Data Architecture and Infrastructure pillar.
3. Supporting materials such as patterns, diagrams, cookbooks etc are adopted as useful assets within and outside Covesa, which in turn helps socialisation.

...

From a communication and community perspective it is important to maintain descriptions of the logical concepts. Discussion at a logical level allows different parties to collaborate on common concepts, whilst making different implementation decisions, e.g. in product/technology selection or system architecture for example. That however does not mean we need spend months in philosophical discussions before moving to implementation. Instead logical concepts (why, what) can be developed alongside implementation.

...

There is a parallel proposal within the Data Architecture group for documenting Covesa concepts such as design patterns, architectures and it proposed Howtos, that this could be used to publish such documents created by work from this proposal.

Central Data Service Playground

...

• Address two high level implementation needs, keeping in mind a path towards production where possible:
  1. Easy to develop: make it easy to build, modify and trial by providing an instance running on a host, e.g. using Docker container(s).
  2. Closer to production: the same base code should be deployable to systems closer to production, including on automotive hardware (or its simulation), e.g. Yocto, container orchestration, SOA etc.
• A path towards production can be helped by using production components, rather than overly simple substitutes, where it makes sense. For instance a particular scenario may use Kafka in a cloud connection.
• A generic code base for the basic building block should allow flexible compilation to meet those needs on x86 and ARM. The target for how it is used being a matter of deployment at a high level.
• Follow the OSS mantra of adopt where you can, extend if needed, create where necessary.

...

• As a starting point it is suggested that the Service could be realised as a basic building block combining VISS Data Server with highly functional VSS Data Store.
• As well as the mentioned flexibility in implementation, flexibility in use is also intended:
  • With some supporting documentation it could help meet the ongoing request from newcomers to the VSS eco-system as to how VSS can be used.
  • The Data Architecture group for instance has various topics it wishes to investigate related to data-centric architectures.
  • The playground can be used to investigate internals of such a service. For example, connecting VISS to medium and high speed data, or adding a protocol.
  • External connections with other systems may also be a focus. For example, how such a Service may help implement a particular touchpoint such as mobile.
• Details Further details can be found in the following sections.

...