vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Set up your own namespace in IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespaceregistry_namespace_setup).
* Install the latest release of [Helm CLI](https://github.com/helm/helm/releases) to work with charts.



To copy a chart between two registries, complete the following steps:



1. [Pull a chart from a registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_pull).
2. [Push the chart to another registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_push). Make sure that you use the correct domain name for the new region that you are targeting.



After you copy your chart, you can [install the Helm chart to the cluster in IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_install).





 Installing a Helm chart to the cluster 

You can install a Helm chart to the cluster in IBM Cloud Kubernetes Service directly from the registry. Follow the instructions in the Helm chart README, and use the full registry reference to the chart and chart version for installation.

helm install <release_name> oci://<region>.icr.io/<my_namespace>/<chart_name> --version <chart_version>

Example, where <release_name> is myrelease, region is uk, <my_namespace> is helm-charts, <chart_name> is mychart, and <chart_version> is 0.1.0:

helm install myrelease oci://uk.icr.io/helm-charts/mychart --version 0.1.0







 Deleting charts from your private repository
: (Optional) List all the namespaces and include information about the resource group and the creation date of the namespace.





 Example 

View a list of all your namespaces, including information about resource groups and creation dates.

ibmcloud cr namespace-list -v







 ibmcloud cr namespace-rm 

Removes a

namespacefrom your IBM Cloud account. Images in this namespace are deleted when the namespace is removed.

ibmcloud cr namespace-rm NAMESPACE [--force | -f]



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

NAMESPACE
: The namespace that you want to remove.

--force, -f
: (Optional) Force the command to run with no user prompts.





 Example 

Remove the namespace birds.

ibmcloud cr namespace-rm birds







 ibmcloud cr plan 

Displays your pricing plan for the registry region that you're targeting.

ibmcloud cr plan



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).







 ibmcloud cr plan-upgrade 

Upgrades you to the standard plan for the registry region that you're targeting.

ibmcloud cr plan-upgrade [PLAN]

For more information about plans, see [Registry plans](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plans).



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

PLAN
After you've successfully created a workspace, you can begin [Generating a plan](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-generate-plan&interface=cli) to validate all of the configuration properties.





 Before you begin 

Before you get started, make sure that you've completed the prerequisites found in [Setting up the IBM Cloud Schematics API](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-setting-up-api).





 Creating a workspace using the API 



1. To create a workspace by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_create_workspace.py.
2. Copy and paste the [Create a Schematics workspace using Python API](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-creating-workspace&interface=apiexample-request-create) example request to your Python file.
3. Change the following parameters as part of the request:



* Replace your IBM Cloud API key to the authenticator = IAMAuthenticator('<ibm-api-key>') variable.
* Change the API endpoint to the endpoint mentioned in [API endpoints](https://cloud.ibm.com/apidocs/schematics?code=pythonapi-endpoints) according to the location that you want your Schematics workspace to reside, for example, schematics_service.set_service_url('https://us.schematics.cloud.ibm.com').
* Provide environment values that you want to have in the form of a key and value pair, such as [{ 'Environment': 'hpc-dev-cluster' }]
* Change the folder location variable template_source_data_request_model['folder'] to the folder name inside your GitHub repository where your Terraform files reside.
The SoapClient should be initialized by using the SoftLayer_Network_CdnMarketplace_Configuration_Mapping class as shown in the following example.

$client = SoftLayerSoapClient::getClient(
'SoftLayer_Network_CdnMarketplace_Configuration_Mapping',
null,
$apiUsername,
$apiKey
);

try {
$uniqueId = 610345992629xxx;

$cdnMapping = $client->verifyDomainMapping($uniqueId);

print_r($cdnMapping);

} catch (Exception $e) {
die('verifyDomainMapping failed with an exception: ' . $e->getMessage());
}
Show more

If your CNAME record was added to your DNS server, the status of your CDN changes to RUNNING after the call to verifyDomainMapping, as shown in the following example.

[0] => stdClass Object
(
...

[status] => RUNNING
[uniqueId] => 610345992629xxx

...
)

If your CNAME record was not added to your DNS server, or your server isn't updated yet, the status of your CDN is CNAME_CONFIGURATION, as shown in the following example.

It can take several minutes (up to 30) for the CNAME chaining to complete.

Array
(
[0] => stdClass Object
(
...

[status] => CNAME_CONFIGURATION
[uniqueId] => 610345992629xxx

...
)

)

To be sure that your CNAME record is configured correctly, run dig <your domain> on the command line. The output looks similar to the following:

;; ANSWER SECTION:
api-testing.cdntesting.net. 900 IN CNAME api-testing.cdn.appdomain.cloud.

Here we see the domain name that is correctly mapped to the CNAME.
The workspace location does not have to match the resource location.
* Select Next.



5. Select Create to create your workspace.
6. On the workspace Settings page, in the Input variables section, review the default input variables and provide values that match your solution:



* Your API key
* Your private SSH key from your local machine
* The ID for the SSH key that you created and uploaded to IBM Cloud. Enter the SSH key ID in square brackets and quotation marks, for example [ "ibmcloud_ssh_key_UUID1","ibmcloud_ssh_key_UUID2",... ].
* The Region for your resources
* The Zone for your resources
* Whether to use an existing VPC or create one
* Whether to use an existing subnet
* Whether to create new port only when a new subnet is created
* TCP port range: mimimun and maximum
* VPC name
* Subnet name
* Security group name
* Hostname
* Profile
* Image
* Minimal recommended disk sizes
* SAP main password - must be at least 10 characters, uppercase and lowercase letters, a number, and a special character, not an exclamation point.
* Click Save changes.



For a more detailed description of each of the parameters, check the GitHub repo readme file, chapter “Input parameter file”. Also, make sure to parameters that contain sensitive information, like passwords, API, and ssh private keys as "sensitive". These parameters are marked as “sensitive” in the readme file, under “Input parameter file”.
7. On the workspace Settings page, click Generate plan. Wait for the plan to complete.
8. Click View log to review the log files of your Terraform execution plan.
9. Apply your Terraform template by clicking Apply plan.
10. Review the log file to ensure that no errors occurred during the provisioning, modification, or deletion process.







 Creating the infrastructure by using Terraform with the Bastion server CLI
After you've successfully created a workspace, you can begin [Generating a plan](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-generate-plan&interface=cli) to validate all of the configuration properties.





 Before you begin 

Before you get started, make sure that you've completed the prerequisites found in [Setting up the IBM Cloud Schematics API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-setting-up-api).





 Creating a workspace using the API 



1. To create a workspace by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_create_workspace.py.
2. Copy and paste the [Create a Schematics workspace using Python API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-creating-workspace&interface=apiexample-request-create) example request to your Python file.
3. Change the following parameters as part of the request:



* Replace your IBM Cloud API key to the authenticator = IAMAuthenticator('<ibm-api-key>') variable.
* Change the API endpoint to the endpoint mentioned in [API endpoints](https://cloud.ibm.com/apidocs/schematics?code=pythonapi-endpoints) according to the location that you want your Schematics workspace to reside, for example, schematics_service.set_service_url('https://us.schematics.cloud.ibm.com').
* Provide environment values that you want to have in the form of a key and value pair, such as [{ 'Environment': 'hpc-dev-cluster' }]
* Change the folder location variable template_source_data_request_model['folder'] to the folder name inside your GitHub repository where your Terraform files reside.
You can filter the table by entering the name of the cluster created in the Before you Begin step in the search field.

In the Project field, select from an existing project or create a new one by entering a unique project name. A project is a Kubernetes cluster namespace, and the list is populated from your Red Hat OpenShift environment. This project name is used as the namespace for the Platform Navigator.





 Step 4. Configure your schematics workspace 

IBM Cloud Paks use the [Schematics](https://www.ibm.com/cloud/schematics) service on IBM Cloud® to automate the installation. The automation runs in a schematics workspace. A suggested name is provided for this workspace. The schematics workspace is only used during the installation process.





 Step 5. Set the deployment values 

You must enter a value for the csDefaultAdminPassword. Do not lose this value, you will need it to log into the Platform Navigator.

The password should be at least 32 characters, and can only include letters, numbers, and -.





 Step 6. Install 

Check the box verifying you have read the license agreements. Click Install.

The namespace you use for installation of the Platform Navigator should match the name you set for the project.





 Next steps 

Once the installation completes, click Offering Dashboard to open the Platform Navigator.

You can also discover the host URL for the Platform Navigator with the following command.

oc get route -n ${NAMESPACE} ${NAMESPACE}-navigator-pn -o json | jq -r .spec.host

The full URL will then resemble "https://(project-name)-navigator-pn.(cluster-name).(region).containers.appdomain.cloud".

The Platform Navigator home page offers the ability to create instances of the various components.

See the full documentation in [IBM Documentation](https://www.ibm.com/support/knowledgecenter/SSGT7J_20.3/welcome.html). See Capability deployment.





 Known limitations
* All steps in [Prepare ASCS and ERS instances for the cluster integration](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel-ensaha-rhel-ensa-prepare-ascs-ers) are complete.





 Configuring resource for sapmnt share 

Create a cloned Filesystem cluster resource to mount the SAPMNT share from an external NFS server to all cluster nodes.

Make sure that the environment variable ${NFS_vh} is set to the virtual hostname of your NFS server ${NFS_vh}, and ${NFS_options} according to your mount options.

Example mount options:

export NFS_options="rw,sec=sys"

Check SAP recommendations for NFS mount options at the [Recommended mount options for read-write directories](https://wiki.scn.sap.com/wiki/display/Basis/Recommended+mount+options+for+read-write+directories) wiki page.

On NODE1, run the following command.

pcs resource create fs_sapmnt Filesystem device="${NFS_vh}:/${SID}" directory="/sapmnt/${SID}" fstype='nfs' "options=${NFS_options}" clone interleave=true





 Configuring ASCS resource group 

Create a resource for the virtual IP address of the ASCS.

On NODE1, run the following commands.

pcs resource create ${sid}_vip_ascs${ASCS_nr} IPaddr2 ip=${ASCS_ip} --group ${sid}_ascs${ASCS_nr}_group

In this example of creating resources for an HA-LVM file system on a shared storage volume, you create resources for LVM-activate and for the instance file system of the ASCS.
DEBUG:urllib3.connectionpool:https://us.schematics.cloud.ibm.com:443 "POST /v1/workspaces HTTP/1.1" 201 1974
INFO:root:Completed Creating Schematic Workspace
{
"id": "us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"name": "Sample Schematic API workspace",
"crn": "crn:v1:bluemix:public:schematics:us-south:a/77efe1030c00b5c89cfd08648d3480bf:6f457fa4-4c59-4a8d-be69-483f16f8f200:workspace:us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"type": [
"terraform_v0.14.11"
],
"description": "HPC Cluster schematic workspace using API",
"resource_group": "Default",
"location": "us-south",
"tags": [
""
],
"created_at": "2021-09-15T13:01:19.944980389Z",
"created_by": "xxxxxx",
"status": "DRAFT",
"failure_reason": "",
"workspace_status_msg": {
"status_code": "",
"status_msg": ""
},
"workspace_status": {
"frozen": false,
"locked": false
},
"template_repo": {
"url": "https://github.com/IBM-Cloud/hpc-cluster-symphony",
"commit_id": "",
* [Setting up a Network Load Balancer for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_nlb)



* [Setting up a public VPC NLB](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_nlb_pub)
* [Setting up an NLB using port range](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaasnlb-setup-portrange)
* [Setting up a private VPC NLB](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_nlb_priv)
* [Registering a DNS record and TLS certificate](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaasvpc_nlb_dns)



* [Setting up an Application Load Balancer for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_ks_vpc_lb)



* [Setting up a public or private VPC ALB](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_alb_pub_priv)
* [Registering a DNS record and TLS certificate](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaasvpc_lb_dns)



* [Persistent VPC load balancers](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaasvpc_lb_persist)
* [Moving a VPC load balancer from one cluster to another](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaasvpc_lb_move)
-n, --namespace KUBERNETES_NAMESPACE
: The Kubernetes namespace that you want to forward logs from. Log forwarding is not supported for the ibm-system and kube-system Kubernetes namespaces. This value is valid only for the container log source and is optional. If you don't specify a namespace, then all namespaces in the cluster use this configuration.

--hostname LOG_SERVER_HOSTNAME
: The hostname or IP address of the log collector server.

--port LOG_SERVER_PORT
: Optional: The port of the log collector server. If you don't specify a port, then the standard port 514 is used for syslog and the standard port 9091 is used for ibm.

--space CLUSTER_SPACE
: Optional: The name of the Cloud Foundry space that you want to send logs to. This value is valid only for log type ibm and is optional. If you don't specify a space, logs are sent to the account level. If you do, you must also specify an org.

--org CLUSTER_ORG
: Optional: The name of the Cloud Foundry org that the space is in. This value is valid only for log type ibm and is required if you specified a space.

-p, --app-path
: The path on the container that the apps are logging to. To forward logs with source type application, you must provide a path. Wildcards, such as /var/log/.log, can be used, but recursive globs, such as /var/log//test.log, can't be used. To specify more than one path, use multiple options, such as -p /var/log/myApp1/&ast; -p /var/log/myApp2/&ast;. This value is required for log source application.

--syslog-protocol
: The transfer layer protocol that is used when the logging type is syslog. Supported values are tcp, tls, and the default udp.
For more information, see the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command and see the [upload a tar file to your workspace](https://cloud.ibm.com/apidocs/schematics/schematicsupload-template-tar) API.
* Make sure that you have the [permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-access) to create a workspace.



Ensure the location and the url endpoint are pointing to the same region when you list the Schematics Workspaces and actions. For more information about location and endpoint, see [Where is your information stored](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)?



* Run a Schematics apply job against your workspace. An apply job provisions, modifies, or removes the IBM Cloud resources that you describe in the Terraform template that your workspace points. Depending on the type and number of resources that you want to provision or modify, this process might take a few minutes, or hours to complete. During this time, you cannot edit your workspace. After all updates are applied, the state of the files persists to determine what resources exist in your IBM Cloud account.







 Perform a workspace apply using the UI 



1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2. Access Schematics > Workspaces > [Workspace](https://cloud.ibm.com/schematics/workspaces).
3. Search your workspace in specific location.
4. Click Workspaces > [workspace](https://cloud.ibm.com/schematics/workspaces).
5. Click Apply plan to provision the configured resources.





 Verifying workspace apply 



1.
DEBUG:urllib3.connectionpool:https://us.schematics.cloud.ibm.com:443 "POST /v1/workspaces HTTP/1.1" 201 1974
INFO:root:Completed Creating Schematic Workspace
{
"id": "us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"name": "Sample Schematic API workspace",
"crn": "crn:v1:bluemix:public:schematics:us-south:a/77efe1030c00b5c89cfd08648d3480bf:6f457fa4-4c59-4a8d-be69-483f16f8f200:workspace:us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"type": [
"terraform_v0.14.11"
],
"description": "HPC Cluster schematic workspace using API",
"resource_group": "Default",
"location": "us-south",
"tags": [
""
],
"created_at": "2021-09-15T13:01:19.944980389Z",
"created_by": "xxxxxx",
"status": "DRAFT",
"failure_reason": "",
"workspace_status_msg": {
"status_code": "",
"status_msg": ""
},
"workspace_status": {
"frozen": false,
"locked": false
},
"template_repo": {
"url": "https://github.com/IBM-Cloud/hpc-cluster-openshift",
"commit_id": "",
If the workspace creation is successful, the Apply Plan action is started to trigger the deployment of the respective IBM Cloud VPC resources in your IBM Cloud account that are linked with the api_key.
8. You can also review the status of your deployment process by identifying the workspace name in the View the existing installations section. When you click a record in View the existing installations section, you are taken to the Schematics workspace view.







 Next steps 

After you've successfully created a workspace, you can begin [Generating a plan](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-generate-plan&interface=ui) to validate all of the configuration properties.





 Before you begin 

Before you get started, make sure that you've completed the prerequisites found in [Setting up the IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-setting-up-cli).





 Creating a workspace using the CLI 

The first step when using Schematics is to create a workspace with the specific configuration parameters defined in the corresponding Terraform source code.

Use the following CLI command to create a workspace with your config.json file. Make sure that the config.json file exists in the directory where you run the command.

ibmcloud schematics workspace new -f hpc_workspace_config.json --github-token GITHUB_TOKEN

The --github-token parameter is optional and only needed if you are using a private git repository. If you are using the [IBM Cloud public GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf), you do not need to provide it.



 Listing available workspaces 

You can list the workspaces in your account by using the following command:

ibmcloud schematics workspace list

Example response with workspace details:

Name           ID       Description           Status         Frozen
In the customized storage class YAML file, reference the Kubernetes secret in the metadata.parameters section as follows. Make sure to enter the name of the Kubernetes secret that you created earlier and the namespace where you created the secret.

csi.storage.k8s.io/provisioner-secret-name: <secret_name>
csi.storage.k8s.io/provisioner-secret-namespace: <secret_namespace>
4. As the cluster user, follow the steps in [Adding Block Storage for VPC to your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-add) to create a PVC from your customized storage class.









 Setting up volume expansion 

To provision volumes that support expansion, you must use storage class that has allowVolumeExpansion set to true.

You can only expand volumes that are mounted by an app pod.

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. If you are not using version 4.2 or later of the add-on, [update the Block Storage for VPC add-on in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-addon-update).
2. [Create a PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc_block_qs) that uses a storage class that supports volume expansion.
3. [Deploy an app](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc_block_qs) that uses your PVC. When you create your app, make a note of the mountPath that you specify.
4.
DEBUG:urllib3.connectionpool:https://us.schematics.cloud.ibm.com:443 "POST /v1/workspaces HTTP/1.1" 201 1974
INFO:root:Completed Creating Schematic Workspace
{
"id": "us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"name": "Sample Schematic API workspace",
"crn": "crn:v1:bluemix:public:schematics:us-south:a/77efe1030c00b5c89cfd08648d3480bf:6f457fa4-4c59-4a8d-be69-483f16f8f200:workspace:us-south.workspace.Sample-Schematic-API-workspace.341cedd5",
"type": [
"terraform_v0.14.11"
],
"description": "HPC Cluster schematic workspace using API",
"resource_group": "Default",
"location": "us-south",
"tags": [
""
],
"created_at": "2021-09-15T13:01:19.944980389Z",
"created_by": "xxxxxx",
"status": "DRAFT",
"failure_reason": "",
"workspace_status_msg": {
"status_code": "",
"status_msg": ""
},
"workspace_status": {
"frozen": false,
"locked": false
},
"template_repo": {
"url": "https://github.com/IBM-Cloud/hpc-cluster-lsf",
"commit_id": "",