vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Enter a name for the workspace.
* Select a Resource group.
* Select a Location for your workspace. The workspace location does not have to match the resource location.
* Click 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
* (Optionl) You can change the ID_RSA_FILE_PATH for your SSH key that will be autogenerated on Schematics and Bastion Server
* 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, nimimun 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, upper 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 mark as “sensitive” the parameters that contain sensitive information like passwords, API, and SSH private keys (they are marked as “sensitive” in the README file in the “Input parameter file”).
7. On the workspace Settings page, click Generate plan. Wait for the plan to complate.
8. Click View log to review the log files of your Terraform execution plan.
9.
* Select a Resource group.
* Select a Location for your workspace. The workspace location does not have to match the resource location.
* Click 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
* (Optionl) You can change the ID_RSA_FILE_PATH for your SSH key that will be autogenerated on Schematics and Bastion Server
* 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, nimimun 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, upper 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 mark as “sensitive” the parameters that contain sensitive information like passwords, API, and SSH private keys (they are marked as “sensitive” in the README file in the “Input parameter file”).
7. On the workspace Settings page, click Generate plan. Wait for the plan to complate.
8. Click View log to review the log files of your Terraform execution plan.
9. Apply your Terraform template by clicking Apply plan.
<br><br> * [ibm_cr_namespace](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cr_namespace)<br> * [ibm_cr_retention_policy](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cr_retention_policy)<br><br><br> <br><br> * [ibm_cr_namespaces](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cr_namespaces)<br><br><br> 







 Context Based Restrictions 



 Resources Data sources 

 <br><br> * [ibm_cbr_rule](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cbr_rule)<br> * [ibm_cbr_zone](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cbr_zone)<br><br><br> <br><br> * [ibm_cbr_rule](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cbr_rule)<br> * [ibm_cbr_zone](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cbr_zone)<br><br><br> 







 Continuous Delivery 



 Resources Data sources
namespace: hpcc Choose your own Namespace
spec:
accessModes:
- ReadWriteMany
storageClassName: nfs-sc-hpcc
resources:
requests:
storage: 100Gi
Show more
2. Before you create the PV and PVC, you need to update the following values in the pvc.yml file that you create:



* Replace the server IP address with the NFS storage node IP address.
* If you used a mount path name other than the default /data when you created the cluster, replace the path name with the one that you specified.
* Replace storage capacity based on the size of the NFS storage volume that you created.



3. After you create and update the pvc.yml file, run the following command to create the PV and PVC:

oc apply -f pvc.yml
4. Check the status of the PV and PVC by running the following command:

oc get pv

oc get pvc







 Validating the PV and PVC 

Complete the following steps to validate the PV and PVC with a sample application:



1. Create a nginx.yml file with the following content:

apiVersion: v1
kind: Pod
metadata:
name: nginx-pv-pod
spec:
volumes: Volume declaration
- name: nginx-pv-storage
persistentVolumeClaim:
claimName: nfs-pvc-hpcc
containers:
- name: nginx
image: nginx
ports:
- containerPort: 80
name: "nginx-server"
volumeMounts:
- mountPath: "/usr/share/nginx/html"
name: nginx-pv-storage
Show more
2. Create a pod by running the following command:

oc apply -f nginx.yml
3. Check the status of the pod by running the following command:

oc get pods
4.
Verify that you can access the URL used for this solution [Automation script for SAP solutions using a BASTION & STORAGE setup deployment through Terraform and IBM Schematics](https://github.com/IBM-Cloud/sap-bastion-setup).







 Procedure 



1. From the IBM Cloud menu, select [Schematics](https://cloud.ibm.com/schematics/overview).
2. Click Create workspace.
3. On the Specify template page:



* Enter the URL of bastion setup folder.
* Select the Terraform version.
* Click Next.



4. On the Workspace details page:



* Enter a name for the workspace.
* Select a Resource group.
* Select a Location for your workspace. 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
* 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, nimimun and maximum
* VPC name
* Subnet name
* Security group name
* Hostname
* Profile
* Image
* Minimal recommended disk sizes.
* Click Save changes.



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.
11.
'Global.Licenses',
'Global.Settings',
'Global.DisableMethods',
'Global.EnableMethods',
'Folder.Create',
'Folder.Delete',
'Datastore.Browse',
'Datastore.DeleteFile',
'Datastore.FileManagement',
'Datastore.AllocateSpace',
'Datastore.Config',
'Network.Config',
'Network.Assign',
'DVPortgroup.Create',
'DVPortgroup.Modify',
'DVPortgroup.Delete',
'Host.Config.Maintenance',
'Host.Config.Storage',
'Host.Config.Network',
'Host.Config.AdvancedConfig',
'Host.Config.Patch',
'VirtualMachine.Inventory.Create',
'VirtualMachine.Inventory.Register',
'VirtualMachine.Inventory.Delete',
'VirtualMachine.Inventory.Unregister',
'VirtualMachine.Interact.PowerOn',
'VirtualMachine.Interact.PowerOff',
'VirtualMachine.Interact.Suspend',
'VirtualMachine.Interact.ConsoleInteract',
'VirtualMachine.Interact.DeviceConnection',
'VirtualMachine.Interact.SetCDMedia',
'VirtualMachine.Interact.SetFloppyMedia',
'VirtualMachine.Interact.GuestControl',
'VirtualMachine.GuestOperations.Query',
'VirtualMachine.GuestOperations.Modify',
'VirtualMachine.GuestOperations.Execute',
'VirtualMachine.Config.Rename',
'VirtualMachine.Config.AddExistingDisk',
'VirtualMachine.Config.AddNewDisk',
'VirtualMachine.Config.Annotation',
[Classic: Setting up basic load balancing with an NLB 1.0](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerloadbalancer)



* [Setting up an NLB 1.0 in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancermulti_zone_config)
* [Setting up an NLB 1.0 in a single-zone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerlb_config)
* [Enabling source IP preservation](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerlb_source_ip)



* [Adding edge node affinity rules and tolerations](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerlb_edge_nodes)
* [Adding affinity rules for multiple public or private VLANs](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalanceredge_nodes_multiple_vlans)





[Classic: Setting up DSR load balancing with an NLB 2.0](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-v2loadbalancer-v2)



* [Prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-v2ipvs_provision)
* [Setting up an NLB 2.0 in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-v2ipvs_multi_zone_config)
* Enter the URL for the Schematics interface.
* Select the Terraform version.
* Click Next.



4. On the Workspace details page:



* Enter a name for the workspace.
* Select a Resource group.
* Select a Location for your workspace. 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 floating IP address for your bastion server.
* 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, nimimun and maximum
* VPC name
* Subnet name
* Security group name
* Hostname
* Profile
* Image
* Minimal recommended disk sizes
* SAP HANA main password - This password must be 8 - 14 characters, upper and lowercase letters, a number, and a special character.
* SAP main password - This password must be 10 - 14 characters, upper and lowercase letters, a number, and a special character that is 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 mark the parameters that contain sensitive information like passwords, API, and ssh private keys as "sensitive".
Setting up Terraform for DNS Services 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud services so that you can rapidly build complex, multi-tier cloud environments following Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the provisioning, update, and deletion of your IBM Cloud® DNS Services instances by using HashiCorp Configuration Language (HCL).

Looking for a managed Terraform on IBM Cloud® solution? Try out [IBM Cloud® Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform scripting language that you are familiar with, but you don't have to worry about setting up and maintaining the Terraform command line and the IBM Cloud® Provider plug-in. Schematics also provides pre-defined Terraform templates that you can easily install from the IBM Cloud® catalog.



 Installing Terraform and configuring resources for DNS Services 

Before you begin, make sure that you have the [required access](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-iam) to create and work with DNS Services resources.



* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform. For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you add the configuration to create a DNS Services service instance and to assign a user an access policy in Identity and Access Management (IAM) for that instance by using HashiCorp Configuration Language (HCL).
This flag is optional.





 Example 

ibmcloud fn namespace get user@domain.com_dev --properties

Output

Name: user@domain.com_dev
Description: This is a description of my namespace.
Resource Plan Id: functions-base-plan
Location: us-south
ID: 58c2e718-8c60-48bc-96de-cf9373fe6709







 ibmcloud fn namespace list 

List the available Cloud Foundry and IAM namespaces.

ibmcloud fn namespace list [--auth KEY] [--cf] [--iam] [--limit NUMBER_OF_NAMESPACES] [--name-sort] [--skip NUMBER_OF_NAMESPACES]



 Command options 

--authKEY, -uKEY
: The wsk authorization KEY. This flag is optional.

--cf
: Display the Cloud Foundry namespaces only. IAM namespaces are not displayed. This flag is optional.

--iam
: Display the IAM namespaces only. Cloud Foundry namespaces are not displayed. This flag is optional.

--limit NUMBER_OF_NAMESPACES, -l NUMBER_OF_NAMESPACES
: List a specified number of namespaces. The default is 30 namespaces. This flag is optional.

--name-sort, -n
: Sort the list of returned namespaces by name, otherwise the list is sorted by creation date. This flag is optional.

--skip NUMBER_OF_NAMESPACES, -s NUMBER_OF_NAMESPACES
: Exclude a specified number of the most recently created namespaces from the result. This flag is optional.





 Example 

ibmcloud fn namespace list







 ibmcloud fn namespace target 

Target an available IAM or Cloud Foundry namespace.

ibmcloud fn namespace target NAMESPACE



 Command options 

NAMESPACE
: The name or ID for a namespace. This value is required.





 Example
* Enter a name for the workspace or use the default.
* Select the Resource Group to use to create resources. Use the Default or create a Resource Group.
* Select a Location to create your Schematics workspace. The workspace location does not have to match the resource location.



3. Enter the required deployment values, review the default input variables, and provide values that match your solution. These parameters are specific to your deployment. For more information, see the [readme file - Input Parameters](https://github.com/IBM-Cloud/sap-s4hana-sz-ha/blob/main/schematics/README.md).



 Parameter Description 

 APP-HOSTNAME-1 APP VSI hostname-1 
 APP-HOSTNAME-2 APP VSI hostname-2 
 BASTION_FLOATING_IP Input the floating IP of the Bastion Server you created before you started this deployment. For more information, see Automate SAP bastion server - SAP media storage. 
 DB-HOSTNAME-1 DB VSI hostname-1 
 DB-HOSTNAME-2 DB VSI hostname-2 
 DOMAIN_NAME Private Domain Name 
 REGION Cloud Region where resources are deployed 
 RESOURCE_GROUP EXISTING Resource Group for VSIs and Volumes 
 SECURITY_GROUP EXISTING Security group name 
 SSH_KEYS SSH Keys ID list to access the VSI 
 SUBNET EXISTING Subnet name 
 VPC EXISTING VPC name 
 ZONE Cloud Zone where resources are deployed 
 ha_password HA cluster password 
 hana_components HANA Components, for example, server 
 hana_main_password HANA main password or use a secret that is stored in Secrets Manager 
 hana_sid HANA sid 
 ibmcloud_api_key IBM Cloud API key or use a secret that is stored in Secrets Manager 
 private_ssh_key Input id_rsa private key content or use a secret that is stored in Secrets Manager 
 sap_main_password SAP main password or use a secret that is stored in Secrets Manager 
 sap_sid SAOP sid 



4. Review and update the optional parameters. The Ansible scripts expect the SAP kits to be in the default locations listed.
3. Select a [namespace](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces).
4. Click Start Creating > Quickstart Templates and select the Hello World template.
5. Create a package for your action by entering a unique name in the Package Name field.
6. Select a runtime for your action. You can preview the code for the sample action in each available runtime before you deploy the template.
7. Click Deploy. You created an action. Great job!
8. Run the action by clicking Invoke. Invoking an action manually runs the app logic that the action defines. In the Activations panel, you can see the "Hello stranger!" greeting produced by the action.
9. Optional: Click Change Input to change the action or try your own.

a. Paste the following code into the Change Input box and change the name value.

{ "name": "xxxx" }

b. Then, click Invoke to run the action with your updates. The result is shown in the Activations panel. You can repeat this process as many times as you like.



Good work! You created your first action. To clean up this action, click the overflow menu and select Delete Action.





 Creating an action in the CLI 

Get up and running quickly with the [Hello World JavaScript](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_js) example code. This example creates a basic hello action, which you can manually invoke to run its app logic.





 What's next in Cloud Functions? 

So you completed your first template deployment, where do you go from here?



* Become familiar with the [terminology](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-about).
To specify multiple IP addresses, use multiple --ip options.

--secret-namespace NAMESPACE
: The Kubernetes namespace where you want to create the Kubernetes secret that holds the SSL certificate information for the NLB. If you don't specify a namespace, the secret is automatically created in the default namespace.

--dns-type public
: The DNS provider type for subdomain registration. Currently, only public is supported.

--type public
: The subdomain type. Currently, only public is supported.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns create classic command 

ibmcloud ks nlb-dns create classic --cluster mycluster --ip 1.1.1.1







 ibmcloud ks nlb-dns create vpc-gen2 

Virtual Private Cloud

Create a DNS record for a Network Load Balancer for VPC or Application Load Balancer for VPC.

When you create a Network Load Balancer for VPC, the load balancer is assigned external IP addresses for each zone in your cluster. When you create an Application Load Balancer for VPC, the load balancer is assigned a hostname. If you want an app subdomain with TLS termination, you can use the ibmcloud ks nlb-dns create vpc-gen2 command to create a DNS record for the IP addresses or hostname. IBM Cloud takes care of generating and maintaining the wildcard SSL certificate for the subdomain for you. You can create subdomains for both public and private VPC load balancers.

ibmcloud ks nlb-dns create vpc-gen2 --cluster CLUSTER (--lb-host VPC_ALB_HOSTNAME | --ip VPC_NLB_IP) [--dns-type public] [--secret-namespace NAMESPACE] [--type (public|private)] [--output json] [-q]

Minimum required permissions
* [Troubleshooting image pull secrets that use API keys](https://cloud.ibm.com/docs/Registry?topic=Registry-ts-app-image-pullimg-pull-api-key)







 Troubleshooting CLI commands 

[Why can't I add a namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-add-namespacetroubleshoot-add-namespace)

[When I create a namespace, why aren't I authorized to access the specified resource?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-namespace-authtroubleshoot-namespace-auth)

[Why can't I find my image or my namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-findtroubleshoot-image-find)

[Why don't all my namespaces show in the Resource list?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-namespace-resource-listtroubleshoot-namespace-resource-list)

[Why is it timing out when I list images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeouttroubleshoot-image-timeout)

[Why can't I pull the newest image by using the latest tag?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-docker-latesttroubleshoot-docker-latest)

[Why do all the tags get deleted when I delete an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-rmtroubleshoot-image-rm)

[Why doesn't the retention command show all the images?]
* UI
* CLI
* API







 Creating a workspace 

With IBM Cloud® Schematics workspaces, you can manage the Terraform-based templates to create and manage IBM Cloud resources. A workspace allows you to view and update configuration properties, view the list of resources that are provisioned through the workspace, and clean up resources if and when needed.



 Creating a workspace using the UI 



1. Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog) by using your unique credentials.
2. In the Software section, select Compute and then select the IBM Spectrum LSF tile.
3. In the Configure your workspace section:



* Specify the Name for your Schematics workspace
* Select a Resource group
* Define any Tags that you want to associate with the resources provisioned through the offering. The tags can later be used to query the resources in the IBM Cloud console.



4. In the Set the deployment values section, specify the values for the required properties: api_key, ibm_customer_number, remote_allowed_ips, ssh_key_name, and zone.
5. Expand the Parameters with default values section, and review it to determine whether you need to override any of the default values provided for the configuration properties.
6. Review and accept the IBM Spectrum LSF license terms and conditions in the order summary.
7. Click Install. The Schematics workspace is created with the name you specified. You can see the list of workspaces in View the existing installations. 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