I wanted to follow-up on my recent Minio S3 post with steps on how to implement a reverse-proxy using Nginx. The purpose of this is to allow an end-user to connect to a single Minio server, and have that connection be redirected in a round-robin fashion to all of my other 16 Minio servers in my Minio S3 deployment. This was surprisingly very straight-forward, and only required a handful of changes to my nginx.conf file. If you want to review the initial deployment steps, you can find these here in my original post. Let’s go through the steps to set…
Some time back, I looked at what it would take to run a container based Minio S3 object store on top of vSAN. This involved using our vSphere Docker Volume Server (aka Project Hatchway, and the details can be found here. However, I wanted to evaluate what it would take to scale out the Minio S3 object store on top of vSAN, paying particular attention to features like distribution and availability, and to examine the various data services that can be provided by both vSAN and Minio. I also wanted to take advantage of the new host-pinning feature in vSAN…
While we are always looking at what other data services vSAN could provide natively, at the present moment, there is no native way to host S3 compatible storage on vSAN. After seeing the question about creating an S3 object store on vSAN raised a few times now, I looked into what it would take to have an S3 compatible store running on vSAN. A possible solution, namely Minio, was brought to my attention. While this is by no means an endorsement of Minio, I will admit that it was comparatively easy to get it deployed. Since the Minio Object Store…