- 05 Dec, 2023 1 commit
-
-
Jérome Perrin authored
See merge request nexedi/slapos!1489
-
- 04 Dec, 2023 18 commits
-
-
Thomas Gambier authored
See merge request nexedi/slapos!1457
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Jérome Perrin authored
There are more recent versions, but they don't use pyproject.toml for metadata. Here we want a version with python3.11 support
-
Jérome Perrin authored
-
Jérome Perrin authored
This comes with a patch because the setup.py does not have version, which is not supported with our old tooling.
-
Jérome Perrin authored
This section is just for setup, it does not make sense to generate scripts here and it cause errors when another section uses the same technique.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Note that we don't use 3 yet because nexedi/pygolang@6446a0be
-
Thomas Gambier authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Webrunner was using this and it's natural for users coming from slaprunner to find slapos wrapper in ~/bin/slapos, but where theia is very incompatible is that ~/bin/sla[TAB] will another slapos-standalone which will conflict with the one from theia.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 01 Dec, 2023 3 commits
-
-
Julien Muchembled authored
Even if 'sed -i' is not posix and we should not use system sed this way: - even busybox supports this option - we already use it in so many other places that it does not make sense to to impose ourselves such extra dependency If we plan to fix all 'sed -i', alternatives to [sed] are: - patch - 'perl -pi -e' (perl is already built for openssl) And we should first have a mechanism to prevent misuse of system sed.
-
Kirill Smelkov authored
Going 0.139 -> 0.140 introduces the following changes: nexedi/slapos.toolbox@0.139...0.140 Test results: https://erp5js.nexedi.net/#/test_result_module/20231130-F8B9BE8D erp5 and slapos-master failed but the failures seem to be unrelated and it was already the same before on master: https://erp5js.nexedi.net/#!display_with_history?p.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F22%26view%3Dview_result_history&p.editable=true&p.selection=8c63bd5c5d74765e1a10d5276fd66ae6914e949b&p.history=235a69ba30d222bbf3194ffbae652f43f6dabe87&p.selection_index=1&p.page=form&p.jio_key=test_result_module%2F20231130-5E15B7D0%2F22&n.jio_key=test_result_module%2F20231130-5E15B7D0%2F22&n.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F22%26view%3Dview_result_history https://erp5js.nexedi.net/#!display_with_history?p.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F57%26view%3Dview_result_history&p.editable=true&p.selection=8c63bd5c5d74765e1a10d5276fd66ae6914e949b&p.history=235a69ba30d222bbf3194ffbae652f43f6dabe87&p.selection_index=41&p.page=form&p.jio_key=test_result_module%2F20231130-5E15B7D0%2F57&n.jio_key=test_result_module%2F20231130-5E15B7D0%2F57&n.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F57%26view%3Dview_result_history
-
Thomas Gambier authored
Now that testnodes are using ipv6 range, we can safely put back this check in place.
-
- 30 Nov, 2023 3 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
Werkzeug 3.0.0 is not compatible with Python3.7: File "/opt/slapos/eggs/werkzeug-3.0.0-py3.7.egg/werkzeug/serving.py", line 76, in <module> t.Union["ssl.SSLContext", t.Tuple[str, t.Optional[str]], t.Literal["adhoc"]] AttributeError: module 'typing' has no attribute 'Literal
-
Thomas Gambier authored
Now that testnodes are using ipv6 range, we can safely put back this check in place. This reverts commit 51a16b0b. See merge request nexedi/slapos!1484
-
- 29 Nov, 2023 6 commits
-
-
Kirill Smelkov authored
- remove no longer used ru/lopcomm/supervision.jinja2.py - restore removed `+ keep on touching RU watchdog` comment. Now it relates to ru/lopcomm/stats which became responsible for this function. - move code of RU-netconf-connection promise to be located nearby stats service because this promise interacts with that service, and grouping code by interaction makes it easier to understand for humans. Previously RU-netconf-connection was interacting with supervision service whcsh is gone after the patch in question. - use double vertical space to delimit logical sections from each other. open questions: - before the patch in question stats code was reconnecting after each error with 10 seconds pause. Now it logs it wants to reconnect but does _not_ because top-level `while True` was removed. Was that intended? If it was not the intent then new stats code will fail after any single error and won't reconnect to RU by itself. /reviewed-by @lu.xu /reviewed-on nexedi/slapos!1483
-
Kirill Smelkov authored
Similarly to sdr-busy, if we have several radio units, we want each of them to have its own rx-saturated promise. See nexedi/slapos.toolbox!126 for corresponding part in slapos.toolbox that makes check_rx_saturated per-RU configurable. Not touching gnb.jinja2.cfg as currently gnb does not support multicell at all, and in the future it will be sole enb.cfg to handle both LTE and NR simultaneously. /cc @xavier_thompson, @Daetalus /reviewed-by @jhuge, @lu.xu /reviewed-on nexedi/slapos!1485
-
Kirill Smelkov authored
If we have several radio units, we want each of them to have its own sdr-busy promise. See nexedi/slapos.toolbox!125 for corresponding part in slapos.toolbox that makes check_sdr_busy per-RU configurable. Not touching gnb.jinja2.cfg as currently gnb does not support multicell at all, and in the future it will be sole enb.cfg to handle both LTE and NR simultaneously. /cc @xavier_thompson, @Daetalus /reviewed-by @jhuge, @lu.xu /reviewed-on nexedi/slapos!1485
-
Kirill Smelkov authored
This promise applies to any CPRI-based Radio Unit not only to Lopcomm RU. -> Move its code to generic part, so that the promise is generated for any CPRI-based RU. /cc @xavier_thompson, @Daetalus /reviewed-by @jhuge, @lu.xu /reviewed-on nexedi/slapos!1485
-
Kirill Smelkov authored
Because for-RU DHCP-server should be provided to all CPRI-based radio unit, not only to Lopcomm. /cc @xavier_thompson, @Daetalus /reviewed-by @jhuge, @lu.xu /reviewed-on !1485
-
Thomas Gambier authored
Also cleanup duplicated section
-
- 28 Nov, 2023 9 commits
-
-
Thomas Gambier authored
-
Kirill Smelkov authored
instead of requiring users to explicitly activate it via additional `dnsmasq` parameter. The reason here is simple: CPRI-based radio units, for example Lopcomm ORAN RU, need to be configured to go to radio, and for that configuration to work we need to be able to talk via TCP/IP to the RU. /cc @jhuge, @xavier_thompson, @Daetalus /reviewed-by @lu.xu /reviewed-on nexedi/slapos!1479
-
Kirill Smelkov authored
We already pushed dnsmasq part, that serves radio units into enb in 9f2b9db5. However we need to push those bits further to ru/ for the following reasons: - DHCP server is used to provide Radio Units with IP address only. - without IP address assigned those RUs cannot be initialized and do not go to radio at all. - in general we will need to initialize and setup radio units not only in eNB - for example UEsim will use the same code library to initialize radio units. Thus the proper place to keep everything required for RU to be operational have to be located inside ru/ and activated by that radio-units library. /cc @jhuge, @xavier_thompson, @Daetalus /reviewed-by @lu.xu /reviewed-on nexedi/slapos!1479
-
Kirill Smelkov authored
The code had check-rx-saturated under `if not ru == "lopcomm"`, but checking RX signal for saturation is implemented on eNB side, not by RU itself, and is RU-independent because eNB only receives raw samples from RU and decides on its own whether those samples are higher than saturation margin or not. As an extra proof that checking for RX saturation is meaningful for Lopcomm too here is how samples.rx data can look like in the case of 2 Lopcomm Radio Units: root@callbox-005:/srv/slapgrid/slappart16/var/log# cat amarisoft-stats.json.log |jq .data.samples.rx [ { "rms": -382.3080749511719, "max": -382.3080749511719, "sat": 0, "count": 1221181440, "rms_dbm": -382.3080749511719 }, { "rms": -382.3080749511719, "max": -382.3080749511719, "sat": 0, "count": 1221179392, "rms_dbm": -382.3080749511719 } ] ... i.e. all the data, that check-rx-saturated promise works on, is there. /cc @jhuge, @xavier_thompson, @Daetalus /reviewed-by @lu.xu /reviewed-on !1478
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
On Fedora, the flag -lm is not correctly added so add it manually.
-