How to Set Up Custom Groups
We need to override the default group configuration, this can be done in the device.json at the top level of your revision. To do so, first clone your device:
pvr clone https://pvr.pantahub.com/anibal/home_rpi64_latest
The device.json file has to look like this to accommodate the groups that we have identified in the previous post:
$ cd home_rpi64_latest
$ cat device.json
{
"disks": [...],
"groups": [
{
"description": "Development Containers that will not be included in production devices",
"name": "devtools",
"restart_policy": "container",
"status_goal": "STARTED",
"timeout": 10
},
{
"description": "The container that sets up the basic device network connectivity",
"name": "net",
"restart_policy": "system",
"status_goal": "READY",
"timeout": 10
},
{
"description": "Containers that will vary depending on the hardware we are running",
"name": "hw-specific",
"restart_policy": "system",
"status_goal": "READY",
"timeout": 10
},
{
"description": "Containers that will enable the communication between the device and the cloud",
"name": "cloud",
"restart_policy": "container",
"status_goal": "STARTED",
"timeout": 30
},
{
"description": "Containers that will provide the configuration user in interface",
"name": "ui",
"restart_policy": "condainer",
"status_goal": "STARTED",
"timeout": 30
},
{
"description": "3rd party or self-made application containers installable by the user",
"name": "app",
"restart_policy": "container",
"status_goal": "STARTED",
"timeout": 60
}
],
"volumes": {...}
}
Notice that we cannot post this new JSON yet, as the existing containers might be still pointing to the legacy groups. We will see how to solve that in further posts in this thread.