Since we use coreos, mount directly into host can’t be done. We used a very complex procedure to handle this before, first mounted into a glusterfs container, then shared to os, then other container mounted it. But I thought It’s too complicated, and abandoned it. As to PV and PVC, I just did some testing. I seted up PVC with glusterfs, limited the capacity to 8GB, but when I mounted the corresponding PV from pod, I had the entire 1.8TB volume. It was not what I expected. Likun 发件人: Vijay Bellur [mailto:vbellur@xxxxxxxxxx] On Fri, Dec 30, 2016 at 4:07 AM, likun <kun.li@xxxxxxxxxxx> wrote:
You can possibly accomplish this by mounting the entire glusterfs volume into the container host and bind mounting different sub-directories of the volume in different containers. Gluster supports configuring quota on sub-directories. Note that data services like geo-replication, snapshots etc. cannot be configured for sub-directories. Are your PVs for read write once or read write many workloads? We are looking at adding read write once support with iSCSI in Gluster 3.10. Regards, Vijay |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
