# demo/minio > 四节点 x 四盘位的高可用 S3 对象存储集群演示；当前源码默认使用 Silo。 --- LLMS 索引： [llms.txt](/zh/llms.txt) --- `demo/minio` 配置模板演示如何部署四节点 x 四盘位、总计十六盘的高可用 S3 对象存储集群。模板沿用 MINIO 模块的兼容命名，并显式设置 `minio_type: silo`；v4.5.0 当前源码只接受这一取值，部署与移除角色也都默认使用 `silo`。删除前仍应把该值连同精确目标、集群身份和数据盘路径一并核对。 更多教程，请参考 **[MINIO](/docs/minio/)** 模块文档。 -------- ## 配置概览 - 配置名称： `demo/minio` - 节点数量： 四节点 - 配置说明：高可用多节点多盘 S3 对象存储集群演示（当前默认 Silo） - 适用系统：`el8`, `el9`, `el10`, `d12`, `d13`, `u22`, `u24`, `u26` - 适用架构：`x86_64`, `aarch64` - 相关配置：[`meta`](/docs/conf/meta/) 启用方式： ```bash ./configure -c demo/minio ``` > 备注：这是一个四节点模版，您需要在生成配置后修改其他三个节点的 IP 地址 -------- ## 配置内容 源文件地址：[`pigsty/conf/demo/minio.yml`](https://github.com/pgsty/pigsty/blob/main/conf/demo/minio.yml) ```yaml --- #==============================================================# # File : minio.yml # Desc : pigsty: 4 node x 4 disk MNMD minio clusters # Ctime : 2023-01-07 # Mtime : 2026-08-09 # Docs : https://pigsty.io/docs/minio # License : Apache-2.0 @ https://pigsty.io/docs/about/license/ # Copyright : 2018-2026 Ruohang Feng / Vonng (rh@vonng.com) #==============================================================# # One pass installation with: # ./deploy.yml #==============================================================# # 1. minio-1 @ 10.10.10.10:9000 - - (9002) svc <-x 10.10.10.9:9002 # 2. minio-2 @ 10.10.10.11:9000 -xx- (9002) svc <-x <---------------- # 3. minio-3 @ 10.10.10.12:9000 -xx- (9002) svc <-x sss.pigsty:9002 # 4. minio-4 @ 10.10.10.13:9000 - - (9002) svc <-x (intranet dns) #==============================================================# # use minio load balancer service (9002) instead of direct access (9000) # mcli alias set sss https://sss.pigsty:9002 minioadmin S3User.MinIO #==============================================================# # https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html # MINIO_VOLUMES="https://minio-{1...4}.pigsty:9000/data{1...4}/minio" all: children: # infra cluster for proxy, monitor, alert, etc... infra: { hosts: { 10.10.10.10: { infra_seq: 1 } } } # minio cluster with 4 nodes and 4 drivers per node minio: hosts: 10.10.10.10: { minio_seq: 1 , nodename: minio-1 } 10.10.10.11: { minio_seq: 2 , nodename: minio-2 } 10.10.10.12: { minio_seq: 3 , nodename: minio-3 } 10.10.10.13: { minio_seq: 4 , nodename: minio-4 } vars: minio_type: silo minio_cluster: minio minio_data: '/data{1...4}' minio_buckets: # list of minio bucket to be created - { name: pgsql } - { name: meta ,versioning: true } - { name: data } minio_users: # list of minio user to be created - { access_key: pgbackrest ,secret_key: S3User.Backup ,policy: pgsql } - { access_key: s3user_meta ,secret_key: S3User.Meta ,policy: meta } - { access_key: s3user_data ,secret_key: S3User.Data ,policy: data } # bind a node l2 vip (10.10.10.9) to minio cluster (optional) node_cluster: minio vip_enabled: true vip_vrid: 128 vip_address: 10.10.10.9 # expose minio service with haproxy on all nodes haproxy_services: - name: minio # [REQUIRED] service name, unique port: 9002 # [REQUIRED] service port, unique balance: leastconn # [OPTIONAL] load balancer algorithm options: # [OPTIONAL] minio health check - option httpchk - option http-keep-alive - http-check send meth OPTIONS uri /minio/health/live - http-check expect status 200 servers: - { name: minio-1 ,ip: 10.10.10.10 ,port: 9000 ,options: 'check-ssl ca-file /etc/pki/ca.crt check port 9000' } - { name: minio-2 ,ip: 10.10.10.11 ,port: 9000 ,options: 'check-ssl ca-file /etc/pki/ca.crt check port 9000' } - { name: minio-3 ,ip: 10.10.10.12 ,port: 9000 ,options: 'check-ssl ca-file /etc/pki/ca.crt check port 9000' } - { name: minio-4 ,ip: 10.10.10.13 ,port: 9000 ,options: 'check-ssl ca-file /etc/pki/ca.crt check port 9000' } #etcd: { hosts: { 10.10.10.10: { etcd_seq: 1 } } } #pgsql: # hosts: # 10.10.10.10: { pg_seq: 1 , pg_role: primary } # 10.10.10.11: { pg_seq: 2 , pg_role: replica } # 10.10.10.12: { pg_seq: 3 , pg_role: replica } # 10.10.10.13: { pg_seq: 4 , pg_role: replica } # vars: # pg_cluster: pgsql # pgbackrest_method: minio vars: version: v4.5.0 # pigsty version string admin_ip: 10.10.10.10 # admin node ip address region: default # upstream mirror region: default|china|europe # build a local repo without PostgreSQL packages repo_modules: infra,node repo_packages: "{{ repo_packages_default | reject('equalto', 'pgsql-utility') | list }}" repo_extra_packages: [] infra_portal: # infra services exposed via portal home : { domain: i.pigsty } # default domain name # domain names to access minio web console via nginx web portal (optional) minio : { domain: m.pigsty ,endpoint: "10.10.10.10:9001" ,scheme: https ,websocket: true } minio10 : { domain: m10.pigsty ,endpoint: "10.10.10.10:9001" ,scheme: https ,websocket: true } minio11 : { domain: m11.pigsty ,endpoint: "10.10.10.11:9001" ,scheme: https ,websocket: true } minio12 : { domain: m12.pigsty ,endpoint: "10.10.10.12:9001" ,scheme: https ,websocket: true } minio13 : { domain: m13.pigsty ,endpoint: "10.10.10.13:9001" ,scheme: https ,websocket: true } minio_endpoint: https://sss.pigsty:9002 # explicit overwrite minio endpoint with haproxy port node_etc_hosts: ["10.10.10.9 sss.pigsty"] # domain name to access minio from all nodes (required) #----------------------------------------------# # PASSWORD : https://pigsty.io/docs/setup/security/ #----------------------------------------------# grafana_admin_password: pigsty haproxy_admin_password: pigsty minio_secret_key: S3User.MinIO ... ``` -------- ## 配置解读 `demo/minio` 模板是对象存储生产部署的参考配置，展示了多节点多盘（MNMD）架构。其卷布局、HAProxy 健康检查与客户端仍使用 MinIO 兼容接口。 **关键特性**： - **多节点多盘架构**：4 节点 × 4 盘 = 16 盘纠删码组 - **L2 VIP 高可用**：通过 Keepalived 绑定虚拟 IP - **HAProxy 负载均衡**：9002 端口统一访问入口 - **细粒度权限**：为不同应用创建独立用户和存储桶 **访问方式**： ```bash # 使用 mcli 配置 S3 别名（通过 HAProxy 负载均衡） mcli alias set sss https://sss.pigsty:9002 minioadmin S3User.MinIO # 列出存储桶 mcli ls sss/ # 使用控制台 # 访问 https://m.pigsty 或 https://m10-m13.pigsty ``` **适用场景**： - 需要 S3 兼容对象存储的环境 - PostgreSQL 备份存储（pgBackRest 远程仓库） - 大数据和 AI 工作负载的数据湖 - 需要高可用对象存储的生产环境 **注意事项**： - 每个节点需要准备 4 块独立磁盘挂载到 `/data1` - `/data4` - 生产环境建议至少 4 节点以实现纠删码冗余 - VIP 需要正确配置网络接口（`vip_interface`）