Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 22 for tenant (0.05 sec)

  1. docs/multi-tenancy/README.md

    ## 1. Standalone Deployment
    
    To host multiple tenants on a single machine, run one MinIO Server per tenant with a dedicated HTTPS port, configuration, and data directory.
    
    ### 1.1 Host Multiple Tenants on a Single Drive
    
    Use the following commands to host 3 tenants on a single drive:
    
    ```sh
    minio server --address :9001 /data/tenant1
    minio server --address :9002 /data/tenant2
    minio server --address :9003 /data/tenant3
    ```
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 29 04:28:45 UTC 2022
    - 3K bytes
    - Viewed (0)
  2. docs/orchestration/README.md

    MinIO is built ground up on the cloud-native premise. With features like erasure-coding, distributed and shared setup, it focuses only on storage and does it very well. While, it can be scaled by just replicating MinIO instances per tenant via an orchestration platform.
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 29 04:28:45 UTC 2022
    - 2.2K bytes
    - Viewed (0)
  3. SECURITY.md

    tenant isolation, resource allocation, model sharing and hardware attacks.
    
    ### Tenant isolation
    
    Since any tenants or users providing models, graphs or checkpoints can execute
    code in context of the TensorFlow service, it is important to design isolation
    mechanisms that prevent unwanted access to the data from other tenants.
    
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Wed Oct 16 16:10:43 UTC 2024
    - 9.6K bytes
    - Viewed (0)
  4. docs/orchestration/kubernetes/README.md

    MinIO is a high performance distributed object storage server, designed for large-scale private cloud infrastructure. MinIO is designed in a cloud-native manner to scale sustainably in multi-tenant environments. Orchestration platforms like Kubernetes provide perfect cloud-native environment to deploy and scale MinIO.
    
    ## MinIO Deployment on Kubernetes
    
    There are multiple options to deploy MinIO on Kubernetes:
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 29 04:28:45 UTC 2022
    - 1.6K bytes
    - Viewed (0)
  5. docs/distributed/DECOMMISSION.md

    - On Operator based MinIO deployments, you need to modify the `tenant.yaml` specification and modify the `pools:` section from two entries to a single entry. After making relevant changes, proceed to execute `kubectl apply -f tenant.yaml`.
    
    > Without a 'Complete' status any 'Active' or 'Draining' pool(s) are not allowed to be removed once configured.
    
    ## NOTE
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Jul 11 14:59:49 UTC 2022
    - 8.3K bytes
    - Viewed (0)
  6. docs/distributed/README.md

    Install MinIO on Kubernetes:
    
    - [MinIO Quickstart Guide for Kubernetes](https://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes).
    - [Deploy a Tenant from the MinIO Operator](https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-minio-tenant.html)
    
    Install Distributed MinIO on Linux:
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Jan 18 07:03:17 UTC 2024
    - 8.8K bytes
    - Viewed (0)
  7. docs/minio-limits.md

    # MinIO Server Limits Per Tenant
    
    For optimal production setup MinIO recommends Linux kernel version 4.x and later.
    
    ## Erasure Code (Multiple Drives / Servers)
    
    | Item                                                            | Specification |
    |:----------------------------------------------------------------|:--------------|
    | Maximum number of servers per cluster                           | no-limit      |
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Jan 18 07:03:17 UTC 2024
    - 5.9K bytes
    - Viewed (0)
  8. docs/fr/docs/history-design-future.md

    J'ai évité la création d'un nouveau framework pendant plusieurs années. J'ai d'abord essayé de résoudre toutes les fonctionnalités couvertes par **FastAPI** en utilisant de nombreux frameworks, plug-ins et outils différents.
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Mon Jul 29 23:35:07 UTC 2024
    - 4.9K bytes
    - Viewed (0)
  9. docs/fr/docs/deployment/https.md

    class="external-link" target="_blank">https://howhttps.works/</a>.
    
    Maintenant, du point de vue d'un développeur, voici plusieurs choses à avoir en tête en pensant au HTTPS :
    
    * Pour le HTTPS, le serveur a besoin de "certificats" générés par une tierce partie.
        * Ces certificats sont en fait acquis auprès de la tierce partie, et non "générés".
    * Les certificats ont une durée de vie.
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 4.1K bytes
    - Viewed (0)
  10. docs/fr/docs/tutorial/query-params.md

    Mais quand on les déclare avec des types Python (dans l'exemple précédent, en tant qu'`int`), elles sont converties dans les types renseignés.
    
    Toutes les fonctionnalités qui s'appliquent aux paramètres de chemin s'appliquent aussi aux paramètres de requête :
    
    * Support de l'éditeur : vérification d'erreurs, auto-complétion, etc.
    * <abbr title="conversion de la chaîne de caractères venant de la requête HTTP en données Python">"Parsing"</abbr> de données.
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Oct 27 17:06:01 UTC 2024
    - 5.6K bytes
    - Viewed (0)
Back to top