User Tools

Site Tools


agl-sat-meetings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
agl-sat-meetings [2020/02/13 15:10]
waltminer
agl-sat-meetings [2020/03/26 13:58]
waltminer
Line 1: Line 1:
 ====== AGL System Architecture Team (SAT) Meetings ====== ====== AGL System Architecture Team (SAT) Meetings ======
  
-Meetings of the System Architecture Team are held every other Thursday at 14:00 UTC. The upcoming schedule can be found below. ​+Meetings of the System Architecture Team are held every other Thursday at 13:00 UTC. The upcoming schedule can be found below. ​
  
 Conference Information:​ Conference Information:​
Line 16: Line 16:
  
 ----- -----
 +
 +
 +
 +==== April 23, 2020 ====
 +Attendees: //Upcoming Meeting//
 +
 +
 +==== April 9, 2020 ====
 +Attendees: //Upcoming Meeting//
 +
 +
 +==== March 26, 2020 ====
 +Attendees: Walt, Jan-Simon, Scott, Dr. Yamaguchi, Ohiwa, Nomoto, Abe, Kusakabe, Haraki, Hosokawa, Stephane, Parth, Nishiguchi, Tanikawa
 +
 +   * 2020 Roadmap Review ​
 +     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM. 
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
 +
 +
 +[[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​
 +   * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​
 +   * 3/26 - Merged. ​
 +
 +   * Icefish final release
 +     * Done
 + 
 +   * SPEC-2927 - Window Manager for WAM
 +
 +   * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
 +     * 8/29 Panasonic is reviewing ​
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon. 
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG. 
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week. 
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko.  ​
 +     * 12/4 - Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday. ​
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP. 
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic. ​
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
 +     * 3/26 - BSP RFI responses to be reviewed. AB tentatively approved purchasing the boards pending the Qualcomm and BSP discussions. ​
 + 
 +   * Radio architecture and Tuner API - Denso Ten will release documentation for radio and tuner functions by the end of September. ​
 +     * 3/26 - Kusakabe-san prepared a draft document that will be reviewed during the Connectivity EG meeting next week. 
 +
 +   * LTS  ​
 +     * 9/26 (Berlin F2F)
 + * AI: identify base services. What is in core-image-minimal that is available in all profiles. ​
 +  * lifecycle
 +    * apps vs platform (which applications ​
 +    * 
 +  * API definition & documentation & Schema
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md
 +    * Follow-up on SAT
 +  * API versions
 +    * -> APPFW / Jose
 +
 +  * '​core'​ LTS vs. IVI or Cluster LTS
 +    * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
 +    * 1/16 - Added LTS to the SC agenda for February. ​
 +    * 3/26 - Tanikawa is working on this and will provided a verbal update. Will provide another update at the next SAT meeting, ​
 +
 +   * Toyota Code Drop
 +     * 10/10 
 +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC. 
 +     * 11/21 - 
 +     * Notes from SC meeting ​
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended.
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.  ​
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0. 
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}} ​
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG. 
 +     * 3/26 - Ohiwa-san can start to upload the code now that it has been approved internally. Code will be uploaded on Monday unless he cannot go to the office due to Coronavirus restrictions. ​
 + 
 + 
 +   * ELISA updates
 +     * ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​
 +     * ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel | here ]]
 +     * New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/​g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up. 
 +     * 3/26 - Dr. Yamaguchi provided an update on the ELISA AGL cooperation proposal. ​
 + 
 +
 +FOSSology/ License Review
 +   * So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year. 
 +   * 3/26 - Multiple issues blocking getting FOSSology server going, ​
 +
 +New Business:
 +
 +   * SPEC-3295 - Apply yocto metadata license file format to AGL layers. ​
 +   * New repository requests for POI (SPEC-3291 and SPEC-3293) ​
 +
 +
 +
 +==== March 12, 2020 ====
 +Attendees: Walt, Jan-Simon, Scott, Stephane, Li, Ohiwa, Kusakabe, Kurokawa, Tanikawa, Haraki, Abe, Hosokawa, Dr. Yamaguchi, Nomoto
 +
 +   * 2020 Roadmap Review ​
 +     * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM. 
 +     * Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]].
 +
 +
 +[[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​
 +   * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​
 +
 +   * Icefish final release
 +     * Being slowed down by issues with CI. 
 +     * Waiting for a fix from Igalia on the WAM issue reported by Scott on Tuesday (SPEC-3181). ​
 + 
 +   * SPEC-2927 - Window Manager for WAM
 +
 +   * RHSA RFQ - updated the RFQ document with comments. The revised version is {{:​eg-rhsa:​agl_referencehardware_rfq_v0.2.pdf|here}}.
 +     * 8/29 Panasonic is reviewing ​
 +     * 9/12 - Panasonic still in review. Sekine-san will check with Panasonic about EG review during the AMM in Monaco. ​
 +     * 9/26 - Still in review at Panasonic. Sekine-san expects a reply soon. 
 +     * 10/10 - Sekine-san thinks Panasonic will release the RFQ in time to be reviewed in Monte Carlo, Walt will be in Yokohama in November, We should plan a F2F meeting at that time with Panasonic and RHSA EG. 
 +     * 11/7 - SC to meet next week and make recommendation to AB. We will make sure that Panasonic and Mazda RHSA team members are invited to that portion of the SC meeting next week. 
 +     * 11/21 - SC meeting last week in Yokohama. Waiting on block diagram from Panasonic which was promised for two weeks (next week). There is a meeting next week in Tokyo to discuss further. There is a on-going discussion between Panasonic and Renesas about BSP.  Also will get a quote for creating the BSP from Konsulko.  ​
 +     * 12/4 - Block diagram [[ https://​wiki.automotivelinux.org/​_media/​eg-rhsa/​r-car_h3_reference_hardware_blockdiagram_20191126.pdf | uploaded to the wiki page]]. Will be reviewed at the steering committee on Monday/​Tuesday. ​
 +     * 12/19 - No update. Was reviewed by SC last week. Will forward and RFI to Konsulko for creating and maintaining the BSP. 
 +     * Panasonic to get agreement with Qualcomm to release firmware for the BT/Wifi chip. No update on this topic. ​
 +     * 1/16 - Panasonic and Qualcomm are talking at the executive level about licensing the WiFi and Bluetooth chip firmware using a click-thru license most likely. ​
 + 
 +   * Gap analysis - Denso Ten will release documentation for radio and tuner functions by the end of September. ​
 +     * 9/12 - document is 60% translated to english. Kusakabe will present an update at the dev call next week. 
 +     * 9/26 
 +       ​* ​ **Radio API review **
 +       * Sample API of Denso Ten released in staging/​documents
 +       * Goal is to refine the radio api with additional functions found in the review of above
 +       * focus on generic calls over hw specifics
 +       * Scott Murray will review the documents and make a proposal for extending the radio api for review in the connectivity call and during AMM
 +       * Lateron a definition is needed how the interface to the various implementations (hw+driver) can be done
 +     * 10/10
 +       * Kusakabe posted the API to Gerrit https://​git.automotivelinux.org/​staging/​documents/​log/?​h=sandbox/​kusakabe/​radio-api
 +       * Kusakabe to release additional APIs by the end of the month
 +       * Scott needs to review. Need some additional Tier 1 or OEM reviewers. ​
 +     * 11/7 - Scott has been blocked on higher priority tasks. Will bring this up to SC as an area for additional Tier One members to review the proposed API. 
 +     * 11/21 - No update. ​
 +     * 12/4 - No update. Further translations from Denso Ten may be available at the end of December. ​
 +     * 12/19 - No update
 +     * 1/16 - No update. Scott will start looking at it now that he is done with CES.  SPEC-1903 - IoT.bzh will provide a POC for the radio API.
 +
 +   * LTS  ​
 +     * 9/26 (Berlin F2F)
 + * AI: identify base services. What is in core-image-minimal that is available in all profiles. ​
 +  * lifecycle
 +    * apps vs platform (which applications ​
 +    * 
 +  * API definition & documentation & Schema
 +    * AI: iot.bzh will follow-up on https://​jira.automotivelinux.org/​browse/​SPEC-1903
 +    * e.g. what about new things like: https://​fuchsia.googlesource.com/​docs/​+/​ea2fce2874556205204d3ef70c60e25074dc7ffd/​development/​languages/​fidl/​tutorial.md
 +    * Follow-up on SAT
 +  * API versions
 +    * -> APPFW / Jose
 +
 +  * '​core'​ LTS vs. IVI or Cluster LTS
 +    * depends on changes required e.g. by IC 
 +  * 11/7 - 3 year Yocto LTS proposal was debated in Lyon last week, but no decision was made. No one was opposed to the proposal as it is written, but funding is a question. Proposal is to maintain OE Core, so it still leaves most of our user space and meta-openembedded as question marks for us.  ​
 +    * There were a number of talks last week in Lyon about using a combination of Debian/​Fedora/​CentOS for user space and Yocto for BSPs for LTS in embedded projects. ​
 +      * Stephane posted link for [[https://​wiki.centos.org/​Manuals/​ReleaseNotes/​CentOSStream CentOS Stream]] which is the CentOS plan for LTS and testing. ​
 +      * Will add to SC agenda for next week. 
 +    * 11/21 - SC did not get to this topic, Will be addressed at December meeting. ​
 +    * 12/5 - Following up next week. 
 +    * 1/16 - Added LTS to the SC agenda for February. ​
 +
 +   * Toyota Code Drop
 +     * 10/10 
 +       * No update. Will need some decisions about how we want APIs to be formatted based on LTS discussion. ​
 +       * Kusakabe-Can will meet with Ohiwa-san next week and provide some feedback to the AGL community,
 +     * 11/7 - Toyota documents are quite large. Were posted on Confluence. Ohiwa-san is working on splitting them up and providing header files. ​ Ohiwa-san will be in Yokohama next week to discuss the next steps with the SC. 
 +     * 11/21 - 
 +     * Notes from SC meeting ​
 +     * Discussed the need to take each of the API documents and deep dive the contents with the appropriate developers within the AGL community. Will need Toyota to do some analysis of the architectural/​ design gaps between AGL and their proposed code changes and work with the community to fill those gaps. For example, the “Peripheral API” document has a lot of details about CAN messaging but it is difficult to determine what the context of API is and how it fits into the overall architecture. There may be parts of it that are already covered by AGL. Suggestion is for Toyota to pick an API to focus on and develop the higher level context with the AGL community to figure out how to fit it into the existing structure. ​
 +     * Ohiwa-san is working on providing the context for the API documents. First task will be System Manager API in the System Service Document (see [[https://​confluence.automotivelinux.org/​display/​TC/​Documents | Confluence]] for more on the documents. ​
 +     * 12/4 - Ohiwa-san presented Persistent Data Manager (Backup Manager) use case ideas.  ​
 +       * Discussion on whether the existing AGL [[ https://​git.automotivelinux.org/​apps/​agl-service-data-persistence/​tree/​src/​persistence-binding.c |data persistence binder]] can be reused/ extended.
 +       * Discussion of whether the backed up data is in a Linux file system, a proprietary file system, or managed memory of some sort (battery backed RAM or flash). ​
 +       * Other requirements need to be documented that were discussed. Ohiwa-san will update and we will review further at the next SAT meeting.  ​
 +     * 12/19 - Ohiwa-san presented some further use cases for persistent storage involving shutdown then rapid restart while meeting the 2 second requirement for review camera after start up. Ohiwa-san will upload the document to the Toyota code drop Confluence page. https://​confluence.automotivelinux.org/​display/​TC/​Documents
 +     * 1/16 - New version of the specification was uploaded to Confluence last week. Code will be uploaded to gerrit in the next week or two. Will be licensed under Apache 2.0. 
 +     * 3/12 - Ohiwa-san showed a presentation on the latest status from Toyota.{{:​sat_meetings:​document_for_sat_20200312.pdf|latest status}} ​
 +     * Nomoto-san showed analysis of Bluetooth use cases. He will forward to the mail list or post in the meeting minutes, Detailed discussion will pick up in the Connectivity EG. 
 +
 +
 +   * Navi EG met last week with Momiyama-san and they will present a new architecture at the November SAT call. 
 +     * 11/7 - More discussion needed before Navi EG is ready to present the new architecture. ​
 +     * 11/21 - Navi EG presented an update last week in Yokohama. Need to get the document from Micware. ​
 + 
 + 
 +   * ELISA updates
 +     * ELISA and IC EG are recruiting AGL members to participate. The next F2F meeting for ELISA is in Brussel the Thursday and Friday before FOSDEM. Registration information can be found [[https://​elisa.tech/​announcement/​2019/​10/​17/​elisa-brussels-workshop-january30-31-2020/​ | here]] ​
 +     * ELISA groups.io page can be found [[https://​lists.elisa.tech/​g/​devel | here ]]
 +     * New ELISA development process subgroup has formed. See their [[ https://​lists.elisa.tech/​g/​devel/​topic/​please_join/​61718502?​p=,,,​20,​0,​0,​0::​recentpostdate%2Fsticky,,,​20,​2,​0,​61718502 | groups.io page]] for more information and to sign up. 
 + 
 +
 +FOSSology/ License Review
 +   * So far there has been no action taken on FOSSology reports. Dan brought up starting a new project to evaluate license file, conflicts etc. and funding someone to go do that work.  Will be brought up to AB at their next meeting.  ​
 +   * Open Chain reported that we have 320 different licenses. ​ How do we plan to collaborate with OpenChain?
 +   * Fujitsu has volunteered to do some work sorting out the licensing which will get started in the new year. 
 +
 +
 +New Business:
 +
 +   * Walt to send out info on the CIP / EILSA webinar scheduled for tomorrow, ​
 +   * Fujitsu wants to buy an i.MX8 board for testing, Scott recommended the [[ https://​www.nxp.com/​design/​development-boards/​i.mx-evaluation-and-development-boards/​evaluation-kit-for-the-i.mx-8m-applications-processor:​MCIMX8M-EVK | NXP i.Mx8 EVKB]]
 +
 +
  
 ==== February 13, 2020 ==== ==== February 13, 2020 ====
Line 23: Line 244:
    * 2020 Roadmap Review ​    * 2020 Roadmap Review ​
      * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM.       * Create Jira tickets for components that may be moved to AGL core and post a request for comments on the mail list.  To be reviewed at SAT F2F at the AMM. 
-     ​* ​+     ​* ​Each EG need to update [[ https://​wiki.automotivelinux.org/​agl-roadmap | Roadmap ]]. 
 + 
 [[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​ [[ https://​jira.automotivelinux.org/​browse/​SPEC-2538 | SPEC-2538]] - Remove support for multiple versions of widgets to be installed simultaneously. ​
    * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​    * 2/13 - Sandbox tested out and will be included in JJ release. Build option will be available for keeping multiple versions, ​
agl-sat-meetings.txt · Last modified: 2024/03/19 13:36 by wminer