diff --git a/source/concepts/erasure-coding.rst b/source/concepts/erasure-coding.rst index 9cf64bce..b2487431 100644 --- a/source/concepts/erasure-coding.rst +++ b/source/concepts/erasure-coding.rst @@ -52,7 +52,6 @@ Zero-Parity Deployments ----------------------- Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, MinIO supports a Single-Node Single-Drive (SNSD) topology with a zero-parity erasure coding backend. -This provides access to erasure coding features while deferring any and all drive-level resiliency to the underlying storage volume. Zero-parity deployments necessarily depend on the underlying storage for resiliency and availability. Erasure Coding protections and behavior do not apply to |SNSD| deployments. diff --git a/source/installation/deploy-minio-standalone.rst b/source/installation/deploy-minio-single-node-single-drive.rst similarity index 93% rename from source/installation/deploy-minio-standalone.rst rename to source/installation/deploy-minio-single-node-single-drive.rst index 84c24d28..17269561 100644 --- a/source/installation/deploy-minio-standalone.rst +++ b/source/installation/deploy-minio-single-node-single-drive.rst @@ -1,6 +1,6 @@ -===================================== -Deploy Single-Node Single-Drive MinIO -===================================== +======================================== +Deploy MinIO as Single-Node Single-Drive +======================================== .. default-domain:: minio @@ -27,19 +27,17 @@ Use an earlier version of MinIO to retain the legacy filesystem-access behavior. .. admonition:: MinIO Avoids Root Disks :class: important - MinIO by default avoids using the root OS disk as part of startup and returns an error if the specifid path is part of the root disk. + By default MinIO returns an error if the specified path is part of the root or OS drive. - You can specify the environment variable ``MINIO_CI_CD=1`` to allow using root disks. - - This variable is intended primarily for CI/CD environments or local testing/evaluation. - MinIO does not support usage outside of those specific use cases. + Specify the environment variable ``MINIO_CI_CD=1`` to direct MinIO to use the root disk in CI/CD environments or for local testing and evaluation. + MinIO does not support usage of this environment variable outside of these use cases. .. _deploy-minio-standalone: -Deploy Single-Node Single-Drive MinIO on Baremetal --------------------------------------------------- +Deploy Single-Node Single-Drive MinIO +------------------------------------- -The following procedure deploys MinIO consisting of a single MinIO server and a single drive or storage volume. Standalone deployments are best suited for evaluation and initial development environments. +The following procedure deploys MinIO consisting of a single MinIO server and a single drive or storage volume. .. admonition:: Network File System Volumes Break Consistency Guarantees :class: note @@ -196,12 +194,10 @@ operations against the MinIO server. .. _deploy-minio-standalone-container: -Deploy Standalone MinIO in a Container --------------------------------------- +Deploy Containerized Single-Node Single-Drive MinIO +--------------------------------------------------- The following procedure deploys a single MinIO container with a single drive. -Standalone deployments are best suited for evaluation and initial development -environments. The procedure uses `Podman `__ for running the MinIO container in rootfull mode. Configuring for rootless mode is out of scope for diff --git a/source/installation/deployment-and-management.rst b/source/installation/deployment-and-management.rst index b1d7cc9f..a3862126 100644 --- a/source/installation/deployment-and-management.rst +++ b/source/installation/deployment-and-management.rst @@ -18,18 +18,23 @@ of operating systems and architectures. MinIO supports three deployment topologies: -Single-Node Single-Drive +Single-Node Single-Drive (SNSD) A single MinIO server with a single storage volume or folder. |SNSD| deployments are best suited for evaluation and initial development of applications using MinIO for object storage. - This topology is also known as :guilabel:`Standalone Mode`. + This topology was previously referred to as :guilabel:`Standalone Mode`. - Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, |SNSD| deployments implement a zero-parity erasure coding backend and includes support for erasure-coding dependent features. - This new feature is incompatible with the older filesystem-style behavior where MinIO acted as a simple S3 API layer while allowing POSIX-style access to managed files. + Starting with :minio-release:`RELEASE.2022-06-02T02-11-04Z`, |SNSD| deployments implement a zero-parity erasure coding backend and include support for the following erasure-coding dependent features: -Single-Node Multi-Drive - A single MinIO server with four or more storage volumes. |SNMD| deployments provide drive-level reliability and failover only and are best suited for early development or small-scale storage with minimal uptime requirements. + - Versioning + - Object Locking / Retention -Multi-Node Multi-Drive + This topology is incompatible with the older filesystem-style behavior where MinIO acted as a simple S3 API layer while allowing POSIX-style access to managed files. + +Single-Node Multi-Drive (SNMD) + 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. @@ -126,7 +131,7 @@ Instead, use the :ref:`MinIO Client `, the :ref:`MinIO Console ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer. +This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and its S3-compatible API layer. For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`. diff --git a/source/quickstart/k8s.rst b/source/quickstart/k8s.rst index b31a53dd..696191d2 100644 --- a/source/quickstart/k8s.rst +++ b/source/quickstart/k8s.rst @@ -8,7 +8,7 @@ Quickstart for Kubernetes .. |OS| replace:: Kubernetes -This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer. +This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and its S3-compatible API layer. For production-ready :ref:`Distributed ` MinIO deployments on Kubernetes, use the :docs-k8s:`MinIO Kubernetes Operator <>`. diff --git a/source/quickstart/linux.rst b/source/quickstart/linux.rst index 438b29aa..248b2abd 100644 --- a/source/quickstart/linux.rst +++ b/source/quickstart/linux.rst @@ -8,7 +8,7 @@ Quickstart for Linux .. |OS| replace:: Linux -This procedure deploys a :ref:`Standalone ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer. +This procedure deploys a :ref:`Standalone ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and its S3-compatible API layer. For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`. diff --git a/source/quickstart/macos.rst b/source/quickstart/macos.rst index 73a0e4a1..8e069fd1 100644 --- a/source/quickstart/macos.rst +++ b/source/quickstart/macos.rst @@ -8,7 +8,7 @@ Quickstart for Mac OSX .. |OS| replace:: MacOS -This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer. +This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and its S3-compatible API layer. For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`. diff --git a/source/quickstart/windows.rst b/source/quickstart/windows.rst index f90b9268..e6cb5bae 100644 --- a/source/quickstart/windows.rst +++ b/source/quickstart/windows.rst @@ -8,7 +8,7 @@ Quickstart for Windows .. |OS| replace:: Windows -This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and it's S3-compatible API layer. +This procedure deploys a :ref:`Single-Node Single-Drive ` MinIO server onto |OS| for early development and evaluation of MinIO Object Storage and its S3-compatible API layer. For instructions on deploying to production environments, see :ref:`deploy-minio-distributed`.