minio Installation, deployment and simple use

Minio follow The minimalist Design concept of , From installation and deployment to operation, it embodies the concept of minimalism . Object storage , Take the object as the operation unit .

1 Stand alone installation

Through the following steps, you can install and run a single machine minio

1. Download from official website minio Binary ：
   Download address

2. newly build minio The installation directory , Execute the following command ：
   mkdir -p /home/minio/data

3. Upload the binary file to the installation directory , perform ：

   chmod +x minio
   export MINIO_ACCESS_KEY=minioadmin
   export MINIO_SECRET_KEY=minioadmin
   ./minio server /home/data
   

2 minio Browser interface operation

Install and start through the above simple steps minio After service ,minio Enabled web Client operation page , You can add folders and upload files through the interface , Can also pass minio Officially provided client , Carry out relevant operations through commands .

1. Sign in minio Of web page
   Interface login access_key and secret_key Respectively minioadmin、minioadmin, The service port is 9000, The service address is as follows ：
   http://10.45.156.156:9000/

2. After login, the interface is as follows ：
   

3. Click on the + Button , Can create bucket And upload files , As shown in the above figure, a test Folder and uploaded image files .

4. The interface can delete files 、 download 、 Preview and share actions , Configurable bucket access policy , If you need a web page, you can visit the address of the uploaded file , You need to set the following permissions ：
   

3 minio Cluster installation

MinIO Support single point 、 Deploy by means of distributed clusters .MinIO Distributed cluster refers to the deployment of multiple server nodes MinIO service , And build it into a distributed storage cluster , Provide standards to the outside world S3 Interface for unified access .

3.1 minio Cluster deployment mode

Cluster deployment methods are divided into the following ：

1. Deploy directly without grouping , Cluster expansion is not supported , It is generally used in a deployment scenario

2. according to server pools How to deploy , Support group expansion

Here's the second one , Support group capacity expansion , The first is less used , And can't get through minio Official Expansion .

3.2 minio Cluster deployment steps

1. Environmental statement （ Two node , Every node 4 A path ）

2. download minio Binary , And upload it to the running directory of two nodes
   Download address

mkdir -p /home/minio/run # Create directory 
wget http://dl.minio.org.cn/server/minio/release/darwin-amd64/minio # Download run file 
scp minio [email protected]:/home/minio/run/ # Copy to another node 

3. Create data directory and configuration directory , Create two nodes respectively

mkdir -p /nas/data1/minio/{
    data1,data2,data3,data4}
mkdir -p /etc/minio

4. Cluster startup file creation , Both nodes are created

Use the default port 9000,access_key and secret_key Set to minioadmin、minioadmin

vi vim /home/minio/run/start.sh # Create startup file 

The contents of the document are as follows

#!/bin/bash
export MINIO_ACCESS_KEY=minioadmin
export MINIO_SECRET_KEY=minioadmin
/home/minio/run/minio server --config-dir /etc/minio \
http://10.45.154.{179...180}/nas/data1/minio/data{1...4}

5. establish minio system service , Both nodes are created

vim /usr/lib/systemd/system/minio.service

The contents of the document are as follows

[Unit]
Description=Minio service
Documentation=https://docs.minio.io/

[Service]
WorkingDirectory=/home/minio/run/
ExecStart=/home/minio/run/start.sh

Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

6. Start cluster ,l The two nodes perform the same operation

Modify boot file permissions

chmod +x /usr/lib/systemd/system/minio.service 
chmod +x /home/minio/run/minio 
chmod +x /home/minio/run/minio-run.sh

Start cluster

systemctl daemon-reload # Reload service 
systemctl start minio   # Start the service 
systemctl enable minio  # Join auto start 

7. Through any node of ip Can be operated , It can be operated through the interface or interface , If you want balanced access , It can be done by nginx Load balancing
   Access through the following connection minio Of web Interface
   http://10.45.154.179:9000/
   Can also pass 180 Node access
   http://10.45.154.180:9000/

3.3 matters needing attention

• Cluster deployment , The corresponding data directory must be a physical disk , Startup time minio Go back and format the hard disk , It cannot be a system disk , Otherwise, the following error will be prompted

API: SYSTEM()
Time: 16:22:26 CST 11/03/2021
Error: Marking http://10.45.154.179:9000/minio/storage/nas/data1/minio/data4/v37 temporary offline; caused by Post "http://10.45.154.179:9000/minio/storage/nas/data1/minio/data4/v37/readall?disk-id=&file-path=format.json&volume=.minio.sys": dial tcp 10.45.154.179:9000: connect: connection refused (*fmt.wrapError)
       6: internal/rest/client.go:147:rest.(*Client).Call()
       5: cmd/storage-rest-client.go:151:cmd.(*storageRESTClient).call()
       4: cmd/storage-rest-client.go:523:cmd.(*storageRESTClient).ReadAll()
       3: cmd/format-erasure.go:406:cmd.loadFormatErasure()
       2: cmd/format-erasure.go:326:cmd.loadFormatErasureAll.func1()
       1: internal/sync/errgroup/errgroup.go:123:errgroup.(*Group).Go.func1()

Pay attention to installing the system , Don't make the data disk raid,minio Through error correcting code mechanism , Ensure data storage security

• Distributed Minio All nodes in need to have the same access Key and secret Secret key , So that these nodes can establish connections . To achieve this , You need to be doing minio server Before the command , First the access Key and secret Secret key export Become an environmental variable

• Distributed Minio The time difference between nodes in cannot exceed 3 second , You can use NTP To make sure the time is the same