- 13 May, 2022 6 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
pim-dm is a python3 only egg and re6st is a python2 only egg. Deploy pim-dm egg inside a totally separated buildout in python3. See merge request nexedi/slapos!1161
-
Thomas Gambier authored
-
Jérome Perrin authored
-
Boxiang Sun authored
See merge request nexedi/slapos!1170
-
Jérome Perrin authored
-
- 12 May, 2022 6 commits
-
-
Boxiang Sun authored
Now the nat-rule-port always has the protocol name, see here: https://lab.nexedi.com/nexedi/slapos/blob/9a886c4b0c6dd229564292eaa0ef2604fa857aea/software/kvm/instance-kvm.cfg.jinja2#L843
-
Boxiang Sun authored
See merge request nexedi/slapos!1166
-
Jérome Perrin authored
fixes CVE-2021-33503
-
Jérome Perrin authored
fixes PVE-2022-47833
-
Boxiang Sun authored
-
Kirill Smelkov authored
@tomo reports that parts/golang1.17/pkg/obj/go-build takes ~ 1GB which makes it wasteful if we want to upload result of compilation to shacache. It turns out we can drop that particular build cache completely, because it is used only during the build and test of Go itself and its standard library. And when Go is installed it will be another - "user" build cache - that will be used to maintain and reuse build artifacts. For the reference: in SlapOS that latter "user" build cache is located inside go.work/ -> Purge internal build cache after compilation is over. Size of parts/golang1.17 before and after hereby patch: before: 1.6G after: 447M See also related discussion in nexedi/slapos!929 (comment 128379) /reviewed-by @tomo, @jerome /reviewed-on nexedi/slapos!1169
-
- 11 May, 2022 2 commits
-
-
Xavier Thompson authored
-
Julien Muchembled authored
-
- 10 May, 2022 1 commit
-
-
Alain Takoudjou authored
New revision include a fix for waitdatabases which cause repman test instability.
-
- 09 May, 2022 12 commits
-
-
Alain Takoudjou authored
-
Jérome Perrin authored
See merge request !1163
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Mostly to address the warning in the test that the request parameters do not comply with schema.
-
Jérome Perrin authored
software/{gitlab,nextcloud}: update options to new redis recipe
-
Jérome Perrin authored
This changes software/nextcloud to be python3 and software/matomo no longer need to explicitly use python3 anymore.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Thomas Gambier authored
This is a fixup of 9a886c4b
-
Jérome Perrin authored
This way we don't need to vendor python-redis (so we don't need to update it for python3 support). This also change the options in a backward incompatible way: - options are now kebab case ( server_bin -> server-bin ) - a new cli-bin option holding the full path to redis-cli command is required to enable promise
-
- 08 May, 2022 2 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 06 May, 2022 8 commits
-
-
Alain Takoudjou authored
This allow to view captured image from the test result log url (snapshot directory).
-
Thomas Gambier authored
This is a fixup of 9a886c4b
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Julien Muchembled authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Xavier Thompson authored
-
- 05 May, 2022 3 commits
-
-
Thomas Gambier authored
FIxup of e8220174fdfc386100a4927400d959c50d1be449
-
Thomas Gambier authored
Also adapt build.sh for bootstrapping with python3. This is a fixup of 4b28ab13. See also nexedi/slapos!1154
-
Łukasz Nowak authored
Instead of dropping some keys (easy to implement, impossible to test and easy to leak) create whitelist of passed keys of slaves to the nodes. Then if there are new keys in slave's connection parameters the nodes are protected against being polluted with them.
-