<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet href="/rss.xsl" type="text/xsl" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Glusterfs | Bacardi55&#39;s Web Cave</title>
    <link>https://bacardi55.io/tags/glusterfs/</link>
    <description>Recent content in Glusterfs on Bacardi55&#39;s Web Cave</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>bac@rdi55.pl (bacardi55)</managingEditor>
    <webMaster>bac@rdi55.pl (bacardi55)</webMaster>
    <copyright>2010-2025 bacardi55</copyright>
    <lastBuildDate>Thu, 04 Feb 2021 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://bacardi55.io/tags/glusterfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      
      <title>Moving away from GlusterFS to a shared folder mounted via sshfs for my cluster storage</title><link>https://bacardi55.io/2021/02/04/moving-away-from-glusterfs-to-a-shared-folder-mounted-via-sshfs-for-my-cluster-storage/</link><pubDate>Thu, 04 Feb 2021 00:00:00 +0100</pubDate><author>bac@rdi55.pl (bacardi55)</author><guid>https://bacardi55.io/2021/02/04/moving-away-from-glusterfs-to-a-shared-folder-mounted-via-sshfs-for-my-cluster-storage/</guid><description>&lt;h2 id=&#34;context&#34;&gt;Context&lt;/h2&gt;&#xA;&lt;p&gt;As I written at the beginning of the&#xA;&lt;a href=&#34;https://bacardi55.io/categories/selfhosting/&#34;&gt;selfhosting series&lt;/a&gt; about my&#xA;&lt;a href=&#34;https://bacardi55.io/tags/dockerswarm/&#34;&gt;docker swarm cluster&lt;/a&gt;, I have used so far a&#xA;&lt;a href=&#34;https://bacardi55.io/2020/03/24/my-home-lab-2020-part-2-glusterfs-setup/&#34;&gt;GlusterFS volume&#xA;mounted on all nodes of the swarm&lt;/a&gt;. It has worked well until now, but&#xA;the truth is I believe it was too heavy for the raspberry pi (mainly on&#xA;the pi2 and 3) and had a few issues with it over the years (issues when&#xA;mounting the drive with only part of the data and other small&#xA;glusterfuck^^).&lt;/p&gt;&#xA;&lt;p&gt;As I finally invested and installed a NAS&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; at home recently (more&#xA;on this later), I decided to leverage it for the storage of the cluster.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: &lt;em&gt;I know that it is not the best way of managing this,&#xA;specially when having a bigger usage and that GlusterFS is made for this&#xA;and is one of the best choice. But for a selfhosted cluster with almost&#xA;no traffic based on raspberry pi, it was overkilled.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;setup&#34;&gt;Setup&lt;/h2&gt;&#xA;&lt;p&gt;On all raspberry pi, I had to install sshfs:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo apt install sshfs&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then, enable the &lt;code&gt;user_allow_other&lt;/code&gt; to manage access permissions and&#xA;right through sshfs:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo vim /etc/fuse.conf&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And uncomment &lt;code&gt;user_allow_other&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Create the directory where the remote directory will be mounted, eg (on&#xA;all cluster&amp;rsquo;s node):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir -p /mnt/nas_storage/&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Now, create an ssh key on all nodes if it is not already the case&#xA;(without passphrase) with &lt;code&gt;ssh-keygen&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Add each keys in the &lt;code&gt;authorized_keys&lt;/code&gt; files of the right user.&lt;/p&gt;&#xA;&lt;p&gt;You can test if it works as expected (and add the server in the&#xA;&lt;code&gt;known_hosts&lt;/code&gt; file):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sshfs -o allow_other user@server:/path/to/remote/directory/ /mnt/nas_storage&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If your data are in &lt;code&gt;/mnt/nas_storage&lt;/code&gt;, it works. Now you can unmount it&#xA;for now:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    fusermount -u /mnt/nas_storage&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To automount on demand the sshfs directory, edit the &lt;code&gt;/etc/fstab&lt;/code&gt; file&#xA;and add:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    user@server:/path/to/remote/directory /mnt/nas_storage/ fuse.sshfs noauto,x-systemd.automount,_netdev,users,IdentityFile=/path/to/sshkey.pub,allow_other,reconnect 0 0&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;Based on &lt;a href=&#34;https://wiki.kobol.io/helios64/intro/&#34;&gt;Helios64&lt;/a&gt; for&#xA;the hardware, &lt;a href=&#34;https://www.armbian.com/&#34;&gt;armbian&lt;/a&gt; and&#xA;&lt;a href=&#34;https://www.openmediavault.org/&#34;&gt;openmediavault&lt;/a&gt; for the&#xA;software. Detailed blog post to follow.&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description></item>
    <item>
      
      <title>My Home Lab 2020, part 2: GlusterFS Setup</title><link>https://bacardi55.io/2020/03/24/my-home-lab-2020-part-2-glusterfs-setup/</link><pubDate>Tue, 24 Mar 2020 00:00:00 +0100</pubDate><author>bac@rdi55.pl (bacardi55)</author><guid>https://bacardi55.io/2020/03/24/my-home-lab-2020-part-2-glusterfs-setup/</guid><description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;As said &lt;a href=&#34;https://bacardi55.io/posts/2020/03/22/my-home-lab-2020-part-1-context-and-architecture-choices/&#34;&gt;previously on this blog&lt;/a&gt;, I&amp;rsquo;ve rebuild my &amp;ldquo;home lab&amp;rdquo; from scratch lately based on&#xA;a &lt;a href=&#34;https://docs.docker.com/engine/swarm/&#34;&gt;docker swarm&lt;/a&gt; architecture and &lt;a href=&#34;https://www.gluster.org/&#34;&gt;GlusterFS&lt;/a&gt;. The goal of this post is to&#xA;go through the storage setup of our cluster :-)&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;assumptions&#34;&gt;Assumptions&lt;/h3&gt;&#xA;&lt;p&gt;You have your raspberry pi or other servers installed, connected to your&#xA;network and internet, up to date and you know a minimum your way in a&#xA;Linux shell :)&lt;/p&gt;&#xA;&lt;p&gt;If you don&amp;rsquo;t, I suggest reading about it first before following the rest&#xA;of this post, there is plenty of great documentation online :-).&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Nota&lt;/em&gt;: I always name my based on&#xA;&lt;a href=&#34;https://en.wikipedia.org/wiki/Manga&#34;&gt;manga&lt;/a&gt;, for all my devices&#xA;(laptop, desktop, phone, servers, &amp;hellip;)&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;. So don&amp;rsquo;t be surprise when&#xA;reading machine name later on :).&lt;/p&gt;&#xA;&lt;h3 id=&#34;simple-tip&#34;&gt;Simple Tip&lt;/h3&gt;&#xA;&lt;p&gt;If like me you use &lt;code&gt;tmux&lt;/code&gt;, you can easily launch a command on all your&#xA;servers at once :).&lt;/p&gt;&#xA;&lt;p&gt;For this, all you need to do is open tmux, create window pane for all&#xA;your servers and ssh to them. Once you are connected on all the servers&#xA;on all pane, you can simply do &lt;code&gt;ctrl(keep pressed) a :&lt;/code&gt;. You&amp;rsquo;ll be shown&#xA;a prompt &lt;code&gt;:&lt;/code&gt; to enter a command. Enter &lt;code&gt;setw synchronize-panes&lt;/code&gt; and&#xA;validate with enter.&lt;/p&gt;&#xA;&lt;p&gt;At this point, any key pressed will be send to all servers, so you can&#xA;type a command once that will be fired on all systems.To stop it, just redo the same (&lt;code&gt;ctrl a :&lt;/code&gt; then&#xA;&lt;code&gt;setw synchronize-panes&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;h3 id=&#34;glusterfs&#34;&gt;GlusterFS&lt;/h3&gt;&#xA;&lt;h4 id=&#34;why&#34;&gt;Why&lt;/h4&gt;&#xA;&lt;p&gt;To be able to have shared storage across your docker swarm cluster. This&#xA;allow all servers to share the same files. Having this is mandatory so&#xA;you don&amp;rsquo;t care anymore on which of these servers your containers are&#xA;launched because they always have access to data :). Just think of it of&#xA;a shared drive mechanism, but built for cloud usage.&lt;/p&gt;&#xA;&lt;p&gt;There are other possible solution to this, but seems like a pretty&#xA;robust one for cluster storage :).&lt;/p&gt;&#xA;&lt;h4 id=&#34;some-definitions&#34;&gt;Some definitions&lt;/h4&gt;&#xA;&lt;p&gt;Basic Concepts of GlusterFS from their &lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;documentation&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Distributed File System&lt;/strong&gt;&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt;: &amp;gt; A file system that allows multiple&#xA;clients to concurrently access data which is spread across&#xA;servers/bricks in a trusted storage pool. Data sharing among multiple&#xA;locations is fundamental to all distributed file systems.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Brick&lt;/strong&gt;&lt;sup id=&#34;fnref:4&#34;&gt;&lt;a href=&#34;#fn:4&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;4&lt;/a&gt;&lt;/sup&gt;: &amp;gt; A Brick is the basic unit of storage in GlusterFS,&#xA;represented by an export directory on a server in the trusted storage&#xA;pool. A brick is expressed by combining a server with an export&#xA;directory&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Node&lt;/strong&gt;&lt;sup id=&#34;fnref:5&#34;&gt;&lt;a href=&#34;#fn:5&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;5&lt;/a&gt;&lt;/sup&gt;: &amp;gt; A server or computer that hosts one or more bricks.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Volume&lt;/strong&gt;&lt;sup id=&#34;fnref:6&#34;&gt;&lt;a href=&#34;#fn:6&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;6&lt;/a&gt;&lt;/sup&gt;: &amp;gt; A volume is a logical collection of bricks.&lt;/p&gt;&#xA;&lt;p&gt;Read the &lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;documentation&lt;/a&gt; for more.&lt;/p&gt;&#xA;&lt;h4 id=&#34;glusterfs-architecture-choice&#34;&gt;GlusterFS architecture choice&lt;/h4&gt;&#xA;&lt;p&gt;With GlusterFS you can create the following types of Gluster Volumes:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Distributed Volumes: (default option): This is for scalable storage&#xA;with no data redundancy - «files are distributed across various bricks&#xA;in the volume. So file1 may be stored only in brick1 or brick2 but not&#xA;on both. Hence there is no data redundancy.»&lt;sup id=&#34;fnref:7&#34;&gt;&lt;a href=&#34;#fn:7&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;7&lt;/a&gt;&lt;/sup&gt;&lt;/li&gt;&#xA;&lt;li&gt;Replicated Volumes: (Better reliability and data redundancy): «Here&#xA;exact copies of the data are maintained on all bricks.»&lt;sup id=&#34;fnref:8&#34;&gt;&lt;a href=&#34;#fn:8&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;8&lt;/a&gt;&lt;/sup&gt;&lt;/li&gt;&#xA;&lt;li&gt;Distributed-Replicated Volumes: (HA of Data due to Redundancy and&#xA;Scaling Storage): «In this volume files are distributed across&#xA;replicated sets of bricks.»&lt;sup id=&#34;fnref:9&#34;&gt;&lt;a href=&#34;#fn:9&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;9&lt;/a&gt;&lt;/sup&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;More detail on&#xA;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/Quick-Start-Guide/Architecture/&#34;&gt;GlusterFS&#xA;Architecture&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I decided to use a &amp;ldquo;Replicated Volumes&amp;rdquo; configuration, making sure I&#xA;have all files on all nodes (aka on all my raspberry pi).&lt;/p&gt;&#xA;&lt;h4 id=&#34;setup-a-gluster-replicated-volumes-on-4-nodes&#34;&gt;Setup a Gluster Replicated Volumes on 4 nodes&lt;/h4&gt;&#xA;&lt;p&gt;On all&lt;sup id=&#34;fnref:10&#34;&gt;&lt;a href=&#34;#fn:10&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;10&lt;/a&gt;&lt;/sup&gt;:&lt;/p&gt;&#xA;&lt;p&gt;Install, enable and start gluster deamon:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo apt install glusterfs-server&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo systemctl enable glusterd.service&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo systemctl start glusterd.service&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then, create the needed volumes (still all on all nodes):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /glusterfs/bricks&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /mnt/cluster-data&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then, you need to make sure they can contact each other. Either you have&#xA;a local dns server that manage this (like&#xA;&lt;a href=&#34;http://www.thekelleys.org.uk/dnsmasq/doc.html&#34;&gt;dnsmasq&lt;/a&gt;) or simply&#xA;edit your &lt;code&gt;/etc/host&lt;/code&gt; file.&lt;/p&gt;&#xA;&lt;p&gt;For the rest of this posts, the machine name will be:&#xA;&lt;code&gt;cell, ptitcell1, ptitcell2, ptitcell3&lt;/code&gt;&lt;sup id=&#34;fnref:11&#34;&gt;&lt;a href=&#34;#fn:11&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;11&lt;/a&gt;&lt;/sup&gt;. Cell is my &amp;ldquo;master&amp;rdquo;&#xA;(docker swarm manager) node in the cluster, but this has no impact for&#xA;GlusterFS.&lt;/p&gt;&#xA;&lt;p&gt;So now, we have to &amp;ldquo;link&amp;rdquo; all the nodes together in a trusted pool&#xA;storage.&lt;/p&gt;&#xA;&lt;p&gt;On your first node (&lt;code&gt;cell&lt;/code&gt; in my case):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo gluster peer probe ptitcell1&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo gluster peer probe ptitcell2&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo gluster peer probe ptitcell3&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Now all nodes should be in the pool storage.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s now create the different bricks on all nodes.&lt;/p&gt;&#xA;&lt;p&gt;On your &amp;ldquo;master&amp;rdquo; or first server:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /glusterfs/bricks/1/brick&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;on all other nodes (&lt;code&gt;ptitcell{1,2,3}&lt;/code&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /glusterfs/bricks/2/brick &lt;span style=&#34;color:#75715e&#34;&gt;# on ptitcell1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /glusterfs/bricks/3/brick &lt;span style=&#34;color:#75715e&#34;&gt;# on ptitcell2&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo mkdir /glusterfs/bricks/4/brick &lt;span style=&#34;color:#75715e&#34;&gt;# on ptitcell3&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then, back on my first node (&lt;code&gt;cell&lt;/code&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    sudo gluster volume create cluster-data replica &lt;span style=&#34;color:#ae81ff&#34;&gt;4&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;&lt;/span&gt;        cell:/glusterfs/bricks/1/brick &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;&lt;/span&gt;        ptitcell1:/glusterfs/bricks/2/brick &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;&lt;/span&gt;        ptitcell2:/glusterfs/bricks/3/brick &lt;span style=&#34;color:#ae81ff&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;&lt;/span&gt;        ptitcell3:/glusterfs/bricks/4/brick&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;(If you are testing at first and use the root partition, you have to add&#xA;&lt;code&gt;force&lt;/code&gt; at the end of the command)&lt;/p&gt;&#xA;&lt;p&gt;Now we can start the volume :)&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      sudo gluster volume start data&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Lastly, you need to update your &lt;code&gt;/etc/fstab&lt;/code&gt; on all your nodes:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      localhost:cluster-data /mnt/cluster-data glusterfs defaults,_netdev,backupvolfile-server&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;localhost &lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To try, you can mount the volume on all nodes:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      sudo mount.glusterfs localhost:cluster-data /mnt/cluster-data/&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If everything works, you can now create a file in &lt;code&gt;/mnt/cluster-data/&lt;/code&gt;&#xA;and see it on all nodes :-).&lt;/p&gt;&#xA;&lt;p&gt;With the line in the &lt;code&gt;/etc/fstab&lt;/code&gt;, now you can reboot your nodes and the&#xA;volume should automatically mounted :)&lt;/p&gt;&#xA;&lt;h2 id=&#34;to-be-continued-dot-dot-dot&#34;&gt;To be Continued&amp;hellip; :-)&lt;/h2&gt;&#xA;&lt;p&gt;That&amp;rsquo;s it for now, it doesn&amp;rsquo;t do anything yet, we just have a shared&#xA;folder between our nodes, but this post is already long enough&amp;hellip; So&#xA;we&amp;rsquo;ll start playing with docker and swarm on the next one.&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;I originally planned to write about glusterFS and Docker Swarm&#xA;setup in this post but the gluster setup was long enough for 1&#xA;post :).&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;Being huge fan since my childhood, I starting doing this with my&#xA;first laptop when I was ±15 and never stopped since, almost 20&#xA;years later&amp;hellip;&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:3&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;GlusterFS glossary&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:3&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:4&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;GlusterFS glossary&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:4&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:5&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;GlusterFS glossary&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:5&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:6&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/glossary/&#34;&gt;GlusterFS glossary&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:6&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:7&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/Quick-Start-Guide/Architecture/&#34;&gt;GlusterFS Architecture&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:7&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:8&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/Quick-Start-Guide/Architecture/&#34;&gt;GlusterFS Architecture&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:8&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:9&#34;&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gluster.readthedocs.io/en/latest/Quick-Start-Guide/Architecture/&#34;&gt;GlusterFS Architecture&lt;/a&gt;&amp;#160;&lt;a href=&#34;#fnref:9&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:10&#34;&gt;&#xA;&lt;p&gt;Remember the tip above^^&amp;#160;&lt;a href=&#34;#fnref:10&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:11&#34;&gt;&#xA;&lt;p&gt;As said before&amp;hellip; I&amp;rsquo;m a huge fan of manga, so in this case I was inspired by &lt;a href=&#34;https://en.wikipedia.org/wiki/Dragon_Ball_Z&#34;&gt;Dragon Ball Z&lt;/a&gt; and the vilain &lt;a href=&#34;https://en.wikipedia.org/wiki/Cell_(Dragon_Ball)&#34;&gt;cell&lt;/a&gt;. &amp;ldquo;Ptitcell&amp;rdquo; means &amp;ldquo;Cell Junior&amp;rdquo; in French^^.&amp;#160;&lt;a href=&#34;#fnref:11&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description></item>
    <item>
      
      <title>My Home Lab 2020, part 1: Context and Architecture choices</title><link>https://bacardi55.io/2020/03/18/my-home-lab-2020-part-1-context-and-architecture-choices/</link><pubDate>Wed, 18 Mar 2020 00:00:00 +0100</pubDate><author>bac@rdi55.pl (bacardi55)</author><guid>https://bacardi55.io/2020/03/18/my-home-lab-2020-part-1-context-and-architecture-choices/</guid><description>&lt;h2 id=&#34;context&#34;&gt;Context&lt;/h2&gt;&#xA;&lt;p&gt;At the end of last year, I decided to rebuild my home self hosting and&#xA;home automation setup. The main reason was that it was starting to get&#xA;old and was really becoming a mess due to creating it bit by bit and on&#xA;the fly^^.&lt;/p&gt;&#xA;&lt;p&gt;I had stopped hosting my services at home for some time (as I moved&#xA;everything to digitalocean), but always wanted to switch back. I was a&#xA;bit familiar with docker as this is what I use on my DO servlets but I&#xA;had never used Docker Swarm or Kubernetes before and wanted to learn&#xA;more one of them (to at least better grasp the concepts).&lt;/p&gt;&#xA;&lt;p&gt;On the home automation part, it became way too complicated, mostly&#xA;because I was learning at the time and was building it little by little.&#xA;I had a old rpi2 B with &lt;a href=&#34;https://github.com/domoticz/domoticz&#34;&gt;domoticz&lt;/a&gt;, a rpi3 with &lt;a href=&#34;https://kalliope-project.github.io/&#34;&gt;kalliope&lt;/a&gt; and&#xA;&lt;a href=&#34;https://nodered.org/&#34;&gt;nodered&lt;/a&gt;, &amp;hellip; For those reading my blog back&#xA;then, you are familiar with the voice assistant &lt;a href=&#34;https://kalliope-project.github.io/&#34;&gt;Kalliope&lt;/a&gt; that was the brain of&#xA;my home and I was actively participating. One thing though&amp;hellip; I noticed&#xA;that I don&amp;rsquo;t like to talk to a software, that I prefer an easy to access&#xA;interface (web, app, cli, &amp;hellip;) to do the action I wanted&amp;hellip; And that I&#xA;was more into automation than voice control.&lt;/p&gt;&#xA;&lt;p&gt;Of course, this meant moving from a voice assistant centric architecture&#xA;to an automation centric architecture&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Because my home automation system mostly sit on my &amp;ldquo;home lab&amp;rdquo; system&#xA;that I wanted to redo, I&amp;rsquo;ve redone everything during end of December and&#xA;January. The first part was setting up the home lab and will be split in&#xA;a series of blog posts that you can follow &lt;a href=&#34;https://bacardi55.io/categories/homelab/&#34;&gt;here&lt;/a&gt; about the basics setup :).&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Nota&lt;/strong&gt;: Don&amp;rsquo;t get me wrong, I love &lt;a href=&#34;https://kalliope-project.github.io/&#34;&gt;Kalliope&lt;/a&gt; and was using it quite&#xA;extensively for a while&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;. But I must admit my needs and&#xA;requirements has changed&amp;hellip; Hence the re-architecture.&lt;/p&gt;&#xA;&lt;h2 id=&#34;my-architecture-choices&#34;&gt;My Architecture choices&lt;/h2&gt;&#xA;&lt;p&gt;As said, I&amp;rsquo;ve been using docker for some time now, but very &amp;ldquo;manually&amp;rdquo;&#xA;or &amp;ldquo;handmade&amp;rdquo;&amp;hellip; Meaning myself playing docker compose command on&#xA;multiple hosts. I wanted to go to the next level during this reset and&#xA;use my favorite hardware: raspberry pis :).&lt;/p&gt;&#xA;&lt;h3 id=&#34;hardware-raspberry-pi-3-and-4&#34;&gt;Hardware: Raspberry Pi 3 and 4&lt;/h3&gt;&#xA;&lt;p&gt;As said above, the hardware is based on raspberry pis. I&amp;rsquo;m using 1&#xA;raspberry 3 and 3 raspberry pi 4 (4gb RAM) for my cluster (though it&#xA;might be easier if you only 1 type of architecture, as the rpi 4 differ&#xA;from the 3).&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve also bought 4 fast USB keys for the cluster storage.&lt;/p&gt;&#xA;&lt;p&gt;And to push the nerdgasm to the limit, I purchased&#xA;&lt;a href=&#34;https://www.amazon.com/GeeekPi-Cluster-Raspberry-Heatsink-Stackable/dp/B07MW24S61/ref=sr_1_5&#34;&gt;this cluster case for 4 raspberry pis&lt;/a&gt; to tidy up the installation. They are&#xA;all connected via short ethernet cables to my Netgear router :-).&lt;/p&gt;&#xA;&lt;h3 id=&#34;software-selection&#34;&gt;Software selection&lt;/h3&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve decided to go with the following stack:&lt;/p&gt;&#xA;&lt;h4 id=&#34;os-raspbian&#34;&gt;OS: Raspbian&lt;/h4&gt;&#xA;&lt;p&gt;I selected (as usual) &lt;a href=&#34;https://www.raspbian.org/&#34;&gt;raspbian&lt;/a&gt; as the OS for my raspberry pis (3 and 4s).&lt;/p&gt;&#xA;&lt;p&gt;For a headless installation of raspbian, see my old post&#xA;&lt;a href=&#34;https://bacardi55.io/posts/2017/11/5/headless-raspberrypi-installation/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;I won&amp;rsquo;t talk about how the post installation of raspbian for a server,&#xA;there are plenty of guide on the internet for this :).&lt;/p&gt;&#xA;&lt;h4 id=&#34;containers-orchestration-docker-swarm&#34;&gt;Containers orchestration: Docker Swarm&lt;/h4&gt;&#xA;&lt;p&gt;This is where I spend most time thinking between &lt;a href=&#34;https://kubernetes.io/&#34;&gt;Kubernetes&lt;/a&gt; and &lt;a href=&#34;https://docs.docker.com/engine/swarm/&#34;&gt;Docker Swarm&lt;/a&gt;&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;The &amp;ldquo;obvious&amp;rdquo; choice, if I wanted to have an architecture as close as&#xA;what most advance containers users are doing, was &lt;a href=&#34;https://kubernetes.io/&#34;&gt;Kubernetes&lt;/a&gt; (or its lighter version&#xA;&lt;a href=&#34;https://k3s.io/&#34;&gt;k3s&lt;/a&gt; perfect for raspberry pis :-)). But the reality&#xA;is that I don&amp;rsquo;t really need that level of complexity for what i&amp;rsquo;m doing&#xA;and I&amp;rsquo;m not a devops / sysadmin&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt; at my job so it wouldn&amp;rsquo;t help on&#xA;my day to day job either to learn it.&lt;/p&gt;&#xA;&lt;p&gt;The other choice was &lt;a href=&#34;https://docs.docker.com/engine/swarm/&#34;&gt;Docker Swarm&lt;/a&gt;, which after reading about it seemed so much simpler than&#xA;Kubernetes. It also seems that it is not that much use in big or complex&#xA;architecture (at least not at K8s scale) but seems to do more than the&#xA;job for my small and limited use case of homemade selfhoster :-).&lt;/p&gt;&#xA;&lt;p&gt;So I made the choice of Docker Swarm last December&amp;hellip;&lt;/p&gt;&#xA;&lt;h4 id=&#34;shared-file-system-glusterfs&#34;&gt;Shared File System: GlusterFS&lt;/h4&gt;&#xA;&lt;p&gt;Of course, the main issue when you talk about containers architecture is&#xA;storage. When I was doing it the poorsman&amp;rsquo;s way&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt; (aka, containers&#xA;started via docker-compose command on the host directly), it was easy to&#xA;bypass this issue by just using the local storage.&lt;/p&gt;&#xA;&lt;p&gt;When you move to a real cluster architecture, meaning multiple servers,&#xA;then you need to have a shared storage between these servers. And it&amp;rsquo;s&#xA;better if the storage is on a dedicated drive&amp;hellip; This is why I purchased&#xA;4 100GB usb keys, to use them as a shared storage.&lt;/p&gt;&#xA;&lt;p&gt;Now for the technology itself, I went with&#xA;&lt;a href=&#34;https://www.gluster.org/&#34;&gt;GlusterFS&lt;/a&gt;: &amp;gt; Gluster is a free and open&#xA;source software scalable network filesystem.&lt;/p&gt;&#xA;&lt;p&gt;By using Gluster, I can create a shared folder (so all the usb keys will&#xA;have a copy of it) and make sure that data are up to date on all&#xA;raspberry pis :).&lt;/p&gt;&#xA;&lt;p&gt;I use it both to store services definition (&lt;code&gt;docker-compose.yml&lt;/code&gt;) and&#xA;services data.&lt;/p&gt;&#xA;&lt;h2 id=&#34;to-be-continued-dot-dot-dot&#34;&gt;To be Continued&amp;hellip; :-)&lt;/h2&gt;&#xA;&lt;p&gt;To avoid having way too long blog post, I&amp;rsquo;ll stop here for now that we&#xA;have an idea of what will be the setup of my home lab! Next we&amp;rsquo;ll go to&#xA;actual setup of docker, docker-compose, docker-swarm and glusterFS.&lt;/p&gt;&#xA;&lt;div class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;&#xA;&lt;hr&gt;&#xA;&lt;ol&gt;&#xA;&lt;li id=&#34;fn:1&#34;&gt;&#xA;&lt;p&gt;A good proof ot that is the &lt;a href=&#34;https://kalliope-project.github.io/neurons_marketplace.html&#34;&gt;number of neuron&lt;/a&gt; I&amp;rsquo;ve created for &lt;a href=&#34;https://kalliope-project.github.io/&#34;&gt;Kalliope&lt;/a&gt; over time :)&amp;#160;&lt;a href=&#34;#fnref:1&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:2&#34;&gt;&#xA;&lt;p&gt;I&amp;rsquo;m just an enthusiast selfhoster as a hobby, not a professional,&#xA;which explains why I really don&amp;rsquo;t know what I&amp;rsquo;m talking about&#xA;:-).&amp;#160;&lt;a href=&#34;#fnref:2&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li id=&#34;fn:3&#34;&gt;&#xA;&lt;p&gt;Not meant in a wrong way, but the way I was doing it was more the&#xA;level 1 of managing docker container. I&amp;rsquo;m not saying I moved to&#xA;10 and achieve perfection, but I feel I&amp;rsquo;m more at 4 or 5 now :P&amp;#160;&lt;a href=&#34;#fnref:3&#34; class=&#34;footnote-backref&#34; role=&#34;doc-backlink&#34;&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/div&gt;&#xA;</description></item>
  </channel>
</rss>
