Operate
Prepare shared storage
Separate private node state from shared documents, indexes, logs, and model files.
Keep the three roots separate
| Root | Purpose | Sharing |
|---|---|---|
| Local | Node caches, transient documents, runtimes, and local logs | Keep local |
| Security | Protected installation state and private node identity | Never share |
| Cluster | Managed documents, models, indexes, and shared logs | Share only with approved service identities |
On Windows these sit beneath the selected installation folder. Ubuntu uses /var/lib/punaha-local, /var/lib/punaha-security, and /srv/punaha-cluster.
Choose the storage type
Filesystem, S3 compatible, and Azure Blob storage have different connection and permission requirements. Check the selected adapter for documents, indexes, and logs separately.
GGUF model weights need a filesystem path available to the Product service. Azure Blob credentials do not mount Azure Files. S3 object access does not provide a model filesystem.
Prepare and test
- Create a private location reserved for this installation.
- Give each approved node's service identity the required access.
- Configure the selected destination through the current authority. Enter credentials only into protected Product fields.
- Test from every node as its service identity, not only as your desktop user.
- Confirm document access, index readiness, model readability, and logs separately.
Model caches and temporary files
Model workers use verified node local copies. Allow space for the model and its staging reserve. Cache hits still verify the authoritative source, so a cache is not an offline storage replacement.
Only clean old model cache versions while all local model workers are stopped. Never treat the Security directory as a cache.
If storage fails
Check the exact path, protocol, service identity, and node. A successful HTTPS test to Azure does not prove SMB access. Changing a storage setting does not migrate existing data.
Next step
Read Plan storage and backups.
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.