vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Carefully select the resource settings (that is, reservations, shares, and limits) for your VMs. Setting reservations too high can leave few unreserved resources in the cluster, thus limiting the options that DRS must balance load.
* Setting limits too low might keep VMs from using extra resources available in the cluster to improve their performance.
* Run your clusters at no more than 80% usage to allow remediation of hosts by using VMware Update Manager. Cluster remediation is most likely to succeed when the cluster is running at maximum of 80% usage.
* Thin provisioning of storage increases the management workload of maintaining your environment as you need to be careful in your capacity management process.
* Analyze your VM growth and understand how your infrastructure is getting used up to support this growth, order more capacity to facilitate this growth.
* Use usable capacity, which considers HA and buffers and not total available capacity.
* Ensure that you are running the current version of the BIOS available for your system.
* Ensure that you are running the current VMware updates to your installed products, including VM hardware and VM tools.







 List of tasks 



Table 1. Proactive tasks

 Title Description 

 Health Using vCenter, check the health of all hosts and VM objects. Methodically step through the clusters, hosts, datastores, VMs, and networks that look for alarms. 
 Alarm and notification check Review to confirm that there not any active alarms in vCenter for which you are not aware of. By default, vCenter has a number of alarms that are defined when installed. These alarms might alert you to issues. However, by default, these alarms deliver a warning or alert only in the VMware vSphere® Web Client. They can be configured to a notification such as an email. As you check the health of the hosts and VM objects, review the alarms, decide whether a notification is needed, and configure as required. You need to be notified for only the most important or critical issues. Consider the following case: do I want to be notified of this issue at 2 AM or can it wait until normal working hours? Too many notifications are considered as "noise" and human nature is to ignore all alarms.
The RabbitMQ datastore is installed only if the sttAsync microservice is installed.

For more information, see Datastore properties in Using the Watson Speech services custom resource in [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech).

Defect fix: Creation of a Network Policy is no longer necessary for the PostgreSQL operator to monitor its operands
: Defect fix: For version 4.6.0, it is not necessary to create a Network Policy to allow the PostgreSQL operator to monitor its operands, as described in the [10 November 2022 (Versions 4.0.x and 4.5.x)](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes-dataspeech-to-text-data-10november2022) service update. As of version 4.6.0, the service handles this situation automatically.

Defect fix: Some next-generation models were updated to improve low-latency response time
: Defect fix: The following next-generation models were updated to improve their response time when the low_latency parameter is used:



* en-IN_Telephony
* hi-IN_Telephony
* it-IT_Multimedia
* nl-NL_Telephony



Previously, these models did not return recognition results as quickly as expected when the low_latency parameter was used. You do not need to upgrade custom models that are based on these models. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

Defect fix: Improve custom model naming documentation
: Defect fix: The documentation now provides detailed rules for naming custom language models and custom acoustic models. For more information, see
Backing up components 

You are responsible for the configuration, management, and monitoring of all software components, including the backup and availability of your management infrastructure and workloads.

As part of the solution, you can optionally deploy the Veeam® add-on service to satisfy the requirement for backing up your management components.

These add-on services are deployed together with IBM Cloud® Endurance storage. The services help you back up your workloads and the management components. The [Veeam architecture overview](https://www.ibm.com/cloud/architecture/architectures/virtualization_backup_veeam) provides helpful guidance on planning and sizing your deployment.

Different solution components require different strategies for backup. Some components are protected by using image-level backup, and other components are protected by using file-based backup for their configuration and data.



 File server for file-based backup 

Some components, such as VMware vCenter Server® with an embedded Platform Services Controller (PSC) and VMware NSX®, require their configuration to be backed up to a file server.

To host these backups, deploy a Linux® file server into your cluster by using the following steps:



1. Order a private portable subnet from the IBM Cloud infrastructure and locate it on the same VLAN as your system components. It is the private VLAN on which the management IP addresses for your hosts exist.
2. Upload an operating system image to your VMware® management datastore, such as Ubuntu Server 18.04 LTS, from the IBM Cloud private mirror.
3. Deploy this virtual machine (VM) into your cluster on the management port group by using a private portable IP address ordered previously. Ensure that the VM is configured to point to your AD/DNS servers and optionally add the VM to your DNS domain.
4. Create a nonroot backup user ID on this server and ensure that all the necessary services are configured and started for file transfers. For example, FTP or SSH.
5. Ensure that this VM is included in your Veeam management backup job.







 vCenter file-based backup
* You can have a remote device (laptop or desktop) connected through the IBM Cloud SSL VPN to the IBM Cloud Private network. This remote device has access to the internet to download the required files and can connect to vCenter and the bastion node through the SSL VPN.







 Scripts overview 

This build process uses the following scripting tools and scripts:



* govc is a vSphere CLI pre-compiled for Linux, OSX, and Windows. The CLI is useful to complete various vCenter Server and vSphere operations and it's used in this process to complete the following tasks:



* Upload the ISO and OVA files to a vSphere datastore.
* Create a persistent volume for the Red Hat OpenShift cluster to use.



* Red Hat Installer - The installer creates the Ignition files that are used by Terraform. Ignition is a first boot installer and configuration tool that is designed specifically for CoreOS Container Linux to partition disks, format partitions, writing files and configuring users. On first boot, Ignition reads its configuration from a remote URL and applies the configuration to the VM.
* Terraform - Terraform is a tool that codifies APIs into declarative configuration files. It uses a "provider" to interact with the infrastructure. A .tf file is used to describe the infrastructure as code. A .tvars file is used to store the variables for the deployment. The main.tf file holds the build instructions.
* PowerShell is used on the AD DNS server to create the DNS entries.
* PowerShell Core is available for Windows, Linux, and macOS systems. This tool is optional and it can be used on the jump-server or remote device to enable the use of PowerCLI. For more information, see [PowerShell Core](https://github.com/PowerShell/PowerShell).
* PowerCLI - PowerCLI is a PowerShell interface for managing VMware vSphere®. You can automate all aspects of vSphere management, including network, storage, VMs, and guest OS.
Plug-ins include the setup and integration with VMware components to synchronize all VMs along with their tenant information.



The following table shows the ports and protocols that are required for each component.



Table 1. Ports and protocols

 Component Port numbers 

 UI 443 
 API 443, 1337 
 RiskForesight 8082, 8083, 8084 
 Central collector (cluster) 8080 
 Remote collector 8081 
 Relational datastore primary or secondary 5432 
 Messaging datastore cluster 9092 
 Index datastore primary nodes 9200, 9300, 5601, 443 



The following diagram shows the network topology with the Caveonix portable private subnet that is associated with Private VLAN A. You are responsible for managing the IP address space for this subnet. If needed, you can scale out from the “all-in-one” deployment model, through the partially distributed model, and to the fully distributed model.

Zoom

![Network diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/caveonix-network.svg)

Figure 2. Network diagram

The IP Subnet, VLAN assignments are described in the following table.



Table 2. VLAN and subnets

 VLAN Subnet type Description 

 Public Primary Assigned to physical hosts for public network access. Not used upon initial deployment. 
 Public Portable Assigned for uplink and NAT usage on customer-nsx-esg. 
 Public Portable Assigned for uplink NAT usage on mgmt-nsx-esg. 
 Public Portable Assigned for uplink NAT usage on hcx-mgmt-esg, if Hybridity Bundle selected. 
 Private A Primary Assigned to physical hosts assigned by IBM Cloud®. Used by the management interface for vSphere management traffic. 
 Private A Portable Assigned to VMs that function as management components. 
 Private A Portable Assigned to NSX VTEP. 
 Private A Portable Assigned to HCX for internal usage, if Hybridity bundle selected.
From the Azure portal, search for Subscription to find a list of your subscriptions. You can also find your subscription ID by running the az account subscription list command. true N/A 
 Azure Active Directory Client ID aadClientId Secret Your Azure Active Directory Client ID. You can find your Client ID in the Azure portal or by running the az ad sp list --display-name appDisplayName command. true N/A 
 Location location Config The location of your Azure hosts. You can find the location of your virtual machines in the Azure portal or by running the az vm list command. Example location: useast. true N/A 
 Azure Active Directory Client Secret aadClientSecret Secret Your Azure Active Directory Client Secret. You can find your client secret in the Azure portal under the App registrations menu. true N/A 
 Resource Group resourceGroup Config The name of your Azure resource group. You can find your resource group detail in the Azure portal or by running the az group list command. true N/A 
 Virtual Machine Type vmType Config You can find your virtual machine type in the Azure portal or by running the az vm list command. Example types: standard or VMSS. true N/A 
 Network Security Group Name securityGroupName Config The name of your security group. You can find your security group details in the Azure portal or by running the az network nsg list command. true N/A 
 Virtual Network Name vnetName Config The name of the virtual network. You can find the name of your virtual network in the Azure portal or by running the az network vnet list command. true N/A 
 Subnet Name subnetName Config Name of one the of the subnets under the provided VNet true N/A 







 1.22.0 parameter reference 



Table 3. 1.22.0 parameter reference

 Display name CLI option Type Description Required? Default value 

 Tenant ID tenantId Secret Tenant ID : The Azure tenant ID that you want to use for your configuration. You can find your tenant ID in the Azure portal or by running the az account tenant list command. true N/A
ClientIP IP address of the client string 
 ClientIPClass unknowncleanbadHostsearchEnginewhitelistgreylistmonitoringServicesecurityScannernoRecordscanbackupServicemobilePlatformtor string 
 ClientRequestBytes Number of bytes in the client request int 
 ClientRequestHost Host requested by the client string 
 ClientRequestMethod HTTP method of client request string 
 ClientRequestPath URI path requested by the client string 
 ClientRequestProtocol HTTP protocol of client request string 
 ClientRequestReferer HTTP request referrer string 
 ClientRequestURI URI requested by the client string 
 ClientRequestUserAgent User agent reported by the client string 
 ClientSSLCipher Client SSL cipher string 
 ClientSSLProtocol Client SSL (TLS) protocol string 
 ClientSrcPort Client source port int 
 ClientXRequestedWith X-Requested-With HTTP header string 
 EdgeColoCode IATA airport code of data center that received the request string 
 EdgeColoID Cloudflare edge colo id int 
 EdgeEndTimestamp Timestamp at which the edge finished sending response to the client int or string 
 EdgePathingOp Indicates what type of response was issued for this request (unknown = no specific action) string 
 EdgePathingSrc Details how the request was classified based on security checks (unknown = no specific classification) string 
 EdgePathingStatus Indicates what data was used to determine the handling of this request (unknown = no data) string 
 EdgeRateLimitAction The action taken by the blocking rule; empty if no action taken string 
 EdgeRateLimitID The internal rule ID of the rate-limiting rule that triggered a block (ban) or simulate action. 0 if no action taken int 
 EdgeRequestHost Host header on the request from the edge to the origin string 
 EdgeResponseBytes Number of bytes returned by the edge to the client int 
 EdgeResponseCompressionRatio Edge response compression ratio float 
 EdgeResponseContentType Edge response Content-Type header value string 
 EdgeResponseStatus HTTP status code returned by Cloudflare to the client int 
 EdgeServerIP IP of the edge server making a request to the origin string 
 EdgeStartTimestamp Timestamp at which the edge received request from the client int or string
Client configuration, deployment, and lifecycle Customer is responsible for managing client configuration, deployment, and lifecycle by following [IBM best practice documentation](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilitiessoftware-packages). 
 Cluster management Customer is responsible for managing the provided resource capacity of their clusters across their organizational user base. 
 Satellite cluster management Event Streams deploys a service instance and cluster that consists of all required Event Streams components onto the customer-provided infrastructure. Event Streams is responsible for monitoring the health of the Event Streams cluster and recovery of that cluster, unless recovery requires customer infrastructure actions. [Satellite incident and operations management](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesincident-and-ops). 







 Security and regulation compliance 



Table 2. Responsibilities for security and regulation compliance

 Task IBM Responsibilities Your Responsibilities 

 Maintain controls Event Streams maintains controls commensurate with various industry compliance standards for which we are certified. 
 IBM Cloud Identity and Access Management (IAM) Event Streams provides security and access control service with IBM Cloud Identity and Access Management (IAM). 
 Security and vulnerability patch updates to cluster Event Streams applies the provided security and vulnerability patch updates to the client cluster, according to IBM X-Force timeframes. 
 Manage users and access Customer is responsible for managing your organizational account users and related access to the Event Streams instance. 
 Compliance controls Customer is responsible for maintaining your organizational compliance controls. 
 Satellite compliance and security The Event Streams Satellite plan is not yet certified for the same standards as the Event Streams Enterprise plan. See [What is supported](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choosewhat_is_supported) for specific compliance standards information. For more information, see [IBM Cloud Service Description](https://www.ibm.com/support/customer/csol/terms?id=i126-6605&lc=endetail-document). For more information, see [Satellite security and regulation compliance](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiessecurity-compliance). 







 IBM Cloud infrastructure and managing the environment
A Kafka Improvement Proposal (KIP) #302 (available from Kafka 2.1.1) ensures that Kafka clients try all available broker IP addresses and not a subset, so a failure in a single IP address does not cause a failure.

You need to opt into this functionality by using one of the following methods:



* Specify a new allowed value in the Consumer and Producer properties of the configuration parameter client.dns.lookup:

client.dns.lookup: "use_all_dns_ips"
* Use the constants CommonClientConfigs.CLIENT_DNS_LOOKUP_CONFIG: ClientDnsLookup.USE_ALL_DNS_IPS.









 Topics and partitions 



* Topic names are restricted to a maximum of 200 characters.
* The default number of partitions for a topic is one.







 Creating and deleting topics in Kafka 

In Kafka, topic creation and deletion are asynchronous operations that might take some time to complete. Avoid usage patterns that rely on the rapid creation and deletion of topics, or on the rapid deletion and re-creation of topics.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.10.5 bc26045116045516ff2427201abd299043eaf8f7

 helm version --client
version.BuildInfo{Version:"v3.10.1", GitCommit:"9f88ccb6aee40b9a0535fcc7efea6055e1ef72c9", GitTreeState:"clean", GoVersion:"go1.18.7"}

 ibmcloud -version
ibmcloud version 2.12.1+b8488a1-2022-10-31T15:08:10+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.61 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.40.0 Update Available true
container-registry 1.0.2 true
container-service[kubernetes-service/ks] 1.0.459 false
cra 1.0.4 false
doi 0.4.0 false
schematics 1.12.3 true

 ibmcloud dev --version
ibmcloud dev version 2.15.0

 java -version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"e0fccafd69541e3750d460ba0f9743b90336f24f", GitTreeState:"clean", BuildDate:"2020-04-16T11:44:03Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

 helm version --client
Client: &version.Version{SemVer:"v2.16.9", GitCommit:"8ad7037828e5a0fca1009dabe290130da6368e39", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}

 ibmcloud -version
ibmcloud version 1.1.0+cc908fe-2020-04-29T04:06:12+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status
cloud-functions/wsk/functions/fn 1.0.44
cloud-internet-services 1.9.9
container-registry 0.1.482
container-service/kubernetes-service 1.0.118
doi 0.2.5
schematics 1.4.17

 ibmcloud dev --version
ibmcloud dev version 2.4.8

 java -version
openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T14:08:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.10.3 c8d25d9a103b70dc300a4fd55e7e576472284e31

 helm version --client
version.BuildInfo{Version:"v3.9.2", GitCommit:"1addefbfe665c350f4daf868a9adc5600cc064fd", GitTreeState:"clean", GoVersion:"go1.17.12"}

 ibmcloud -version
ibmcloud version 2.9.0+6abd6f8-2022-07-05T14:46:06+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.59 false
cloud-internet-services[cis] 1.14.4 true
code-engine[ce] 1.38.1 true
container-registry 0.1.571 true
container-service[kubernetes-service/ks] 1.0.431 false
cra 0.1.22 false
doi 0.3.8 false
schematics 1.12.1 true

 ibmcloud dev --version
ibmcloud dev version 2.13.0

 java -version
openjdk version "17.0.3" 2022-04-19
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T14:08:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.10.3 c8d25d9a103b70dc300a4fd55e7e576472284e31

 helm version --client
version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.17.5"}

 ibmcloud -version
ibmcloud version 2.7.0+04dfeac-2022-04-28T17:14:20+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.59 false
cloud-internet-services[cis] 1.14.4 true
code-engine[ce] 1.35.0 true
container-registry 0.1.571 true
container-service[kubernetes-service/ks] 1.0.420 false
cra 0.1.20 false
doi 0.3.8 false
schematics 1.10.0 true

 ibmcloud dev --version
ibmcloud dev version 2.12.0

 java -version
openjdk version "17.0.3" 2022-04-19
clientCountryName
datetime
}

Group sorting by aggregation function:

httpRequests1hGroups (orderBy: [sum_bytes_DESC]){
sum {
bytes
requests
}
dimensions {
datetime
}
}







 Pagination 

Pagination, breaking up query results into smaller parts, can be done using limit, orderBy, and filtering parameters. The GraphQL Analytics API does not support cursors for pagination.



* limit (integer) defines how many records to return.
* orderBy (string) defines the sort order for the data.





 Query pages without cursors 

The following examples assume that date and clientCountryName relationships are unique.





 Get the first n results of a query. 

To limit results, add the limit parameter. For example, query the first two records.

firewallEventsAdaptive (limit: 2, orderBy: [datetime_ASC, clientCountryName_ASC]) {
datetime
clientCountryName
}

Specifying a sort order by date returns less specific results than specifying a sort order by both date and country.

The query response follows:

{
"firewallEventsAdaptive" : [
{
"datetime": "2018-11-12T00:00:00Z",
"clientCountryName": "UM"
},
{
"datetime": "2018-11-12T00:00:00Z",
"clientCountryName": "US"
}
]
}





 Query for the next page using filter 

To get the next n results, specify a filter to exclude the last result from the previous query. Using the previous example, you can append the greater-than operator (_gt) to the clientCountryName field and the greater-or-equal operator to the datetime field. By making a specific order, you can get the most complete results.