- 18 Jan, 2021 1 commit
-
-
Xavier Thompson authored
See merge request nexedi/slapos!886
-
- 15 Jan, 2021 4 commits
-
-
Xavier Thompson authored
-
Łukasz Nowak authored
-
Kazuhiko Shiozaki authored
In reality, proxy.config.http.cache.max_stale_age was used for stale cache lifetime in current ATS implementation. Thus we increase proxy.config.http.negative_revalidating_lifetime value to the same value as proxy.config.http.cache.max_stale_age whose default is 604800.
-
Łukasz Nowak authored
-
- 14 Jan, 2021 1 commit
-
-
Cédric Le Ninivin authored
-
- 13 Jan, 2021 5 commits
-
-
Xavier Thompson authored
-
Thomas Gambier authored
See merge request nexedi/slapos!887
-
Xavier Thompson authored
-
Jérome Perrin authored
We want the tests to use the code from the repository, but when we have a pinned version, buildout will use the code from repository only when the version from the repository match the version spec from the pin. The way slapos.recipe.template was pinned to 4.4 caused issues when we made a change in slapos.recipe.template to make it 4.5, because tests were no longer using code from slapos.recipe.template repository, but from 4.4 egg from pypi. To prevent this kind of issues, unset the slapos.recipe.template = 4.4 version pin and also unset the version for all tested egg, to prevent similar issues if extended profiles also have version pins.
-
- 12 Jan, 2021 5 commits
-
-
Xavier Thompson authored
See merge request nexedi/slapos!876
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Thomas Gambier authored
This reverts commit 2f461da8.
-
- 11 Jan, 2021 2 commits
-
-
Thomas Gambier authored
Since Galene is behind our frontend, no need to take care of the HTTPS certificates.
-
Thomas Gambier authored
-
- 08 Jan, 2021 2 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
-
- 07 Jan, 2021 1 commit
-
-
Xavier Thompson authored
See merge request nexedi/slapos!880
-
- 05 Jan, 2021 1 commit
-
-
Vincent Pelletier authored
-
- 03 Jan, 2021 1 commit
-
-
Kirill Smelkov authored
This also pulls in crawshaw.io/sqlite because it is used by lonet.
-
- 31 Dec, 2020 3 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Due to unknown yet reason ATS and Caddy are loosing connections to haproxy, which results with increased amount of 5xx (about 0.5% more cases). No known solution was found yet on haproxy side, but this kind of workaround stabilises frontend and definitely drops amount of in-frontend 5xx. The observed situation with this workaround is no more 5xx sourcing in frontend itself.
-
- 28 Dec, 2020 2 commits
-
-
Xavier Thompson authored
-
Xavier Thompson authored
-
- 24 Dec, 2020 4 commits
-
-
Xavier Thompson authored
-
Thomas Gambier authored
See merge request nexedi/slapos!878
-
Alain Takoudjou authored
See https://galene.org Use first official version (0.1) Co-authored-by: Thomas Gambier <thomas.gambier@nexedi.com>
-
Thomas Gambier authored
-
- 23 Dec, 2020 1 commit
-
-
Xavier Thompson authored
-
- 22 Dec, 2020 2 commits
-
-
Thomas Gambier authored
See merge request nexedi/slapos!868
-
Jérome Perrin authored
Introduce a new "software release upgrade test", which tests a scenario of keating an ERP5 instance with an old version of software release and then update it to current version. To support this test and because we are using this technique for most of slapos softwares nowadays, configure zopes to restart automatically when their configuration change. See merge request nexedi/slapos!875
-
- 21 Dec, 2020 4 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
Confirms SlapOS ERP5 software release can be updated from a reference version to current version
-
Jérome Perrin authored
When root instance is updated to a new software release URL, it will re-request all the instances with the new software release URL. To make sure the new root instance does not appear has ready when it is re-requested with new software release URL, introduce a promise that will check that the instances requested by the root instance have the same software release URL. For now we do this only for Zope instances, because they are stateless and restart automatically on configuration changes, unlike stateful instances like mariadb or ZEO that we don't restart automatically (yet ?).
-
Jérome Perrin authored
We are using this pattern for most of our services since several months without any issue, so let's also use it for zopes. This makes automatic upgrade possible. Also remove "zope running current products" promise, since we restart we no longer need to check this.
-
- 17 Dec, 2020 1 commit
-
-
Léo-Paul Géneau authored
moves python2 release to component/jupyter-py2 because it is required by ERP5 but not maintained anymore moves to python 3 : - test/test.py - jupyter_notebook_config.py.jinja - ERP5kernel.py modifies custom.js to create a workaround for events issue see (https://github.com/jupyter/notebook/issues/2499) upgrades slapos.cookbook version to 1.0.171 to use zero_knowledge recipe with python 3 adds jupyter partition check in software/erp5/test/test_erp5.py
-