Creating a service instance for Analytics Engine powered by Apache
Spark with the cpd-cli
service-instance
create command
After you install Analytics Engine powered by Apache
Spark, you must create at least
one Analytics Engine powered by Apache
Spark service instance in the operands project. If you are a
Cloud Pak for Data user, you can use the cpd-cli
service-instance
create command to script the process of creating
service
instances.
- Who needs to complete this task?
- To create a service instance by using the
cpd-cli, you must have the Create service instances (can_provision) permission in Cloud Pak for Data.
- When do you need to complete this task?
- Complete this task only if you want to create a service instance from the
cpd-cliby using thecpd-cli service-instance createcommand.
Alternative methods for creating a service instance
- From the web client. For more information, see Creating a service instance for Analytics Engine powered by Apache Spark from the web client.
- By using the
/v3/service_instancesREST API call. For more information, see Creating a service instance for Analytics Engine powered by Apache Spark programmatically.
Information you need to complete this task
Review the following information before you create a service instance for Analytics Engine powered by Apache Spark:
- Version requirements
-
All of the components that are associated with an instance of Cloud Pak for Data must be installed or created at the same release. For example, if Analytics Engine powered by Apache Spark is installed at Version 5.0.3, you must create the service instance at Version 5.0.3.
- Environment variables
-
The commands in this task use environment variables so that you can run the commands exactly as written.
- If you don't have the script that defines the environment variables, see Setting up installation environment variables.
- To use the environment variables from the script, you must source the environment variables
before you run the commands in this task. For example,
run:
source ./cpd_vars.sh
Before you begin
This task assumes that the following prerequisites are met:
| Prerequisite | Where to find more information |
|---|---|
| Analytics Engine powered by Apache Spark is installed. | If this task is not complete, see Installing Analytics Engine powered by Apache Spark. |
The cpd-cli command-line interface is installed on the workstation from
which you will create the service instance. |
If this task is not complete, see Setting up a client workstation. |
| You generated an API key or authorization token The API key or token must be associated
with a user who has the Create service instances
( |
If this task is not complete, see Generating an API authorization token. |
Procedure
Complete the following tasks to create a service instance:
Creating a service instance
To create a service instance:
- Change to the directory on your workstation where you want to create the JSON file that defines the service instance payload.
- Set the environment variables that are used to populate the JSON payload
for the service instance:
- Set the
INSTANCE_NAMEenvironment variable to the unique name that you want to use as the display name for the service instance:export INSTANCE_NAME="<display-name>"This name is displayed on the Instances page of the Cloud Pak for Data web client.
The display name is a
stringand can contain alphanumeric characters (a-z, A-Z, 0-9), spaces ( ), dashes (-), underscores (_), and periods (.). Make sure that you surround the display name with quotation marks, as shown in the precedingexportcommand. - Set the
INSTANCE_DESCRIPTIONenvironment variable to the description that you want to use for the service instance:export INSTANCE_DESCRIPTION="<description>"This description is displayed on the Instances page of the Cloud Pak for Data web client.
The description is a
stringand can contain alphanumeric characters, spaces, dashes, underscores, and periods. Make sure that you surround the display name with quotation marks, as shown in the precedingexportcommand. - Set the
INSTANCE_VERSIONenvironment variable to the version that corresponds to the version of Cloud Pak for Data on your cluster:export INSTANCE_VERSION=<version>Use the following table to determine the appropriate value:
Cloud Pak for Data version Service instance version 5.0.3 5.0.3 5.0.2 5.0.2 5.0.1 5.0.1 5.0.0 5.0.0 - Set the
VOLUME_NAMEenvironment variable to the name of the storage volume that you created to store the data associated with this service instance:export VOLUME_NAME=<volume-name>The volume name has the format
<namespace>::<unique-name>.
- Set the
- Create the
analytics-engine-instance.jsonpayload file:cat << EOF > ./analytics-engine-instance.json{ "addon_type": "spark", "display_name": "${INSTANCE_NAME}", "namespace": "${PROJECT_CPD_INST_OPERANDS}", "addon_version": "${INSTANCE_VERSION}", "preExistingOwner": false, "create_arguments": { "description": "${INSTANCE_DESCRIPTION}", "metadata": { "storageClass": "", "storageSize": "", "volumeName": "${VOLUME_NAME}" } } } EOFThe following environment variables use the values that are already defined in your installation environment variables script:${PROJECT_CPD_INST_OPERANDS}
- Set the
PAYLOAD_FILEenvironment variable to the fully qualified name of the JSON payload file on your workstation:export PAYLOAD_FILE=<fully-qualified-JSON-file-name> - Create the service instance from the payload
file:
cpd-cli service-instance create \ --profile=${CPD_PROFILE_NAME} \ --from-source=${PAYLOAD_FILE}
Validating that the service instance was created
To validate that the service instance was created, run the following command:
cpd-cli service-instance status ${INSTANCE_NAME} \
--profile=${CPD_PROFILE_NAME} \
--output=json
- If the command returns
PROVISIONED, the service instance was successfully created. - If the command returns
PROVISION_IN_PROGRESS, wait a few minutes and run the command again. - If the command returns
FAILED, review the pod logs for thezen-core-apiandzen-watcherpods for possible causes.
What to do next
You must give users access to the service instance. For more information, see Managing user access to instances.
You can manage your provisioned instances. For more information, see Managing provisioned instances.