[Bug]: Randomize order of external mounts

[wdec]

Describe the bug
When mounting externally created volumes, kadalu should randomize the order of the servers used, in a multi-server setup. Currently, the order is fixed, leading to all client mounts ending up being attached to the first server, affecting performance.
Furthermore, if the server list contains the node-ip of the node itself, it should be used in preference to other nodes as it represents a local server.

Fix identified

To Reproduce
Steps to reproduce the behavior:

1. Define list of gluster servers with external volumes
2. Create pods

Expected behavior
Randomized order of the servers used, with preference for local server if viable.

Actual behavior
In a setup with multiple servers, 192.168.21.51, 192.168.21.52, 192.168.21.53, all client mounts are established against the first of the servers:

pod-h-0:/var/log/robot# mount | grep glusterfs
192.168.21.51:glustervol1 on /mnt/showtech type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
192.168.21.51:glustervol2 on /mnt/common type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
192.168.21.51:glustervol3 on /mnt/backup type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
192.168.21.51:cw_localfs on /mnt/local type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
192.168.21.51:rsmibsyg on /mnt/yang type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)

Environment:
kadalu 1.1

Screenshots or Logs
If applicable, add any screenshots to help explain your problem. Try capturing relevant logs, post them to http://gist.github.com/ and post the links in the issue.

Additional context
Add any other context about the problem here.

[leelavg]

it should be used in preference to other nodes as it represents a local server.
gluster servers with external volumes

• quick check, in above setup does the external gluster storage runs on the k8s node but outside of k8s?

[wdec]

it should be used in preference to other nodes as it represents a local server.
gluster servers with external volumes

* quick check, in above setup does the external gluster storage runs on the k8s node but outside of k8s?

Yes