Shulou(Shulou.com)06/02 Report--

1. Distributed advantages 1.minio distributed introduction MinIO in distributed mode allows you to merge multiple drives (even on different computers) into a single object storage server. Because the drives are distributed on multiple nodes, the distributed MinIO can withstand multiple node failures, but still ensures complete data protection.

MinIO in distributed mode can help you set up a high-availability storage system through a single object storage deployment. With distributed MinIO, you can make the best use of storage devices regardless of their location in the network.

two。 Data protection distributed MinIO uses erasure codes to provide protection against multiple node / drive failures and bit decay. Because the minimum disk required for a distributed MinIO is 4 (the same as the minimum disk required for erasure coding), the erasure code starts automatically when the distributed MinIO is started.

3. High availability if the server hosting the disk is offline, the stand-alone MinIO server will shut down. Conversely, a distributed MinIO setting with n disks will make your data secure as long as n / 2 or more disks are online. However, you need at least (n / 2 + 1) legal disks to create new objects.

For example, a 16-node distributed MinIO setup (with 16 disks per node) can continue to provide files even if up to 8 servers are offline. However, you need at least 9 servers online to create new objects.

4. Limits like MinIO in stand-alone mode, each tenant of a distributed MinIO is limited to a minimum of 2 and a maximum of 32 servers. There is no limit to the number of disks on these servers. If you need multi-tenant setup, you can easily start multiple MinIO instances managed by orchestration tools such as Kubernetes,Docker Swarm, and so on.

Note that with distributed MinIO, you can handle the number of nodes and drives as long as you comply with the limit. For example, you can have 2 nodes, 4 drives per node, 4 drives each, 2 drives each of 8 nodes, 64 drives each of 32 servers, and so on.

5. Consistency ensures that all inputs and outputs of the MinIO following a strict post-read-write and list-post-read / consistency model operate in distributed and independent modes.

2. Prerequisites for deploying MinIO using Helm Chart:

1. A K8s cluster

two。 Have helm environment

1. Deploy minio to create the pv required for minio

# vim pv1.yamlapiVersion: v1kind: PersistentVolumemetadata: name: minio-pv1spec: capacity: storage: 10Gi volumeMode: Filesystem accessModes:-ReadWriteOnce persistentVolumeReclaimPolicy: Retain hostPath: path: / helm/minio/pv1

Hostpath is used here, and the corresponding directory is created in the worker node.

two。 To install minio#, pull it locally to install helm pull stable/miniotar-zxvf minio-3.0.4.tgzhelm install minio. / minio# or install helm install minio stable/minio directly.

View pod

3. Log in to access minio default parameters:

Access the web interface

Both access Key and secret Key are defaults, as shown in the figure above

3. Gitlab and minio are associated.

Kubectl get deploy minio-oyaml view associated Key

Add to the yaml file of gitlab

Kubectl edit deploy gitlab-gitlab-ce

-name: MINIO_ACCESS_KEY valueFrom: secretKeyRef: key: accesskey name: minio- name: MINIO_SECRET_KEY valueFrom: secretKeyRef: key: secretkey name: minio

Check that the status is normal.

Log in to gotlab to create a file

Delete the original pod

Gitlab's pod takes a long time to start. When the startup is completed, you can see it in the access interface.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.