github.com/pachyderm/pachyderm@v1.13.4/doc/docs/1.10.x/deploy-manage/deploy/non-cloud-object-stores.md (about)

     1  # Deploying Pachyderm On-Premises With Non-Cloud Object Stores
     2  
     3  Coming soon.
     4  This document, when complete, will discuss common configurations for on-premises objects stores.
     5  
     6  ## General information on non-cloud object stores
     7  
     8  Please see [the on-premises introduction to object stores](../on_premises/#deploying-an-object-store) for some general information on object stores and how they're used with Pachyderm.
     9  
    10  ### EMC ECS
    11  Coming soon.
    12  
    13  ### MinIO
    14  Coming soon.
    15  
    16  ### SwiftStack
    17  Coming soon.
    18  
    19  ## Notes
    20  ### S3 API Signature Algorithms and Regions
    21  
    22  The S3 protocol has two different ways of authenticating requests through its api.
    23  `S3v2` has been [officially deprecated by Amazon](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#UsingAWSSDK-sig2-deprecation),
    24  so it's not likely that you'll run into it.
    25  You don't need to know the details of how they work
    26  (though you can follow these links, S3v2 & [S3v4](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html), if you're curious),
    27  but you may run into issues with either mismatch of the signature method or availability regions.
    28  
    29  If you have trouble getting Pachyderm to run,
    30  check your Kubernetes logs for the `pachd` pod,
    31  Use `kubectl get pods` to find the name of the `pachd` pod and
    32  `kubectl logs <pachd-pod-name>` to get the logs.
    33  
    34  If you see an error beginning with
    35  ```
    36  INFO error starting grpc server pfs.NewBlockAPIServer
    37  ```
    38  
    39  It could have either of two causes.
    40  
    41  #### Availability Region Mismatch
    42  If the error is of the form
    43  ```
    44  INFO error starting grpc server pfs.NewBlockAPIServer: storage is unable to discern NotExist errors, "The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'z1-a'" should count as NotExist
    45  ```
    46  It may be [a known issue](https://github.com/pachyderm/pachyderm/issues/3544) with hardcoded region `us-east-1` in the minio libraries.
    47  You can correct this by either using the `--isS3V2` flag on your the `pachctl deploy custom ...` command
    48  or by changing the region of your storage to `us-east-1`.
    49  
    50  #### Signature version mismatch
    51  
    52  You're not likely to run into this in an on-premises deployment
    53  unless your object store has deliberately been set up to use the deprecated `S3v2` signature or
    54  you are running your on-premises deployment against Google Cloud Storage,
    55  which is not recommended. See [Infrastructure in general](../on_premises/#infrastructure-in-general).
    56  
    57  You'll need to determine what signature algorithm your object store uses in its S3-compatible API:  `S3v2` or `S3v4`.
    58  If it's `S3V2`,
    59  you can solve this by using the `--isS3V2` flag on your the `pachctl deploy custom ...` command.
    60