# Storage certification ## Why a certification is per-volume Atomic rename, same-file-store guarantees, and symlink refusal are properties of a specific filesystem behind a specific mount — not of "Kubernetes" or "a PVC". Change the CSI driver, the StorageClass, the access mode, the backend, or the mount options and any of them can differ. A certification that does not name all five is not transferable. ## What is certified | Property | Why it matters | |---|---| | Same file store for staging and content | A rename across stores is a copy, so publication stops being atomic. | | Atomic rename | The publish path's default strategy. | | Atomic create (`O_EXCL`) | Makes a publish create-only rather than a silent overwrite. | | Symlink refusal | Stops a replaced parent from redirecting a write outside the root. | | Ranged read | The download contract depends on it. | ## Running the certification 이 repo는 인증 job 매니페스트를 두지 않는다(2026-11-07 소유자 결정). 배포하는 쪽이 대상 volume을 저장 루트(`/var/lib/backend/files`)에 마운트한 일회성 pod에서 아래를 차례로 확인한다. 1. `staging`과 `content` 폴더를 만들고, `staging`의 파일을 `content`로 `mv`해 원자적 rename이 되는지 본다. 2. 두 폴더의 장치 번호(`stat -c %d`)가 같은지 본다. 다르면 rename이 복사가 된다. 3. `set -o noclobber` 상태에서 같은 파일을 두 번 만들어 `O_EXCL` 생성이 막히는지 본다. 4. 결과와 함께 묶음(Kubernetes 버전, CSI driver, StorageClass, 접근 모드, backend, mount 옵션)을 기록한다. 결과는 묶음 전체를 담은 기계가 읽는 형식으로 그 volume에 남긴다: ```json { "kubernetesVersion": "...", "csiDriver": "...", "storageClass": "...", "accessMode": "ReadWriteOnce", "backend": "ext2/ext3", "mountOptions": "rw,relatime", "atomicMove": true, "sameFileStore": true, "atomicCreate": true } ``` 2번이 실패하면 인증하지 않는다. staging과 content가 다른 저장소인 volume은 게시가 소리 없이 복사로 바뀐다. ## Network filesystems ```bash docker compose -f src/adapter/outbound/fileserver/compose/nfs/compose.yml up -d FILESERVER_NFS_TESTS=true ./gradlew :adapter:outbound:fileserver:test ``` The mount is `hard`, deliberately. A `soft` mount converts a slow server into a short write, which is exactly the corruption this design refuses to accept. ## Startup enforcement `FileserverStartupValidator` re-runs the probe at boot and refuses to accept traffic when a required capability is missing — `ATOMIC_MOVE_REQUIRED` on a filesystem that cannot prove an atomic move fails closed rather than degrading silently. ## Adding a new store Pass two executable contracts. A prose claim of compatibility is not accepted. - `UploadStoragePortContract` — the application port's contract, in `application-fileserver` testFixtures (`testImplementation testFixtures(project(':application-fileserver'))`). The application's `FakeUploadStorageGateway` extends it too, so use case tests and the real store obey the same offset, chunk-checksum and size-ceiling rules (a declared 0-byte upload refuses its first byte). - `ContentStoreContract` — the local adapter's internal `BlockingContentStore` SPI, in this adapter's tests. That SPI stays in the adapter by design (review S1-#12: the application never calls it), so its contract stays with it; a store that reuses the SPI extends it as well.