Installing Third-Party Software Using Bootstrap Actions

Updated on 2024-11-29 GMT+08:00

View PDF

Prerequisites

The bootstrap action script has been prepared by referring to Preparing the Bootstrap Action Script.

Adding a Bootstrap Action When Creating a Cluster

Click the Custom Config tab.
Configure the cluster software and hardware by referring to Creating a Custom Cluster.

In the Set Advanced Options area, select Configure and click Add in the Bootstrap Action area.

**Table 1** Parameters
Parameter	Description
Name	Name of a bootstrap action script The value can contain only digits, letters, spaces, hyphens (-), and underscores (_) and must not start with a space. The value can contain 1 to 64 characters. NOTE: A name must be unique in the same cluster. You can set the same name for different clusters.
Script Path	Script path. The value can be an OBS file system path or a local VM path. An OBS file system path must start with obs:// and end with .sh, for example, obs://mrs-samples/xxx.sh. A local VM path must start with a slash (/) and end with .sh. NOTE: A path must be unique in the same cluster, but can be the same for different clusters.
Parameter	Bootstrap action script parameters
Execution Node	Select a type of the node where the bootstrap action script is executed.
Executed	Select the time when the bootstrap action script is executed. Before initial component start After initial component start NOTE: You can only manually run the third-party component installation script on the node to install a running cluster component.
Action upon Failure	Whether to continue to execute subsequent scripts and create a cluster after the script fails to be executed. NOTE: You are advised to set this parameter to Continue in the debugging phase so that the cluster can continue to be installed and started no matter whether the bootstrap action is successful.
Run as root	Whether to escalate the permission to user root If the bootstrap action requires root user operations, enable this function, or the bootstrap action may fail to execute.

Click OK.

After the bootstrap action is added, you can edit, clone, or delete it in the Operation column.

Adding an Automation Script on the Auto Scaling Page

Log in to the MRS management console.
Choose Clusters > Active Clusters. In the cluster list, select a running cluster to access its details page.
On the page that is displayed, click the Auto Scaling tab.

You can configure policies by resource pool or node group as needed. For details, see Creating an Auto Scaling Policy for an Existing Cluster
NOTE:
- Auto scaling policies of different node groups are mutually exclusive. That is, you can enable auto scaling policies only for one node group.
(Optional) Configure automation scripts.
1. Click Configure Automation Script.
2. Click Add.
3. Configure Name, Script Path, Execution Node, Parameter, Executed, and Action upon Failure. For details about the parameters, see Table 4.
4. Click OK to save the automation script configurations.

Parent topic: Configuring a Cluster

Previous topic: Configuring a Hive Data Connection

Next topic: Viewing Failed MRS Tasks

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot