---

##### GLOBAL METADATA

- meta:
    cluster: elasticsearch-ci

##### JOB DEFAULTS

- job:
    vault:
      url: https://secrets.elastic.co:8200
      role_id: 1ba1ac3e-aee4-d040-d9a3-6ae23bd2b3db
    node: "general-purpose"
    concurrent: true
    logrotate:
      daysToKeep: 30
      numToKeep: 500
      artifactDaysToKeep: 7
    parameters:
      - string:
          name: branch_specifier

    display-name: "elastic / elasticsearch # %BRANCH% - platform support"
    description: "Testing of the Elasticsearch %BRANCH% branch platform support tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:

    display-name: "elastic / elasticsearch # %BRANCH% - third party tests"
    description: "Testing of the Elasticsearch %BRANCH% branch against third-party service integrations.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Third party repository compatibility tests
          projects:

    display-name: "elastic / elasticsearch # %BRANCH% - packaging tests"
    description: "Testing of the Elasticsearch %BRANCH% branch packaging tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:

  encrypted. The encryption key has to be passed as environment variable.
- Run MinIO with KES (minio/kes) in combination with any supported KMS as
  secure key store. For example, you can run MinIO + KES + Hashicorp Vault.

> What about an exiting MinIO deployment? Can I just upgrade my cluster?

Yes, MinIO will try to transparently migrate any existing IAM data and either stores
it in plaintext (no KMS) or re-encrypts using the KMS.

|:---------------------------------------------------------------------------------------------|:------------------------------------------------------------------|
| [Hashicorp Vault](https://github.com/minio/kes/wiki/Hashicorp-Vault-Keystore)                | Local KMS. MinIO and KMS on-prem (**Recommended**)                |

## Configuring Site Replication

- Configure an alias in `mc` for each of the sites. For example if you have three MinIO sites, you may run:

```sh

case "${VERSION}" in
devtoolset-7)
  wget "http://vault.centos.org/centos/6/sclo/Source/rh/devtoolset-7/devtoolset-7-gcc-7.3.1-5.15.el6.src.rpm"
  rpm2cpio "devtoolset-7-gcc-7.3.1-5.15.el6.src.rpm" |cpio -idmv
  tar -xvjf "gcc-7.3.1-20180303.tar.bz2" --strip 1
  ;;
devtoolset-9)
  wget "https://vault.centos.org/centos/7/sclo/Source/rh/devtoolset-9-gcc-9.3.1-2.2.el7.src.rpm"

     */
    int DCERPC_FAULT_NDR = 0x000006F7;
    /**
     * Invalid tag fault code
     */
    int DCERPC_FAULT_INVALID_TAG = 0x1C000006;
    /**
     * Context mismatch fault code
     */
    int DCERPC_FAULT_CONTEXT_MISMATCH = 0x1C00001A;
    /**
     * Operation range error fault code
     */
    int DCERPC_FAULT_OP_RNG_ERROR = 0x1C010002;
    /**
     * Unknown interface fault code
     */

package jcifs.smb1.dcerpc;

/**
 * DCE/RPC error codes and fault constants for SMB1 compatibility
 */
public interface DcerpcError {

    /**
     * Generic fault code for other errors
     */
    int DCERPC_FAULT_OTHER = 0x00000001;
    /**
     * Access denied fault code
     */
    int DCERPC_FAULT_ACCESS_DENIED = 0x00000005;
    /**
     * Cannot perform operation fault code
     */