An error occurred fetching the project authors.
- 05 May, 2021 2 commits
-
-
Xavier Thompson authored
This commit introduces the `local_software_release_root` parameter. This parameter is then forwarded as the SR root path for slapproxy. By default the value is `/`, the same as the default in slapproxy.
-
Xavier Thompson authored
By default standalone will use the `slapos` executable in PATH. This option allows a specific slapos binary to be used instead.
-
- 03 May, 2021 1 commit
-
-
Xavier Thompson authored
This is to take advantage of !290
-
- 03 Feb, 2021 1 commit
-
-
Xavier Thompson authored
See merge request nexedi/slapos.core!280
-
- 20 Jan, 2021 1 commit
-
-
Jérome Perrin authored
Because some programs did not have proper configuration for log files, they were using automatically generated file names for log files. Correctly define stdout_logfile configuration for all programs, used with redirect_stderr=true, so that both stderr and stdout are in the same log file.
-
- 02 Dec, 2020 1 commit
-
-
Jérome Perrin authored
We were doing this because we use to run tests with `python setup.py test` which automatically sets PYTHONPATH, so it was affecting sub processes started by standalone. Nowadays we no longer use this method of running tests, so we are not really supposed to use PYTHONPATH, so we don't unset this environment variable, there might be valid cases where users want to force a different python path (but I can not think of any) and it simplifies the code a bit.
-
- 27 Nov, 2020 1 commit
-
-
Jérome Perrin authored
Instead of letting slapos commands start supervisord in daemon mode, run it as a program from standalone supervisord daemon. The $INSTANCE/etc/supervisord.conf will be created by `slapos node instance` the first time user runs it, until this, the service will restart in a loop, complaining that config file is not found. Also review stop to expose timeout argument and use a longer timeout by default (and cleanup some unused imports).
-
- 16 Sep, 2020 1 commit
-
-
Jérome Perrin authored
In 58fbaabf (svcbackend/standalone: use shorter names for supervisor sockets , 2020-07-17) we changed the socket path from supervisord.sock to a shorter sv.sock, but this caused issues when updating running slapos node instances, because this was trying to start a new supervisord process using the new socket path, while the old one was still running. To keep services running after upgrade, introduce a compatibility layer in this socket path - if we still have a supervisord running with a socket at this previous path, keep using this old socket name.
-
- 17 Jul, 2020 1 commit
-
-
Jérome Perrin authored
On test nodes, these socket path sometimes exceed the linux limit.
-
- 29 Jun, 2020 1 commit
-
-
Łukasz Nowak authored
In some cases partitions can chmod -w some paths, so use util.rmtree to overcome this situation.
-
- 22 Jun, 2020 1 commit
-
-
Jérome Perrin authored
Also change places where xml_marshaller were used directly to always use the wrapper from utils (except in tests for simplicity)
-
- 11 May, 2020 1 commit
-
-
Jérome Perrin authored
This allow to use standalone slapos with some requests being forwarded to another slapos master. The intended use case is to make have frontend requests forwarded to "real" slapos master when embedding slapos in theia or slaprunner.
-
- 20 Feb, 2020 1 commit
-
-
Jérome Perrin authored
-
- 17 Feb, 2020 1 commit
-
-
Jérome Perrin authored
In our normal operations, we are not using PYTHONPATH but using buildout to generate wrappers. We are still using python setup.py test to run tests, which sets PYTHONPATH to the eggs used by this python and this cause issues when this python starts subprocesses, especially when it starts another version of python which is supposed to use a different set of eggs.
-
- 27 Dec, 2019 1 commit
-
-
Jérome Perrin authored
50 was too much now that we keep snapshots in tests.
-
- 18 Dec, 2019 1 commit
-
-
Łukasz Nowak authored
The supervisord binary in some environments (like webrunner), seems to not follow the automatic way to find the configuration file, so instead of relying on it, just explicitly provide the file. /reviewed-on nexedi/slapos.core!168
-
- 30 Oct, 2019 1 commit
-
-
Jérome Perrin authored
Now that slapos node instance outputs summary of problems, no need to pollute the logs so much
-
- 25 Oct, 2019 1 commit
-
-
Jérome Perrin authored
destroying instance is supposed to remove these, but when there are issues removing instances we sometimes have supervisor config left from previous instances. Reformating now delete theses after logging the problem.
-
- 23 Oct, 2019 2 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
maybe this is something slapos node instance should do instead ...
-
- 10 Oct, 2019 1 commit
-
-
Jérome Perrin authored
When having more than one read_only_shared_part_list, the template was first rendered with indentation and then dedented, but since dedent only remove the common indentation, we ended up with slapos.cfg like this: ``` $ cat /data/slappart11_testnode/cqg/inst/test0-9/tmp/etc/slapos.cfg [slapos] software_root = /data/slappart11_testnode/cqg/inst/test0-9/tmp/soft instance_root = /data/slappart11_testnode/cqg/inst/test0-9/tmp/inst shared_part_list = /srv/slapgrid/slappart11/srv/shared /srv/slapgrid/slappart11/srv/testnode/cqg/shared /data/slappart11_testnode/cqg/inst/test0-9/tmp/shared master_url = http://10.0.12.198:46312 computer_id = local root_check = False ``` First dedent, then render the template to prevent this issue. Apply this to other uses of textwrap.dedent for consistency. /reviewed-on nexedi/slapos.core!140
-
- 01 Oct, 2019 1 commit
-
-
Jérome Perrin authored
A set of utility classes to run a local slapos computer and control softwares/instances on this computer
-