This page provides an overview of AIStor Server deployment architectures from a production perspective. A production AIStor Server deployment consists of at least 4 hosts with homogeneous storage and compute resources. Each AIStor Server host in this pool has matching compute, storage, and network configurations These hosts make up a server pool, where the AIStor Server presents the aggregated compute, memory, and storage as a single resource to clients. Each pool consists of one or more erasure sets

Distributed AIStor deployments rely on Erasure Coding to provide built-in tolerance for multiple drive or node failures. Depending on the deployment topology and the selected erasure code parity, AIStor can tolerate the loss of up to half the drives or nodes in the deployment while maintaining read access (“read quorum”) to objects. For Kubernetes deployments, you can further enhance fault tolerance by configuring spread zones to distribute pods across different failure domains, such as racks or availability zones.

The AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The keyrotate batch job type cycles the SSE-S3 or SSE-KMS keys for encrypted objects on an AIStor deployment. The YAML configuration supports filters to restrict key rotation to a specific set of objects by creation date, tags, metadata, or kms key. You can also define retry attempts or set a notification endpoint and token.

Syntax The mc admin uncordon command returns a cordoned node to active service after maintenance. This command notifies all other nodes in the cluster that the specified node is returning to service. When you run mc admin uncordon, the command: Removes the node from the cluster’s internal list of cordoned nodes. Notifies all peer nodes that the target node is returning to service. Allows peer nodes to re-establish grid connections to the node. See Node Maintenance for a complete procedure on cordoning and uncordoning nodes.

Use mc admin maintenance hosts to create lists of maintenance groups. The command generates lists of hosts that do not share erasure sets. Hosts that do not share a erasure sets can go into maintenance at the same time without causing service disruptions. Syntax The mc admin maintenance hosts command DESCRIPTION

AIStor supports publishing audit logs to one or more configured Apache Kafka receivers. AIStor send an event for each API operation to the receiver for processing and storage. The receiver is responsible for correctly processing events, including returning 200OK or similar success messages upon receipt of the event. AIStor cannot recover events that were successfully sent but not correctly stored on the receiver. You can configure a new Kafka audit endpoint using either environment variables or runtime configuration settings. If you configure both, AIStor uses the environment variables.

The mc admin cluster iam import command imports IAM metadata as created by the mc admin cluster iam export command. You can use this command to manually restore IAM metadata settings for an AIStor deployment. The command outputs the results of the import, including the following: count of individual entities imported by entity type list of policies imported by entity type they imported to list of entities that failed to import Syntax Example The following command imports the IAM metadata of the specified file onto the myaistor deployment.

The mc admin scanner status command displays a real-time summary of scanner information for an AIStor Server. This command has an alias of mc admin scanner info. Syntax Example The following example returns information about the current state of the scanner process.

The mc anonymous set command sets anonymous (that is, unauthenticated or public) access policies for a bucket. Buckets with anonymous policies allow clients to access the bucket contents and perform actions consistent with the specified policy without authentication. To set anonymous bucket policies using an IAM JSON policy, use the mc anonymous set-json command. Syntax Example The following command sets the anonymous access policy for the mydata bucket on the myaistor AIStor deployment:

Description The mc anonymous command supports setting or removing anonymous policies to a bucket and its contents. Buckets with anonymous policies allow public access where clients can perform any action granted by the policy without authentication. Subcommands mc anonymous includes the following subcommands: