This document describe how to build AGL instrument cluster with container integration.
Step1. Select Image type and target board
AGL IC container integration has various type. Developer need to choice which integration type. Those type show in table1.
Table 1. Integration type.
| No. | Type name | Detail of type | Required storage (SD card) size - board. | Required storage size-build. |
|---|---|---|---|---|
| 1 | Simple container host | This integration aim to core package definition for container host using LXC. This integration is not include demo package. This integration aim to define starting point for downstream product development. | 1G Byte | 150GByte |
| 2a | Instrument cluster with four demo IVI install to one partition. | This integration aim to get most simple integration with demo feature. This container runtime and management is constructed with LXC package only. On the other hand, it has limitation for supported use case. This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn drm lease and LXC container by developer. | 2GByte | 300GByte |
| 3a | Instrument cluster with demo IVI install to one by one partition. | This integration aim to get simple integration with demo feature. This container runtime and management is constructed with container management daemon with liblxc. This integration will improve to support many embedded use case. This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn and develop AGL IC container integration by developer. | 16GByte (Including pre-allocated partition for 3 guests.) | 300GByte |
| 3b | Instrument cluster with four demo IVI install to one by one partition. | This integration aim to get full demo integration with AGL demo IVI. This integration is extend from 3a integration. This integration support instrument cluster guest and four IVI guest (momi, qt, flutter, html5). This integration aim to use AGL demonstration in each event by developer. | 16GByte | 600GByte |
We recommend to choice 3a. It can extend to 3b.
AGL IC container integration supported two board. Those board show in table2.
Table2. Supported board.