3 ms·
What are you doing for storage? We're thinking of deploying Docker Swarm where I work onto a VMWare cluster and basically the options boil down to sharing a st
by bityard 4y ago
What are you doing for storage?
We're thinking of deploying Docker Swarm where I work onto a VMWare cluster and basically the options boil down to sharing a storage volume between VMs (which vSphere makes difficult) and replicating storage across nodes with something like gluster (which drastically increases storage used and has performance implications).
- sofixa 4y ago> We're thinking of deploying Docker Swarm where I work onto a VMWare cluster IMHO that's an anti-pattern. Why would you run two orchestrators on top of one another? Containers also cause scheduling contention on the vSphere side, on top of the waste of CPU from the virtualisation layer. Unless you're in some very specific circumstances, run your container orchestrator on bare metal when on prem.
- Alir3z4 4y agoMajority of the applications are purely stateless, for a very few and apps we had to use either a shared volume/storage or simply locking to a specific node. We did first locking to specific node, but later decided to use s3fs for those kind of needs. Never needed the shared storage critically to setup anything heavy-lifting reliable. Although worth noting, from the beginning I had psql running within docker swarm as well, but it was locked to 1 node only, we had a good backup solution to spin up (tried it too) on another node quickly as well. With mode nodes in the cluster, I made the PSQL into its own machine completely separated from docker environment.