The ip-addresses above is for server 1, server 2 and server 3. The data in bf_images and bf_config is gonna be replicated 3 times, one for each server. This is not space efficient, but in environments where high-availability and high-reliability are critical, it is the most optimal solution.
### Task 5
To check whether the volumes now is a part of the file system, we run the command ```df -h ``` on server 1:
```
Filesystem Size Used Avail Use% Mounted on
tmpfs 393M 1.4M 392M 1% /run
/dev/vda1 39G 16G 23G 42% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/vda15 105M 5.3M 100M 5% /boot/efi
tmpfs 393M 4.0K 393M 1% /run/user/1000
```
We have created the folders bf_images and bf_config, but they does not appear in the list above. This is because we have not mounted the folders/volumes to the servers yet. This have to be done on every server, included server1.
To make the folders bf_images and bf_config available on each server, we have to run two mount commands on each server:
```
mount -t glusterfs serverX:bf_config /bf_config
mount -t glusterfs serverX:bf_images /bf_images
```
> **_NOTE:_** The _serverX_ part in the commands above have to be changed to the servers own ip-address. With this means; 192.168.134.127 on server1, 192.168.134.194 on server2, and
192.168.130.56 on server3.
After we have run the mount commands on a server, we can verify that the folders is indeed mounted on the server by running this command again: ```df -h```. This give us following output:
Note that the bf_config and bf_images folders is now appearing on the list. This means that the folders/volumes is succsessfully mounted. The output above is from server1, and the ip-address listed is therefore 192.168.134.127. On the other servers, the ip-address will be the current servers ip-address. Everything that is saved in the folders on one server, will become available on the other servers as well.
To make the containers be able to save files to the folders, we have to give the folders the correct rights:
