Software checklist
Use the following checklist when planning the software configuration for a production, distributed MinIO deployment.
AIStor pre-requisites
| Description | |
|---|---|
| ☐ | Servers running a Linux operating system with a 5.x+ kernel, such as Red Hat Enterprise Linux (RHEL) 9 or Ubuntu LTS 20.04+. Ensure the chosen OS uses LTS and in-support releases of the Linux Kernel 5.x or 6.x series. |
| ☐ | A method to synchronize time servers across nodes, such as with ntp, timedatectl or timesyncd.The method to use varies by operating system. Check with your operating system’s documentation for how to synchronize time with a time server. |
| ☐ | Disable system services that index, scan, or audit the filesystem, system-level calls, or kernel-level calls. These services can reduce performance due to resource contention or interception of AIStor operations. MinIO strongly recommends uninstalling or disabling the following services on hosts running AIStor: - mlocate or plocate- updatedb- auditd- Crowdstrike Falcon - Antivirus software ( clamav)The above list represents the most common services or softwares known to cause performance or behavioral issues with high performance systems like AIStor. Consider removing or disabling any other service or software which functions similarly to those listed above on AIStor hosts. Alternatively, configure these services to ignore or exclude the AISTOR process and all drives or drive paths accessed by AISTOR. |
| ☐ | System administrator access to the remote servers |
| ☐ | A management tool for distributed systems, such as Ansible, Terraform, or Kubernetes for orchestrated environments. Kubernetes infrastructures should use the MinIO Operator for best results. |
| ☐ | Load balancer to handle routing of requests (for example, NGINX) |
| ☐ | [Prometheus](# relref “/operations/monitoring/metrics-and-alerts/collect-minio-metrics-using-prometheus#minio-metrics-collect-using-prometheus” %}}) or a Prometheus-compatible setup for monitoring and metrics |
| ☐ | Grafana or similar Prometheus-compatible visual dashboard |
| ☐ | (Optional) mc installed on the local host system |
AIStor install
Install a matching version of AIStor across all nodes in the deployment.
Post-install tasks
| Description | |
|---|---|
| ☐ | (Optional) Create an mc alias for each server with mc alias set from your local machine for command line access to work with the AIStor Server from a local machine |
| ☐ | Configure Bucket replication to duplicate contents of a bucket to another bucket location |
| ☐ | Configure Site replication to synchronize contents of multiple dispersed data center locations |
| ☐ | Configure Object retention rules with lifecycle management to manage when objects should expire |
| ☐ | Configure Object storage level rules with tiering to move objects from the AIStor Server nodes to a warm or cold storage location, maximizing storage cost efficiencies |
3rd party identity provider tasks
| Description | |
|---|---|
| ☐ | Authenticate to AIStor with Security Token Service (STS) Enabling this requires MinIO support through SUBNET. |