It looks like all is good and the connectivity is in place. Now, we can test what the status looks like: :~# gluster peer status Once the connectivity is in place, we can create a GlusterFS cluster by running from one node: :~# gluster peer probe node2 GlusterFS uses port 24007 for connectivity between the nodes we must make sure that it is open and accessible by all of the nodes. └─48919 /usr/sbin/glusterd -p /var/run/glusterd.pid -log-level INFOįeb 21 11:42:34 node1 systemd: Starting GlusterFS, a clustered file-system server.įeb 21 11:42:35 node1 systemd: Started GlusterFS, a clustered file-system server.

Process: 48918 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid -log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Mon 11:42:35 UTC 7s ago

rvice - GlusterFS, a clustered file-system server.

Then we can install the GlusterFS on all of our TeamCity nodes: sudo apt install glusterfs-server

To do that, we need to setup the repository for the latest packages of GlusterFS on all of them: sudo add-apt-repository ppa:gluster/glusterfs-7 We want to configure hostnames and /etc/hosts on our TeamCity nodes, where we will also be deploying GlusterFS. As for the database, we will use one of the supported relational database management systems - PostgreSQL, and we’ll use ClusterControl to build a high availability stack based around it. There are different options that you can use to build a shared mount however, we will use GlusterFS. We must ensure that those are also highly available. As we can see, there are two shared elements - the data directory and the database.

Download teamcity ci cd