recordevolution/reswarmos

A small, customized host operating system for IoT devices meeting the needs of Reswarm

reswarmos's Issues

Wifi not online after Raspi restart

Even though a wifi is entered it does not connect on boot. I have to plug in a LAN cable to get connection. Only then it switches to wifi.

On Wednsday I have a product presentation in front of two team leaders and others. This could decide the fate of Record Evolution in Conti.

connectivity: wifi not activated after LTE unplug

1. The Raspi3 is on wifi
2. Plug in LTE
3. Restart wifi using the device view in Reswarm
4. networkmanager seems to switch to LTE
5. unplug LTE

Device never comes online again.

After repower it does.

ReswarmOS layer

use any "base" image, like i.a. ubuntu, Raspbian, arch, manjaro and turn it into a Reswarm(OS) compatible image by adding the "Reswarm layer" including addition of required dependencies, setup of services, etc.

Prepare an image for use as virtual machine in the cloud

A version has to be prepared for intel/amd.

See here what to take care of to use a custom image as the boot disk for gcloud instance:

https://cloud.google.com/compute/docs/import/import-existing-image?_ga=2.186626336.-867078282.1597174099#create_image_file

I created a bucket for holding the reswarm images already https://console.cloud.google.com/storage/browser/reswarmos;tab=objects?project=record-1283&prefix=&forceOnObjectsSortingFiltering=false

sshd configuration

employ security hardening configuration options to sshd_config by:

• no root login
  -allow login only by users configured
• allow login only on local subnet
• etc.

Reagent management daemon

integrate Reagent management daemon

container build

set up a docker container as environment for building the buildroot image

Pi zero image

add image configured for Pi zero

user and groups

set up proper user and groups, i.e. custom user including its own group, add custom user to sudoer list

interactive login

transition to support both Pi3 and Pi4 broke the interactive login (keyboard + screen) in commit d628776

reswarm user

create unix system user on first boot corresponding to Reswarm user the device belongs to

redesign OS network management

• switch WiFi automatically
• add WiFi (SSID/credentials) anytime/anywhere
• support mobile network/LTE/GPRS
• ... etc.
  related to RecordEvolution/DeviceManagementAgent#28

shell dashboard

provide some shell dashboard (e.g. triggered by motd.sh) showing:

• network status
• memory/disk/device status, free disk space
• service status
• ReswarmOS version/update status

reagent cgroup for mem,cpu usage

reswarm os updater

implement update mechanism to avoid the need for reflashing a device with latest version of reswarmOS

initial boot resizing

fix unstable resizing/repartitioning on Pi3 during first boot

prioritize reagent network usage

especially in low bandwidth scenarios the ping pong should have high priority.

https://superuser.com/questions/309063/how-can-i-prioritise-network-bandwidth-on-a-per-application-basis

related to RecordEvolution/DeviceManagementAgent#35

restructure repo

clean up/simplify structure of repository focusing on buildroot

list of boards

compile list of interesting boards to be targeted

dtparam=spi=on in config.txt

Pi 3 image

add image configuration for Raspberry Pi 3

update bundle certificate

avoid trying to install unverified update bundle because of expired certificate by either:

• use certificate with unlimited validity ?! (=> no, probably not)
• renew certificate during build/install process (only possible as long as certificate in charge on device is valid !?)
• daemon on device to renew and issue new certificate!!

long terminal text doesn't wrap properly and makes second line unreadable

Seems to be like this on multiple terminal apps, (default mac one and iterm2)
I'm not 100% sure if this is OS related? Feel free to close if it isn't.

Just something I noticed while typing/copying long commands:
Example I used:
sudo ./reagent-linux-arm-7 -config demo_demo_swarm_TestDevice.reswarm -logFile /home/ruben/reagent.log -appsDirectory /home/ruben -debug

Result in terminal:

vim config

for every user provide default .vimrc config

automatic switching of WiFi

automatically switch between know (preconfigured) WiFi networks depending on availability, signal strength and range.

Devices /dev/i2c are not mounted

the required parameters are set in the config.txt, but the devices are not mounted.

Banana Pi/Orange Pi support

rootfs resizing

during very first boot perform rootfs resizing to adapt to overall disk size

Create a custom ReswarmOS builder front end.

Create a web front end that allows users to customize ReswarmOS for their purposes.

In a web frontend, they should

1. Choose the CPU
2. The desired drivers from a list
3. Click "create ReswarmOS"

interactive terminal (with HDMI and USB keyboard) does not seems to work or is disabled

Version 0.2.9 in this case
To be able to properly debug things like e.g. 'LTE stick without WiFi' it's necessary that this works
In general needed for testing and debugging in environments without any (W)LAN connection

NVIDIA Jetson AGX Xavier support

setup 'reagent' user

set up 'reagent' user with root privileges (instead of using root user) that runs the reagent for better customization of

• process priorities
• traffic control
• permissions

fake-hwclock

employ fake hardware clock to provide approximately correct timestamp during early boot process

config.txt CAN module

dtoverlay=mcp2515-can0

GPS app not working with new ReswarmOS

Very important, because this is one of the apps we are using in the conti NVH use case.
It can not identify the GPS modem.

I am testing with https://studio.record-evolution.com/de/RecordEvolution/swarms/Lab/devices/device/Auto_Marko5

it has the SIM7600 HAT. I did not change anything else but the new ReswarmOS

container overview

provide overview over running containers on login

Test/Fix latest version on Pi0w

make latest version work/adjust to Pi0w

bluetooth support

Bluetooth is currently not setup, and not accessible/usable from within Docker
Not really urgent, would currently only be useful for hobby projects 😋

Device does not come online after clicking restart in device-view

... while LAN cable is plugged in.

Not sure if this is agent or ReswarmOS related.

After repowering the Raspi it came online.

upgrade docker version to 20.10.6 (EOF error)

This would fix the EOF error we currently experience with the current Docker version of ReswarmOS

Example of bug:

sync time and fix clock (ntpd)

enable proper hostname resolution on local network

use u-boot as bootloader

most of the updating frameworks (including RAUC, ostree) rely on a specific bootloader like i.a. u-boot

provide firewall (e.g. ufw) tools

LTE device quirk

Setup:

• The device has a working WLAN connection or has an Ethernet cable plugged in
• An LTE device is plugged in, and is recognized by NetworkManager as 'connected'
  • However: The LTE device has no data left or has no reception

Problem:
It seems like the NetworkManager does not consider switching over to another interface since it assumes that when the stick is 'connected', it also has internet access
This results in, in this case, the agent unable to connect to RESWARM even though it is has a working Ethernet/WLAN connection

Unplugging the stick in this situation, forces the NetworkManager to switch to Ethernet or WLAN, and makes the agent come back online.

Ideal way this is solved:
The NetworkManager always uses an Ethernet or WLAN connection over the LTE device OR It is somehow detected if the stick has no service or has run out of data (if there's no valid connection) and the traffic is passed to any other available interface.

Possible solution:
Maybe the priority settings in the NetworkManager config can resolve this issue.
This would be resolved if the NetworkManager always switches over to either Ethernet or WLAN whenever that interface is available and connected.

Control docker daemon resource usage

reference: https://docs.docker.com/engine/reference/commandline/dockerd/

Add this to the docker daemon config

{
    "max-concurrent-downloads": 3,
    "max-concurrent-uploads": 5,
    "cpu-rt-period": 100000,
    "cpu-rt-runtime": 95000
}

Explanation for CPU config: https://www.kernel.org/doc/Documentation/scheduler/sched-rt-group.txt

So if I understand correctly it will reserve 5% CPU for non docker related tasks and is responsive at 100ms. (The params are to be given in microseconds)

NOOS fails to restart

successfully set up and first time started device does not come up again after restart

Access dynamically plugged USB devices in docker

Currently, a USB device is not accessible if plugged into an existing container.

config in BOOT partition

all configuration must be done with configuration files in the boot (FAT32) partition since this is the only one that is also supported by Windows and macOS

docker insecure registries

setup docker insecure registries in /etc/docker/daemon.json and add any configured insecure regs provided in a reswarm file