Content integrity checker is already packaged in swh.objstorage and ready to be used.
We need to create its corresponding puppet manifest first to permit the standard deployment.
Description
Description
Revisions and Commits
Revisions and Commits
| rSPSITE puppet-swh-site | |||
| rSPSITEa1117f018a99 Revert profile tryout on grandpalais | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T304 content integrity checker | ||
| Migrated | gitlab-migration | T545 Create puppet manifests for the content integrity checkers |
Event Timeline
Comment Actions
Debian packages have been reworked since swh.objstorage needed a dependency on swh.storage.archiver (but only python3-swh.storage was available).
So, now here is the package layout regarding swh-storage and swh-objstorage (no new git repository has been added).
swh-storage spawns 3 debian packages (using our usual toolchain ./bin/make-package -b swh-storage):
- python3-swh.storage (already there)
- python3-swh.storage.listener (already there)
- python3-swh.storage.archiver - That one is the new one and provides the means to depend only on swh.storage.archiver
In the same vein, swh-objstorage spawns 2 debian packages (using our usual toolchain ./bin/make-package -b swh-objstorage):
- python3-swh.objstorage (already there)
- python3-swh.objstorage.checker (depends on swh.objstorage and swh.storage.archiver) - (to now deploy at the same time an objstorage and a checker without any puppet clash.
This permits to depend only on the checker if we need them and not the all objstorage.
Note:
The archiver manifest has been updated to depend on the python3-swh.storage.archiver (0b191fe)
(This solves a known issue on the archiver manifest where we voluntarily did not declare the python3-swh.storage dependency to avoid a puppet clash when deploying an archiver instance on a node with storage ability).