How do I remove Mistral actions from NSP?
Purpose
Perform this procedure to specify Mistral actions to drop, if required for network security. An action that is dropped cannot be called by a workflow. Dropping actions requires adding an environment variable to each Mistral engine in the NSP deployment.
You must perform the procedure on each NSP cluster in the deployment.
Steps
1 |
Log in as the root user on the NSP cluster host. |
2 |
Open a console window. |
3 |
Open each of the following files for editing:
|
4 |
Enter the following in the env section of each file: ACTIONS_DROP "action_1 action_2 . . . action_n" where action_1 to action_n are the actions to drop |
5 |
Obtain the engine name, namespace, chart name and chart version of each Mistral engine; enter the following: # helm list -A ↵ Output like the following is displayed: engine namespace 1 timestamp deployed chart_name-chart_version release |
6 |
Obtain the Helm repository name and URL; enter the following: # helm repo list ↵ Output like the following is displayed: NAME URL nokia-nsp repository URL |
7 |
Enter the following for each Mistral engine: # helm upgrade engine -n namespace chart_name --version chart_version --repo repository URL -f path ↵ where engine, namespace, chart_name, and chart_version are the values obtained in Step 5 repository and URL are the values obtained in Step 6 path is the path of the associated engine configuration file, and is one of:
The new environment variables are put in effect and the actions are unavailable to workflows. |
8 |
Close the console window. End of steps |