MEMSQL-DEPLOY

On this page

Deploy a SingleStore node (Master Aggregator, child aggregator or leaf) into a specific host where MemSQL Ops is installed.

Usage

usage: memsql-ops memsql-deploy [--settings-file SETTINGS_FILE] [--async]
                                [-a AGENT_ID] [-r {leaf,aggregator,master}]
                                [-P PORT] [-L LICENSE | --developer-edition]
                                [--version-hash VERSION_HASH]
                                [--redundancy-level {1,2}]
                                [--availability-group {1,2}]

Deploy a SingleStore node.

optional arguments:
  --settings-file SETTINGS_FILE
                        A path to a MemSQL Ops settings.conf file. If not set,
                        we will use the file in the same directory as the
                        MemSQL Ops binary.
  --async               If this option is true, we will exit without waiting
                        for SingleStore to be fully deployed.
  -a AGENT_ID, --agent-id AGENT_ID
                        The MemSQL Ops agent ID to use. Defaults to the
                        locally running agent if available.
  -r {leaf,aggregator,master}, --role {leaf,aggregator,master}
                        The role of the SingleStore node.
  -P PORT, --port PORT  The port to use for this SingleStore node.
  -L LICENSE, --license LICENSE
                        The license key to use.
  --developer-edition   Whether or not to use the Developer Edition of SingleStore.
  --version-hash VERSION_HASH
                        A SingleStore version hash to use.
  --redundancy-level {1,2}
                        What redundancy level to run this SingleStore node in. This
                        is only applicable when deploying a master aggregator
                        and it is only available to users with Enterprise
                        licenses.
  --availability-group {1,2}
                        Which availability group to run this SingleStore node in.
                        This is only applicable when deploying a leaf node and
                        it is only available to users with Enterprise
                        licenses.

Last modified: April 25, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK