Variables should be defined before their use

Docker extension API reference

AIStor supports publishing bucket notification events to a MySQL service endpoint. AIStor supports MySQL 5.7.8 and later only. Prerequisites MySQL 5.7.8 and later AIStor relies on features introduced with MySQL 5.7.8. The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.

The mc admin user sts info command retrieves information on the specified STS credential, such as the parent AIStor user who generated the credentials, associated policies, and expiration. Credentials provide temporary access to the AIStor deployment. Syntax Example The following command retrieves information on the STS credentials with specified access key:

The mc admin user disable command disables an AIStor user on the target AIStor deployment. Clients cannot use the user credentials to authenticate to the AIStor deployment. Disabling a user does not remove that user from the deployment. Use mc admin user enable to enable a disabled user on an AIStor deployment. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command disables user myuser on the myaistor AIStor deployment:

The mc admin user ls command lists all AIStor users on the target AIStor deployment. The mc admin user list command has equivalent functionality to mc admin user ls. mc admin user ls does not return the access key or secret key associated to a user. Use mc admin user info to retrieve detailed user information, including the user access key. To manage external Identity Provider users, see OIDC or AD/LDAP.

This page documents the steps necessary to initialize site replication between two AIStor deployments. The procedures assume at least two existing AIStor installations. Only one of the two sites can have any data at the time of setup. All other sites must be empty of buckets and objects. All sites must otherwise having the following matching configurations: AIStor Server version Key Management Server for Server-Side Encryption Identity Manager Ensure each peer site has a Load Balancer, Reverse Proxy, or similar network control plane component to handle routing connections to its AIStor Server nodes. Using a single node hostname for a peer site creates a single point of failure for site replication where replication can fail if that single node goes down.

The mc admin accesskey create command adds a new access key and secret key pair for an existing AIStor user. Syntax Example The following command creates a new access key associated to an existing AIStor user:

Drive type MinIO recommends using flash-based storage (NVMe or SSD) for all workload types at any scale. Workloads that require high performance should prefer NVMe over SSD. For best performance, use 30+TB drives with NVMe over PCIe 4.0 or 5.0. Directly attached storage For best performance, provide AIStor with drives attached directly to each host node as a JBOD array with no RAID or similar management layers. AIStor requires the XFS filesystem for best performance and behavior at scale. Using any other type of backing storage (SAN/NAS, ext4, RAID, LVM) typically results in a reduction in performance, reliability, predictability, and consistency.

tutorial: Tutorial === Why +OptionParser+? When a Ruby program executes, it captures its command-line arguments and options into variable ARGV. ruby argv.