The following procedure adds a server pool to an existing AIStor cluster running on bare-metal infrastructure. Each pool expands the total available storage capacity of the cluster while maintaining the overall availability of the cluster. A new pool is a set of new nodes and drives that meet the cluster’s erasure set requirements and parity levels. You can use MinIO’s Erasure Code Calculator to check the Erasure Code Stripe Size (K+M) of your new pool to confirm that it meets the EC:M value of current cluster. MinIO strongly recommends seeking an architecture review from MinIO Engineering through SUBNET to analyze potential performance impacts before committing to a new pool for your cluster.

This page documents upgrade procedures for AIStor Server deployments on bare-metal Linux infrastructure. All AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Upgrade AIStor using DEB or RPM Use these steps to upgrade an AIStor deployment where the server process is managed by systemctl, such as those created using the AIStor DEB/RPM packages.

The following procedures decommissions one or more pools on a Linux bare-metal deployment. Review the AIStor deployment topology The mc admin decommission command returns a list of all pools in the AIStor deployment: mc admin decommission status myaistor The command returns output similar to the following: ┌─────┬──────────────────────────────────────────────────────────────────┬──────────────────────────────────┬────────┐ │ ID │ Pools │ Capacity │ Status │ │ 1st │ https://aistor-{01...04}.example.com:9000/mnt/disk{1...4}/aistor │ 10 TiB (used) / 10 TiB (total) │ Active │ │ 2nd │ https://aistor-{05...08}.example.com:9000/mnt/disk{1...4}/aistor │ 60 TiB (used) / 100 TiB (total) │ Active │ │ 3rd │ https://aistor-{09...12}.example.com:9000/mnt/disk{1...4}/aistor │ 40 TiB (used) / 100 TiB (total) │ Active │ └─────┴──────────────────────────────────────────────────────────────────┴──────────────────────────────────┴────────┘ The example deployment above has three pools. Each pool has four servers with four drives each.

AIStor bucket notifications allow administrators to send notifications to supported external services when events occur on objects or buckets, similar to Amazon S3 Event Notifications. This page lists supported event types that trigger notifications, including bucket-level and object-level S3 events. Supported notification targets AIStor supports publishing event notifications to the following targets:

Description The mc admin group command manages groups on an AIStor deployment. A group is a collection of users. Each group can have one or more assigned policies that explicitly list the actions and resources to which group members are allowed or denied access. Groups provide a simplified method for managing shared permissions among users with common access patterns and workloads.

The mc du command summarizes the disk usage of buckets and folders. You can also use mc du against the local filesystem to produce similar results as the du command. Syntax Example The following command prints the disk usage of the mybucket bucket on the myaistor AIStor deployment:

The mc admin kms key command performs cryptographic key management operations through the AIStor Key Encryption Service (KES). Syntax mc admin kms key create Creates a new master key on a Key Management System (KMS).

Description The mc alias commands provide a convenient interface for managing the list of S3-compatible hosts that mc can connect to and run operations against. Subcommands mc alias includes the following subcommands:

Returns the specified policy in JSON format if it exists on the target AIStor deployment. Syntax Example The following command returns the policy readonly in JSON format from the deployment at alias myaistor.

The mc admin user command and its subcommands manage AIStor users. Clients must authenticate to the AIStor deployment with the access key and secret key associated to a user on the deployment. AIStor users constitute a key component in AIStor Identity and Access Management. To manage users who authenticate using a third-party IDP, use the command for the appropriate provider: For AD/LDAP, use mc idp ldap For OpenID Connect (OIDC) compatible providers, use mc idp openid Subcommands mc admin user includes the following subcommands: