- 25 Feb, 2022 1 commit
-
-
Ophélie Gagnard authored
-
- 24 Feb, 2022 1 commit
-
-
Ophélie Gagnard authored
The scripts do everything until the first run of buildout (actual run, not just bootstraping).
-
- 11 Feb, 2022 1 commit
-
-
Julien Muchembled authored
-
- 07 Feb, 2022 2 commits
-
-
Levin Zimmermann authored
Previously it only worked with Debian 10. This commit reflects the removal of the apt package 'python-pip' in Debian 11 and the change of the i2c bus number.
-
Levin Zimmermann authored
There were still two issues which are solved with this commit: 1. Previously the firewall prevented the installation of Fluentd (because no connection via http/https was possible). 2. Previously the sensor couldn't send data to the IoT gateway ( the opened port wasn't sufficient).
-
- 11 Jan, 2022 30 commits
-
-
Levin Zimmermann authored
When importing the slapos playbook after running re6stnet-install role, the user defined computer_name will be ignored and will be overridden by 'set_facts', line 16 in re6stnet-install/tasks/main.yml. Therefore the slapos install role is directly called (instead of importing the playbook) which seems to solve the issue.
-
Levin Zimmermann authored
-
Levin Zimmermann authored
(due to activated firewall)
-
Levin Zimmermann authored
-
Levin Zimmermann authored
(wrong indentation)
-
Levin Zimmermann authored
-
Levin Zimmermann authored
(wasn't possible because of too restrictive ipv6 firewall)
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
Add restrictive firewall settings to avoid any security risk.
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
Bug appeared due to wrong pip version. Therefore the version has been set explicitly.
-
Levin Zimmermann authored
Now the Python script name is consistent with the file name in the Fluentd config file as described in the learning track.
-
levinericzimmermann authored
Should be installed via rapid.space panel.
-
Levin Zimmermann authored
-
Levin Zimmermann authored
Previously it failed because setuptools wasn't installed.
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
Replaced 'computer_name' with 'computer_id'. Previously I confused both. Now the user has to enter the respective computer reference.
-
Levin Zimmermann authored
-
levinericzimmermann authored
It won't run in an issue anymore if the file already exists.
-
levinericzimmermann authored
Fluentd couldn't be installed because we first have to configure the SlapOS client via `slapos configure client` before being able to use `slapos console` (to supply and request Fluentd from a Python script).
-
Levin Zimmermann authored
-
Levin Zimmermann authored
In the Wendelin learning track this permission is granted to the user via "chgrp SLAPUSER /dev/i2c-3". Because we don't know the particular slapuser we have to add the permission to all users of the slapsoft group. Because /sys/bus/i2c/devices/i2c-3 is a virtual directory and we want to make sure that even after rebooting or unplugging / replugging of the sensor the permission is still granted udev rules have been added.
-
Levin Zimmermann authored
-
Levin Zimmermann authored
-
Levin Zimmermann authored
Initial commit for adding automatic preperation of Olimex boards as an IoT Gateway and for a Sensor to send data to Wendelin (see https://wendelin.nexedi.com/wendelin-Learning.Track/wendelin-Tutorial.Setup.Sensor.IOTGateway/WebPage_viewAsWeb ).
-
- 05 Jan, 2022 1 commit
-
-
Joanne Hugé authored
-
- 27 Dec, 2021 2 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
Since tests are launched inside namespace, we don't have SUID ping available anymore so we explicitely allow all users to do ping. Please note that this works for both IPv4 and IPv6 despite the name. See nexedi/slapos!1107 (comment 148968) for more information.
-
- 23 Dec, 2021 1 commit
-
-
root authored
While bootstraping a host, the network can be in unknown state, and a lot of tasks depend on the network, thus make sure that network is available. By extracting the hostname task to vm-bootstrap-hostname it's possible to setup it as a dependency role for vm-bootstrap, before package role, which depends on the network setup.
-
- 22 Dec, 2021 1 commit
-
-
Łukasz Nowak authored
-