Skip to content

Instantly share code, notes, and snippets.

@nitisht
Forked from mrmrcoleman/Minio Announcement
Last active February 5, 2017 06:14
Show Gist options
  • Save nitisht/1e66160a46064b8ababfe38540d56041 to your computer and use it in GitHub Desktop.
Save nitisht/1e66160a46064b8ababfe38540d56041 to your computer and use it in GitHub Desktop.
Minio_Hyper.sh_Announcement

Introducing Minio: Run your own S3 compatible cloud storage on Hyper.sh!

Storage has been long thought of as a complex, difficult to setup system. Even after the advent of quick deployment mechanisms like containers, problem somewhat persisted because of ephemeral nature of containers - it seemed counter-intuitive to store mission critical data on something that itself is supposed to be disposable.

Minio is an open source, S3 compatible, cloud-native object storage server, that makes storage as easy as launching a Docker container. On Hyper.sh, Minio servers are backed by Hyper.sh volumes that make sure, even if a container running Minio server goes down, the data is safe in the volume. As a true cloud-native application, Minio scales very well in a multi-tenant cloud environment.

Docker containers provide isolated environment for application execution, Hyper.sh enables effortless scaling by running multiple instances of these isolated applications. To scale Minio as per your storage needs, you can easily spawn one Minio instance per tenant using Hyper.sh Compose files. This makes a sustainable and limited error domain scaling plan.

Some of our users have been using Minio for a while. But, we've had other users asking for something similar, unaware that Minio existed.

To address this problem we joined forces with the Minio team to officialize the Minio deployment template.

Why use Minio?

There are two main reasons why people have been using Minio on Hyper.sh:

  1. Total control over object store configuration.
  2. True cloud-native scalability with a Minio instance running for each tenant.
  3. Easy to setup and deploy.

How to use Minio?

Minio team helped us create these three reference Hyper Compose files for small, medium and large configurations*.

Small - link

Medium - link

Large - link

* To increase or decrease the addressable storage space, see the commands below.,

Note that, you'll first you need to create the storage volumes that Minio will uses as backend storage.

For example,

hyper volume create --name minio-disk-1 --size=50
hyper volume create --name minio-disk-2 --size=50
hyper volume create --name minio-disk-3 --size=50
hyper volume create --name minio-disk-4 --size=50

This will create 4 volumes which in this case are each 50GB in size which will be treated as a storage pool for Minio to use. After that it is as simple as saving one of the above three compose files locally and running:

hyper compose up -f <YOUR COMPOSE FILE>

That's it!

With Minio it really is that simple, and we're very pleased to be working with them to bring this functionality to the Hyper.sh platform.

We are always looking for feedback.

  • Does this solve a problem for you?
  • Are there any tools that you think we should be working more closely with?
  • Are there any features that you think are currently missing from Hyper.sh?

To let us know you can always contact us on the in-console support chat, or on the forum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment