Atin Mukherjee
Atin Mukherjee
Taking this out from GCS/1.0 tag considering we're not going to make brick multiplexing a default option in GCS/1.0 release.
With rescoped MVP of GCS/1.0 this item isn't possible to work on. Removing the label.
Descoped for GCS/1.0.
I'm seeing performance implications because of this. Please don't merge it.
Not considered to be a blocker for GCS/1.0 based on the revised MVP.
This doesn't look like a candidate for GCS/0.2. @amarts @aravindavk Please move it to GCS/0.3 ?
gluster-block implementation (RWO) will be based on the loopback devices which is currently work in progress. This issue was to track the iSCSI/TCMU based gluster-block integration which is not a...
@aravindavk Is this a valid scenario in a opinionated GCS cluster?
[root@localhost glusterd2]# ./build/glustercli cluster get +--------------------------------+----------+-------+---------------+ | NAME | MODIFIED | VALUE | DEFAULT VALUE | +--------------------------------+----------+-------+---------------+ | cluster.shared-storage | no | off | off | | cluster.op-version | no...
@Madhu-1 Are we good with this PR?