vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Supported memory and CPU combinations 

IBM Cloud® Code Engine applications, jobs, and functions consume CPU and memory. These amounts can vary, depending on if your workload is compute-intensive, memory-intensive, or balanced.

The use of ephemeral storage is now bounded by memory. The ephemeral storage in Code Engine cannot exceed the default value of 0.4 GB (400 MB) or the configured value for memory. If you need more than the default for ephemeral storage, you must increase your memory according to the valid combinations of vCPU and memory.

Consider the following examples of setting valid values for ephemeral storage:



* If memory is set to 0.25 GB, you can set ephemeral storage up to the default value of 0.4 GB.
* If ephemeral storage is set to 0.4 GB and memory is set to 2 GB, and you want to reduce the memory to 0.25 GB, this operation is valid because the ephemeral storage is set to its default value.
* If ephemeral storage is set to 0.5 GB and memory is set to 2 GB, and you want to reduce the memory to 0.25 GB, this operation is not valid because the ephemeral storage is now greater than the memory and its default of 0.4 GB. The ephemeral storage cannot exceed the default value of 0.4 GB or the configured value for memory.
* If ephemeral storage is set to 1 GB and memory is set to 4 GB, and you want to increase the ephemeral storage to 4 GB, this operation is valid because the ephemeral storage is less than or equal to the memory.
* If ephemeral storage is set to 1 GB and memory is set to 4 GB, and you want to reduce the memory to 2 GB, this operation is valid because the ephemeral storage is less than or equal to the memory.



For more information about memory or CPU limitations, see [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).



 Supported combinations 

See the following table for valid combinations of vCPU and memory.



Table 1. Valid vCPU and memory combinations

 CPU-intensive Balanced Memory-intensive
[Connection Details](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/equinix-connection-details.png)

Connection Details







 AT&T TAO / NetBond Essentials submits your Equinix order using the Equinix Fabric portal 

After the order is completed, AT&T will need to notify you that the Equinix order was submitted.

The IBM Special Network Services (SNS) team receives the Equinix request (submitted by AT&T on your behalf) and is able approve the connection in the buyer-side portal. You can view your newly created virtual connection for Direct Link by going to Connections. The connection will be in a pending, provisioning state (Pending Provider VLAN).

The timeline for approval is within 24-48 hours. If the 48-hour Service Level Agreement (SLA) is not acceptable, you can create an [IBM Support case](https://cloud.ibm.com/unifiedsupport/cases/form) and request that it be routed to the SNS team.
NFSv3 supports safe asynchronous writes and is more robust at error handling than the previous NFSv2. It supports 64-bit file sizes and offsets, allowing clients to access more than 2 GB of file data. NFSv3 natively supports no_root_squash that allows root clients to retain root permissions on the NFS share. NFSv4.1 is also supported. When File Storage for Classic is used in a VMware® deployment, NFSv4.1 might be the better choice for your implementation. For more information about the different features of each version and what is supported by VMware®, see [NFS Protocols and ESXi](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html).
* Follow VMware® specific best practice for teaming. If you plan to use teaming to increase the availability of your network access to the storage array, you must turn off port security on the switch for the two ports on which the virtual IP address is shared. The purpose of this port security setting is to prevent spoofing of IP addresses. Thus, many network administrators enable this setting. However, if you don't change it, the port security setting prevents failover of the virtual IP from one switch port to another. Then, teaming cannot fail over from one path to another. For most LAN switches, the port security is enabled on a port level and thus can be set on or off for each port.
Strings are matched regardless of whether the value is specified in uppercase or lowercase letters. The specified value can be a string or a number.

${Items}.contains('two')

This example returns true if the Items array contains any capitalization of the string two (for example, TWO or Two would also match).





 Array.filter(temp_var, "temp_var.property operator comparison_value") 

Filters an array by comparing each array element to a value you specify, returning a new array that contains only the matching elements.

The filter expression consists of the following values:



* temp_var: An arbitrary name for a temporary variable that is used to hold each array element as it is evaluated. For example, if the original array contains objects describing cities, you might use city as the temporary variable name.
* property: The element property that you want to filter on. This must be a property of the elements in the source array. Specify the property as a property of temp_var, using the syntax temp_var.property. For example, if latitude is a valid property name for the source elements, you might specify the property as city.latitude.
* operator: The operator to use to compare the property value to the comparison value. You can use any of the following operators:



Supported filter operators

 Operator Description 

 == Is equal to 
 > Is greater than 
 < Is less than 
 >= Is greater than or equal to 
 <= Is less than or equal to 
 != Is not equal to 



* comparison_value: The value that you want to compare each array element property value to. You can specify a literal value or reference a variable.





 Filter examples 

For example, you might have an array of objects containing city names and their population numbers:

[
{
"name":"Tokyo",
"population":13988129

},
{
"name":"Rome",
"population":2860009

},
{
"name":"Beijing",
"population":21893095

},
{
* lt (less than)
* lte (less than or equal to)



The results will be an exact match in case any of these operators are missing.
* --key-states

The state of the keys to be retrieved. List of strings containing valid states - Active, Suspended, Deactivated, Destroyed. (default: active,suspended,deactivated).
* -l, --key-search

List keys based on search string with prepended qualifiers (e.g. exact, not, alias, name). For more details, see the [API Documentation](https://cloud.ibm.com/apidocs/key-protectkp-get-key-search-api).
* -n, --number-of-keys

Restricts the number of keys to be retrieved. The default is 200 and the maximum is 5000.
* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.

Setting the output to JSON (--output json) includes the cloud resource name (CRN) in the output.
* -r, --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.
* -s, --starting-offset

Retrieves keys starting at the offset specified. The offset is zero-based, meaning offset 0 (zero) is the first key.
* -t, --key-type

The type of keys to be retrieved. If set to standard-key, standard keys will be retrieved. If set to root-key, root keys will be retrieved.









 kp region-set 

Target a different Key Protect regional endpoint.

ibmcloud kp region-set REGION
-i, --instance-id INSTANCE_ID
[-u, --unset]



 Examples 

These are examples of kp region-set.



 Example 1 

If the REGION parameter is not specified, you are prompted to select a region.
How to fix it 

It might be possible that the 32768 - 65535 range isn't large enough. Two possible solutions to this are the following options.



* Add more nodes and have at least one pod per node that make all these egress connections so that each node needs less than 30,000 SNAT ports. This is the preferred solution
* Explicitly set the pod natPortRange in Calico to a larger range. Note that this might cause the occasional port conflicts listed previously if you use VPC NLBs or add NodePort services or hostPort pods that use specific hardcoded ports



If you do want to set this port range, you must download the calicoctl binary, set the KUBECONFIG environment variable for the cluster, and run the following command where LOWER_RANGE_LIMIT is between 1025 and 32767.

This change takes effect immediately, and if you do this before updating your cluster master to 1.25 then the update doesn't overwrite what you set.

calicoctl patch felixconfiguration default --patch '{"spec":{"natPortRange": "LOWER_RANGE_LIMIT:65535"}}'
The Application Load Balancer for VPC automatically adjusts its capacity based on the load. When horizontal scaling takes place, the number of IP addresses associated with the application load balancer's DNS changes.





 What do I do if I use ACLs on the subnets that are used to deploy the application load balancer? 

Make sure that the proper ACL rules are in place to allow incoming traffic for configured listener ports. Traffic between the application load balancer and back-end instances need also be allowed.





 Why is my application load balancer in maintenance_pending state? 

The application load balancer is in maintenance_pending state during various maintenance activities, such as:



* Horizontal scaling activities
* Recovery activities
* Rolling upgrades to address vulnerabilities and apply security patches







 Why do I need to choose multiple subnets during provisioning? 

The Application Load Balancer for VPC (ALB) is Multi-Zone Region (MZR) ready. Load balancer appliances are deployed to the subnets you selected. To achieve higher availability and redundancy, deploy the application load balancer to subnets in different zones.





 Do I need extra IPs in the subnet for application load balancer operations? 

It is recommended to allocate 8 extra IPs per MZR to accommodate horizontal scaling and maintenance operations. If you provision your application load balancer with one subnet, allocate 16 extra IPs.





 What are the default settings and allowed values for health check parameters? 



* Health check interval - Default is 5 seconds, and the range is 2 - 60 seconds.
* Health check response timeout - Default is 2 seconds, and the range is 1 - 59 seconds.
* Maximum retry attempts - Default is two retry attempts, and the range is 1-10 retries.



The health check response timeout value must be less than the health check interval value.





 Are the ALB IP addresses fixed? 

Application load balancer IP addresses are not guaranteed to be fixed. During system maintenance or horizontal scaling, you see changes in the available IPs associated with the FQDN of your load balancer.

Use FQDN, rather than cached IP addresses.





 Does the load balancer support layer 7 switching?
The health check response timeout value must be less than the health check interval value.





 Are the ALB IP addresses fixed? 

Application load balancer IP addresses are not guaranteed to be fixed. During system maintenance or horizontal scaling, you see changes in the available IPs associated with the FQDN of your load balancer.

Use FQDN, rather than cached IP addresses.





 Does the load balancer support layer 7 switching? 

Yes, the load balancer supports layer 7 switching.





 Why does HTTPS listener creation or update tell me that my certificate is invalid? 

Check for these possibilities:



* The provided certificate CRN might not be valid.
* The certificate instance in the Secrets Manager might not have an associated private key.







 What is the role of application load balancer front-end listeners? 

Load balancer front-end listeners are the listening ports for the application. They act as proxies for back-end pools.





 Why are there only 2 IPs instead of 3? 

The Application Load Balancer for VPC (ALB) operates in ACTIVE-ACTIVE mode, a configuration that makes it highly available. Horizontal scaling might further add extra appliances when your load increases. The recommendation is that you choose subnets in different zones to make your load balancers support MZR. This way, if a zone is negatively impacted, a new load balancer is provisioned in a different zone.





 If a pool is attached to an instance group, what is the maximum number of back-end members that I can have in a pool? 

The maximum number of back-end members that are allowed in a pool is 50. So if an instance group is attached to a pool, the number of instances in the group can't scale up beyond this limit.





 Why is my listener not receiving traffic? 

Make sure that the security group rules that are attached to your load balancer allow incoming ingress and outgoing egress traffic on your listener's port. Security groups attached to your load balancer can be found on your load balancer's overview page. Locate the Attached security groups tab from the load balancer overview, then select the security groups that you want to view and modify their rules.
A "true" value indicates that you have agreed to one of the following two conditions:



1. If you are deploying a production cluster, you have confirmed with your business team that you have enough licenses to deploy the IBM Spectrum LSF on IBM Cloud and that these licenses are covered for use under the International Program License Agreement (IPLA).
2. You are deploying an evaluation cluster with IBM Spectrum LSF on IBM Cloud and agree to abide by the International License Agreement for Evaluation of Program (ILAE).



IBM terms of software use for both IPLA and ILAE can be found [here](https://www-03.ibm.com/software/sla/sladb.nsf/sla/bla).

 How to fix it 

After you agree to one of the two conditions, update the property value to "true" and try again.





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an authorization error? 

 What’s happening 

Schematics isn't able to provision the cluster, and you are seeing the following error message: Request is not authorized. Check your user permissions and authorizations and try again.

 Why it’s happening 

You don't have the required access to get any VPC resources provisioned.

 How to fix it 

Contact your account administrator and get all of the required accesses. For more information, see [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an error that the provided name is not unique? 

 What’s happening 

Schematics isn't able to provision the cluster, and you are seeing the following example error message:

"code": "validation_unique_failed",
"message": "Provided Name (sample-symphony-vpc) is not unique",
"target": {
"name": "name",
"type": "field",
"value": "sample-symphony-vpc"
}
Modifying a Power Systems Virtual Server instance 

Learn how to modify your Power® Systems Virtual Server to better meet your business needs.



 Resizing an instance by using the Power Systems Virtual Server user interface 

To resize a Power Systems Virtual Server instance after its [initial creation](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-creating-power-virtual-server), complete the following steps:



1. Go to Virtual server instances in the Power Systems Virtual Server user interface and click your instance.
2. Click the Edit details in the server details pane.
3. A menu appears after you click the Edit icon. Here, you can change your instance's Name, Entitled capacity, Memory (GB), and VM pinning state.

If the VM is inactive or shut down, you can change the processor type to Dedicated processor, Uncapped shared processor or Capped shared processor.
4. Check the service agreement box and click Order to complete the instance modification process and accept the price.
5. View the Server details pane to verify your instance modification.





 Resizing the virtual machine core count and memory 

You can scale up and scale down the core count and memory of the virtual machine (VM) as per your workload requirements. When the VM is active, you can resize the memory and core counts to a maximum of eight times of the specified values, and to a minimum of 1/8 times of the specified values when the VM was provisioned. However, you cannot resize the memory and core count to less than 0.25 cores and 2 GB memory. You can resize the memory and core count beyond the 8x and 1/8x boundaries when the VM is shut down. The following table shows an example of recalculated values:

When VM is active

When VM is shut down



Table 1. Resizing VM core count and memory when the VM is active

 Specified value when the VM instance was provisioned Minimum resize value (must be greater than or equal to 0.25 cores, 2 GB memory) Maximum resize value
The property lsf_license_confirmation only accepts "true" as a valid value. A "true" value indicates that you have agreed to one of the following two conditions:



1. If you are deploying a production cluster, you have confirmed with your business team that you have enough licenses to deploy the IBM Spectrum LSF on IBM Cloud and that these licenses are covered for use under the International Program License Agreement (IPLA).
2. You are deploying an evaluation cluster with IBM Spectrum LSF on IBM Cloud and agree to abide by the International License Agreement for Evaluation of Program (ILAE).



IBM terms of software use for both IPLA and ILAE can be found [here](https://www-03.ibm.com/software/sla/sladb.nsf/sla/bla).

 How to fix it 

After you agree to one of the two conditions, update the property value to "true" and try again.





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an authorization error? 

 What’s happening 

Schematics isn't able to provision the cluster, and you are seeing the following error message: Request is not authorized. Check your user permissions and authorizations and try again.

 Why it’s happening 

You don't have the required access to get any VPC resources provisioned.

 How to fix it 

Contact your account administrator and get all of the required accesses. For more information, see [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an error that the provided name is not unique? 

 What’s happening 

Schematics isn't able to provision the cluster, and you are seeing the following example error message:

"code": "validation_unique_failed",
"message": "Provided Name (sample-lsf-vpc) is not unique",
"target": {
"name": "name",
"type": "field",
If you prefer a different default logging level than Information for all loggers on the node, select a new logging level (Fatal, Panic, Error, Warning, Information, Debug) from the Default logging level list. All loggers for the node will use use the selected default log level unless overridden on this panel by providing the specific log levels for the loggers that you need for debugging. There is no “master list” of loggers, and this panel does not validate whether the loggers exist. You can see the names of the available loggers in the node logs, or you can read the Fabric source code to discover what loggers are available. For ease of use, the following set of logging specification strings is provided and can be pasted into the Logging specification field on the Advanced tab to customize the logging according to your debug needs:



Table 2. Useful logging specification strings

 Component Debug type Logging specification 

 Peer Smart contracts info:dockercontroller,endorser,chaincode,chaincode.platform=debug 
 Peer Private data info:kvledger,ledgerstorage,transientstore,pvtdatastorage,gossip.privdata=debug 
 Peer Ledger and state database info:kvledger,lockbasedtxmgr,ledgerstorage,stateleveldb,statecouchdb,couchdb=debug 
 Peer Full debug, with the noisy components set to info debug:cauthdsl,policies,msp,grpc,peer.gossip.mcs,gossip,leveldbhelper=info 
 Ordering node Full debug, with the noisy components set to info debug:cauthdsl,policies,msp,grpc,orderer.consensus.etcdraft,orderer.common.cluster,orderer.common.cluster.step,common.configtx,blkstorage=info 



A word on the logging specification syntax. Notice that the terms are separated by a colon. If a term does not include a specific logger, for example info: then it is applied as the default log level, regardless of what is specified on the Simple tab.
RAID 1 (Mirrored set without parity) Implements data mirroring. Data is duplicated on 2 or 4 disks through a hardware raid controller and provides some fault tolerance. The array is recoverable if at least one drive does not fail. It provides faster read performance than a single drive and provides drive redundancy if a drive failure occurs. Write speed is slightly reduced.

RAID 5 (Striped set with dual distributed parity) Implements data striping at a block level and distributes parity among the disks. The parity information allows recovery from the failure of any single drive because any following reads can be calculated from the distributed parity. RAID 5 also allows for increased read/write speeds and allows the most efficient use of disk space. RAID 5 requires a minimum of three disks.

RAID 6 (Double parity) Implements double parity stripes on each disk and allows two disks to fail before any data is lost. Because RAID 6 has a capacity of two disk units that are dedicated to storing parity data in a parity set, greater I/O operations occur with RAID 6 than with RAID 5. These greater I/O operations can decrease performance. RAID 6 requires a minimum of 4 disks and maximum of 18 disks.

RAID 10 (RAID 1 + 0) Creates multiple mirrors, where data is organized as stripes across multiple disks and then the striped disk sets are mirrored. RAID 10 offers the same fault tolerance as RAID 1 with increased read/write speeds over a single Raid 1 volume or single drive. RAID Level 10 requires four disks to implement.