seanerstack 0.1.3__tar.gz → 0.1.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. {seanerstack-0.1.3 → seanerstack-0.1.4}/PKG-INFO +36 -43
  2. {seanerstack-0.1.3 → seanerstack-0.1.4}/README.md +35 -42
  3. seanerstack-0.1.4/data/share/seanerstack/config.toml +114 -0
  4. {seanerstack-0.1.3/data/share/seanerstack/environments/demobus-dev → seanerstack-0.1.4/data/share/seanerstack/environments/priorisea-dev}/spack.yaml +2 -2
  5. seanerstack-0.1.4/data/share/seanerstack/environments/seanerbus-dev/spack.yaml +10 -0
  6. seanerstack-0.1.4/data/share/seanerstack/environments/telemetry-collector-dev/spack.yaml +10 -0
  7. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/flux_core/package.py +25 -0
  8. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/priorisea/package.py +50 -0
  9. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/pscom/package.py +71 -0
  10. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/psmpi/package.py +156 -0
  11. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/py_pycapnp/package.py +36 -0
  12. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbroker/package.py +62 -0
  13. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus/package.py +20 -0
  14. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus_cli/package.py +37 -0
  15. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus_cpp/package.py +95 -0
  16. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus_msg/package.py +33 -0
  17. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus_python/package.py +43 -0
  18. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanerbus_rs/package.py +41 -0
  19. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/seanergys_meta/package.py +26 -0
  20. seanerstack-0.1.4/data/share/seanerstack/spack_repo/seanerstack/packages/telemetry_collector/package.py +78 -0
  21. {seanerstack-0.1.3 → seanerstack-0.1.4}/pyproject.toml +1 -1
  22. seanerstack-0.1.4/src/seanerstack/_spack_cache_access.py +48 -0
  23. seanerstack-0.1.4/src/seanerstack/_spack_detect.py +32 -0
  24. seanerstack-0.1.4/src/seanerstack/_spack_hashdiff.py +107 -0
  25. seanerstack-0.1.4/src/seanerstack/_spack_update_index.py +63 -0
  26. seanerstack-0.1.4/src/seanerstack/bootstrap.py +344 -0
  27. seanerstack-0.1.4/src/seanerstack/buildcache.py +162 -0
  28. seanerstack-0.1.4/src/seanerstack/cli.py +590 -0
  29. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/config.py +77 -1
  30. seanerstack-0.1.4/src/seanerstack/discovery.py +133 -0
  31. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/isolation.py +142 -26
  32. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/paths.py +6 -0
  33. seanerstack-0.1.4/src/seanerstack/pins.py +20 -0
  34. seanerstack-0.1.4/src/seanerstack/prepare.py +326 -0
  35. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/secrets.py +11 -0
  36. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/sync.py +21 -6
  37. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/validate.py +50 -1
  38. seanerstack-0.1.3/data/share/seanerstack/config.toml +0 -37
  39. seanerstack-0.1.3/data/share/seanerstack/spack_repo/seanerstack/packages/demobus/package.py +0 -38
  40. seanerstack-0.1.3/data/share/seanerstack/spack_repo/seanerstack/packages/seanergys_meta/package.py +0 -13
  41. seanerstack-0.1.3/src/seanerstack/bootstrap.py +0 -161
  42. seanerstack-0.1.3/src/seanerstack/buildcache.py +0 -68
  43. seanerstack-0.1.3/src/seanerstack/cli.py +0 -397
  44. {seanerstack-0.1.3 → seanerstack-0.1.4}/LICENSE +0 -0
  45. {seanerstack-0.1.3 → seanerstack-0.1.4}/data/share/seanerstack/environments/flux-core-dev/spack.yaml +0 -0
  46. {seanerstack-0.1.3 → seanerstack-0.1.4}/data/share/seanerstack/environments/properdocs-dev/spack.yaml +0 -0
  47. {seanerstack-0.1.3 → seanerstack-0.1.4}/data/share/seanerstack/spack-repo-index.yaml +0 -0
  48. {seanerstack-0.1.3 → seanerstack-0.1.4}/data/share/seanerstack/spack_repo/seanerstack/packages/properdocs/package.py +0 -0
  49. {seanerstack-0.1.3 → seanerstack-0.1.4}/data/share/seanerstack/spack_repo/seanerstack/repo.yaml +0 -0
  50. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/__init__.py +0 -0
  51. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/auth.py +0 -0
  52. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/docsgen.py +0 -0
  53. {seanerstack-0.1.3 → seanerstack-0.1.4}/src/seanerstack/recipe.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: seanerstack
3
- Version: 0.1.3
3
+ Version: 0.1.4
4
4
  Summary: Curated Spack recipes and environments for SEANERGYS, with synchronization, bootstrap, and validation tooling.
5
5
  License-Expression: Apache-2.0
6
6
  License-File: LICENSE
@@ -46,12 +46,18 @@ seanerstack paths env --package properdocs
46
46
  For example:
47
47
 
48
48
  ```console
49
- export SEANERSTACK_STATE_DIR=/path/to/seanerstack-state
50
- seanerstack toolchain bootstrap gcc@15
51
- eval "$(seanerstack activate)"
52
- spack env activate "$(seanerstack paths env --package properdocs)"
49
+ seanerstack --secrets-file secrets.toml init
50
+ export PATH=/opt/seanergys/state/spack/bin:$PATH
51
+ seanerstack toolchain bootstrap
52
+ eval "$(spack env activate --sh "$(seanerstack paths env --package properdocs)")"
53
53
  ```
54
54
 
55
+ `init` sets up the state directory, by default `/opt/seanergys/state`, once:
56
+ the pinned Spack, the configuration, the credentials, the build caches and the
57
+ CPU target. It checks access to every resource and installs no compiler; no
58
+ later command needs its options again. `seanerstack --version` prints the
59
+ Seanerstack version and the Spack version it pins.
60
+
55
61
  ## Development
56
62
 
57
63
  ```console
@@ -63,16 +69,16 @@ uv run seanerstack --help
63
69
  The unit tests are in `tests/unit`. The end-to-end tests in `tests/e2e` install
64
70
  the wheel of the checkout into a fresh environment and run it against the
65
71
  SEANERGYS GitLab, with credentials from a keyloom secrets file. They read the
66
- demobus repository, and build a small package, push it to a test build cache,
72
+ seanerbroker repository, and build a small package, push it to a test build cache,
67
73
  and install it back from there. Each build-cache test pushes to its own
68
74
  repository, `test-e2e-buildcache-<test>`, under the registry location given by
69
75
  `SEANERSTACK_E2E_REGISTRY`, never to the project build cache. They need Git,
70
- Spack, a C compiler, make, and a GitLab token that can read demobus and write to
71
- that location; without a token they are skipped:
76
+ a C compiler, make, and a GitLab token that can read seanerbroker and write to
77
+ that location; without a token they are skipped. Seanerstack installs its pinned
78
+ Spack for each test, unless `SEANERSTACK_E2E_SPACK` names one of the same version:
72
79
 
73
80
  ```console
74
81
  export SEANERSTACK_E2E_TOKEN=<GitLab personal access token>
75
- export SEANERSTACK_E2E_SPACK=/path/to/spack/bin/spack
76
82
  export SEANERSTACK_E2E_REGISTRY=oci://registry.seanergys.fz-juelich.de/<namespace>/<project>
77
83
  tests/e2e/run.sh
78
84
  ```
@@ -166,11 +172,8 @@ seanerstack \
166
172
  For interactive use, omit `--secrets-password-file`; Seanerstack prompts for the
167
173
  vault password. CI may use `--secrets-password-stdin` instead.
168
174
 
169
- Configure the Spack binary build caches from `config.toml` in the selected isolated state with:
170
-
171
- ```console
172
- seanerstack --state-dir /path/to/seanerstack-state buildcache configure
173
- ```
175
+ `seanerstack init` configures the Spack binary build caches from `config.toml`
176
+ in the state; `seanerstack buildcache configure` does it again on its own.
174
177
 
175
178
  A build cache with an `oci://` URL lives in a container registry and takes
176
179
  `username` plus `password` or `token`; Spack cannot sign OCI caches, so such a
@@ -182,43 +185,33 @@ cache, `seanerstack-buildcache`, is the seanerstack GitLab container registry.
182
185
 
183
186
  Seanerstack stores only environment-variable references in Spack's mirror
184
187
  configuration. It never writes S3 keys or registry tokens into Spack
185
- configuration. The actual variables must be present in any later native
186
- `spack` process that accesses a private cache; this is intentionally left as a
187
- process/session concern rather than storing decrypted credentials on disk.
188
+ configuration. `seanerstack init --secrets-file FILE` stores the credentials
189
+ that the resources name in the state directory instead, readable only by
190
+ their owner, and the state's `spack` wrapper loads them into every Spack
191
+ process.
188
192
 
189
- ## Isolated Spack session
193
+ ## Isolated Spack state
190
194
 
191
- Seanerstack keeps Spack configuration and mutable state inside one explicitly selected
192
- state directory. It does not use `~/.spack`, `/etc/spack`, another Spack store, or
193
- another Spack cache for Seanerstack-managed operations.
195
+ Seanerstack keeps its Spack, the Spack configuration and the mutable state
196
+ inside one state directory, by default `/opt/seanergys/state`; `--state-dir DIR`
197
+ or `SEANERSTACK_STATE_DIR` selects another. It does not use `~/.spack`,
198
+ `/etc/spack`, another Spack store, or another Spack cache.
194
199
 
195
- Activate a shell with:
200
+ `seanerstack init` writes a `spack` wrapper into the state. Put it on `PATH`
201
+ once, for example in `~/.bashrc`:
196
202
 
197
203
  ```console
198
- $ eval "$(seanerstack --state-dir /path/to/seanerstack-state activate)"
204
+ $ export PATH=/opt/seanergys/state/spack/bin:$PATH
199
205
  $ spack find
200
206
  $ spack install <spec>
201
207
  ```
202
208
 
203
- After activation, plain `spack` is the native Spack CLI executed with Seanerstack's
204
- private configuration. The session sets `SEANERSTACK_STATE_DIR`, disables normal
205
- local Spack configuration, redirects Spack user data, and places a transparent
206
- launcher first on `PATH`. The private tree contains the install store, build
207
- stages, source and miscellaneous caches, managed environments, and configuration.
208
-
209
- If the private build cache needs credentials, activate with the existing secrets
210
- options, for example:
211
-
212
- ```console
213
- $ eval "$(seanerstack --state-dir /path/to/seanerstack-state --secrets-file secrets.toml activate)"
214
- ```
215
-
216
- Leave the session with:
217
-
218
- ```console
219
- $ eval "$(seanerstack deactivate)"
220
- ```
209
+ Plain `spack` is then the native Spack CLI of the pinned version, run with
210
+ Seanerstack's private configuration and the stored credentials, in any shell.
211
+ The wrapper redirects Spack user data and removes `SPACK_DISABLE_LOCAL_CONFIG`.
212
+ The private tree contains the install store, build stages, source and
213
+ miscellaneous caches, managed environments, and configuration.
221
214
 
222
215
  `toolchain bootstrap`, Spack-backed validation, and build-cache commands use the
223
- same isolated state. Outside an activated shell, pass `--state-dir DIR` or set
224
- `SEANERSTACK_STATE_DIR`. There is intentionally no public Spack `--scope` option.
216
+ same state and what `init` recorded in it. There is intentionally no public
217
+ Spack `--scope` option.
@@ -34,12 +34,18 @@ seanerstack paths env --package properdocs
34
34
  For example:
35
35
 
36
36
  ```console
37
- export SEANERSTACK_STATE_DIR=/path/to/seanerstack-state
38
- seanerstack toolchain bootstrap gcc@15
39
- eval "$(seanerstack activate)"
40
- spack env activate "$(seanerstack paths env --package properdocs)"
37
+ seanerstack --secrets-file secrets.toml init
38
+ export PATH=/opt/seanergys/state/spack/bin:$PATH
39
+ seanerstack toolchain bootstrap
40
+ eval "$(spack env activate --sh "$(seanerstack paths env --package properdocs)")"
41
41
  ```
42
42
 
43
+ `init` sets up the state directory, by default `/opt/seanergys/state`, once:
44
+ the pinned Spack, the configuration, the credentials, the build caches and the
45
+ CPU target. It checks access to every resource and installs no compiler; no
46
+ later command needs its options again. `seanerstack --version` prints the
47
+ Seanerstack version and the Spack version it pins.
48
+
43
49
  ## Development
44
50
 
45
51
  ```console
@@ -51,16 +57,16 @@ uv run seanerstack --help
51
57
  The unit tests are in `tests/unit`. The end-to-end tests in `tests/e2e` install
52
58
  the wheel of the checkout into a fresh environment and run it against the
53
59
  SEANERGYS GitLab, with credentials from a keyloom secrets file. They read the
54
- demobus repository, and build a small package, push it to a test build cache,
60
+ seanerbroker repository, and build a small package, push it to a test build cache,
55
61
  and install it back from there. Each build-cache test pushes to its own
56
62
  repository, `test-e2e-buildcache-<test>`, under the registry location given by
57
63
  `SEANERSTACK_E2E_REGISTRY`, never to the project build cache. They need Git,
58
- Spack, a C compiler, make, and a GitLab token that can read demobus and write to
59
- that location; without a token they are skipped:
64
+ a C compiler, make, and a GitLab token that can read seanerbroker and write to
65
+ that location; without a token they are skipped. Seanerstack installs its pinned
66
+ Spack for each test, unless `SEANERSTACK_E2E_SPACK` names one of the same version:
60
67
 
61
68
  ```console
62
69
  export SEANERSTACK_E2E_TOKEN=<GitLab personal access token>
63
- export SEANERSTACK_E2E_SPACK=/path/to/spack/bin/spack
64
70
  export SEANERSTACK_E2E_REGISTRY=oci://registry.seanergys.fz-juelich.de/<namespace>/<project>
65
71
  tests/e2e/run.sh
66
72
  ```
@@ -154,11 +160,8 @@ seanerstack \
154
160
  For interactive use, omit `--secrets-password-file`; Seanerstack prompts for the
155
161
  vault password. CI may use `--secrets-password-stdin` instead.
156
162
 
157
- Configure the Spack binary build caches from `config.toml` in the selected isolated state with:
158
-
159
- ```console
160
- seanerstack --state-dir /path/to/seanerstack-state buildcache configure
161
- ```
163
+ `seanerstack init` configures the Spack binary build caches from `config.toml`
164
+ in the state; `seanerstack buildcache configure` does it again on its own.
162
165
 
163
166
  A build cache with an `oci://` URL lives in a container registry and takes
164
167
  `username` plus `password` or `token`; Spack cannot sign OCI caches, so such a
@@ -170,43 +173,33 @@ cache, `seanerstack-buildcache`, is the seanerstack GitLab container registry.
170
173
 
171
174
  Seanerstack stores only environment-variable references in Spack's mirror
172
175
  configuration. It never writes S3 keys or registry tokens into Spack
173
- configuration. The actual variables must be present in any later native
174
- `spack` process that accesses a private cache; this is intentionally left as a
175
- process/session concern rather than storing decrypted credentials on disk.
176
+ configuration. `seanerstack init --secrets-file FILE` stores the credentials
177
+ that the resources name in the state directory instead, readable only by
178
+ their owner, and the state's `spack` wrapper loads them into every Spack
179
+ process.
176
180
 
177
- ## Isolated Spack session
181
+ ## Isolated Spack state
178
182
 
179
- Seanerstack keeps Spack configuration and mutable state inside one explicitly selected
180
- state directory. It does not use `~/.spack`, `/etc/spack`, another Spack store, or
181
- another Spack cache for Seanerstack-managed operations.
183
+ Seanerstack keeps its Spack, the Spack configuration and the mutable state
184
+ inside one state directory, by default `/opt/seanergys/state`; `--state-dir DIR`
185
+ or `SEANERSTACK_STATE_DIR` selects another. It does not use `~/.spack`,
186
+ `/etc/spack`, another Spack store, or another Spack cache.
182
187
 
183
- Activate a shell with:
188
+ `seanerstack init` writes a `spack` wrapper into the state. Put it on `PATH`
189
+ once, for example in `~/.bashrc`:
184
190
 
185
191
  ```console
186
- $ eval "$(seanerstack --state-dir /path/to/seanerstack-state activate)"
192
+ $ export PATH=/opt/seanergys/state/spack/bin:$PATH
187
193
  $ spack find
188
194
  $ spack install <spec>
189
195
  ```
190
196
 
191
- After activation, plain `spack` is the native Spack CLI executed with Seanerstack's
192
- private configuration. The session sets `SEANERSTACK_STATE_DIR`, disables normal
193
- local Spack configuration, redirects Spack user data, and places a transparent
194
- launcher first on `PATH`. The private tree contains the install store, build
195
- stages, source and miscellaneous caches, managed environments, and configuration.
196
-
197
- If the private build cache needs credentials, activate with the existing secrets
198
- options, for example:
199
-
200
- ```console
201
- $ eval "$(seanerstack --state-dir /path/to/seanerstack-state --secrets-file secrets.toml activate)"
202
- ```
203
-
204
- Leave the session with:
205
-
206
- ```console
207
- $ eval "$(seanerstack deactivate)"
208
- ```
197
+ Plain `spack` is then the native Spack CLI of the pinned version, run with
198
+ Seanerstack's private configuration and the stored credentials, in any shell.
199
+ The wrapper redirects Spack user data and removes `SPACK_DISABLE_LOCAL_CONFIG`.
200
+ The private tree contains the install store, build stages, source and
201
+ miscellaneous caches, managed environments, and configuration.
209
202
 
210
203
  `toolchain bootstrap`, Spack-backed validation, and build-cache commands use the
211
- same isolated state. Outside an activated shell, pass `--state-dir DIR` or set
212
- `SEANERSTACK_STATE_DIR`. There is intentionally no public Spack `--scope` option.
204
+ same state and what `init` recorded in it. There is intentionally no public
205
+ Spack `--scope` option.
@@ -0,0 +1,114 @@
1
+ # SPDX-License-Identifier: Apache-2.0
2
+ # External resources are named here. Recipes and build-cache configuration refer
3
+ # to the resource name; credential values live only in the keyloom-encrypted
4
+ # secrets file.
5
+
6
+ # Private SEANERGYS Git resource. A recipe names the resource, never the
7
+ # credential; the token itself lives in the secrets file under the credential name
8
+ # below. Seanerstack authenticates `git ls-remote` with it, and sends it as
9
+ # the PRIVATE-TOKEN header when downloading a release archive to checksum it.
10
+ [resources.seanergys-gitlab]
11
+ kind = "git"
12
+ url = "https://gitlab.seanergys.fz-juelich.de/"
13
+ credentials = "seanergys-gitlab"
14
+
15
+ # Project binary build cache in the seanerstack GitLab container registry. Spack
16
+ # cannot sign OCI build caches, so registry access control is the trust boundary.
17
+ [resources.seanerstack-buildcache]
18
+ kind = "spack-buildcache"
19
+ url = "oci://registry.seanergys.fz-juelich.de/software/seanerstack/buildcache"
20
+ credentials = "seanergys-registry"
21
+ signed = false
22
+
23
+ # What `seanerstack buildcache prepare` builds and where it pushes it. Binaries
24
+ # carry the operating system and CPU target in their hash, so the toolchain is
25
+ # built once per platform, in that platform's image.
26
+ [toolchain]
27
+ compiler = "gcc@15"
28
+ packages = ["rust", "capnproto"]
29
+ cache = "seanerstack-buildcache"
30
+ target = "x86_64_v3"
31
+
32
+ # What every platform with that package manager installs before Spack runs.
33
+ [toolchain.system_packages]
34
+ dnf = [
35
+ "python3", "python3-pip", "git", "tar", "gzip", "bzip2", "xz", "zstd", "unzip", "patch", "file",
36
+ "which", "findutils", "diffutils", "gcc", "gcc-c++", "gcc-gfortran", "make",
37
+ ]
38
+ apt = [
39
+ "python3", "python3-venv", "python3-pip", "git", "ca-certificates", "tar", "gzip", "bzip2", "xz-utils",
40
+ "zstd", "unzip", "patch", "file", "findutils", "diffutils", "gcc", "g++", "gfortran", "make",
41
+ ]
42
+ pacman = [
43
+ "python", "python-pip", "git", "tar", "gzip", "bzip2", "xz", "zstd", "unzip", "patch", "file",
44
+ "which", "findutils", "diffutils", "gcc", "gcc-fortran", "make",
45
+ ]
46
+
47
+ [toolchain.platforms.rocky10]
48
+ image = "docker.io/rockylinux/rockylinux:10"
49
+ operating_system = "rocky10"
50
+ package_manager = "dnf"
51
+
52
+ # Seanerstack needs Python 3.12, and the python3 of Rocky 9 is 3.9.
53
+ [toolchain.platforms.rocky9]
54
+ image = "docker.io/rockylinux/rockylinux:9"
55
+ operating_system = "rocky9"
56
+ package_manager = "dnf"
57
+ python = "python3.12"
58
+ system_packages = ["python3.12", "python3.12-pip"]
59
+
60
+ # The last two Fedora releases.
61
+ [toolchain.platforms.fedora45]
62
+ image = "docker.io/library/fedora:45"
63
+ operating_system = "fedora45"
64
+ package_manager = "dnf"
65
+
66
+ [toolchain.platforms.fedora44]
67
+ image = "docker.io/library/fedora:44"
68
+ operating_system = "fedora44"
69
+ package_manager = "dnf"
70
+
71
+ [toolchain.platforms.debian13]
72
+ image = "docker.io/library/debian:13"
73
+ operating_system = "debian13"
74
+ package_manager = "apt"
75
+
76
+ # Debian 14 is still testing, so its image and Spack go by its code name. When
77
+ # it is released, this becomes debian:14 and debian14, and its binaries are
78
+ # built again.
79
+ [toolchain.platforms.debian14]
80
+ image = "docker.io/library/debian:forky"
81
+ operating_system = "debianforky"
82
+ package_manager = "apt"
83
+
84
+ [toolchain.platforms."ubuntu26.04"]
85
+ image = "docker.io/library/ubuntu:26.04"
86
+ operating_system = "ubuntu26.04"
87
+ package_manager = "apt"
88
+
89
+ [toolchain.platforms."ubuntu24.04"]
90
+ image = "docker.io/library/ubuntu:24.04"
91
+ operating_system = "ubuntu24.04"
92
+ package_manager = "apt"
93
+
94
+ # A rolling release has no version, so Spack names it plain arch.
95
+ [toolchain.platforms.arch]
96
+ image = "docker.io/library/archlinux:latest"
97
+ operating_system = "arch"
98
+ package_manager = "pacman"
99
+
100
+ # Example S3-backed Spack binary build cache:
101
+ # [resources.jsc-buildcache]
102
+ # kind = "spack-buildcache"
103
+ # url = "s3://seanerstack-buildcache"
104
+ # endpoint_url = "https://objectstore.example.org"
105
+ # credentials = "jsc-objectstore"
106
+ # autopush = true
107
+ # signed = false
108
+
109
+ # Example build cache in a directory on a local or shared filesystem. It takes
110
+ # no credentials and is unsigned unless signed = true is set:
111
+ # [resources.local-buildcache]
112
+ # kind = "spack-buildcache"
113
+ # url = "file:///scratch/seanerstack/buildcache"
114
+ # autopush = true
@@ -1,10 +1,10 @@
1
1
  # SPDX-License-Identifier: Apache-2.0
2
2
  spack:
3
3
  specs:
4
- - demobus@main
4
+ - priorisea@main
5
5
 
6
6
  # A source checkout is deliberately not committed here. After activating this
7
7
  # environment, bind one with:
8
- # spack develop --path /path/to/demobus demobus@main
8
+ # spack develop --path /path/to/priorisea priorisea@main
9
9
  concretizer:
10
10
  unify: true
@@ -0,0 +1,10 @@
1
+ # SPDX-License-Identifier: Apache-2.0
2
+ spack:
3
+ specs:
4
+ - seanerbus@main
5
+
6
+ # A source checkout is deliberately not committed here. After activating this
7
+ # environment, bind one with:
8
+ # spack develop --path /path/to/seanerbroker seanerbroker@main
9
+ concretizer:
10
+ unify: true
@@ -0,0 +1,10 @@
1
+ # SPDX-License-Identifier: Apache-2.0
2
+ spack:
3
+ specs:
4
+ - telemetry-collector@main
5
+
6
+ # A source checkout is deliberately not committed here. After activating this
7
+ # environment, bind one with:
8
+ # spack develop --path /path/to/telemetry-collector telemetry-collector@main
9
+ concretizer:
10
+ unify: true
@@ -0,0 +1,25 @@
1
+ # SPDX-License-Identifier: Apache-2.0
2
+ import re
3
+
4
+ from spack_repo.builtin.packages.flux_core.package import FluxCore as BuiltinFluxCore
5
+
6
+ from spack.package import *
7
+
8
+
9
+ class FluxCore(BuiltinFluxCore):
10
+ """Flux as Spack has it, which can also build a commit"""
11
+
12
+ # configure takes the version from `git describe`, which needs the tags. Spack
13
+ # clones a commit alone, and the refspec of that clone makes the builtin recipe
14
+ # fail to fetch the history, so configure stops at an invalid version.
15
+ get_full_repo = True
16
+
17
+ def test_version(self):
18
+ """check that flux reports a version that starts with a release"""
19
+ output = which(self.prefix.bin.flux, required=True)("version", output=str, error=str)
20
+ assert re.search(r"^commands:\s+\d+\.\d+\.\d+", output, re.MULTILINE), output
21
+
22
+ def test_run_a_job(self):
23
+ """run a job in an instance of one broker"""
24
+ flux = which(self.prefix.bin.flux, required=True)
25
+ assert flux("start", "flux", "run", "echo", "ran", output=str, error=str).strip() == "ran"
@@ -0,0 +1,50 @@
1
+ # Copyright Spack Project Developers. See COPYRIGHT file for details.
2
+ #
3
+ # SPDX-License-Identifier: (Apache-2.0 OR MIT)
4
+ import os
5
+
6
+ from spack_repo.builtin.build_systems.cmake import CMakePackage
7
+
8
+ from spack.package import *
9
+
10
+
11
+ class Priorisea(CMakePackage):
12
+ """Job priority manager for SEANERGYS."""
13
+
14
+ homepage = "https://gitlab.seanergys.fz-juelich.de/software/priorisea"
15
+ git = "https://gitlab.seanergys.fz-juelich.de/software/priorisea.git"
16
+ seanerstack_resource = "seanergys-gitlab"
17
+
18
+ test_requires_compiler = True
19
+
20
+ license("LGPL-3.0-only")
21
+
22
+ version("main", branch="main", submodules=True)
23
+
24
+ # Variant to enable building and running the tests
25
+ variant("test", default=False, description="Enable Priorisea testing capabilities")
26
+
27
+ depends_on("c", type="build")
28
+ depends_on("cxx", type="build")
29
+ depends_on("cmake@3.22:", type="build")
30
+ depends_on("pkgconfig", type="build")
31
+ depends_on("capnproto")
32
+ depends_on("jansson")
33
+ depends_on("sqlite")
34
+ depends_on("seanerbus-cpp")
35
+ depends_on("flux-core@0.81.0:")
36
+ depends_on("cli11")
37
+ depends_on("catch2@2.13.10", when="+test", type="build")
38
+ #depends_on("seanerbroker", when="+test", type=("build", "run"))
39
+
40
+ def cmake_args(self):
41
+ return [self.define_from_variant("BUILD_TESTING", "test")]
42
+
43
+ def test_priorisea_help(self):
44
+ """run the priorisea CLI and print its help"""
45
+ which(self.prefix.bin.priorisea, required=True)("--help", output=str, error=str)
46
+
47
+ def test_plugin_installed(self):
48
+ """the flux jobtap plugin is installed into flux's job-manager plugin dir"""
49
+ plugin = join_path(self.prefix.lib, "flux", "job-manager", "plugins", "sea_priority.so")
50
+ assert os.path.isfile(plugin), f"the sea_priority plugin was not installed at {plugin}"
@@ -0,0 +1,71 @@
1
+ # SPDX-License-Identifier: Apache-2.0
2
+
3
+ from spack_repo.builtin.build_systems.cmake import CMakePackage
4
+
5
+ from spack.package import *
6
+
7
+
8
+ class Pscom(CMakePackage):
9
+ """ParaStation is a robust and efficient cluster middleware, consisting of a
10
+ high-performance communication layer (MPI) and a sophisticated management
11
+ layer. This package provides its low-level communication layer pscom.
12
+ """
13
+
14
+ homepage = "https://par-tec.com"
15
+ git = "https://gitlab.seanergys.fz-juelich.de/software/pscom.git"
16
+ seanerstack_resource = "seanergys-gitlab"
17
+
18
+ maintainers = ["pickartz1", "happ1"]
19
+
20
+ license("QPL")
21
+
22
+ version("6.1.1-1", tag="6.1.1-1")
23
+ version("6.0.1-1", tag="6.0.1-1")
24
+
25
+ variant(
26
+ "build_type",
27
+ default="RelWithDebInfo",
28
+ description="Specify CMake build type",
29
+ values=("Release", "RelWithDebInfo", "MinSizeRel", "Debug"),
30
+ )
31
+ variant("cuda", default=False, description="Compile with CUDA support")
32
+ variant("openib", default=False, description="Compile with native IB Verbs support")
33
+ variant("ucp", default=True, description="Compile with UCX support")
34
+ variant("psm2", default=False, description="Compile with PSM2 support")
35
+ variant("portals4", default=False, description="Compile with Portals4 support")
36
+ variant("utest", default=False, description="Enable unit tests")
37
+ variant("rrcomm", default=False, description="Compile with RRComm Precon support")
38
+
39
+ depends_on("cmake@3.10.0:", type="build")
40
+ depends_on("rrcomm", when="+rrcomm")
41
+ depends_on("cmocka", when="+utest")
42
+ depends_on("cuda", when="+cuda")
43
+ depends_on("opa-psm2", when="+psm2")
44
+ depends_on("rdma-core", when="+openib")
45
+ depends_on("ucx", when="+ucp")
46
+
47
+
48
+ # We need to explicitly create a VERSION file to obtain the correct version
49
+ # information during the CMake phase.
50
+ def cmake(self, spec, prefix):
51
+ # Write the VERSION file
52
+ with open(self.root_cmakelists_dir + "/VERSION", "w") as f:
53
+ f.write("pscom-{0}".format(self.version))
54
+
55
+ # Run CMake as usual
56
+ super(Pscom, self).cmake(spec, prefix)
57
+
58
+ def cmake_args(self):
59
+ variant_bool = lambda feature: "ON" if feature in self.spec else "OFF"
60
+
61
+ args = [
62
+ "-DCUDA_ENABLED={0}".format(variant_bool('+cuda')),
63
+ "-DRRCOMM_PRECON_ENABLED={0}".format(variant_bool('+rrcomm')),
64
+ "-DOPENIB_ENABLED={0}".format(variant_bool('+openib')),
65
+ "-DUCP_ENABLED={0}".format(variant_bool('+ucp')),
66
+ "-DPSM2_ENABLED={0}".format(variant_bool('+psm2')),
67
+ "-DPORTALS4_ENABLED={0}".format(variant_bool('+portals4')),
68
+ "-DUTEST_ENABLED={0}".format(variant_bool('+utest')),
69
+ ]
70
+
71
+ return args