Files
nmd-md5sum-manifest/readme.md
T

38 lines
1.3 KiB
Markdown
Raw Normal View History

2026-02-27 14:15:42 +02:00
Under clusterwide-file-manifest we should have directory tree of the form
2026-03-24 09:43:53 +00:00
`dir` - `K-Y-Z-M`:
- `K-Y-Z-M`/`clusterwide-manifest.nmd5`
2026-02-27 14:15:42 +02:00
These are the clusterwide manifests - i.e manifests that are produced by comparing the md5s of different nodes from the same cluster,
and producing 2 lists for each of those clusters:
2026-03-24 09:43:53 +00:00
- List 1 (matches):
2026-02-27 14:15:42 +02:00
md5sum:/file/path
2026-03-24 09:43:53 +00:00
- List 2 (diffs):
2026-02-27 14:15:42 +02:00
md5sum:/file/path
2026-03-24 09:43:53 +00:00
> Where List 1 is a list of all files that have the same path, and have the same path and md5sum across the cluster
> While list 2 is a list of the inverse of the above.
2026-02-27 14:15:42 +02:00
# Stages
2026-03-24 09:43:53 +00:00
## Stage 0 - ssh backbone for propogating stage1 across the cluster
```bash
2026-03-24 11:06:55 +00:00
yum install git -y
2026-03-24 09:43:53 +00:00
git clone https://git.adspem.com/opthq/nmd-md5sum-manifest.git
cd nmd-md5sum-manifest/stages
chmod +x *
./stage0-remote-run.sh
hsctl cmd run 'ls -la /root/manifest*'
```
2026-02-27 14:15:42 +02:00
## Stage 1 - Md5:filepath
- Param 1 - base path (i.e `stage1.sh /` - would produce md5sum for everything under root)
- Produces a file containing the md5:file on a given system
- Excludes directories known to contain node-specific directories
## Stage 2 - Base manifest producer -
Takes in files produced from Stage 1 across a cluster and produces an output base-manifest
## Stage 3 - Compares a stage 1 output against a known stage 2 manifest