vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To enable communication between workers that are on different subnets on the same VLAN in non-VRF accounts, you must [enable routing between subnets on the same VLAN](https://cloud.ibm.com/docs/containers?topic=containers-subnetssubnet-routing).

ibmcloud ks cluster subnet add --cluster CLUSTER --subnet-id SUBNET [-q]

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

Command options:

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

--subnet-id SUBNET
: Required: The ID of the subnet.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster subnet add command 

ibmcloud ks cluster subnet add --cluster my_cluster --subnet-id 1643389







 ibmcloud ks cluster subnet create 

Classic infrastructure

Create a portable classic subnet in an IBM Cloud infrastructure account on your public or private VLAN and make it available to a cluster.

Portable public IP addresses are charged monthly. If you remove portable public IP addresses after your cluster is provisioned, you still must pay the monthly charge, even if you used them only for a short amount of time. When you make a subnet available to a cluster, IP addresses of this subnet are used for cluster networking purposes. To avoid IP address conflicts, make sure that you use a subnet with one cluster only. Do not use a subnet for multiple clusters or for other purposes outside of IBM Cloud Kubernetes Service at the same time. If you use the same subnet across multiple clusters, your default Ingress TLS certificate might become invalidated. In classic clusters, if you have multiple VLANs for your cluster, multiple subnets on the same VLAN, or a multizone classic cluster, you must enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so your worker nodes can communicate with each other on the private network.
The certificate types are X.509 public key, WTLS public key certificate, and X.509 attribute certificate. Not applicable 
 CKA_CHECK_VALUE The checksum of the key or certificate. AES keys, DES keys 
 CKA_CLASS Object class (type) and is common for all objects. EC private keys, EC public keys, RSA private keys, RSA public keys, DH private keys, DH public keys, DSA private keys, DSA public keys, AES keys, DES keys, Generic keys 
 CKA_COEFFICIENT Used for C_CreatObject. RSA private keys 
 CKA_COPYABLE If set to CKA_TRUE, the object can be copied using C_CopyObject. EC private keys, EC public keys, RSA private keys, RSA public keys, DH private keys, DH public keys, DSA private keys, DSA public keys, AES keys, DES keys, Generic keys 
 CKA_DECRYPT CK_TRUE if key supports decryption. EC private keys, RSA private keys, DH private keys, DSA private keys, AES keys, DES keys, Generic keys 
 CKA_DERIVE CK_TRUE if key supports key derivation (other keys can be derived from this key). Default is CK_FALSE. EC private keys, EC public keys, RSA private keys, RSA public keys, DH private keys, DH public keys, DSA private keys, DSA public keys, AES keys, DES keys, Generic keys 
 CKA_EC_PARAMS (CKA_ECDSA_PARAMS) DER-encoding of an ANSI X9.62 Parameters value. EC private keys, EC public keys 
 CKA_EC_POINT DER-encoding of ANSI X9.62 ECPoint value Q. EC public keys 
 CKA_ENCRYPT CK_TRUE if key supports encryption. EC public keys, RSA public keys, DH public keys, DSA public keys, AES keys, DES keys, Generic keys 
 CKA_END_DATE End date for the certificate or key. Default is empty.
For more information, see [Using VMware Chargeback as a tenant](https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations/8.10/vmware-chargeback-for-vcd-for-a-tenant/GUID-4D7030B6-AF73-464B-8FE8-75B879EE76B8.html).

The billing link in VMware Chargeback is disabled. All billing for VMware Shared is processed through the VMware Solutions console.





 Deleting the OpenID Connect configuration in your VMware Cloud Director Organization 

You must delete all OpenID Connect (OIDC) users and imported groups with the OIDC type, then the OIDC provider before you can reset the IAM integration for a VMware Shared instance site.

Single sign-on is available only when your site VMware Cloud Director Organization is integrated with IAM.



1. From the VMware Cloud Director Console, click SIGN IN WITH SINGLE SIGN-ON to log in to the portal.
2. Click Administration on the top menu bar.
3. Under Access Control on the left navigation pane, click Users.
4. In the Users panel, select all OIDC type users and click DELETE.
5. Under Access Control on the left navigation pane, click Groups.
6. In the Groups panel, select all groups with the OIDC type and click DELETE.
7. Under Identity Providers on the left navigation pane, click OIDC.
8. In the OpenID Connect panel, click DELETE.







 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Ordering virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
Not only are the test utterances and responses removed, but this action also clears the values of any variables that were set as a result of your previous interactions.



Queries that you submit through the Preview pane generate /message API calls, but they are not logged and do not incur charges.



 Saving changes before testing 

Preview represents updates from the last time that the assistant was saved.

Changes are saved when you:



* Select the save icon
* Click a new step
* Open Preview
* Reset Preview



To learn more about saving changes, see [Saving your work](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-save-work).

If you make several edits without saving, the preview pane shows a message that you need to save before you test your changes.

Zoom

![Save your action](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/review-preview-save.png)

Save your action







 Using debug mode in Preview 

Preview has a debug mode that you can turn on to see information that helps you understand why the assistant responds or doesn't respond to a particular input.

Debug mode has four tools to analyze your action:



* [Start and end of an action](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-debug-start-end)
* [Confidence scores](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-debug-confidence)
* [Step locator](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-debug-step-locator)
* [Follow along](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-debug-follow-along)
Akamai Edge servers add the True-Client-IP and X-Forwarded-For headers in the requests to the origin. Then, in your backend origin server, you can get the client IP address from the value of the True-Client-IP, or extract the first IP in the chain of X-Forwarded-For.
* FAQs for CDN with ICOS



 Can I use ICOS private endpoints for CDN? 

No. The CDN edge servers can only access the ICOS public endpoints, so objects in the ICOS buckets should provide public access.





 Will traffic sent from ICOS to CDN be charged? 

Yes. The CDN and ICOS don't have a way of measuring each other's traffic, so both traffic from ICOS and CDN are charged.





 How does the CDN edge server retrieve content from the ICOS objects? 

The CDN uses the S3 endpoint to access the ICOS objects, and replaces the path in the url to the bucket name. For example, if your ICOS S3 endpoint s3.us-south.cloud-object-storage.appdomain.cloud with bucket name xyz-bucket-name is added in path /example-cos/, when you open the CDN URL www.example.com/example-cos/, the CDN edge server retrieves the content from s3.us-south.cloud-object-storage.appdomain.cloud/xyz-bucket-name/.





 How do I use the ICOS default index page with CDN? 

The CDN does not support the default index page for the ICOS objects because the ICOS S3 endpoint does not have the default index. You must specify the complete request path in the browser's address bar (for example, www.example.com/index.html). If you want the CDN to automatically access the default index page of the ICOS, create a CDN with Server type of origin instead of an Object Storage type.
Relation types (Version 1) 

The following table lists the relation types returned by the Version 1 relation type system. The relation type system that Natural Language Understanding uses differs based on which language you are using. For more details, see the [Relation type systems](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-relation-type-systems) page.

In the Version 1 type system, the entity types in relations results are different than the entity types returned in entities results. To see the list of entity types used in Version 1 relations, see the [Entity types (Version 1)](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-entity-types-version-1relations-entity-types) page.



 Relation Description 

 affectedBy Exists between an entity and an event that has clear directionality and affects the entity. 
 affiliatedWith Exists between two entities that have an affiliation or are similarly connected. 
 ageOf Relates an age to an entity. 
 agentOf Exists between an entity and an event in which the entity plays the most active role according to the text. No background knowledge should be required. 
 authorOf Exists between a person and a TitleWork that he or she created. 
 awardedBy Exists between an Award or Degree and the person or organization by which it was awarded or conferred. 
 awardedTo Exists between an Award or Degree and the person or organization to which it was awarded or conferred. 
 basedIn Exists between an Organization and the place where it is mainly, only, or intrinsically located. 
 before Signifies the temporal relation "before" between two Times or Events. Marked only when the text clearly specifies the relation. 
 bornAt Exists between a Person or Animal and the place where she, he, or it was born. 
 bornOn Exists between a Person or Animal and the Date or Time on which she, he, or it was born. 
 capitalOf Exists between a capital and its country, state, or province. Marked only when the text explicitly states the relation, not based on world knowledge. 
 citizenOf Exists between a person and the GeopoliticalEntity of which he or she is a citizen.
For languages that use the Version 1 entity type system that also support relations, relations results contain entity types that are different from the entity types returned in entities results. To return the relations entity types in your entities results, you can specify one of the following public entity models in the model option for the entities feature to override the default entity detection model.



 Model ID Description 

 ar-news Arabic news 
 en-news English news 
 es-news Spanish news 



The following entity types can be identified with the relations entity models:



 Entity type 

 Age 
 Anatomy 
 Animal 
 Award 
 Cardinal 
 Crime 
 Date 
 Degree 
 Duration 
 EmailAddress 
 Event 
 EventBusiness 
 EventCommunication 
 EventCustody 
 EventDemonstration 
 EventEducation 
 EventElection 
 EventGathering 
 EventLegal 
 EventLegislation 
 EventMeeting 
 EventPerformance 
 EventPersonnel 
 EventViolence 
 Facility 
 Food 
 GeographicFeature 
 GeopoliticalEntity 
 HealthCondition 
 Law 
 Location 
 Money 
 Measure 
 NaturalEvent 
 Organization 
 Ordinal 
 Percent 
 Person 
 Phone 
 Plant 
 Product 
 SportingEvent 
 Substance 
 Ticker 
 Time 
 TitleWork 
 Vehicle 
 Weapon 
 Weather 
 Web
Therefore, a connection between different types of VPNs associated with multiple network ranges on either side might result in a connection that only works for a single-network range.

Zoom

![Mixed VPN Types use case](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/vpn-mixed-types.png)

Figure 2. Mixed VPN Types use case

If possible, combine contiguous subnets into a single network range in a VPN configuration. For example, subnets 192.168.0.0/24 and 192.168.1.0/24 can be defined as 192.168.0.0/23 in a VPN or routing configuration.
* An IBM Cloud policy-based VPN gateway resides in the zone that is associated with the subnet that you select during provisioning. The VPN gateway serves only the virtual server instances in the same zone of the VPC. Therefore, instances in other zones can't use the VPN gateway to communicate with an on-premises private network. For zone fault tolerance, you must deploy one VPN gateway per zone.
* An IBM Cloud route-based VPN gateway resides in the zone that is associated with the subnet that you select during provisioning. It is recommended that a VPN gateway serves only virtual server instances in the same zone of the VPC. Instances in other zones can use the route-based VPN gateway to communicate with an on-premises private network, but this is not recommended. For zone fault tolerance, you must deploy one VPN gateway per zone.
curl -X POST -u "apikey:{apikey}" --header "Transfer-Encoding: chunked" --header "Content-Type: audio/flac" --data-binary @{path}audio-file1.flac "{url}/v1/recognize?inactivity_timeout=60"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Transfer-Encoding: chunked" --header "Content-Type: audio/flac" --data-binary @{path}audio-file1.flac "{url}/v1/recognize?inactivity_timeout=60"





 Session timeout 

A session timeout (HTTP status code 408) occurs when you fail to send sufficient audio to keep a streaming session active. The service can consider a session idle and trigger a session timeout for the following reasons:



* You fail to send at least 15 seconds of audio to the service in any 30-second window.

Until you send the last chunk to indicate the end of the stream, you must send at least 15 seconds of audio within any 30-second period. The audio can be silence if you set the inactivity_timeout parameter to a larger value or to -1. You are charged for the duration of any audio that you send to the service, including silence.
* You stream audio at a rate that is much slower than real-time.

Ideally, you would initiate a request to establish a session just before you obtain audio for transcription. You would then maintain the session by sending audio at a rate that is close to real-time.



You do not need to worry about the session timeout after you send the last chunk to indicate the end of the stream. The service continues to process the audio until it returns the final transcription results.

When you transcribe a long audio stream, the service can take more than 30 seconds to process the audio and generate a response. The service does not begin to calculate the session timeout until it finishes processing all audio that it has received. The service's processing time cannot cause the session to exceed the 30-second session timeout.
Entity types (Version 1) 

The following tables list the entity types and subtypes that are used in the Version 1 entity type system.

The entity type system that Discovery uses differs based on which version date and which language you are using. For more details, see the [Entity type systems](https://cloud.ibm.com/docs/discovery?topic=discovery-entity-type-systems) page. For information about available enrichments, see [Adding enrichments](https://cloud.ibm.com/docs/discovery?topic=discovery-configserviceadding-enrichments).



 Entity types 



 Entity type 

 Anatomy 
 Award 
 Broadcaster 
 Company 
 Crime 
 Drug 
 EmailAddress 
 Facility 
 GeographicFeature 
 HealthCondition 
 Hashtag 
 IPAddress 
 JobTitle 
 Location 
 Movie 
 MusicGroup 
 NaturalEvent 
 Organization 
 Person 
 PrintMedia 
 Quantity 
 Sport 
 SportingEvent 
 TelevisionShow 
 TwitterHandle 
 Vehicle 







 Entity subtypes 

Subtypes are determined by the disambiguated entity, not the entity type. There is no strict relationship between entity types and entity subtypes.



 Entity subtype 

 AbusedSubstance 
 Academic 
 AcademicInstitution 
 AcademicPostTitle 
 AccidentType 
 Accommodation 
 Actor 
 AdministrativeDivision 
 AircraftDesigner 
 AircraftManufacturer 
 Airline 
 AirlinerAccident 
 Airport 
 AirportOperator 
 AmericanIndianGroup 
 AminoAcid 
 Animal 
 AnimalBreed 
 API 
 Appellation 
 AppointedRole 
 Appointer 
 Architect 
 ArchitecturalContractor 
 ArchitectureFirm 
 ArmedForce 
 Artery 
 ArtSeries 
 Artwork 
 Asteroid 
 Astronaut 
 AstronomicalDiscovery 
 AstronomicalObservatory 
 Athlete 
 AutomobileCompany 
 AutomobileGeneration 
 AutomobileModel 
 Award 
 AwardCeremony 
 AwardDiscipline 
 AwardJudge 
 AwardNominee 
 AwardPresentingOrganization 
 AwardWinner 
 BasketballConference
Entity types (Version 2) 

The following tables list the entity types and subtypes that are used in the Version 2 entity type system.

The entity type system that Natural Language Understanding uses differs based on which version date and which language you are using.



 Entity types 



 Entity type 

 Date 
 Duration 
 EmailAddress 
 Facility 
 GeographicFeature 
 Hashtag 
 IPAddress† 
 JobTitle 
 Location 
 Measure 
 Money 
 Number* 
 Ordinal 
 Organization 
 Percent* 
 Person 
 PhoneNumber* 
 Time 
 TwitterHandle 
 URL* 



* This entity type is not yet detectable in French or Japanese text.

† IPv6 addresses are not yet detectable in Japanese text.





 Entity subtypes 

Subtypes are determined by the disambiguated entity, not the entity type. There is no strict relationship between entity types and entity subtypes.



 Entity subtype 

 AbusedSubstance 
 Academic 
 AcademicInstitution 
 AcademicPostTitle 
 AccidentType 
 Accommodation 
 Actor 
 AdministrativeDivision 
 AircraftDesigner 
 AircraftManufacturer 
 Airline 
 AirlinerAccident 
 Airport 
 AirportOperator 
 AmericanIndianGroup 
 AminoAcid 
 Animal 
 AnimalBreed 
 API 
 Appellation 
 AppointedRole 
 Appointer 
 Architect 
 ArchitecturalContractor 
 ArchitectureFirm 
 ArmedForce 
 Artery 
 ArtSeries 
 Artwork 
 Asteroid 
 Astronaut 
 AstronomicalDiscovery 
 AstronomicalObservatory 
 Athlete 
 AutomobileCompany 
 AutomobileGeneration 
 AutomobileModel 
 Award 
 AwardCeremony 
 AwardDiscipline 
 AwardJudge 
 AwardNominee 
 AwardPresentingOrganization 
 AwardWinner 
 BasketballConference 
 BasketballDivision 
 BasketballPlayer 
 BasketballTeam 
 Bassist 
 Beer 
 Belief 
 Beverage 
 BicycleManufacturer 
 BipropellantRocketEngine 
 Blog 
 Blogger 
 BoardMember 
 BoardMemberTitle 
 BodyOfWater 
 Bone
VideoGameDeveloper 
 VideoGameEngine 
 VideoGamePlatform 
 VideoGamePublisher 
 VisualArtist 
 WebBrowserExtension 
 Website 
 WineProducer 
 WineRegion 
 WorkOfFiction 
 Writer 







 Relations entity types 

For languages that use the Version 1 entity type system that also support relations, relations results contain entity types that are different from the entity types returned in entities results. To return the relations entity types in your entities results, you can specify one of the following public entity models in the model option for the entities feature to override the default entity detection model.



 Model ID Description 

 ar-news Arabic news 
 en-news English news 
 es-news Spanish news 



The following entity types can be identified with the relations entity models:



 Entity type 

 Age 
 Anatomy 
 Animal 
 Award 
 Cardinal 
 Crime 
 Date 
 Degree 
 Duration 
 EmailAddress 
 Event 
 EventBusiness 
 EventCommunication 
 EventCustody 
 EventDemonstration 
 EventEducation 
 EventElection 
 EventGathering 
 EventLegal 
 EventLegislation 
 EventMeeting 
 EventPerformance 
 EventPersonnel 
 EventViolence 
 Facility 
 Food 
 GeographicFeature 
 GeopoliticalEntity 
 HealthCondition 
 Law 
 Location 
 Money 
 Measure 
 NaturalEvent 
 Organization 
 Ordinal 
 Percent 
 Person 
 Phone 
 Plant 
 Product 
 SportingEvent 
 Substance 
 Ticker 
 Time 
 TitleWork 
 Vehicle 
 Weapon 
 Weather 
 Web
The vSAN deduplication and compression option is available for enablement only when you order a cluster.





 Bare metal server requirements 

You can select from various bare metal server CPU and memory sizes based on your selction of location and profile storage type.

For vSAN cluters, you can select Dual Intel 8260 Xeon (2 Sockets - 48 Cores, 768 GB RAM) with either 15 TB, 23 TB, or 30 TB of vSAN usable capacity.

The following options are available for NFS only clusters.



* Dual Intel® 5218 Xeon® (2 Sockets - 32 Cores, 192 GB RAM)
* Dual Intel 8260 Xeon (2 Sockets - 48 Cores, 384 GB RAM)
* Dual Intel 8260 Xeon (2 Sockets - 48 Cores, 768 GB RAM)
* Dual Intel 8260 Xeon (4 Sockets - 96 Cores, 1536 GB RAM)







 Performance characteristics 

Review the available storage performance tiers.



* 0.25 IOPS/GB
* 2 IOPS/GB
* 4 IOPS/GB
* 10 IOPS/GB



For NFS only storage, you must select at least one unit of 2 IOPS/GB or higher.





 Configuration limits for VMware Cloud Director 

Review [VMware Cloud Director 10.4 Configuration Limits](https://configmax.esp.vmware.com/guest?vmwareproduct=%20VMware%20Cloud%20Director&release=VMware%20Cloud%20Director%2010.4&categories=35-0) to ensure that you understand configuration limits in VMware Cloud Director™.





 Services for VMware as a Service 

The Veeam® Backup and Replication service is preinstalled and included by default for your instance order. You can remove the service from your instance order. Service charges are incurred only if you choose to include the service in your order.





 Related links 



* [FAQ](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-faq-general)
The primary replica in the secondary availability group is charged with replicating transactions to the other secondary replicas in the secondary availability group. This architecture is useful for OS and SQL Server version upgrades as you can have different versions of Windows Server in each availability group. Although each availability group in a distributed scenario has its own listener, the distributed availability group as a whole does not. Applications, perhaps with the aid of DNS aliases, will connect to each availability group directly after a failover to take advantage of readable secondary replicas.









 Distributed Network Names 

This deployment uses Distributed Network Names (DNN), which is a name resource in WSFC and Always On availability groups, used for name resolution of the cluster resources. It differs from a standard network name resource because it does not require a separate IP address from the IP addresses of the nodes and does not require the use of Gratuitous Address Resolution Protocol (GARP) on the network when a failover occurs. In Windows Server 2019, the name of the WSFC, which is also the Cluster Name Object (CNO) in Active Directory Domain Services and the database listener can both be created with DNNs.
Causes: The AIX Tier 1 (NVMe-based flash storage) disk's default settings are hindering optimal performance.

Resolve: To improve disk performance, increase its queue_depth to 64 or 128 and change the algorithm to shortest_queue with a no_reserve policy. These modifications can improve performance by up to 50%.

To look at your AIX disk's current settings, enter the following commands:



* lsattr -El hdiskX -a algorithm
* lsattr -El hdiskX -a reserve_policy
* lsattr -El hdiskX -a queue_depth



In the output of these lsattr commands, you'll see either True or True+ at the very end. True indicates that the attribute is user-changeable. True+ indicates that the attribute is user-changeable, and can be modified while the disk is open by using the -U flag.

You can set your disk's queue_depth to 64 and change the algorithm to shortest_queue with a no_reserve policy by using the following command:

chdev -l hdiskX -a algorithm=shortest_queue -a reserve_policy=no_reserve -a queue_depth=64

If the AIX disk is open, an error message appears that states that the disk is busy. To prevent this error from occuring, add a -U flag to the chdev command and the values are updated without disruption (assuming the Object Data Manager (ODM) for the disk has that feature enabled).