oVirt开源超融合平台，对于没钱，爱折腾的伙伴来说oVirt不失为一个比较好的选择。普通超融合平台每个CPU基本上都在3W左右，确实比较昂贵。
安装和配置
Gluster故障处理
Transport endpoint is not connected
oVirt的卷管理界面中有3个互为复制关系的bricks总是有2个bricks一直在同步文件，其中一个bricks状态出现问题：Status: Transport endpoint is not connected。
[root@host1 ~]# gluster vol heal vmstore info ... Brick storage1.ovirt.cacah.internal:/gluster_bricks/vmstore_d/vmstore /.shard/ecb12841-6666-4612-9681-f3a853c540f9.14 / /.shard/f1314f07-3ba2-4999-92b4-04593341430f.46 /.shard/f1314f07-3ba2-4999-92b4-04593341430f.600 Status: Connected Number of entries: 4 Brick storage2.ovirt.cacah.internal:/gluster_bricks/vmstore_d/vmstore Status: Transport endpoint is not connected Number of entries: - Brick storage3.ovirt.cacah.internal:/gluster_bricks/vmstore_d/vmstore /.shard/ecb12841-6666-4612-9681-f3a853c540f9.14 / /.shard/f1314f07-3ba2-4999-92b4-04593341430f.46 /.shard/f1314f07-3ba2-4999-92b4-04593341430f.600 Status: Connected Number of entries: 4
一般如果不是磁盘问题，就万能的重启，在故障节点上把glusterd服务器重启就好了。
[root@host2 ~]# systemctl restart glusterd
https://docs.gluster.org/en/latest/Troubleshooting/troubleshooting-glusterd/
"Transport endpoint is not connected" errors but all bricks are up
This is usually seen when a brick process does not shut down cleanly, leaving stale data behind in the glusterd process. Gluster client processes query glusterd for the ports the bricks processes are listening on and attempt to connect to that port. If the port information in glusterd is incorrect, the client will fail to connect to the brick even though it is up. Operations which would need to access that brick may fail with "Transport endpoint is not connected".
Solution : Restart the glusterd service.
如果还是不能解决，那就换个目录替换bricks
cd /gluster_bricks/engine/
mkdir engine_2
chown -R vdsm:kvm engine_2/
gluster volume replace-brick engine storage3.ovirt.cacah.internal:/gluster_bricks/engine/engine storage3.ovirt.cacah.internal:/gluster_bricks/engine/engine_2 commit force