vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Add-ons



* Accept default values.



* Storage Disks



* Type - RAID 1
* Number of disks - 2
* Disk Media - SATA (preselected)
* Disk Size - 4 TB.



* Network interface



* Uplink Port Speeds - 10 Gbps Public and Private Network Uplinks.
* Ensure that you enable both public and private NICs (four ports total).
* Add-ons - accept default values. Optionally select IPv6 address.





Review order and click Create. Provisioning takes three to four hours.





 Post deployment 

If you deployed the IaaS KVM-based Juniper vSRX HA Cluster, you can continue with configuration of the vSRX cluster as described in [IBM Cloud performing vSRX basics](https://cloud.ibm.com/docs/vsrx?topic=vsrx-performing-ibm-cloud-juniper-vsrx-basics).

If you opted to deploy the No-OS gateway offering, then follow the guidance in [Installing an operating system on the gateway](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-order-byoainstalling-an-operating-system-on-the-gateway) to prepare the hosts for your appliance.





 Related links 



* [Getting started with IBM Cloud Juniper vSRX](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-started)
* [Juniper Networks vSRX deployment guide for VMware](https://www.juniper.net/documentation/en_US/vsrx/information-products/pathway-pages/security-vsrx-vmware-guide-pwp.html)
* [Juniper Networks requirements for vSRX on VMware](https://www.juniper.net/documentation/en_US/vsrx/topics/reference/general/security-vsrx-vmware-system-requirement.html)
: The URL of the Git repository or the path to local source that contains your source code; for example https://github.com/IBM/CodeEngine or .. This value is optional.

--build-strategy, --strategy, --bstr, --str
: The strategy to use for building the image. Valid values are dockerfile and buildpacks. The build strategy option is allowed only if the --build-source option is set. If not specified, the build strategy is determined by Code Engine if --build-source is specified and the source is on your local machine. This value is optional. The default value is dockerfile.

--build-timeout, --bto
: The amount of time, in seconds, that can pass before the build must succeed or fail. The build timeout option is allowed only if the --build-source option is set. This value is optional. The default value is 600.

--command, --cmd, -c
: Set commands for runs of the job. Specify one command per --command option; for example, --cmd cmdA --cmd cmdB. This value overrides the default command that is specified within the container image. This value is optional.

--cpu
: The amount of CPU to set for runs of the job. For valid values, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). This value is optional. The default value is 1.

--env, -e
: Set environment variables for runs of the job. Must be in NAME=VALUE format. This action adds a new environment variable or overrides an existing environment variable. Specify one environment variable per --env option; for example, --env envA=A --env envB=B. This value is optional.

--env-cm, --env-from-configmap
[Performing key management operations with the CLI - Standard Plan only](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-cliset-up-cli)



* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-clicli-next-steps)







 Setting up Terraform 

[Setting up Terraform for Hyper Protect Crypto Services Standard Plan](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-terraform-setup-for-hpcsterraform-setup-for-hpcs)



* [Example: Provisioning and initializing service instances by using Terraform](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-terraform-setup-for-hpcsterraform-provision-initialize-instance-hpcs)
* [What's next?](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-terraform-setup-for-hpcsterraform-setup-hpcs-next)



[Setting up Terraform for Hyper Protect Crypto Services with Unified Key Orchestrator](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-terraform-setup-for-hpcsuko-terraform-setup-for-hpcs)



* [Example: Provisioning and initializing service instances by using Terraform](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-terraform-setup-for-hpcsuko-terraform-provision-initialize-instance-hpcs)
* [What's next?](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-terraform-setup-for-hpcsuko-terraform-setup-hpcs-next)
* --catalog-offering: The CRN for the IBM Cloud catalog offering. If specified, the latest version of that offering is used. For more information about creating a catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --catalog-offering-version: The CRN for the version of a IBM Cloud catalog offering. For more information about creating a version for the catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --total-volume-bandwidth: The amount of bandwidth (in megabits per second) that is allocated exclusively to instance storage volumes. An increase in this value results in a corresponding decrease to total network bandwidth.
* --boot-volume: BOOT_VOLUME_JSON|@BOOT_VOLUME_JSON_FILE, boot volume attachment in JSON or JSON file. For the data schema, see the boot_volume_attachment property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --volume-attach: VOLUME_ATTACH_JSON|@VOLUME_ATTACH_JSON_FILE, volume attachment in JSON or JSON file, list of volumes. For the data schema, see the volume_attachments property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --keys: Comma-separated IDs or names of SSH keys.
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
Deploying your infrastructure 



 Before you begin 

Determine the amount of memory that you need for your application.





 Step 1: Provision your server 

Order your Bare Metal SAP HANA server using the steps in [Deploying your infrastructure](https://cloud.ibm.com/docs/sap?topic=sap-bm-set-up-infrastructure). Select the profile for the amount of PMem that you need for your application.





 Step 2: Post-Provisioning Intel Optane PMem 

After you order your Bare Metal server and the server is provisioned, you complete the provisioning by creating namespaces for your system.

PMem on Bare Metal supports the App Dir mode. In App Dir mode, PMem and DRAM DIMMs act as independent memory resources that are directly accessed by the applications.

The App Dir mode uses regions, and namespaces to represent persistent memory devices in an interleaved set. A region represents the physical persistent memory devices. A region is made up of one or more namespaces. A namespace represents a unit of storage that can be used for input/output (I/O).

Regions are created as part of the provisioning process. You must create the namespaces, create mount points, and mount the PMem devices.

For more information about regions and namespaces, see [Intel Optane Persistent Memory and SAP HANA Platform Configuration](https://www.sap.com/documents/2019/05/7a278c36-507d-0010-87a3-c30de2ffd8ff.html).



1. Log in to the Bare Metal server as root.
2. Download the current version of the zypper (for SLES) or yum (for RHEL).
3. Install the ndctl software for your system:



* For SLES:

$ zypper in ndctl

Refreshing service
'SMT-https_susesapsmtamr_service_networklayer_com'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
In the Storage Disks section, the Storage Disk is already selected for your fast provisioning servers selection. Expand the Add-ons section if you want to add [IBM Cloud Backup](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-started) to your server.
6. In the Network Interface section, select the Uplink Port Speeds. Expand the Add-ons section to select the appropriate options or use the default values. For more information about network options, see [Network options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-network-options).
7. Review your order.
8. If you have a promo code to apply to your order, expand Apply Promo Code.
9. Review any third-party service agreements that are listed and click the Third-Party Service Agreement checkbox.
10. Click Provision. You are redirected to a screen with your provisioning order number. You can print the screen because it's also your provisioning order receipt.



A series of emails is sent to your administrator: Acknowledgment of the provisioning order, provisioning order approval and processing, and provisioning complete. The provisioning complete email includes a link to your Device Details page so that you can log in to IBM Cloud. You can also log directly in to the IBM Cloud® console.



 Next Steps 

After your Bare Metal Servers is provisioned, you can start managing it. For more information, see [Managing Bare Metal Servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-manage-servers).
3. Click Create.

A Discovery service instance is created and a summary page is displayed.



2. Copy the credentials to authenticate to your service instance:



1. Click Show credentials.
2. Copy the API key and URL values.



3. Make sure that you have the curl command.



* Test whether curl is installed. Run the following command on the command line. If the output lists the curl version with SSL support, you are set for the tutorial.

curl -V
* If necessary, install a version with SSL enabled from [curl.haxx.se](https://curl.haxx.se/). Add the location of the file to your PATH environment variables if you want to run curl from any command-line location.









 Step 1: Create an environment 

In a bash shell or equivalent environment, such as Cygwin with the curl application installed, use the POST /v1/environments method to create an environment. Think of an environment as the warehouse where you are storing all your boxes of documents.



1. Issue the following command to create an environment that is called my-first-environment. Replace {apikey} and {url} with the API key and URL you copied earlier:

curl -X POST -u "apikey:{apikey}" -H "Content-Type: application/json" -d "{"name":"my-first-environment","description":"exploring environments"}" "{url}/v1/environments?version=2019-04-30"

Windows users: Replace the backslash () at the end of each line with a caret (^). Make sure that there are no trailing spaces.

The API returns information such as your environment ID, environment status, and how much storage your environment is using.
2. Check the environment status periodically until you see a status of active.

Issue a call to the GET /v1/environments/{environment_id} method to retrieve the status of your environment. Replace {apikey}, {url}, and {environment_id} with your information:
Why won't my deployment process finish successfully? 

  What’s happening 

As part of the development of the Deployable Architecture we verify the workflows described in this guide. In the stable IBM Cloud® environment, no errors are expected. But because several infrastructure layers and components are included in the deployment, you might see issues that aren't anticipated. For example, the maintenance activity in the particular data center, errors in DevSecOps Application Lifecycle Management, or network services, or issues in Operating System software updates can cause deployment failures.

  Why it’s happening 

If the deployment process does not finish successfully, first look at the IBM Cloud® Schematics logs. These logs typically provide the information about the component that causes the issue.

  How to fix it 

If you still cannot solve your issue, open a case in the IBM Cloud® support center.
Specify one mount configuration per --mount-secret option; for example, --mount-secret /etc/secret-a=secret--a --mount-secret /etc/secret-b=secret-b. This value is optional.

--no-wait, --nw
: Do not wait for the build run to complete. If you specify the --no-wait option, the build run begins and does not wait. Use the buildrun get command to check the build run status. The no-wait option is allowed only if the --build-source option is set on this job update command or your job currently has an associated build. This value is optional. The default value is true.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--rebuild
: Rebuild image from source. The rebuild option is allowed if your job currently has an associated build. This value is optional. The default value is false.

--registry-secret, --rs
: The name of the registry secret. The registry secret is used to authenticate with a private registry when you download the container image. This value is optional.

--registry-secret-clear, --rsc
: Clear the registry secret. This value is optional. The default value is false.

--retrylimit, -r
: The number of times to rerun an instance of the job before the job is marked as failed. An array index of a job is rerun when it gives an exit code other than zero. This option can only be specified if mode is task. This value is optional. The default value is 3.

--service-account, --sa
Many extra software packages require access to or from the host, so extra software packages are not allowed to be installed.

Maintenance: IBM provides software updates that you choose when to apply to the host. Because IBM is responsible for providing these updates, you cannot install extra software that is not managed by IBM. Extra software also uses mores CPU, memory, and disk storage resources on the host, which impacts the amount available to your Satellite-enabled IBM Cloud services and applications that run on the hosts.





 What am I charged for when I use IBM Cloud Satellite? 

IBM Cloud Satellite provides a convenient way for you to consume IBM Cloud services in any location that you want, with visibility across your locations. For more information, see [Pricing](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-pricing).





 Can I estimate my costs? 

When you create a resource such as a location or cluster, you can review a cost estimate in the Summary pane of the console. For other types of estimates, see [Estimating your costs](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost).

Keep in mind that some charges are not reflected in the estimate, such as the costs for your underlying infrastructure.





 Can I view and control my current usage? 

See [View your usage](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusageviewingusage) and [Set spending notifications](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-spending) for general IBM Cloud account guidance.





 What are the terms of the service level agreement? 

See the [IBM Cloud terms of service](https://cloud.ibm.com/docs/overview?topic=overview-slas) and the [Satellite additional service description](http://www.ibm.com/software/sla/sladb.nsf/sla/bm-8913-01).
Installing XenServer tools with Linux 

Use the followings steps to install XenServer Tools on your virtual machines that use CentOS, Debian, and Red Hat operating systems.

These steps are specifically for customer-managed XenServers, not IBM Cloud® provided virtual server instances.



1. Open XenCenter and establish a connection to your XenServer. See the example of a new virtual machine that does not have XenServer Tools set up. You can see that for Virtualization State:, the software says, "Tools not installed".
2. Right-click on the name of the virtual machine that you want to install XenServer Tools and then click Install XenServer Tools. A warning appears stating that, "Any CD or DVD that is in the virtual machine's CD drive ejects when xenServer Tools are installed."
3. Click Install XenServer Tools to continue.

On the console tab of XenCenter for your virtual machine, you see a CD image of "xs-tools.iso" that is loaded into the DVD drive. It also provides you with the device name within the system.
4. You can complete the following steps through either the console or through an SSH session to the system. By following this example, the installation uses SSH. The drive device name is provided by XenCenter.

$ ssh 10.17.37.243
root@10.17.37.243's password:
Last login: Thu Sep 11 12:57:31 2008 from 10.0.80.84
[root@ns0 ] cd /mnt
[root@ns0 mnt] ls
[root@ns0 mnt] mkdir xs-tools
[root@ns0 mnt] mount /dev/xvdd /mnt/xs-tools/
mount: block device /dev/xvdd is write-protected, mounting read-only
[root@ns0 mnt] cd /mnt/xs-tools/Linux/
[root@ns0 Linux] bash install.sh

The following changes are made to this virtual machine:
Using rclone 

Getting the most out of IBM Cloud® Object Storage when you have access to tools and solutions like rclone and the command-line interface (cli).



 Install rclone 

The rclone tool is useful for keeping directories synchronized and for migrating data between storage platforms. It's a Go program and comes as a single binary file.



 Quickstart Installation 



* [Download](https://rclone.org/downloads/) the relevant binary.
* Extract the rclone or rclone.exe binary from the archive.
* Run rclone config to set up.







 Installation by using a script 

Install rclone on Linux/macOS/BSD systems:

curl https://rclone.org/install.sh | sudo bash

Beta versions are available as well:

curl https://rclone.org/install.sh | sudo bash -s beta

The installation script checks the version of rclone installed first, and skips downloading if the current version is already up-to-date.





 Linux installation from precompiled binary 

First, fetch, and unpack the binary:

curl -O https://downloads.rclone.org/rclone-current-linux-amd64.zip
unzip rclone-current-linux-amd64.zip
cd rclone--linux-amd64

Next, copy the binary file to a sensible location:

sudo cp rclone /usr/bin/
sudo chown root:root /usr/bin/rclone
sudo chmod 755 /usr/bin/rclone

Install the documentation:

sudo mkdir -p /usr/local/share/man/man1
sudo cp rclone.1 /usr/local/share/man/man1/
sudo mandb

Run rclone config to set up:

rclone config





 macOS installation from precompiled binary 

First, download the rclone package:

cd && curl -O https://downloads.rclone.org/rclone-current-osx-amd64.zip
Key Protect instance and disk encryption key - If you use Key Protect, an instance and key can be selected to encrypt the deployment's disk. If you do not use your own key, the deployment automatically creates and manages its own disk encryption key.
Optional

Initial resource allocation - Specify initial memory and disk sizes for your databases. The minimum sizes of memory and disk are selected by default.
Optional

CPU allocation - Choose dedicated compute resources for your deployment. With dedicated cores, your resource group is given a single-tenant host with a minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. If not specified in the provisioning request by using the API or CLI, the default minimum is used.
Optional

Endpoints - Configure the [Service Endpoints](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-service-endpoints) on your deployment. The default is that connections to your deployment can be made from the public network.



After you select the appropriate settings, click Create to start the provisioning process.





 Using the CLI 

Use the [IBM Cloud CLI tool](https://www.ibm.com/cloud/cli) to communicate with IBM Cloud from your CLI.

To create a Cloud Databases deployment, use the IBM Cloud CLI tool to request a service instance with the service ID of the Cloud Databases resource you want to provision.

The command looks like:

ibmcloud resource service-instance-create <service-name> <service-id> <service-plan-id> <region> --service-endpoints <SERVICE_ENDPOINTS_TYPE>

For more information, see [Working with resources and resource groups](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_create).

To check provisioning status, use the following command that reports the current state of the service instance.

ibmcloud resource service-instance <service-name>
The installation may take a few minutes to complete.
11. [Verify that your PX-Backup service is installed correctly](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_backuppx-backup-verify).







 Verifying your PX-Backup installation 

Verify that PX-Backup is correctly installed on your cluster.

From the console



1. From the IBM Cloud [Resource list](https://cloud.ibm.com/resources), find the PX-Backup service that you created.
2. Review the Status column to see if the installation succeeded or failed. The status might take a few minutes to update.
3. If the status changes to Active, verify that the PX-Backup pods, services and jobs are running in your cluster.



1. From the IBM Cloud [Resource list](https://cloud.ibm.com/resources), select the cluster where you installed PX-Backup.
2. Open the Red Hat OpenShift web console.
3. Click on Projects.
4. Select the namespace where you installed the PX-Backup service components.
5. In the Inventory section, select the option to display your pods.
6. In the Pods table, verify that the status of each pod is Running.
7. Click on Networking>Routes.
8. Find the px-backup-ui route and verify that a URL is listed in the Location column.
9. Click Workloads>Jobs.
10. Verify that the pxcentral-post-install-hook job is complete.





From the CLI



1. From the IBM Cloud [Resource list](https://cloud.ibm.com/resources), find the PX-Backup service you created.
2. Review the Status column to see if the installation succeeded or failed. The status might take a few minutes to update.
3. If the status changes to Active, verify that the PX-Backup pods are running in your cluster.



1.
In [shared/install.sh](https://github.com/IBM-Cloud/vpc-tutorials/blob/master/vpc-app-deploy/shared/install.sh) is the cloud-init file used to initialize the frontend and the backend servers. You can pass the script with the --user-data parameter like this:

ibmcloud is instance-create ... --user-data @shared/install.sh
3. With the frontend and backend VSIs deployed and in maintenance mode, you could send a script to, e.g., the frontend server, then run the script to install software from the Internet. Send a script to the frontend server:

scp -F ../scripts/ssh.notstrict.config -o ProxyJump=root@$BASTION_IP_ADDRESS shared/uploaded.sh root@$FRONT_NIC_IP:/uploaded.sh

Then execute this script:

ssh -F ../scripts/ssh.notstrict.config -o ProxyJump=root@$BASTION_IP_ADDRESS root@$FRONT_NIC_IP sh /uploaded.sh

It can take a few minutes for the ssh service on the server to be initialized, and it will take a few more minutes for the cloud-init script to complete. The uploaded.sh script will wait for the initialization to complete before exiting.









 Step 3: Provisioning infrastructure with Terraform 

[Terraform](https://www.terraform.io/) enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.



 Before you begin 

Follow the instructions to [install Terraform and the IBM Cloud Provider plug-in for Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform) on your workstation.





 Provision a single virtual server instance