- 27 Nov, 2020 5 commits
-
-
Jérome Perrin authored
Until now, standalone subsystem was started as a daemon first time a terminal was openned and since it was running as daemon, stopping the theia instance did not stop any of the services running in the embedded slapos. Before nexedi/slapos.core!265 there was two supervisor running as daemon: - ~/srv/slapos/etc/supervisord.conf which runs slapos proxy etc - ~/srv/slapos/inst/etc/supervisord.conf with runs instances in the embedded slapos After, the second one runs as a service in the first one, but the first one was still running as daemon. This changes so that the first supervisor runs as a service managed by the Theia instance, so stopping Theia instance will effectively stop the services. When upgrading, running instances should continue to run as detached. To attach them to the new service, procedure could be something like this Stop supervisors inside Theia instance: supervisorctl -c ~/srv/slapos/etc/supervisord.conf shutdown supervisorctl -c ~/srv/slapos/inst/etc/supervisord.conf shutdown Restart slappartX:slapos-standalone-instance-XXX-on-watch from host slapos
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
We are observing some segmentation fault with python curses applications that might be because the TERMINFO are different from the system one. I did not debugged, but since I set this environment variable I did not observe any segmentation fault. By comparing strace, the invocations seems same with or without $TERMINFO. In both cases the termcaps from the correct ncurses are selected, this just seem to workaround for some reason.
- 26 Nov, 2020 4 commits
-
-
Łukasz Nowak authored
fixes "component/trafficserver: Version up to 8.1.0"
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 24 Nov, 2020 3 commits
-
-
Kirill Smelkov authored
Jérome reports that Pygolang build on Python3 fails because geventmp turned out to be not pinned: nexedi/slapos!862 (comment 121359) Geventmp is indeed used by pygolang only on Python3 nexedi/pygolang@cd67996e and with Python2-only testing I missed to handle it. -> Fix it and add test for pygolang/py3. /reviewed-on nexedi/slapos!864
-
Jérome Perrin authored
-
Thomas Gambier authored
See merge request nexedi/slapos!856
-
- 20 Nov, 2020 5 commits
-
-
Kirill Smelkov authored
Globbing can be unreliable after incremental profile update and rebuild because buildout does not remove old eggs. Also it is much more clean to be precise. -> Use [python-interpreter] to build bin/python with sys.path to wendelin.core and other needed eggs.
-
Kirill Smelkov authored
Without referencing component/numpy/ numpy will be installed from just PyPI.
-
Kirill Smelkov authored
Go1.15 is incremental improvement over Go1.14 with better compiler and runtime: https://blog.golang.org/go1.15 https://golang.org/doc/go1.15 Don't drop support for Go1.13 yet, as that (no longer supported) Go release is still being used by replication-manager and restic components. Remain default at Go1.14 yet. Switch helloworld to Go1.15 and test this patch on that software-release.
-
Kirill Smelkov authored
Going Go1.14.10 -> Go1.14.12 brings in runtime and security fixes: https://golang.org/doc/devel/release.html#go1.14 Tested on helloworld SR.
-
Léo-Paul Géneau authored
Tests added: - connexion parameters - monitor url - slaves instanciation Adds connexion parameters: - ipv6 - port - ipv4 Upgrade dnspython from 1.15.0 to 1.16.0 Removes unused parameters in instance-powerdns-replicate.cfg.jinja: - private-ipv4 - public-ipv4 - domain
-
- 19 Nov, 2020 2 commits
-
-
Thomas Gambier authored
See merge request nexedi/slapos!860
-
Jérome Perrin authored
When invoking tests with setup.py test, missing eggs are installed before running tests, using their latest available version, but we want to always install eggs using buildout and using pinned versions.
-
- 18 Nov, 2020 6 commits
-
-
Thomas Gambier authored
The section template-slapuser-script creates the "bin/slapos" wrapper which is needed inside runner-import.sh script.
-
Łukasz Nowak authored
Otherwise it's almost impossible to check for which node statistics are shown.
-
Łukasz Nowak authored
Fixes 8d5910dc
-
Łukasz Nowak authored
Limit stats to frontend entries only, as they are the most important for the frontend operator, and also having thousands of entries makes the stats page unusable. fixes 8d5910dc
-
Łukasz Nowak authored
Despite the introspection has replaced old style Caddy-based log-access, some bits were not removed, so remove then now. fixes 0c830c4c
-
Łukasz Nowak authored
It was done in frontend partition, but missed in kedifa. fixes 3469e864
-
- 16 Nov, 2020 2 commits
-
-
Julien Muchembled authored
-
Yusei Tahara authored
-
- 12 Nov, 2020 1 commit
-
-
Julien Muchembled authored
-
- 11 Nov, 2020 4 commits
-
-
Jérome Perrin authored
This reverts commit 5d46a499. Changes to "fix argument parsing" (to allow passing argument containing space) had a regression that backslash characters are escaped. Let's go back to slapos.toolbox 0.112 for now.
-
Jérome Perrin authored
When updating existing instance, running slapos node instance failed with: ln: failed to create symbolic link '/srv/slapgrid/slappart9/srv/frontend-static/logo.png': File exists This fixes by doing nothing if logo.png already exists
-
Jérome Perrin authored
-
Jérome Perrin authored
In 74d18b9d I switched ERP5 to use caucase certificate, but caucase is not yet usable for this and this caused issues with upgrading existing instances. We'll maybe try caucase again here, in that case 620c9332 can be reverted if we want to reuse some parts of what was made. See merge request !857
-
- 10 Nov, 2020 6 commits
-
-
Jérome Perrin authored
Revert "software/erp5: use a caucase managed certificate for balancer" This reverts commit 74d18b9d and also follow up fixup ( 555b26a2 ). We are not ready to use caucase here, there are still too many problems with caucase (keys are lost at each SR update etc) and design might still evolve, so let's go back to self signed certificate for now. Also remove the promise and the updater, since they are also not working and causing problems on instances that have been updated (and where the key no longer match the certificate)
-
Jérome Perrin authored
fix balancer CSR generation: Caucase rerequest uses a CSR *template* and use it to generate a new CSR with a new key, so we should not use the actual key to generate this CSR, because it is caucase rerequest job to generate the key. Also, we should be careful not to generate a new CSR every time this command run, otherwise a new key will be generated and a new CSR will be sent to caucase, but caucase will not sign it automatically (since we configure it to sign only one certificate). This means that the case of IP address changes is currently not supported automatically. To support it we would need to: - force generation of a new CSR template - force caucase rerequester to request a new certificate (by removing existing certificate) - force caucased to sign the new certificate This commit also fix indentation and remove simplefile macro that is no longer used
-
Łukasz Nowak authored
See merge request nexedi/slapos!837
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Just running test.py with ip and port allows to expose the internal testing backend. IPv4 and IPv6 are supported.
-
Łukasz Nowak authored
By default there is no sense to play with software type, since it's fixed in slapos.testing.testcase.
-
- 09 Nov, 2020 1 commit
-
-
Łukasz Nowak authored
slapos.cookbook:softwaretype tends to lowercase keys in each section, which has been undetected due to using lowercase references of slaves in the tests. By restructuring information in the sections, and putting slave references inside of dumped part of information, now the slave reference case is kept. Also real care was taken to stabilise published lists by sorting them, as it also slipped, that they could be unstable. Tests has been updated to catch this issue, also other tests were fixed, as they had wrong assertions.
-
- 06 Nov, 2020 1 commit
-
-
Julien Muchembled authored
See commit e83edfc9.
-