b3b90caabe
Several updates for the MinIO Console docs related to [v0.22.2](https://github.com/minio/console/releases/tag/v0.22.2) and [v0.22.3](https://github.com/minio/console/releases/tag/v0.22.3). Also takes the opportunity to break up the Console doc and remove screenshots. - Splits MinIO Console doc into three separate pages - Removes screenshots from console pages - Adds toctree to MinIO Console page and references to new pages Closes #709 - Adds OIDC and LDAP sections to console Closes #683 - Adds details on object browser (now separated out from bucket browser) Closes #686
4.2 KiB
SUBNET Registration and Support
minio
Table of Contents
You can use the MinIO Console to perform several of the license and subscription related functions available in MinIO, such as:
- View the license you are currently using for your MinIO deployment.
- Subscribe to |SUBNET|.
- Manage the deployment's SUBNET license.
- Access Support tools for sharing with MinIO Engineering.
License
MinIO offers two licensing options:
- Open source with the
GNU AGPLv3 license <mc/blob/master/LICENSE> - Paid commercial license with included support direct from MinIO Engineers
This page shows the current license status of the deployment. You can also begin the registration process to sign up for a paid subscription or add the deployment to an existing subscription.
Deployments licensed under AGPLv3 must comply to the terms of the license. MinIO cannot make the determination as to whether your application's usage of MinIO is in compliance with the AGPLv3 license requirements. You should instead rely on your own legal counsel or licensing specialists to audit and ensure your application is in compliance with the licenses of MinIO and all other open-source projects with which your application integrates or interacts.
MinIO Commercial Licensing is the best option for applications which trigger AGPLv3 obligations (for example, open sourcing your application). Applications using MinIO — or any other OSS-licensed code — without validating their usage do so at their own risk.
Support
Proprietary application stacks that register for a commerical license
choose engineering support under either the Standard or Enterprise License and
Support plans. Both support plans share the same commercial license to
MinIO.
The Support
section provides an interface for generating health and performance
reports. Support functionality requires registering your deployment with
|subnet|. Unregistered deployments
display a Register Your Cluster button to register with
your |subnet| account. See the License section in the
Console or visit the MinIO SUBNET
<https://min.io/pricing?jmp=docs> website for more
information on registration.
This section contains several subsections.
Health
The Health
section provides an interface for running a health diagnostic for the
MinIO Deployment.
The resulting health report is intended for use by MinIO Engineering via |subnet| and may contain internal or private data points such as hostnames. Exercise caution before sending a health report to a third party or posting the health report in a public forum.
Performance
The Performance
section provides an interface for running a performance test of the
deployment. The resulting test can provide a general guideline of
deployment performance under S3 GET and PUT
requests.
For more complete performance testing, consider using a combination
of load-testing using your staging application environments and the
MinIO WARP <warp> tool.
Profile
The Profile
section provides an interface for running system profiling of the
deployment. The results can provide insight into the MinIO server
process running on a given node.
The resulting report is intended for use by MinIO Engineering via |subnet|. Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk.
Inspect
The Inspect
section provides an interface for capturing the erasure-coded metadata
associated to an object or objects. MinIO Engineering may request this
output as part of diagnostics in |subnet|.
The resulting object may be read using MinIO's debugging tool <minio/tree/master/docs/debugging#decoding-metadata>.
Independent or third-party use of the output for diagnostics or
remediation is done at your own risk. You can optionally encrypt the
object such that it can only be read if the generated encryption key is
included as part of the debugging toolchain.