Preparing your Google Cloud account
BigAnimal requires you to check the readiness of your Google Cloud (GCP) account before you deploy your clusters. (You don't need to perform this check if you're using BigAnimal's cloud account as your deployment option.) The checks that you perform ensure that your Google Cloud account is prepared to meet your clusters' requirements and resource limits.
Before proceeding, see Understanding requirements in Google Cloud for details on planning for your clusters' requirements and resource limits in Google Cloud.
Ensure you have at least the following combined roles:
Alternatively, you can have an equivalent single role, such as:
Ensure the following Google Cloud APIs are enabled:
EDB provides a shell script, called biganimal-csp-preflight, which checks whether requirements and resource limits are met in your Google Cloud account based on the clusters you plan to deploy.
Open Google Cloud Shell in your browser.
From Google Cloud Shell, run the following command:
The required arguments are:
Argument Description <project-id> Google Cloud project ID of your BigAnimal deployment. <region> Google Cloud region where your clusters are being deployed. See Supported regions for a list of possible regions.
Possible options are:
Displays the command help.
Google Cloud instance type for the BigAnimal cluster. The help command provides a list of possible VM instance types. Choose the instance type that best suits your application and workload. Choose an instance type in the memory optimized M1, M2, or M3 series for large data sets. Choose from the compute-optimized C2 series for compute-bound applications. Choose from the general purpose E2, N2, and N2D series if you don't require memory or compute optimization.
Defines the Cluster architecture and can be
eha. See Supported cluster types for more information.
Type of network endpoint for the BigAnimal cluster, either
private. See Cluster networking architecture for more information.
Specifies region activation if no clusters currently exist in the region.
Checks if the user and subscription are correctly configured.
The behavior of the script defaults to
--onboardif you provide no other options.
For example, if you want to deploy a cluster in a Google Cloud account having an ID of
1234-5678-9012, with an instance type of
n2-standard-8, in the
us-east1region, with a
publicendpoint, and with no existing cluster deployed, run the following command:
The script displays the following output:
If any APIs are listed as not enabled, see Enabling and Disabling Services in the Google Cloud documentation to enable the required APIs.
If you need to increase your quotas, see Request a higher quota limit.