vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Storage volumes for Databases for EnterpriseDB deployments are provisioned on [Block Storage Endurance Volumes in the 10 IOPS per GB tier](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingthroughConsoleorderingthroughConsoleEndurance). If your operational load saturates or exceeds the IOPS limit, database requests and operations are delayed until the disk can catch up. Extended periods of heavy-load can cause your deployment to be unable to process queries and become effectively unavailable. If you experience delayed responses and failing operations, you might be exceeding the disk's IOPS limit. You can increase the number IOPS available to your deployment by increasing disk space.





 Memory Usage 

Databases for EnterpriseDB deployment's memory settings are auto-tuned based on the deployment's total memory. Specifically, [work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.htmlGUC-WORK-MEM), [maintenance_work_mem](https://www.postgresql.org/docs/current/runtime-config-resource.htmlGUC-MAINTENANCE-WORK-MEM), and [effective_cache_size](https://www.postgresql.org/docs/current/runtime-config-query.htmlGUC-EFFECTIVE-CACHE-SIZE) are set on provision, restore, or scale.

You can set the amount of memory that is dedicated to the databases' shared buffer pool by adjusting the [shared_buffers](https://www.postgresql.org/docs/current/runtime-config-resource.htmlGUC-SHARED-BUFFERS) in your [Databases for EnterpriseDB configuration](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-changing-configuration). The recommended value to use is 25% of the deployment's total memory. Allocating too much to the shared buffer pool can starve the system of memory for other purposes and hurts performance (or crash the database).
Removing Block Storage for VPC from your cluster 

When you set up persistent storage in your cluster, you have three main components: the Kubernetes persistent volume claim (PVC) that requests storage, the Kubernetes persistent volume (PV) that is mounted to a pod and described in the PVC, and the storage instance. Depending on how you created your storage, you might need to delete all three components separately.

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.

If you [dynamically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your PVC, PV, and the storage instance are automatically deleted when you delete the cluster. For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
No, any SSH connection to the bootstrap, compute, or storage nodes is only possible through the bastion node for security reasons. You would use the following command to connect to your bootstrap, compute, or storage nodes (the IP address is specific to your particular node): ssh -J ubuntu@<bastion_IP_address> vpcuser@<IP_address>





 Can I establish an SSH connection between compute and storage nodes? 

The compute and storage clusters are created to not have the same passwordless SSH keys. This ensures that there are separate administration domains for the compute and storage clusters; therefore, SSH between nodes from different clusters is not possible.





 Does the Spectrum Scale offering support multiple key_pairs to establish SSH to all of the nodes? 

No, the current version of the Spectrum Scale offering supports only a single key_pair that can be provided for access to all of the nodes that are part of the cluster.





 Can I use my own resource group to configure the resources? 

Yes, you can provide the resource group of your choice for the deployment of your cluster's VPC resources. Due to the use of trusted profiles in this offering, you must ensure that all of the key_pair values that are specified in the deployment values are created in the same resource group.





 Which operating system versions are supported for the images used for the compute and storage nodes in Spectrum Scale? 

With Spectrum Scale, you can use custom or stock images based on RHEL 7.9 or RHEL 8.4. For compute nodes, both RHEL 7.9 or 8.4 can be used. For storage nodes, only RHEL 8.4 is supported.





 Why does Spectrum Scale not allow use of the default value of 0.0.0.0/0 for security group creation? 

For security reasons, Spectrum Scale does not allow you to provide a default value that would allow network traffic from any external device. Instead, you can provide the address of your user system (for example, by using [https://ipv4.icanhazip.com/](https://ipv4.icanhazip.com/)) or a multiple IP address range.
Understanding Satellite storage 

Before you can decide what type of storage is the right solution for your Satellite clusters, you must understand the infrastructure provider, your app requirements, the type of data that you want to store, and how often you want to access this data. For more information, see [choosing a storage solution](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).

Before you can use storage templates and configurations to manage your storage resources across locations and clusters, make sure you [Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig) in your location.



 What are my options for deploying storage to Satellite? 

You have two options when configuring storage in Satellite. The first is by using one of the provided storage templates. The second is by bringing your own storage drivers (BYOD), Helm charts, or Operators from the IBM Cloud Catalog, OperatorHub, or GitHub repo.

Satellite storage templates
: You can create storage configurations by [using the Satellite storage template for the storage provider or driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-template-ovstorage-template-ov-providers) that you want to use. After you create a storage configuration by using a template, you can assign your storage configuration to your clusters or services. By using storage templates, you can create storage configurations that can be consistently assigned, updated, and managed across the clusters, service clusters, and cluster groups in your location.

Bring your own Operators, drivers, and plug-ins
: You can also bring your own storage drivers to Satellite by installing them from the Catalog, OperatorHub, Helm charts, or by using your preferred method of deploying images to your clusters including images and drivers from various IBM Cloud storage and partner solutions, for example Portworx. Bringing your own storage driver is functionally supported, but you are responsible for the entire lifecycle operations, installation, troubleshooting, and support.
Your responsibilities when using IBM Cloud Object Storage 

Learn about the management responsibilities and terms and conditions that you have when you use IBM Cloud® Object Storage. For overall terms of use, see [Cloud Services terms](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-termsterms).



 Operational responsibilities 

IBM responsibilities



* Maintaining SLAs as stated in IBM Cloud Object Storage Service Description.
* Ensure client gets appropriate notifications regarding availability and downtime of its resources.
* Monitor service performance related metrics such as network, storage, and compute capacities.
* Monitor and manage service health and availability.



Your responsibilities



* Ensuring data back-ups if necessary.
* Mitigating potential accidental deletion of data. If applicable the client should store archive data in buckets configured with a data retention policy to help address data loss due to accidental deletion. IBM is unable to “un-delete” data.
* Monitor and manage non-IBM network resources to ensure appropriate access to IBM Cloud service endpoints including capacity and availability.
* Provisioning Object Storage buckets with the appropriate resiliency option, storage class, data locality, and optional configurations necessary for the specific workload and use case.







 Managing infrastructure and the cloud environment 

IBM responsibilities



* Deployment, provisioning, managing IBM Cloud Object Storage resources offered to clients.
* Ensuring availability of adequate resources to allow for scaling of client resources as per client usage requirements.
* All physical and environmental controls.



Your responsibilities



* Ensure proper network access and capacity is available and can reach the designated Object Storage service endpoints. (private or public).
* Ensure applications can interact with the COS S3 API either via native support or with the addition of a hardware or software gateway solution.







 Security 

IBM responsibilities



* Security and monitoring of the environment as per IBM data center security guidelines.
* Encrypting client data when at-rest and in-transit between different IBM Cloud data center locations as part of resiliency options offered to clients.
* Continuous monitoring of resources to check for vulnerabilities and security breaches.



Your responsibilities
Removing Block Storage for VPC from your cluster 

When you set up persistent storage in your cluster, you have three main components: the Kubernetes persistent volume claim (PVC) that requests storage, the Kubernetes persistent volume (PV) that is mounted to a pod and described in the PVC, and the storage instance. Depending on how you created your storage, you might need to delete all three components separately.

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.

If you [dynamically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your PVC, PV, and the storage instance are automatically deleted when you delete the cluster. For storage that was [statically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsstatic_provisioning), VPC Block Storage, or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
* [Upgrading Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-upgrading-watson-speech), specifically Migrating data from IBM Cloud Pak for Data Version 3.5.



Updated recommendation for OpenShift Container Storage
: Starting with Speech services version 4.0.6, the recommended storage class for OpenShift Container Storage is ocs-storagecluster-ceph-rbd.



* If you are installing Speech services 4.0.6 or upgrading to Speech services 4.0.6 from IBM Cloud Pak for Data version 3.5, specify the ocs-storagecluster-ceph-rbd storage class during installation or upgrade.
* If you are upgrading to Speech services 4.0.6 from a previous refresh of Cloud Pak for Data version 4.0, continue to use ocs-storagecluster-cephfs. You cannot change the storage that is used in an existing deployment.



The value is specified with the storageClass property in the Speech services custom resource:


 Storage class

storageClass: "ocs-storagecluster-ceph-rbd"

The Speech services work with either version of OpenShift Container Storage. The newly recommended version has more restrictive access permissions. For more information, see



* [Installing Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-installing-watson-speech)
* [Upgrading Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-upgrading-watson-speech)



New beta en-WW_Medical_Telephony model is now available
: A new beta next-generation en-WW_Medical_Telephony is now available. The new model understands terms from the medical and pharmacological domains. Use the model in situations where you need to transcribe common medical terminology such as medicine names, product brands, medical procedures, illnesses, types of doctor, or COVID-19-related terminology.
* Where can I find the custom image name to image ID mappings for each cloud region?

The mappings can be found in the image-map.tf file in this [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf).
* Which Spectrum LSF and Spectrum Scale versions are used in cluster nodes deployed with this offering?

Cluster nodes that are deployed with this offering include IBM Spectrum LSF 10.1 Standard Edition plus Data Manager plus License Scheduler. See the following for a brief description of each of those programs: [IBM Spectrum LSF 10 family of products](https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS220-174/index.html&lang=en&request_locale=en)

If the cluster uses Spectrum Scale storage, the storage nodes include IBM Spectrum Scale 5.1.3.1 software. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/docs/en/spectrum-scale/5.1.3) product documentation.
* How many compute worker and storage nodes can I deploy in my Spectrum LSF cluster through this offering when spectrum_scale is enabled?

Before you deploy a cluster, it is important to ensure that the VPC resource quota settings are appropriate for the size of the cluster that you would like to create (see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas)).

The maximum number of compute nodes that are supported for the deployment value total_compute_cluster_instances is 64. The maximum number of storage nodes that are supported for the deployment value total_storage_cluster_instances is 18.
* Why is the CPU number displayed on an LSF worker node different than what is shown in the LSF Application Center GUI?

The CPU column in the LSF Application Center GUI and the ncpus column when you run the lscpu command on an LSF worker node might not show the same value.
You can log in to any node only through the bastion host by using the following command:

ssh -J ubuntu@<IP_address_bastion_host> vpcuser@<IP-address-of-nodes>

Although all of the nodes of each cluster have passwordless SSH set up among them, due to security constraints, you can't directly log in to a node from one cluster to another cluster.





 How many compute and storage nodes can I deploy in my Spectrum Scale cluster through this offering? 

Before you deploy a cluster, it is important to ensure that the VPC resource quota settings are appropriate for the size of the cluster that you would like to create (see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas)).

See the following minimum and maximum number of nodes that are supported in a cluster:



* Compute nodes: For all storage clusters, a minimum of 3 and a maximum of 64 virtual server instance compute nodes are supported.
* Scratch and evaluation cluster storage nodes: For a scratch and evaluation storage clusters, a minimum of 3 and a maximum of 18 virtual server instance storage nodes are supported.
* Persistent cluster storage nodes: For a persistent storage cluster, a minimum of 3 and a maximum of 10 bare metal server storage nodes are supported.



For more information, see [Deployment values](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-deployment-values).





 What storage types are available through this offering? 

The Spectrum Scale solution offers three different storage types: scratch, persistent, and evaluation. For more information, see [Storage types](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-storage-types).





 Why are there two different resource group parameters that can be specified in the IBM Cloud catalog tile? 

The first resource group parameter entry in the Configure your workspace section in the IBM Cloud catalog applies to the resource group where the Schematics workspace is provisioned on your IBM Cloud account.
Workload edge cluster hosts workload Tier 0 and Tier 1 Gateways for your workloads. A predefined example overlay network topology with one Tier 1 Gateway is provided by the automation. You can customize it for your own requirements by changing or deleting example segments or by adding new segments.







 VMware vCenter Server clusters 

The vCenter Server deployment might consist of several clusters. The following diagram provides an overview of the key cluster types.

Zoom

![vCenter Server clusters](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/arch-pattern-vcs-nsx-t-edge-services-cluster.svg)

Figure 2. vCenter Server clusters

This clustering can be summarized as follows:



1. You can select an initial deployment to include one consolidated cluster or separate management and workload clusters.
2. You can optionally deploy a gateway cluster to host Juniper vSRX or your own routing or firewall device.
3. You can expand the solution after initial deployment, by adding more hosts to existing clusters, by adding new clusters or by adding NFS storage to your instance.
4. Each cluster might have different bare metal server hardware options and different storage options.
5. The automation deploys four edge nodes in your deployment and forms two NSX-T edge clusters - Services edge cluster and Workload edge cluster.
6. Gateway cluster is used to host services Tier 0 Gateway, which provides network connectivity services for your management components.
7. Workload edge cluster hosts workload Tier 0 and Tier 1 Gateways for your workloads. A predefined example overlay network topology with one Tier 1 Gateway is provided by automation. You can customize it for your own needs by changing or deleting example segments or by adding new segments.



The gateway cluster must not be mixed with the NSX-T edge cluster, which consists of VMware NSX-T™ edge transport nodes.
Target details are not valid message when configuring an Event Streams target 

When attempting to create an IBM Cloud Activity Tracker Event Routing event_streams target using the CLI, you are unable to do so and are getting errors indicating your command failed because the target details are not valid.

  What’s happening 

Your CLI command return the message: Your request to test a target has failed because the target details are not valid. The service could not write to the Event Streams topic that is configured.

  Why it’s happening 

If you are limiting access to a specific Event Streams topic, you must have an IAM policy defined for both the policy and cluster.

  How to fix it 

[Correct your Event Streams IAM policy definitions](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_iestarget_es) and retry your CLI command.
Streaming data 

Stream data from an IBM Cloud Activity Tracker instance to other corporate tools such as Security Information and Event Management (SIEM) tools.

When you stream data to data lakes, other analysis tools, or other SIEM tools, you can add additional capabilities to the ones provided by the Activity Tracker service:



* You can gain visibility into enterprise data across on-premises and cloud-based environments.
* You can identify and prioritize security threats that might affect your organization.
* You can detect vulnerabilities by using Artificial Intelligence (AI) to investigate threats and incidents.



You can stream data to an Event Streams instance or to an Activity Tracker instance. For example, when you enable streaming on an Activity Tracker instance, you configure Activity Tracker to send data to an Event Streams instance. Then, you can configure Kafka Connect to consume the data and forward it to your destination tool. Once the data is persisted within Event Streams, you can configure any application or service to create a subscription and take action on log data being streamed.

You can also also configure streaming from one Activity Tracker instance to a second Activity Tracker instance.

Zoom

![Streaming example](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/Activity-Tracker-Search-04-Data-Streaming.svg)

Figure 1. Streaming example

You can only stream from one Activity Tracker instance to one other Activity Tracker instance. You cannot stream from the second Activity Tracker instance to another Activity Tracker instance.

Currently, you can only stream up to 1TB of data per day.

If you have any regulatory requirement for data residency and compliance needs, you must control the location where Activity Tracker, Event Streams, Kafka Connect and the destination tool are available.



 Configure streaming 

Consider the following information when streaming data to an Event Streams instance:



* You must have manager role to configure streaming in the Activity Tracker instance.
Are you getting an error message when starting the Windows 3.6 agent? 

You are are trying to start the IBM® Log Analysis 3.6 agent for Windows and it fails to start with a 1067 error.

You receive a message: Windows could not start the Mezmo Agent service on Local Computer. Error 1067: The process terminated unexpectedly.

Additional error details can be found in the agent service log.

  What’s happening 

C:ProgramDatalogslogdna-agent-svc_???.log

  Why it’s happening 

The logdna.conf file has an incorrect configuration.

  How to fix it 

[Edit your logdna.conf file](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_agent_windows_v3) and correct any configuration errors. For example, this error occurs if you specify a file name in the dirs: section of the logdna.conf file. The dirs: section must only include directories, not individual files.