Page History

...

• Playground Kanban "stand-up meeting": In-progress task status, major new items
• Fall  AMM
• Knowledge Layer Connector update: BMW want to give an update on their work on the Knowledge Layer components
• AoB

Knowledge Layer Sync topic input:

Minutes:

• Playground Kanban
  • Steve has fixed issue #57 (online doc ToC not rendered correctly).
  • Updates from BMW - see below
• Fall AMM
  • Steve and Haonan will discuss Knowledge Layer slides offline
• Knowledge Layer components
  • Andre reports that BMW have made good internal progress on engineering the knowledge layer components and wants to discuss how to progress publically in terms of PRs etc.
  • Steve suggests following:
    • 1st step would be concentrating on getting the Knowledge layer components public as the info layer ones currently are so we can all see what is being talked about. This could be in the existing PR or a new one if you prefer.
    • Commits can be added as you go to get early feedback. No need for "big bang" single push at the end of development.
    • With AMM coming that gives you some weeks to prepare.
  • Steve's non-exhaustive list of related topics to be discussed during and after this process as input:
    • Information Layer abstraction
      • data get/set limitations vs data tablet and higher level queries.
        • Need: Agree how to document current limitations and not limit research in higher level and faster queries.
      • database path consolidation for the various containers, e.g. VISS access vs information layer set need to coordinate (now) where to get the data in the DB
        
        • Need: out of the box components work together
    • Use cases for online documentation
      • Currently intended for more general abstracted documentation and guides that need a lot of cross-referencing, e.g. integration guides
        • Need: Add appropriate doc for the newly introduced features
    • Architecture communication / arch visualisation / C4 model
      • Need: Need arch view of the Playground and how the new features are integrated at different levels of abstraction to be able to discuss within the group and outside.
    • Docker images and packaging of CDSP Core building blocks
      • Pre-built images?
      • Need: Agree on how to handle the dockerisation of Core building blocks in a consistent manner.
  • Discussion:
    • Agreement that current naming of Knowledge and Info layer 'boxes' in current C4 Model are not correct (Steve just added them as placeholders).
      • Collectively need to come up with what is 'better'.
      • Haonan says that Knowledgebase would be traditional way from knowledge perspective but it is also perhaps a little outdated.
      • Ulf suggests "Knowledge Server" as starting point for KL part and both Haonan/Steve agree that is better. Steve changes diagram.
    • Andre happy to add appropriate online documentation
    • Docker
      • Andre wonders about flexibility in selecting docker containers to include when using docker compose.
      • Sebastian says as end user he would simply consume Dockerfiles and deploy with kubernates but sees desire for 'easy' starting point
      • Steve agrees balance needed between out of box experience and both flexibility and maintainability. Docker compose does not preclude someone from really doing some bespoke for themselves.
• Information Layer abstraction
  • data get/set limitations vs data tablet and higher level queries
  • database path consolidation for the various containers, e.g. VISS access vs information layer set.
• Use cases for online documentation
  • Currently intented for more general abstracted documentation and guides that need a lot of cross-referencing, e.g. integration guides
• Architecture communication / arch visualisation / C4 model
  • Clearly communicating options at different levels of abstraction
• Docker images and packaging of CDSP Core building blocks
  • Pre-built images

4th September 2024

Agenda:

...