gcs Tracker: Enable thin arbiter

Add support for thin arbiter to CSI driver
- [ ] Parent of gluster/gluster-csi-driver#46

Oct 29 '18 19:10 JohnStrunk

@Madhu-1 @aravindavk We need to see how we can get the information required for thin arbiter passed. I am inclined towards having a ENV variable with thin-arbiter details, which is set by Admin (or operator / ansible installer), which gets picked up by CSI driver depending on the type of volume chosen.

We have to handle this in CSI driver, and also specify the details of how to use this in StorageClass for our users.

Nov 13 '18 11:11 amarts

@amarts In the CSI driver, we have defined (but not implemented) the following parameters:

parameters:
  # Type of arbiter for replicate volumes. default=none
  arbiterType: none  # (none | normal | thin)
  # Supplying arbiterZones restricts the placement of arbiter bricks to the
  # provided zone(s). Only applicable for replicate volumes with arbiter. If
  # not specified, dataZones will be used.
  arbiterZones: "az4,az5"

(above is taken from gluster/gluster-csi-driver#30)

Zones, above, are supposed to use node tags via IVP to do placement.

Are we missing any parameters or do we just need to prioritize appropriately?

Nov 13 '18 17:11 JohnStrunk