Warning
This page was translated from the original Japanese version by PLaMo Translate. The Japanese version is authoritative; the English translation may contain inaccuracies.
Storage Types and Comparison
PFCP provides two storage options for persistent data storage: file storage and block storage. PFCP’s file storage utilizes NFS (Network File System) as its communication protocol to connect to storage systems, while block storage uses NVMe/TCP.
File Storage
PFCP’s file storage enables data sharing among multiple Pods using the NFS protocol. It is particularly suitable for storing data that is commonly accessed by workloads across an organization, as well as for storing logs and processed results.
Block Storage
PFCP’s block storage leverages NVMe/TCP to enable more advanced operations from Pods against storage systems.
When creating a filesystem on block storage and using it accordingly, multiple Pods cannot access it simultaneously but can perform faster data access. This makes it ideal for use cases requiring high response performance, such as in databases.
When handling block storage as a raw device rather than creating a filesystem, it can be directly used as a standard Linux block device. This approach is useful for achieving functionality not possible with existing filesystems, such as:
- Specialized applications requiring device-level encryption
- Use as virtual disks employing proprietary formats
Comparison
This section outlines the available access modes for the storage types provided by PFCP. The access modes listed in the table are abbreviated as follows: ReadWriteOnce (RWO), ReadOnlyMany (ROX), ReadWriteMany (RWX), and ReadWriteOncePod (RWOP)
| Storage Type | RWO | ROX | RWX | RWOP | Notes |
|---|---|---|---|---|---|
| File Storage | ◯ | ◯ | ◯ | ◯ | |
| Block Storage | ◯ | - | - | ◯ | When creating a filesystem and using it accordingly |
| Block Storage | ◯ | ◯ | ◯ | ◯ | When handling as a raw block device without creating a filesystem |