User Tools

Site Tools


agl-roadmap

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-roadmap [2020/02/13 15:07]
waltminer Revised SAT roadmap
agl-roadmap [2020/02/18 19:58]
SebD [2020 Roadmap/ Workplan from SAT]
Line 25: Line 25:
      * New reference board for 2020? Switch to RHSA board.      * New reference board for 2020? Switch to RHSA board.
      * Smartphone connectivity - no OS solution that allows integration of proprietary solutions such as CarPlay or Android Auto.  We do not have all of the components (video and audio especially) that are required for these integrations. What do we need to add?      * Smartphone connectivity - no OS solution that allows integration of proprietary solutions such as CarPlay or Android Auto.  We do not have all of the components (video and audio especially) that are required for these integrations. What do we need to add?
-     * Long-Term Stable updates+     * Long-Term Stable updates, proposal and agreement on a roadmap ot make each UCB components LTS
      * Improve collaboration with other projects to resolve many issues.ELISA,​ Yocto, OE, CIP      * Improve collaboration with other projects to resolve many issues.ELISA,​ Yocto, OE, CIP
      * Increase production readiness based on OEM and Tier One gap analysis of missing features in UCB.       * Increase production readiness based on OEM and Tier One gap analysis of missing features in UCB. 
        * Toyota code drop and other contributions from Tier One and OEM members        * Toyota code drop and other contributions from Tier One and OEM members
      * Increase QA and testing by increasing code coverage of our existing automated and manual tests      * Increase QA and testing by increasing code coverage of our existing automated and manual tests
 +     * Apis
 +       * Define an AGL APIs description format and implement command line tools to generates C/C++ code skeleton and JSON marshaling/​un-marshaling and API documentation (SPEC-1903)
 +     * Signaling
 +       * Implement a per-signal (or per-class) permission model
 +       * Define & agree on Key Performance Indicator to ensure QA validation
 +     * Vehicle to Cloud
 +       * Propose an identity model to manage local/​remote identity to enable smartphone cooperation etc
 +       * Add MQTT as native transport for AGL
 +     * Security / Application Framework
 +       * Finalize and improve token logic in order to support smartphone replication ​
 +       * Set-up Firewall (in relation with the App. Framework)
 +       * Implement Security Manager hosted and maintained by AGL
 +       * Turn on widget signing and security enforcement
 +       * App. Framework: allow customers extensions (plugable transport / security / protocol) and make sustainable LTS source code
 +       * add support for legacy applications (for example support AGL Java client) and add LXC/systemd container to run 3rd party or legacy apps. 
 +       * Implement a secured single port reverse proxy
 +       * Better handling of reconnections (add connection session persistence,​ keep alive, ...)
 +       * Move from widget (now deprecated by W3C) to RPM package format for AGL services and applications
 +       * Add support for Javascript and Python bindings
 +     * Power resource & boot management
 +       * Integrate a boot configuration manager to reduce boot time, monitor, select boot mode, ...
 +       * Leverage TPM, trusted apps to secure key AGL services (App Framework, Identity, ...)
 +       * Support sleep on RAM and cryogenics for apps
 +     * System
 +       * minimize AGL footprint to support small systems (eg. small ECUs running cluster or telematic AGL profile)
 +       * Add real time capabilities on APIs (priorities,​ predictable execution) to guarantee QoS
 +
  
  
Line 40: Line 67:
  
      * 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.
-     * Define the list of privileges we are going to enforce in the security model. ​   
-     * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} **Running apps not as root/ multi-user** 
-     * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​ 
      * 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      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Application signing and installation mechanism
Line 50: Line 74:
        * 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.
-     * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs) 
      * Improved Developer workflow for debugging apps including ​      * Improved Developer workflow for debugging apps including ​
        * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Round trip download/​debug/​fix/​download apps.         * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Round trip download/​debug/​fix/​download apps. 
-       * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} **Supervision daemon for apps and services for development mode.** Allows a developers to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder. 
  
-     * **Task manager app** to allow developers to see what tasks/​process are running in an app. Allow for killing apps.  ​ 
-       * Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them.  
      * Terminal app on home screen      * Terminal app on home screen
  
-     * Introduce resource widgets to share content/ resources across multiple apps.  
      * 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. 
-     * Connection glitches in multi-ECU system shall be properly handled. ​+     ​* ​[HH - partial support] ​Connection glitches in multi-ECU system shall be properly handled. ​
      * **XDS features**      * **XDS features**
        * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th)        * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th)
agl-roadmap.txt ยท Last modified: 2020/03/25 13:20 by waltminer