mirror of
https://github.com/minio/docs.git
synced 2025-04-22 19:02:57 +03:00
c783e10594
This commit also generally cleans up the Installation docs and uses /includes/<platform>/steps-*.rst as a pattern for storing platform-specific tutorials within a single root URL. Finally, due to API rate limits, this commit adds some Makefile magic to allow skipping of sync'ing dependencies. Pass `make BUILD_DEPENDENCIES=FALSE <platform>` to skip building any deps and use what is already in the branch.
58 lines
2.5 KiB
ReStructuredText
58 lines
2.5 KiB
ReStructuredText
.. _minio-installation:
|
|
|
|
========================
|
|
Install and Deploy MinIO
|
|
========================
|
|
|
|
.. default-domain:: minio
|
|
|
|
.. contents:: Table of Contents
|
|
:local:
|
|
:depth: 1
|
|
|
|
MinIO is a software-defined high performance distributed object storage server.
|
|
You can run MinIO on consumer or enterprise-grade hardware and a variety of operating systems and architectures.
|
|
|
|
MinIO supports three deployment topologies:
|
|
|
|
Single-Node Single-Drive (SNSD or "Standalone")
|
|
A single MinIO server with a single storage volume or folder.
|
|
|SNSD| deployment provides failover protections. Drive-level reliability and failover depends on the underlying storage volume.
|
|
|
|
|SNSD| deployments are best suited for evaluation and initial development of applications using MinIO for object storage.
|
|
|
|
|SNSD| deployments implement a zero-parity erasure coding backend and include support for the following erasure-coding dependent features:
|
|
|
|
- :ref:`Versioning <minio-bucket-versioning>`
|
|
- :ref:`Object Locking / Retention <minio-object-retention>`
|
|
|
|
Single-Node Multi-Drive (SNMD or "Standalone Multi-Drive")
|
|
A single MinIO server with four or more storage volumes.
|
|
|SNMD| deployments provide drive-level reliability and failover only.
|
|
|
|
Multi-Node Multi-Drive (MNMD or "Distributed")
|
|
Multiple MinIO servers with at least four drives across all servers.
|
|
The distributed |MNMD| topology supports production-grade object storage with drive and node-level availability and resiliency.
|
|
|
|
This documentation provides instructions for |SNSD| and |SNMD| for supporting local development and evaluation of MinIO on a single host machine. For |MNMD| deployments, use the MinIO Kubernetes Operator to deploy and manage MinIO tenants in a containerized and orchestrated environment.
|
|
|
|
.. _minio-installation-platform-support:
|
|
|
|
Platform Support
|
|
----------------
|
|
|
|
MinIO provides container images at the following repositories:
|
|
|
|
- https://hub.docker.com/r/minio/minio
|
|
- https://quay.io/repository/minio/minio?tab=info
|
|
|
|
Use of MinIO images from any other repository, host, or organization is at your own risk.
|
|
|
|
The :ref:`Single-Node Single-Drive <minio-snsd>` and :ref:`Single-Node Multi-Drive <minio-snmd>` tutorials provide instructions for the `Docker <https://www.docker.com/>`__ and :podman-docs:`Podman <>` container managers.
|
|
|
|
.. toctree::
|
|
:titlesonly:
|
|
:hidden:
|
|
|
|
/operations/install-deploy-manage/deploy-minio-single-node-single-drive
|
|
/operations/install-deploy-manage/deploy-minio-single-node-multi-drive |