An error occurred fetching the project authors.
- 23 Oct, 2017 7 commits
-
-
Kirill Smelkov authored
This tool can be used to measure disk IO latency for various workloads (random read, sequential read, direct or cached, write, ...). We use a bit patched version shows not only avg latency but also its distribution. (the patches are currently dirty/not very robust and not yet sent to upstream). In the upcoming neotest SR ioping will be used to automatically benchmark underlying disk characteristics.
-
Kirill Smelkov authored
ethtool can be used to adjust NIC settings, such as e.g. interrupt coalescing and various others. It usually requires root to do so. However regular users can query NIC settings via ethtool just ok. This way upcoming neotest SR will use it to query/display NIC setting which are essential to get good networked latency and automatically produce warnings if it is not.
-
Kirill Smelkov authored
Starting from this version zodbtools requires zodburi to open ZODB storages by URL (see nexedi/zodbtools@db3b84ec and nexedi/zodbtools@82b06413) zodburi in turn requires ZEO (maybe we might patch it to only optionally depend on it), so we move ZEO requirement from stack/ERP5 to the place where it is actually first needed.
-
Kirill Smelkov authored
In Go world development workflow is organized around so-called workspace where multiple packages can be installed / worked on etc. The following page describes Go workspaces: https://golang.org/doc/code.html A new [gowork] section and infrastructure around it is introduced. Quoting code: # gowork is a top-level section representing workspace # # users should add `install` field to [gowork] to describe packages they want to # be installed (+ automatically their dependencies are installed too). e.g. # # [gowork] # install = # lab.nexedi.com/kirr/neo/go/... \ # github.com/pkg/profile \ # golang.org/x/perf/cmd/benchstat The way it all works inside is: - gowork organizes to create go.work/ directory in buildout root - inside it creates env.sh which when sources in shell adjusts all paths so that appropriate go compiler is in path, GOPATH is also set appropriately, etc - in other words everything needs for using/working on this workspace is setup in the environment. - in actual user software profile the list of Go projects which needs to be installed by SlapOS has to be listed. The [gowork] machinery takes care about git-cloning these projects and `go install`s them after. - by SlapOS design builds have to be reproducible and so every component state/version has to be fixed. A convenient helper (gowork-snapshot) to get snapshot of git go packages installed with their exact revisions is added. This should be used to automatically (re-)generate list of go git repositories & their pinning for a workspace. For a new Go project that needs to be slaposified the workflow should be: - first get a project into working state via any convenient way (`go get`, etc.) - generate list of go packages & their pinning with gowork-snapshot - extend golang/buildout.cfg and in project software profile add [gowork] install = your-top-level-packages as it was outlined above. P.S. [golang] is removed because 1. it is not used anywhere in slapos.git tree, and 2. the canonical way to work on go projects from now on will be to use [gowork]. There latest go version is preconfigured, but users can override it to some particular other version in their projects as they need. /reviewed-on nexedi/slapos!242 /also-needed-for nexedi/slapos!243
-
Rafael Monnerat authored
This reverts merge request !243
-
Eteri authored
The first proof of concept of Caddy in Slapos. For now, everything is inside software/caddy but in the next merge request we will move to stack. @rafael @romain /reviewed-on nexedi/slapos!243
-
eteri authored
-
- 20 Oct, 2017 12 commits
-
-
eteri authored
-
eteri authored
-
eteri authored
-
eteri authored
-
eteri authored
-
eteri authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
WIP
-
Alain Takoudjou authored
-
Julien Muchembled authored
-
Vincent Pelletier authored
-
- 19 Oct, 2017 1 commit
-
-
Cédric Le Ninivin authored
-
- 18 Oct, 2017 2 commits
-
-
Julien Muchembled authored
-
Alain Takoudjou authored
-
- 17 Oct, 2017 4 commits
-
-
Rafael Monnerat authored
Environment requires new lines instead spaces
-
Rafael Monnerat authored
This is required got the usage of git
-
Rafael Monnerat authored
MD5SUM update was missing.
-
Yusei Tahara authored
-
- 13 Oct, 2017 7 commits
-
-
Julien Muchembled authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
Experimental. Not automatically executed. Restores given backup, configures service as a slave to given master, starts replication. Like for "normal" backup restoration, any running mariadb is killed, started with backup-restoration-friendly parameters, and killed again once restored. As there is AFAIK no way to ask supervisor to start even one of our own services, this script unfortunately leaves the partition in a not-immediately useful state.
-
Vincent Pelletier authored
Nothing references this section otherwise.
-
Vincent Pelletier authored
This value is supposed to come from configuration file, which is already implicitly provided inside used wrapper.
-
Vincent Pelletier authored
-
Vincent Pelletier authored
Back-porting a patch from upstream's github repository.
-
- 12 Oct, 2017 5 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Yusei Tahara authored
-
Yusei Tahara authored
This reverts commit 18c4c3e2.
-
Yusei Tahara authored
-
- 11 Oct, 2017 2 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Reduce a little the path+filename for the socket file, as NGINX/Linux has a limitation for long paths on this instruction. This small change allow the resilience test works w/o kernel patches or workarrounds.
-