vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Options:
-o, --origin-snapshot-id INTEGER
ID of an origin volume snapshot to use for
duplcation.
-c, --duplicate-size INTEGER Size of duplicate block volume in GB. If
no size is specified, the size of the origin
volume will be used.
Potential Sizes:
[20, 40, 80, 100, 250, 500, 1000, 2000,
4000, 8000, 12000] Minimum: [the size of the
origin volume]
-i, --duplicate-iops INTEGER Performance Storage IOPS, between 100 and
6000 in multiples of 100 [only used for
performance volumes] If no IOPS value is
specified, the IOPS value of the origin
volume will be used.
Requirements: [If
IOPS/GB for the origin volume is less than
0.3, IOPS/GB for the duplicate must also be
less than 0.3. If IOPS/GB for the origin
volume is greater than or equal to 0.3,
IOPS/GB for the duplicate must also be
greater than or equal to 0.3.]
-t, --duplicate-tier [0.25|2|4|10]
Endurance Storage Tier (IOPS per GB) [only
used for endurance volumes] If no tier is
specified, the tier of the origin volume
will be used.
Requirements: [If IOPS/GB
for the origin volume is 0.25, IOPS/GB for
the duplicate must also be 0.25. If IOPS/GB
for the origin volume is greater than 0.25,
IOPS/GB for the duplicate must also be
greater than 0.25.]
-s, --duplicate-snapshot-size INTEGER
The size of snapshot space to order for the
duplicate. If no snapshot space size is
specified, the snapshot space size of the
origin block volume will be used.
Input
"0" for this parameter to order a duplicate
volume with no snapshot space.
See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 What is the impact if I don't upgrade vSphere 6.x on my VMware Solutions - vCenter Server hosts? 

Upgrading your vSphere software is a customer responsibility and the decision to upgrade to a supported version is yours. However, your business might be at risk because VMware is under no obligation to provide product patches and updates, such as security updates and bug fixes. IBM Cloud support for ordering all update levels of VMware vSphere 6.x ended on 10 October 2021 and you can no longer order new vCenter Server instances with vSphere 6.x.

IBM Cloud recommends upgrading to 7.x. If your vCenter Server instance is running NSX-V, consider moving to vCenter Server with NSX-T. This lift and shift upgrade approach can be more beneficial due to the end of support of NSX-V. You might benefit from a target platform with updated hardware, upgraded VMware software, NSX-T, and less of an impact lift and shift migration rather than an in-place upgrade.

See also [different ways to run VMware workloads in IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-v2t-migrationfaq-v2t-migration-vmware-platforms).





 If I'm using BYOL on my IBM Cloud bare metal hosts, how does it impact the upgrade? 

Upgrading vSphere software is your responsibility. However, with Bring Your Own License (BYOL) you can access VMware Support directly by using your license agreement. IBM Cloud provides support for your bare metal servers infrastructure on IBM Cloud.
Why do I see a vSphere console configuration issue when I add a high-availability cluster? 

  What’s happening 

When you add a High Availability (HA) cluster configuration with only one file share, the following configuration issue is seen on the VMware ESXi™ hosts:

The number of heartbeat datastores for host is 1, which is less than required: 2

  Why it’s happening 

This issue occurs if redundancy is not in shared storage to allow for data store heart beating.

  How to fix it 

For more information about how to fix the problem, see [How to add the number of vSphere HA heartbeat datastores for the ESXi host](https://communities.vmware.com/t5/VMware-vSphere-Discussions/How-to-add-the-number-of-vSphere-HA-heartbeat-datastores-for-the/td-p/1415119).
(https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/max-path-length.svg)

Figure 3. Three-level certificate authority hierarchy

The maximum path length that you define does not include leaf certificates. In the previous example, the subordinate CA in level 4 can issue leaf certificates but is unable to have more CA certificates in its path.





 Choosing a validity period for your certificates 

The validity period of an X.509 certificate is a required field that determines how long the certificate is trusted and remains valid. When you plan your CA hierarchy, work backwards from your preferred lifespan for the leaf certificates that you want to issue to your applications. Then, determine the validity period of the CA certificates.

A certificate must have a validity period that is shorter than or equal to the validity period for the CA that issued it. For example, if you create a root CA with a time-to-live (TTL) of 10 years, any intermediate CAs that are subordinate to it must have a TTL that is equal to or less than 10 years. Likewise, if an intermediate CA has TTL of 3 years, any leaf certificates must have a TTL that is equal to or less than 3 years.



1. Choose a validity period for your leaf certificates that is appropriate for your use case.

The private certificates that you can create with Secrets Manager are considered leaf certificates that can be issued to an end-entity, such as a client or server app. With Secrets Manager, you can create certificates with a maximum validity period of three years or 36 months. After you determine a TTL or validity period for leaf certificates, you set the value by using a [certificate template](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificate-templates) so that your preferred TTL is applied each time a new leaf certificate is generated.

The shorter the TTL of your leaf certificates, the more protected you are against inadvertent exposure or compromise of your certificate and its private key.
If you need assistance with IBM Cloud for VMware Solutions, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).
* Can I bring my own firewall?

Yes. Each customer virtual data center comes with an edge firewall in the ESG and a distributed firewall that protects the internal virtual data center environment. If you want to bring your own firewall such as Fortinet or Cisco CSR, you can do so and run it between the ESG and your internal virtual machines.
* Can I bring my own IP addresses?

You can bring your own IP addresses within your virtual data centers with a few restrictions:



* The IP addresses 166.9.0.0/16 is reserved for IBM Cloud service endpoints.
* The IP addresses 52.117.132.0/24 is reserved for other IBM Cloud services.



Other than the IP addresses used for internet access on each customer ESG, you can use any IP address that you want. Typically, you use an IPsec tunnel from the on-premises environment to your virtual data centers, which provides transparent networking with full BYIP capabilities.
* Can I bring a custom image?

Yes. VMware Cloud Director supports the same set of guest operating systems as VMware vSphere® 6.7. For more information, see [VMware Guest OS Compatibility Guide](https://www.vmware.com/resources/compatibility/pdf/VMware_GOS_Compatibility_Guide.pdf).

VMware Shared provides Microsoft® Windows® server 2016/2019 templates. You can provide your own image to run other versions.
* What are the Service Level Agreement options with VMware Shared?

VMware Shared uses the IBM Cloud standard Service Level Agreement (SLA). SLAs are not offered for virtual machines and vApps.
Understanding high availability for projects 

IBM Cloud® projects is a general availability (GA) service that is offered in multiple regions: Dallas, Washington, Toronto, Sao Paulo, Frankfurt, Tokyo, Sydney, Osaka, and London. Each location has three different data centers for redundancy. The data for each location is kept in the three data centers near that location. If all of the data centers in a location fail, the projects service for that location becomes unavailable.

See [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the disaster recovery standards. You can also find information about IBM Cloud [Service Level Objectives](https://cloud.ibm.com/docs/overview?topic=overview-slo).



 Responsibilities 

For more information about high availability and disaster recovery and your responsibilities when you use projects, see [Understanding your responsibilities when using projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-responsibilities-projects).





 What level of availability do I need? 

You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that is correct for you depends on several factors, such as your business requirements, the service level agreements (SLAs) that you have with your customers, and the resources that you want to expend.





 What level of availability does IBM Cloud offer? 

The level of availability that you set up for your cluster impacts your coverage under the IBM Cloud high availability service level agreement terms.

Service level objectives (SLOs) describe the design points that the IBM Cloud services are engineered to meet. Projects are designed to achieve the following availability target.



Table 1. SLO for projects

 Availability target Target Value 

 Availability % 99.999% 



The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs.
* The version component provides the operating system version, such as 18-04 for Ubuntu 18.04, or 2012-r2 for Windows 2012 R2.
* The type component provides the minimization level of the operating system image, such as minimal or full.
* The architecture component provides the vCPU architecture that is supported by the operating system image, such as amd64.
* The build component is a small, non-negative integer that is incremented each time a new build of the operating system is created. For image names that are otherwise identical, the image with the highest build value is the most recent image for that operating system.



You can obtain the current list of images, including stock images, by running the following command in the command-line interface: [ibmcloud is images](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencecompute-images).

The image naming convention is subject to change. The list of image names is not intended to be programmatically parsed or interpreted. You can use the [GET /images](https://cloud.ibm.com/apidocs/vpcget-image) API to obtain metadata in a structured format.







 Custom images 

You can import an image from IBM Cloud Object Storage to use for creating a new virtual server instance.



 Requirements 

Custom images must meet the following requirements:



* Contain a single file or volume
* Is in qcow2 or vhd format
* Is cloud-init enabled
* The operating system is supported as a stock image
* Size doesn't exceed 250 GB
* Size isn't less than 10 GB, images less than 10 GB are rounded up to 10 GB



For more information about custom images, see [Planning for custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images).







 Next steps 

After you choose a profile, it's time to plan for and create an instance.



* [Planning for instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_best_practices)
Often that requires the restoring of backups that are taken in the primary site. This approach is not recommended when losing data can be a problem, for example when the RPO is less than a few hours or when the availability of the service is critical and the RTO objective is less than a few hours.

Active/Standby
: In the Active/Standby case, the full application stack is active in both the primary and backup location. However, user's transactions are served by the primary site only. The backup site takes care of keeping a replica of the status of the main location though data replication, such as database replication or disk replication. In cases of prolonged unavailability of the primary site, all client transactions are routed to the backup site. This approach provides good RPO and RTO, generally measured in minutes; however, it is significantly more expensive than the Active/Passive options because of the double deployment. For example, resources are wasted because the standby assets can't be used to improve scalability and throughput.

Active/Active
: In the Active/Active case both locations are active, and client transactions are distributed to both regions according to predefined policies, such as round-robin, geographical load balancing, and so on. In the case of the failure of one site, the other site must be able to serve all clients. It's possible to achieve both an RPO and RTO close to zero with this configuration. The drawback is that both regions must be sized to handle the full load, even if they are used at half of their capabilities when both locations are available. In such cases, auto scaling can help in keeping resources allocated according to the needs. Of course, the data across the two sites is continuously synced with some kind of replication mechanism.





 Site strategy 

Site strategy is the most predominant aspect of the overall resiliency solution because it determines what classes of physical events the solution is able to address, sets the requirements in terms of distances, and it also sets constraints on the technology side.

IBM Cloud offers a redundant infrastructure with several layers of resiliency that can be summarized as:

Local
* [Version 4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-49)
* [Version 4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-48)







 Using the benchmark 

As a security administrator or auditor, you might want to compare your company's internal standards and external regulatory requirements with the CIS Kubernetes Benchmark. The benchmark recommendations are provided by the Center for Internet Security, not by IBM. IBM might not configure default settings in a way that meets every recommendation, but documents whether the recommendation is met to help you in your review. For example, you might use the benchmark in an audit to confirm that basic security measures are in place, and to identify areas where you might enhance your security.



 What does the benchmark cover? 

The benchmark covers recommendations for master components, etcd, control plane configurations, worker nodes, and policies such as for users, network, and pod security.





 What do the benchmark recommendations mean? 

The benchmark recommendations have scoring, levels, result status, and responsibilities as follows.



* Scoring



* Scored: The overall benchmark score increases or decreases depending on whether the recommendation is met.
* Not scored: The overall benchmark score is not impacted, whether the recommendation is met.



* Levels



* Level 1: Practical security measures that can be configured without inhibiting the service.
* Level 2: More in-depth security measures that might reduce the performance or functionality of a service.



* Result



* Pass: The service complies with the benchmark recommendation.
* Fail: The service does not comply with the benchmark recommendation by default. Refer to the remediation section for an explanation and possible actions that you can take to comply with the benchmark recommendation.



* Responsibility



* IBM: IBM is responsible for configuring the setting that the benchmark recommends.
* Shared: You and IBM share responsibility for configuring the setting that the benchmark recommends.









 What parts of the benchmark am I responsible for?
ips_not_equals<br><br>[8] String The property value is not an exact match to the condition value. Yes 
 num_equals<br><br>[9] Numeric The property value numerically matches to the condition value. Yes 
 num_not_equals<br><br>[10] Numeric The property value does not numerically match the condition value. Yes 
 num_less_than Numeric The property value is numerically less than the condition value. Yes 
 num_less_than_equals Numeric The property value is numerically less than or equal to the condition value. Yes 
 num_greater_than Numeric The property value is numerically greater than the condition value. Yes 
 num_greater_than_equals Numeric The property value is numerically greater than or equal to the condition value. Yes 
 days_less_than Numeric The property value is less than the condition value. Yes 







 Formatting complex rules 

Most often, rules are more complex than a single property. To create more complex scenarios, you can include multiple conditions. To define multiple property conditions in a single rule, you can use the logical operators and and or to express the relationship between them. For example, the following scenarios would all evaluate as compliant.



1. If all three - A, B, and C are true.
2. If any of the three options are true.
3. If A is true or if B and C are both true.



Zoom

![The diagram shows the correlation between multiple conditions. The information is conveyed in the surrounding text.](https://cloud.ibm.com/docs-content/v1/content/a6478671e8f845a84102d9cf49bf28ee7f4f3227/security-compliance/images/config-rules-property.svg)

Figure 1. The ways in which properties can relate to each other.







 Creating a rule 

You can use the Security and Compliance Center UI to define the configuration rules that you want monitor for your IBM Cloud resources.
Audio terminology and characteristics 

The following terminology is used to describe the characteristics of audio data and its processing. This information is helpful for using your audio with the IBM Watson® Speech to Text service.



* If you are unfamiliar with audio and how it is described and specified, begin with this topic to help you get started.
* If you already understand how to work with audio data, start with [Supported audio formats](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audio-formats).





 Sampling rate 

Sampling rate (or sampling frequency) is the number of audio samples that are taken per second. Sampling rate is measured in Hertz (Hz) or kilohertz (kHz). For example, a rate of 16,000 samples per second is equal to 16,000 Hz (or 16 kHz). With the Speech to Text service, you specify a model to indicate the sampling rate of your audio:



* Broadband and multimedia models are used for audio that is sampled at no less than 16 kHz, which IBM® recommends for responsive, real-time applications (for example, for live-speech applications).
* Narrowband and telephony models are used for audio that is sampled at no less than 8 kHz, which is the rate that is typically used for telephonic audio.



The service supports both sampling rates for most languages and formats. It automatically adjusts the sampling rate of your audio to match the model that you specify before it recognizes speech.



* For broadband and multimedia models, the service converts audio recorded at higher sampling rates to 16 kHz.
* For narrowband and telephony models, it converts audio recorded at higher sampling rates to 8 kHz.



You can, for instance, send 44 kHz audio with any model, but that needlessly increases the size of the audio. To maximize the amount of audio that you can send, match the sampling rate of your audio to the model that you use.

The service does not accept audio that is sampled at a rate that is less than the sampling rate of the model. For example, you cannot use a broadband or multimedia model to recognize audio that is sampled at a rate of 8 kHz.



 Notes about audio formats
The order of entities in the array that is returned matches the order in which they are mentioned in the user input.





 Entity properties 

Each entity has a set of properties associated with it. You can access information about an entity through its properties.



 Property Definition Usage tips 

 confidence A decimal percentage that represents your assistant's confidence in the recognized entity. The confidence of an entity is either 0 or 1, unless you have activated fuzzy matching of entities. When fuzzy matching is enabled, the default confidence level threshold is 0.3. Whether or not fuzzy matching is enabled, system entities always have a confidence level of 1.0. You can use this property in a condition to have it return false if the confidence level is not higher than a percent you specify. 
 location A zero-based character offsets that indicates where the detected entity values begin and end in the input text. Use .literal to extract the span of text between start and end index values that are stored in the location property. 
 value The entity value identified in the input. This property returns the entity value as defined in the training data, even if the match was made against one of its associated synonyms. You can use .values to capture multiple occurrences of an entity that might be present in user input. 







 Entity property usage examples 

In the following examples, the skill contains an airport entity that includes a value of JFK, and the synonym 'Kennedy Airport". The user input is I want to go to Kennedy Aiport.



* To return a specific response if the 'JFK' entity is recognized in the user input, you could add this expression to the response condition: entities.airport[0].value == 'JFK' or @airport = "JFK"
* To return the entity name as it was specified by the user in the dialog response, use the .literal property: So you want to go to <?entities.airport[0].literal?>... or So you want to go to @airport.literal ...

Both formats evaluate to `So you want to go to Kennedy Airport...' in the response.
* Expressions like @airport:(JFK) or @airport.contains('JFK') always refer to the value of the entity (JFK in this example).
Predicted data is only displayed when the system has been collecting historical data for at least 7 days. Until then, the graph displays a data point for each day. After 7 days, a prediction for an extra two weeks' worth of information appears.





 Historical and Predicted NZP 

The purple and pink lines represent Historical NZP and Predicted NZP.

NZP (Netezza Performance Metric) is a measure of system utilization.
High level NZP indicates elevated levels of utilization. Low NZP indicates decreased resource usage.
The historical and predicted NZP lines are measured on the scale to the left of the chart between 0% and 100%.





 Historical and Suggested contour profile 

Historical Contour Profile and Suggested Contour Profile are visualized by the blue bars.

The contours that are displayed to the left of the current date line are historical contours. They represent the profiles that are used on each time interval.
The bars that are displayed on the right side of the current date line are suggested contours for each time interval.

Contour profiles are suggested based on the predicted NZP during that time interval. If NZP exceeds 80%, it is suggested that contour profile is scaled up the next closest contour to increase compute and improve performance for heavy workload periods. When the algorithm predicts NZP at or below 20% for a time interval, the graph suggests to scale down to a lower profile.





 Confidence score 

Confidence score reflects the accuracy of the predictions that are provided based on your system historical workload patterns. By analyzing the confidence score, you can choose how to use your system resources.







 Smart scaling example 



1. [Log in to the web console](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted-console).
2. Go to Administering > Workload patterns.
3. Review the smart scaling utilization graph.
In this example, as a database administrator, you want to to get a deeper understanding of your system utilization over time.

In this scenario, it turns out that every Sunday, your system utilization drops below average as compared to other days of the week.