I know this has been asked several times or mentioned in several posts… but I am curious to know what people are using for shared storage on Rancher hosts in production now - and what you are planning on using when rancher 1.2 comes out in a few weeks with the new storage stuff? Especially if you are not using AWS.
Is GlusterFS really so bad that it should not be used? It seems to be one of the most advanced solutions out there with regards to being distributed and with replication. I can see some of you are using it in big setups and seem quite happy with GlusterFS.
Is an NFS setup with synched / replicated storage, with something like convoy the way to go?
What other options are there people with good experience with that they would recommend?
Any thoughts you are willing to share are welcome.
We are in Azure and using the Azure Files service for persistent storage. I posted our strategy here:
We tried using the GlusterFS/Convoy solution that was in the public catalog, but we found it was really sensitive to underlying system issues, and when it went down it would cause a cascade of stack/service failures. It just wasn’t ready for prime time.
In general in our rancher environments we avoid persistent storage for our applications. We run a couple of services like Redis and RabbitMQ which use the storage for persistence, but really do their work out of memory, so they don’t require really fast storage.
Due to the lack of mature technology in regard to container storage options, we made a decision to avoid persistent storage as part of the container platform. In order to also increase portability and be cloud IaaS agnostic, we utilize as many cloud services as we can, like CloudAMQP for RabbitaaS, Elasticsearch cloud for ES, instaclustr.com for Cassandra, elephantsql.com for Postgres, etc.
This way we can utilize different cloud vendors for the container platform, and maintain consistent configs for dependent resources.