The mc admin user enable command enables an AIStor user on the target AIStor deployment. Clients can only use enabled users to authenticate to the AIStor deployment. Users created using mc admin user add are enabled by default. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command enables user myuser on the myaistor AIStor deployment:

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.

Run a command from a local or remote npm package

Why, What & How We Log

This page documents environment variables that manage OpenTelemetry-formatted trace information. Trace capture can support ongoing troubleshooting and diagnostics with MinIO Engineering. The information can be relayed to a specified collector, recorded to a local encrypted or unencrypted file, or replayed from a local file to a collector. You can also run the mc support telemetry commands for some of these settings. MINIO_TELEMETRY_TARGET_ENABLE Enable (or disable) telemetry collection on a specified target.

The mc tag set command sets one or more tags to a bucket or object. AIStor supports adding up to 10 custom tags to an object. Example The following command sets tags for the mydata bucket on the myaistor AIStor deployment: mc tag set myaistor/mydata "tag1=value1&tag2=value2" Syntax The command has the following syntax:

Log out of the registry

NEWS-3.1.0: NEWS for Ruby 3. This document is a list of user-visible feature changes since the **3.

Retrieve funding information

The following section documents environment variables for configuring AIStor to publish audit logs to a Kafka broker. The top-level configuration key for defining a Kafka broker target for publishing AIStor audit logs. Example Environment Variables export MINIO_AUDIT_KAFKA_BROKERS="https://kafka-endpoint.example.net:9092" Configuration Settings Use mc admin config set to set or update a Kafka audit target. Specify additional optional arguments as a whitespace (" ")-delimited list.