This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
agl-roadmap [2020/02/20 00:18] khosokawa [From Graphics EG] |
agl-roadmap [2021/02/24 14:34] waltminer |
||
---|---|---|---|
Line 62: | Line 62: | ||
==== From App FW and Security EG ==== | ==== From App FW and Security EG ==== | ||
- | * **HTML5 apps** | + | * Updated 24 Feb 2021 |
- | * HTML5 home screen | + | * Open questions for IVI PR effort |
- | * Chromium | + | * Continued use of systemd |
+ | * Linux Security Module for AGL (SMACK, SELinux, AppArmor, or none). None implies leaving the LSM to the product developer. Choosing one effectively locks in the Product developer to a solution. | ||
+ | * API mechanism. Continue to use OpenAPI or change to a different mechanism for platform services. Ideally we have an IDL that autogenerates the API code. (grpc, OpenAPI, or another) | ||
+ | * Long-term use of Qt | ||
+ | * IPC should be defined and selected. | ||
* Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | ||
* Changes necessary at binder level for V2C (SSL transport) | * Changes necessary at binder level for V2C (SSL transport) | ||
- | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Application signing and installation mechanism | + | * App Signing and Installation Mechanism |
- | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} Mechanism for checking signature is in place. | + | |
- | * Require all apps to be signed in GG | + | |
* Developer workflow is needed for managing keys | * Developer workflow is needed for managing keys | ||
- | * Development mode and Production mode for app management | + | * Development mode and Production mode for app management |
* Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | ||
- | * Improved Developer workflow for debugging apps including | + | |
- | * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Round trip download/debug/fix/download apps. | + | |
- | + | ||
- | * Terminal app on home screen | + | |
* App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | ||
* App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | ||
* App Framework binder communications shall be able to manage return from sleep mode. | * App Framework binder communications shall be able to manage return from sleep mode. | ||
- | * [HH - partial support] Connection glitches in multi-ECU system shall be properly handled. | ||
- | * **XDS features** | ||
- | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th) | ||
- | * Board console/terminal integration within XDS dashboard | ||
- | * Documentation improvement of debug section | ||
- | * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v6.0.0 - targeted release date: ALS (2018 June 20th) | ||
- | * Monitoring integration | ||
- | * v7.0.0 | ||
- | * Improved development cycle (based on partial Widget installation) | ||
- | * First step to support package manager for SDKs (Yomo) | ||
- | * **GG Priorities for App FW** | + | * App Life Cycle |
* Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | ||
* Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | * Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | ||
* Kill apps individually from life cycle manager | * Kill apps individually from life cycle manager | ||
* Need to define state diagram for app life cycle | * Need to define state diagram for app life cycle | ||
- | + | ||
- | * **HTML5 app support as necessary** | + | |
- | * Multi-user use case | + | |
* API for abstraction of hardware mechanism for signing apps, packages, etc. | * API for abstraction of hardware mechanism for signing apps, packages, etc. | ||
- | * Headless/ Telematics use case | + | * //Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms.// |
- | * Unit testing for app framework | + | * //Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]// |
- | * Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms. | + | |
- | * Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]] | + | |
* Allow keys to be changed by the device developers - git repo and recipe for keys | * Allow keys to be changed by the device developers - git repo and recipe for keys | ||
* Library (or binding) to plug in key management to the app FW. | * Library (or binding) to plug in key management to the app FW. | ||
Line 111: | Line 95: | ||
* Sign at build time in AGL CI system with a check at run time | * Sign at build time in AGL CI system with a check at run time | ||
+ | * **Web Apps/ HTML 5** | ||
+ | * Upstream Chromium Webview the API required by Web Application Manager | ||
+ | * Simplify the communication between Chromium and WAM | ||
+ | * Make WAM upstream independent of WebOSE Chromium (use baseline Chromium for easier maintence) | ||
+ | * Integration between WAM and the new Window Manager | ||
+ | * Web apps - Complete the integration with the new security model | ||
+ | * Web Apps - Improve application life cycle | ||
+ | * Web Apps - Support for containerization of the HMTL5 demo platform | ||
+ | * Web Apps - Improvements on the demo-webapp libraries for theming and websockets integration | ||
+ | * Additional demo apps | ||
==== From Graphics EG ==== | ==== From Graphics EG ==== | ||
- | Updated 20 Feb 2020 | + | Updated 29 Jul 2020 |
Our responsibilities have been almost completed in 2019. Our individual activities are not planned for next year. | Our responsibilities have been almost completed in 2019. Our individual activities are not planned for next year. | ||
Line 119: | Line 113: | ||
* Graphic | * Graphic | ||
* **Finish Window Manager and Homescreen work** | * **Finish Window Manager and Homescreen work** | ||
- | * Home Screen API / service | + | * Home Screen API / service -Complete for JJ |
- | * UI for Qt | + | * UI for Qt - Complete for JJ |
- | * UI for HTML5 | + | * UI for HTML5 - in-flight for JJ |
* High level API for virtual keyboard in english and Japanese | * High level API for virtual keyboard in english and Japanese | ||
* Pop-up support | * Pop-up support | ||
Line 195: | Line 189: | ||
==== From Virtualization EG ==== | ==== From Virtualization EG ==== | ||
+ | * VirtIO Porting | ||
+ | * Add VirtIO frontend (OASIS v1.1) to AGL | ||
+ | * Create documents to illustrate how to enable VirtIO | ||
+ | * Add VirtIO support and provide reference implementation on AGL reference hardware. | ||
+ | * EG Demo in ALS | ||
* AGL virtualization support (HOST) | * AGL virtualization support (HOST) | ||
* Add support for open-source hypervisors in meta-egvirt for both ARM and Intel AGL platforms. In this way, at compilation time it will be possible to select the hypervisor to use | * Add support for open-source hypervisors in meta-egvirt for both ARM and Intel AGL platforms. In this way, at compilation time it will be possible to select the hypervisor to use | ||
Line 210: | Line 209: | ||
* VMs/AGL profiles communication | * VMs/AGL profiles communication | ||
* define, design and develop a common API to enable communication/interaction between different VMs/AGL profiles | * define, design and develop a common API to enable communication/interaction between different VMs/AGL profiles | ||
- | * CES2019 demonstrator integration | ||
- | * include virtualization in the CES2019 demo, in a way that all the new features developed in 2018 are demonstrated | ||
- | * showcase at least two operating systems running concurrently (e.g., two AGL profiles), interacting and exchanging data with each other | ||