vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you add a worker pool, it is not assigned a zone by default. You specify the number of workers that you want in each zone and the flavors for the workers. The worker pool is given the default Kubernetes versions. To finish creating the workers, [add a zone or zones](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_zone_add) to your pool.

To create a worker pool in a VPC cluster, use the [ibmcloud ks worker-pool create vpc-gen2 command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clicli_worker_pool_create_vpc_gen2).

ibmcloud ks worker-pool create classic --name POOL_NAME --cluster CLUSTER --flavor FLAVOR --size-per-zone WORKERS_PER_ZONE --hardware ISOLATION [--disable-disk-encrypt] [--label KEY1=VALUE1] [--operating-system SYSTEM] [-q] [--output json]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--name POOL_NAME
: The name that you want to give your worker pool.

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--flavor FLAVOR
: Choose a machine type, or flavor. You can deploy your worker nodes as virtual machines on shared or dedicated hardware, or as physical machines on bare metal. Available physical and virtual machines types vary by the zone in which you deploy the cluster. For more information, see the documentation for the ibmcloud ks flavors (machine-types)[command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_machine_types). This value is required for standard clusters and is not available for free clusters.

--size-per-zone WORKERS_PER_ZONE
: The number of workers to create in each zone.
* 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. At the end of the log is information that you need to deploy different SAP products and databases. Copy and save this information for your deployments. For example:

2022/08/17 10:30:11 Terraform apply | FLOATING-IP = "xxx.xxx.xxx.xx"
2022/08/17 10:30:11 Terraform apply | HOSTNAME = "myhost"
2022/08/17 10:30:11 Terraform apply | PRIVATE-IP = "xx.xxx.xx.x"
2022/08/17 10:30:11 Terraform apply | REGION = "eu-gb"
2022/08/17 10:30:11 Terraform apply | SECURITY_GROUP = "secgrp-myhost"
2022/08/17 10:30:11 Terraform apply | SUBNET = "myvpc-subnet"
2022/08/17 10:30:11 Terraform apply | VPC = "myvpc"
2022/08/17 10:30:11 Terraform apply | ZONE = "eu-gb-1"



This automation is offered free of charge however, the provisioned infrastructure comes at cost.
For more information, see [MP3](https://wikipedia.org/wiki/MP3).





 audio/mulaw format 

8-bit mu-law (or u-law) audio is a single-channel, lossy audio format that is encoded by using 8-bit mu-law data. You must specify the sampling rate with this audio format. For example, specify audio/mulaw;rate=16000 for audio that is sampled at 16 kHz.

For more information, see [M-law algorithm](https://wikipedia.org/wiki/M-law_algorithm).





 audio/ogg format 

Ogg format (.ogg) is a free, open container format that is maintained by the Xiph.org Foundation. You can specify the codecs parameter with the format to request an audio stream that is compressed with one of the following codecs:



* The Opus codec by specifying audio/ogg;codecs=opus. You can optionally specify a sampling rate other than the default 48,000 Hz. Only the following values are valid sampling rates: 48000, 24000, 16000, 12000, or 8000. If you specify a value other than one of these, the service returns an error.

A current limitation causes the service to disregard a valid sampling rate. The service always returns the audio with a sampling rate of 48 kHz.
* The Vorbis codec by specifying audio/ogg;codecs=vorbis or simply audio/ogg. You can optionally specify a sampling rate other than the default 22,050 Hz.



Both codecs are free, open, lossy audio-compression formats. Opus is the preferred codec, but per the Ogg specification, the service returns the audio in Vorbis format if you omit the codec. If you omit an audio format altogether, the service returns the audio in Ogg format with the Opus codec by default.

For more information, see



* [xiph.org/ogg](https://www.xiph.org/ogg/)
* [xiph.org/vorbis](https://xiph.org/vorbis/)
Whereas for IBM purposes, after a completed migration, the license can be reused for a different server migration. The original host that the license was assigned to just needs to be deleted from the RMM server database.

The number of concurrent migrations that can occur is limited up to the number of licenses procured.





 How do I obtain and activate my promotional license? 

You can retrieve the promotional license through the discovery script that is part of the RMM software appliance. For more information on how to use the script, see [Bare metal to virtual server migration on a private network with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-pv-migration-private-network).





 What are the considerations or limitations for the physical to virtual migration? 

For more information on considerations and limitations of the physical to virtual migration, see [Bare metal to virtual server migration overview](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-pv-migration-overview).





 Is the migration intrusive? 

In most cases, the migration is not intrusive. The migration can be done when the server is up and running. The source server does need some free space to do an image capture of the server. In addition, RMM does require SSH (port 22) reachability to both server and target to perform the migration. The CPU consumption for image capture and copying to the target is minimal.





 Can RackWare RMM create the target virtual server instance? 

Yes. With RMM Auto-Provision feature, you can create the target virtual server instance. For more information, see ["Bare metal to virtual server migration on a private network with RMM": option 2 of Step 1: Set up and provision VPC and virtual server instance](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-pv-migration-private-networkset-up-provision-vpc-vsi).
About bare metal custom image templates 

Image templates provide an imaging option for IBM Cloud® Bare Metal Servers. With Bare Metal Servers custom image templates, you can capture an image of a bare metal server to replicate its configuration with minimal changes in the order process.

Image templates are not intended for backing up your data.



 How bare metal custom image templates work 

The two main actions for any image template are create and deploy. When you request to create an image, a compressed backup of your data is created. The configuration information is recorded and the image template is stored on the IBM Cloud. During the deployment stage of the image template, the automated system constructs a new server that is based on the data that is gathered from the selected image. The deployment process makes adjustments for volume, restores the copied data, and then makes final configuration changes (for example, network configurations) for the new host.

Make sure that your image works fine during deployment before you reclaim the source server.



 Compatible system configurations 

The following features and configurations are supported when you create an image template.



* Full traditional BIOS boot mode support and limited UEFI boot mode support (images must be deployed on their respective servers)
* Only available for X10, X11, and Lenovo systems
* vGPU support
* RAID 0, 1, 10







 Supported operating systems 

The following operating systems are supported when you create an image template.



* CentOS 7.x
* RHEL 7.x, 8.x
* Ubuntu 18, 20
* Windows 2012 R2, 2016, 2019







 Supported add-ons 

The following add-ons are compatible with image templates.



* McAfee (free license add-on)
* MySQL (free license add-on)
* Microsoft SQL Server
* R1Soft client



If your bare metal server has add-on software such as cPanel, MS SQL Server, Plesk, or R1Soft Backup Agent, you need to follow the vendor migration guidelines instead of capturing and deploying a custom image.
For more information about how to increase the size of a cluster, see scaling [Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-caca) or [OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-ca) clusters. If you have enough space in your cluster, you can continue with step 3.
3. Use the console to deploy or resize your node. If your Kubernetes pod is large enough to accommodate the new size of the node, the reallocation should proceed smoothly. If the worker node that the pod is running on is running out of resources, you can add a new larger worker node to your cluster and then delete the existing working node.





Table 2. Default resources for nodes on IBM Blockchain Platform

 Component (all containers) CPU** Memory (GB) Storage (GB) 

 Peer (Hyperledger Fabric v1.4) 1.1 2.8 200 (includes 100GB for peer and 100GB for state database) 
 Peer (Hyperledger Fabric v2.x) 0.7 2.0 200 (includes 100GB for peer and 100GB for state database) 
 CA 0.1 0.2 20 
 Ordering node 0.35 0.7 100 
 Operator 0.1 0.2 0 
 Console 1.2 2.4 10 



** Actual VPC allocations are visible in the blockchain console when a node is deployed.

Note that when smart contracts are installed on peers that run a Fabric v2.x image, the smart contract is launched in its own pod instead of a separate container on the peer, which accounts for the smaller amount of resources required on the peer.

While users of a free cluster must use default sizes for the containers associated with their nodes, users of paid clusters can set these values while the node is being created by clicking the Resource allocation box during the creation of their nodes. If this box is not checked, the default resource allocations, which can be seen below, will be used.
The name must not begin or end with a special character, and must be limited to 40 characters in length. Enter a unique load balancer name. For example, "ui-servers" or "backend-servers". 
 Format error found in given load balancer name. The load balancer name is mandatory. Use only alphanumeric characters (or special characters '-' and '.') for the name. The name must not begin or end with a special character, and must be limited to 40 characters in length. Enter a unique load balancer name. For example, "ui-servers" or "backend-servers". 
 Load balancer with the same name (case insensitive) already exists. A load balancer with the same name exists. Enter a unique load balancer name to proceed further, for example, "ui-servers" or "backend-servers". 
 Load balancer description must be a string and not exceed 255 characters. The load balancer description must be a string that does not exceed 255 characters. Limit the description to 255 characters. 
 Frontend port 80 is already used. You might have entered a front-end port that is already in use. Enter a unique front end port. 
 Backend port must be an integer. You might have entered an invalid back-end port value. Enter a back-end port number between 1 and 65535. 
 Since the protocol and port are not editable in health monitor, this error is impossible from UI. Your private subnet is not a standard type and cannot be used to create the load balancer. Contact IBM Support. 
 Private subnet 'xyz' must have at least 'n' free IP addresses. The selected private subnet does not have any free IP addresses. Check these [troubleshooting steps](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-load-balancer-provisioning-troubleshooting) for more information. 
 Specified private subnet VLAN is on router 'xyz'.
A managed key or internal keystore can be created only in a vault. When you connect to an external keystore, you need to assign it to a vault. To use a managed key for encryption and decryption, you need to install it in one or more keystores within the same vault. The vault keeps all installations of a managed key in sync.





 Managed key 

A managed key is a key that is created in and assigned to a vault. You can use a managed key for encryption and decryption only when it is activated in at least one target keystore.





 Target keystore 

A target keystore is keystore that is assigned to a vault. If it is an internal keystore, it can be created only in a vault.





 Internal keystore 

An internal keystore is a keystore that is created in your Hyper Protect Crypto Services instance to store the cryptographic keys in your service instance. You can create up to five free KMS keystores to manage your keys.





 External keystore 

An external keystore is a keystore that is not in your Hyper Protect Crypto Services instance. You can connect your service instance to another key management instance on IBM Cloud such as Hyper Protect Crypto Services, Key Protect, or Key Protect on Satellite, potentially in another region. Or, you can connect your service instance to external keystores from other cloud providers such as Microsoft Azure Key Vault, AWS Key Management Service (KMS), and Google Cloud KMS.
(https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/bfcircle3.svg) After a Snapshot copy is created, the active file system and Snapshot copy point to the same disk blocks. The Snapshot copy doesn't use extra disk space. 
 ![The space that is used when something changes after a snapshot copy was taken.](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/bfcircle2.svg) After myfile.txt is deleted from the active file system, the Snapshot copy still includes the file, and references its disk blocks. Thus, deleting active file system data doesn't always free up disk space. 



For more information about snapshot space usage, see [Managing Snapshots](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-managingSnapshots).
Loading data from on-premises systems with IBM Lift CLI 

[IBM Lift CLI](https://www.lift-cli.cloud.ibm.com) is a free ground-to-cloud data migration tool that securely moves your data from on-premises systems to IBM® Db2® Warehouse on Cloud plans hosted on IBM Cloud. IBM Lift CLI is available for the Flex One, Flex, and Flex Performance plans hosted on IBM Cloud.

The Lift application migrates your data to the IBM Cloud from the various data sources listed in Table 1.



Table 1. Migration data sources

 Target database on IBM Cloud  Data source                       

 IBM Db2 Warehouse on Cloud    IBM Db2                           
                               IBM Db2 Warehouse                 
                               IBM Integrated Analytics System   
                               IBM PureData System for Analytics 
                               Oracle Database                   
                               Microsoft SQL Server              
                               CSV file format                   



To download and install Lift, see: [Download Lift](https://www.lift-cli.cloud.ibm.com/download).

For step-by-step instructions about migrating your data to the IBM Cloud by using Lift, see: [Migrate data to IBM® Db2® Warehouse on Cloud](https://www.lift-cli.cloud.ibm.com/docs).
Categories are used to organize products in the catalog based on common solutions, function, or use.
4. Enter keywords that users might use when they search the catalog for your product, for example, virtual machine, compute,terraform, and power.
5. Provide a list of features that highlights your product's attributes and benefits for users.

Use a descriptive title and 1 - 2 sentences for each feature. You want the information to be visually scannable for users.
6. Provide a detailed description of your product that explains its value and what users gain by using it. The detailed description is displayed at the beginning of your product page in the catalog. You can expand on the short description that you provide for your catalog entry, but don't simply repeat it.
7. Provide links to high-quality images or videos to help illustrate what your product is, its value, and user benefits. The supported media types are images, videos in MP4 or WebM file format, and videos hosted on YouTube or Vimeo.

Some examples of effective media include an introductory walkthrough of your product, an explanation of what your product is and why users might want to use it, or a comparison of certain features.
8. Provide a link to your product's warranted documentation.







 Step 4: Define your pricing model 

IBM Cloud supports two pricing models: free or bring your own license (BYOL). With the free pricing model, users can deploy as many instances with no additional software charges incurred. With the BYOL pricing model, IBM Cloud doesn't charge users for the usage of the software, and the third-party provider is responsible for licensing entitlement and enforcement.

For the purposes of this tutorial, complete the following steps to add a BYOL pricing plan.



1. Click Pricing > Pricing plans.
2. Click Add plan > BYOL.
3. Enter the name, URL, and description of the license, for example:





* Name: BYOL for Example Corp Virtual Server Image 1.0.0
* URL: byol.vsimage.examplecorp.html
* Description: This BYOL license is required for the installation and use of the Example Corp Virtual Server Image.
* Can the NetScaler be configured to report the client's source IP address instead of the source IP of the NetScaler appliance?

Yes, the Use Source IP (USIP) parameter can be set to YES within the NetScaler Advanced Management Interface to allow reporting of the client's source IP instead of that of the NetScaler.

Enabling the USIP address mode on the appliance adds flexibility to the appliance to use the client IP address, available in the IP header, when communicating to the server. By enabling this mode, the appliance opens server connections with the client IP address and also factors the client IP address in connection reuse. Therefore, this mode facilitates limited reuse per client based on client IP address.
* What are the various ports used to exchange the HA-related information between the nodes in an HA configuration?

Port 3010, for synchronization and command propagation. UDP Port 3003, to exchange heartbeat packets.
* What version of NetScaler VPX includes global server load balancing (GSLB)?

Platinum.
* Can I have NetScaler in HA configuration?

Yes, NetScaler VPX appliances support High Availability (HA) configurations.

NetScaler VPX servers are not redundant, unless configured in HA mode with a partner. As part of your back up and recovery strategy, it is highly recommended to deploy an HA environment when using NetScaler VPX.

It is also important to provide redundancy for other hardware and software components. For example, power supplies and local disk drives may not have redundancy. A failure in these components may result in data loss.
* Does the IBM Cloud NetScaler offering include SSL VPN functionality?

Yes, this feature is known as NetScaler Gateway™ and is included in all editions. For more information regarding this feature please visit the [Citrix website")](https://www.citrix.com/products/netscaler-adc/)



Cloud Internet Services (CIS)



* What do I get with a Free Trial Plan?

The Free Trial plan, by design, allows only one zone per account. It is recommended that only one instance be created per account and the zone name be verified.
With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $30 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with 3 dedicated cores per member, that is a total of 9 cores and is billed at $270 per month.

Dedicated cores are an optional feature. The default Shared CPU setting provisions your deployment on hosts with shared compute resources and incurs no additional charge.





 Backups Pricing 

You receive your total disk space purchased, per database, in free backup storage. For example, in a given month, if your Databases for Elasticsearch deployment has 20 GB of disk per member and three data members, you receive 60 GB of backup storage free for that month. If your backup storage utilization is greater than 60 GB for the month (in this scenario), you are charged an overage of $0.03/month per gigabyte.

By default, Cloud Databases provides a daily backup that is stored for 30 days. These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB. In this scenario, your backup costs are (450 GB - 60 GB) * 0.03 = $11.7 per month.

Most deployments will not ever go over the allotted credit.





 Scaling per Member 

Databases for Elasticsearch deployments have minimum and maximum allocation for disk and RAM as shown. Scaling deployments through the API/CLI provides more granularity and also allows a user to scale a database instance up to 4 TB of disk per member.



Table 1. Per Member Scaling Limits

 Resource Minimum Maximum Scaling Granularity (API/CLI) 

 Disk 5 GB per member 4 TB per member 1024 MB per member
Learn more about IBM Cloud Hyper Protect Virtual Servers' Data usage and Certifications [here](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=165C6EF0FFDA11E8BABD512A6952EE1F).





 CLI commands 





 hpvs help 

This command displays a list of hpvs commands.

ibmcloud hpvs help





 hpvs instances 

This command lists all your Hyper Protect Virtual Servers instances.

ibmcloud hpvs instances [--output json]



 Command options 

--output
: Displays results in the requested format. The only valid value is json.







 hpvs instance 

This command shows details about the server instance.

ibmcloud hpvs instance (NAME | CRN) [--output json]

NAME
: The name of your new instance. An error message is displayed if you specify a NAME that is not unique, for example,

VS name 'ABC' is ambiguous: more than one VS exist for the provided name: [crn1 crn2].

Specify the CRN if your instance name is not unique.

CRN
: The server's Cloud resource name (CRN). Specify the CRN if NAME is not unique. You can run the ibmcloud hpvs instances command to get the CRN.



 Command options 

--output
: Displays results in the requested format. The only valid value is json.





 Example output 

Name hpvs-env-test
CRN crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:0b2df6e9-ec2c-4b4a-87dd-60f53f6a2a0d::
Location dal13
Cloud tags
Cloud state active
Server status running
Plan Free
Public IP address 52.116.29.73
Internal IP address 172.17.151.218
Storage 50 GiB