MyFavMirrors
/
minio
mirror of https://github.com/minio/minio.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
minio/docs/site-replication
History
Harshavardhana dcff6c996d
fix: do not list delete-marked objects (#13864) 
delete marked objects should not be considered
for listing when listing is delimited, this issue
as introduced in PR #13804 which was mainly to
address listing of directories in listing when
delimited.

This PR fixes this properly and adds tests to
ensure that we behave in accordance with how
an S3 API behaves for ListObjects() without
versions.
 		2021-12-08 17:34:52 -08:00
..
README.md cleanup site-replication docs (#13812) 2021-12-02 13:27:01 -08:00
ldap.yaml fix: do not list delete-marked objects (#13864) 2021-12-08 17:34:52 -08:00
run-multi-site.sh fix: do not list delete-marked objects (#13864) 2021-12-08 17:34:52 -08:00
rw.json fix: site replication issues and add tests (#13861) 2021-12-08 11:50:15 -08:00

README.md

Automatic Site Replication

This feature allows multiple independent MinIO sites (or clusters) that are using the same external IDentity Provider (IDP) to be configured as replicas. In this situation the set of replica sites are referred to as peer sites or just sites. When site-replication is enabled on a set of sites, the following changes are replicated to all other sites:

  • Creation and deletion of buckets and objects
  • Creation and deletion of all IAM policies
  • Creation of STS credentials
  • Creation and deletion of service accounts (for users authenticated by an external IDP)
  • Changes to Bucket features such as:
    • Bucket Policies
    • Bucket Tags
    • Bucket Object-Lock configurations (including retention and legal hold configuration)
    • Bucket Encryption configuration

NOTE: Bucket versioning is automatically enabled for all new and existing buckets on all replicated sites.

The following Bucket features will not be replicated, is designed to differ between sites:

  • Bucket notification configuration
  • Bucket lifecycle (ILM) configuration

Pre-requisites

  • Initially, only one of the sites added for replication may have data. After site-replication is successfully configured, this data is replicated to the other (initially empty) sites. Subsequently, objects may be written to any of the sites, and they will be replicated to all other sites.
  • Replication of LDAP IDP is currently supported, support for OIDC (OpenID) is in progress.
  • All sites must have the same deployment credentials, i.e (MINIO_ROOT_USER, MINIO_ROOT_PASSWORD).
  • Removing a site is not allowed from a set of replicated sites once configured.
  • SSE-S3 or SSE-KMS encryption via KMS, all sites must have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server.

Configuring Site Replication

To configure site replication, ensure that all MinIO sites are using the same external IDP.

  • Configure an alias in mc for each of the sites. For example if you have three MinIO sites, you may run:
$ mc alias set minio1 https://minio1.example.com:9000 adminuser adminpassword
$ mc alias set minio2 https://minio2.example.com:9000 adminuser adminpassword
$ mc alias set minio3 https://minio3.example.com:9000 adminuser adminpassword

or

$ export MC_HOST_minio1=https://adminuser:adminpassword@minio1.example.com
$ export MC_HOST_minio2=https://adminuser:adminpassword@minio2.example.com
$ export MC_HOST_minio3=https://adminuser:adminpassword@minio3.example.com
  • Add site replication configuration with:
$ mc admin replicate add minio1 minio2 minio3
  • Once the above command returns success, you may query site replication configuration with:
$ mc admin replicate info minio1