I have not gone through this implementation nor the new iscsi implementation being worked on for 3.9 but I thought I'd share the design behind a distributed iscsi implementation that we'd worked on some time back based on the istgt code with a libgfapi hook.
The implementation used the idea of using one file to represent one block (of a chosen size) thus allowing us to use gluster as the backend to store these files while presenting a single block device of possibly infinite size. We used a fixed file naming convention based on the block number which allows the system to determine which file(s) needs to be operated on for the requested byte offset. This gave us the advantage of automatically accessing all of gluster's file based functionality underneath to provide a fully distributed iscsi implementation.
The implementation used the idea of using one file to represent one block (of a chosen size) thus allowing us to use gluster as the backend to store these files while presenting a single block device of possibly infinite size. We used a fixed file naming convention based on the block number which allows the system to determine which file(s) needs to be operated on for the requested byte offset. This gave us the advantage of automatically accessing all of gluster's file based functionality underneath to provide a fully distributed iscsi implementation.
Would this be similar to the new iscsi implementation thats being worked on for 3.9?
On Wed, Jun 29, 2016 at 4:04 PM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:
Prasanna explains how Gluster can be used as a distributed block store with Kubernetes cluster at:
https://pkalever.wordpress.com/2016/06/29/non-shared-persistent-gluster-storage-with-kubernetes
Please note that the current version of kubernetes doesn't have support for multi-path.
We will be sending out an updated version of this post once Kubernetes 1.3.0. is released.
This is a follow-up post to:
"Gluster Solution for Non Shared Persistent Storage in Docker Container "
https://pkalever.wordpress.com/2016/06/23/gluster-solution-for-non-shared-persistent-storage-in-docker-container/We would love to hear your feedback to both of these solutions.
--Pranith
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
