vania-janet/multiturn-rag-retrieval-data huggingface dataset:
customers_partitioned.csv/country=USA/cust-1.csv
customers_partitioned.csv/country=USA/cust-2.csv
customers_partitioned.csv/country=USA/cust-3.csv
customers_partitioned.csv/country=Sweden/cust-1.csv

To query partitioned tables, you must perform two mandatory steps:



 Step 1: Register the table 

This data partitioning is reflected in the PARTITIONED BY clause of the following CREATE TABLE statement:

CREATE TABLE customers (
customerID string,
companyName string,
contactName string,
contactTitle string,
address string,
region string,
postalCode string,
country string,
phone string,
fax string
)
USING CSV
PARTITIONED BY (country)
LOCATION cos://us-geo/sql/customers_partitioned.csv

Automatic schema detection also recognizes partitioned tables from the structure of the object names, so the same table definition is created from the following statement:

CREATE TABLE customers
USING CSV
LOCATION cos://us-geo/sql/customers_partitioned.csv

If your data on Object Storage does not adhere to this naming convention, you can convert it to a Hive-partitioned layout by using Data Engine in a data preparation step. Use SELECT * to copy the data to a new location and specify [PARTITION BY](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencepartitionedClause) in the INTO clause:

SELECT * FROM cos://us-geo/sql/customers.csv
INTO cos://us-geo/mybucket/customers_partitioned.csv
PARTITIONED BY (country)





 Step 2: Attach table partitions 

After you defined a partitioned table, it is initially empty and you must attach the partitions to it explicitly. A convenient way to add all partitions that exist on Object Storage, is to use the following RECOVER PARTITIONS clause.

ALTER TABLE customers RECOVER PARTITIONS
The EP11 endpoint address starting from 'ep11'. For example: "ep11.us-south.hs-crypto.cloud.ibm.com"
address: "<EP11_endpoint_URL>"
port: "<EP11_endpoint_port_number>" The EP11 endpoint port number
tls:
enabled: true EP11 requires TLS connection.
 Set it 'true' if you want to enable mutual TLS connections.
 By default, set it 'false' because EP11 requires server-only authentication.
mutual: <enable_mtls>
 'cacert' is a full-path certificate file. In Linux with the 'ca-ca-certificates' package installed, this is normally not needed.
cacert:
 Specify the file path of the client certificate if you enable mutual TLS. Otherwise, keep it empty.
certfile: <client_certificate>
 Specify the file path of the client certificate private key if you enable mutual TLS. Otherwise, keep it empty.
keyfile: <client_certificate_private_key>
storage:
 'remotestore' needs to be enabled if you want to generate keys with the attribute CKA_TOKEN.
remotestore:
enabled: true
users:
0: The index of the Security Officer (SO) user MUST be 0.
 The name for the Security Officer (SO) user. For example: "Administrator".
name: "<SO_user_name>"
iamauth: defaultiamcredential
1: The index of the normal user MUST be 1.
 The name for the normal user. For example: "Normal user".
name: "<normal_user_name>"
 The 128-bit UUID of the private keystore. For example: "f00db2f1-4421-4032-a505-465bedfa845b".
tokenspaceID: "<private_keystore_spaceid>"
iamauth: defaultiamcredential
sessionauth:
Select DataStore1, click Next.
7. Change Port group to be dpg-management.
8. Click Next, then click Finish.



After the vCenter migration, you may execute the following IBM Cloud CLO command to validate that the vCenter's VLAN NIC has been moved to VMWARE_BMS002 / esx-002.

ibmcloud is bm-nics $VMWARE_BMS002





 Migrate the management network (vmk0) and its associated uplink (vmnic0) - BMS001 

In this step, you need to migrate the management network (vmk0) and its associated uplink (vmnic0) from the standard vSwitch to the distributed vSwitch (vDS) for VMWARE_BMS001.

Perform this only for VMWARE_BMS001 / esx-001 at this point.

Configure the distributed vSwitch as follows:



1. Log into the vCenter Server using vSphere Client via Web Browser on the Jump machine.
2. Right-click the vDS and select menu Add and Manage Hosts.
3. Add hosts to the vDS. Click the green Add icon (+), and add esx-002/esx-003 from the cluster.
4. Configure the physical adapters (assign uplink-1) and VMkernel adapters (assign to dpg-vmk).
5. Click Manage physical adapters to migrate the physical adapters and VMkernel adapters, vmnic0 and vmk0 to the vDS.
6. Select an appropriate uplink on the vDS for physical adapter vmnic0. For this example, use Uplink1. The physical adapter is selected and an uplink is chosen.
7. Select to migrate the management network on vmk0 from the standard vSwitch to the distributed vSwitch as follows.
For more information, see [Using speaking styles](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-synthesis-expressivesyntheses-expressive-styles).





 The <lexicon> element 

This <lexicon> element introduces pronunciation dictionaries for the given SSML document. It is not supported.

You can use the service's customization interface to define a dictionary of custom entries (word/translation pairs) for use during speech synthesis. For more information, see [Understanding customization](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-customIntro).





 The <mark> element 

The <mark> element is supported only by the service's WebSocket interface, not by its HTTP interface, which ignores the element. For more information, see [Specifying an SSML mark](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-timingtiming-mark).

The <mark> element is an empty element that places a marker into the text to be synthesized. The client is notified when all of the text that precedes the <mark> element has been synthesized. The element accepts a single name attribute that specifies a string that uniquely identifies the mark; the name must begin with an alphanumeric character. The name is returned along with the time at which the mark occurs in the synthesized audio.

Hello <mark name="here"/> world.





 The <meta> and <metadata> elements 

The <meta> and <metadata> elements are containers in which you can place information about the document. They are not supported.





 The <paragraph> and <sentence> elements 

The <paragraph> (or <p>) and <sentence> (or 
) elements are optional elements that can be used to give hints about textual structure. If the text that is enclosed in a <paragraph> or <sentence> element does not end with an end-of-sentence punctuation character (like a period), the service adds a longer than normal pause to the synthesized audio.
VM restart priority Medium 
 Response for Host Isolation Power off and restart VMs 
 Response for Datastore with Permanent Device Loss (PDL) Disabled 
 Response for Datastore with All Paths Down (APD) Disabled 
 Response for APD recovery after APD timeout Disabled 
 VM monitoring sensitivity Custom 
 Failure interval 50 s 
 Minimum uptime 90 s 
 Maximum per-VM resets 10 
 Maximum resets time window Within 1 hr 



For more information about configuring these settings in the vSphere Web Client, see [Configure virtual machine responses](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.avail.doc/GUID-3DAED2B1-55B8-4877-BD0F-BC57C10A516C.html).





 Admission control 

vCenter Server uses admission control to ensure that sufficient resources are available in a cluster to provide failover protection and to ensure that VM resource reservations are respected. In this design, the failover capacity is reserved by specifying a percentage of the cluster resources. The defined failover capacity is set to 25% CPU and 25% memory.





 Datastore heart beating 

vSphere HA uses datastore heart beating to identify hosts that failed and hosts that are on a network partition. Datastore heart beating allows vSphere HA to monitor hosts when a management network partition occurs and to continue to respond to failures that occur. In this design, the heartbeat datastore selection policy is set to “Automatically select datastores accessible from the host”.









 Related links 



* [Overview of VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_overview)
}
],
"queueManager": "qm1"
},
"transmissionSecurity": {
"cipherSpecification": "ANY_TLS12_OR_HIGHER",
},
"type": "clientConnection"
},
...
]
}
Show more
5. Create a Keystore file



* Follow these instructions to [create a keystore file](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_configure_chl_sslmqoc_chl_ssl_keystore) for use in this application setup.
* Once the keystore has been created you must set the MQSSLKEYR environment variable.



MQSSLKEYR is the full path from the system root to the key store file. Note that the filename requires no suffix - so for a key store named key.kdb, specify just "key".



* Mac/Linux - export MQSSLKEYR=/Users/you/store/key
* Windows (Command prompt) - set MQSSLKEYR=c:mystorekey
* Windows (PowerShell) - $env:MQSSLKEYR=c:mystorekey









 Prepare for connection 

Open a command shell on your own machine.



1. Set the 'MQCCDTURL' variable:



* Mac/Linux: export MQCCDTURL=file:////Users/you/definitions/connection_info_ccdt.json
* Windows: set MQCCDTURL=file:///c:/mydefinitions/connection_info_ccdt.json
* Windows (PowerShell): $env:MQCCDTURL=file:///c:/mydefinitions/connection_info_ccdt.json
"enabled": false,
"certfiles": null,
"client": {
"certfile": null,
"keyfile": null
}
}
},
"csr": {
"cn": "ca",
"keyrequest": {
"algo": "ecdsa",
"size": 256
},
"names": [
{
"C": "US",
"ST": "North Carolina",
"L": "Location",
"O": "Hyperledger",
"OU": "Fabric"
}
],
"hosts": [
"<<<MYHOST>>>",
"localhost"
],
"ca": {
"expiry": "131400h",
"pathlength": "<<<PATHLENGTH>>>"
}
},
"idemix": {
"rhpoolsize": 1000,
"nonceexpiration": "15s",
"noncesweepinterval": "15m"
},
"bccsp": {
"default": "SW",
"sw": {
"hash": "SHA2",
"security": 256,
"filekeystore": null
}
},
"cfg": {
"identities": {
"passwordattempts": 10,
"allowremove": true
}
},
"metrics": {
"provider": "prometheus",
"statsd": {
"network": "udp",
"address": "127.0.0.1:8125",
"writeInterval": "10s",
"prefix": "server"
}
}
}
}
Show more
apiconnect.tls_client_profile_del.delete Delete the TLS Client Profile object by ID 
 apiconnect.tls_client_profile_updateByNameVersion.update Update the TLS Client Profile object by name and version 
 apiconnect.tls_client_profile_delByNameVersion.delete Delete a TLS Client Profile 
 apiconnect.keystore_create.create Create a Keystore object 
 apiconnect.keystore_clear.delete Clear the Keystore objects 
 apiconnect.keystore_update.update Update the Keystore object by name or ID 
 apiconnect.keystore_del.delete Delete the Keystore object by name or ID 
 apiconnect.truststore_create.create Create a Truststore object 
 apiconnect.truststore_clear.delete Clear the Truststore objects 
 apiconnect.truststore_update.update Update the Truststore object by name or ID 
 apiconnect.truststore_del.delete Delete the Truststore object by name or ID 
 apiconnect.entry_createTruststoreScope.create Create a Entry object 
 apiconnect.entry_clearTruststoreScope.delete Clear the Entry objects 
 apiconnect.entry_updateTruststoreScope.update Update the Entry object by name or ID 
 apiconnect.entry_delTruststoreScope.delete Delete the Entry object by name or ID 
 apiconnect.catalog_setting_singletonUpdate.update Update the Catalog Setting object 
 apiconnect.configured_gateway_service_createCatalogScope.create Create a Configured Gateway Service object 
 apiconnect.configured_gateway_service_clearCatalogScope.delete Clear the Configured Gateway Service objects 
 apiconnect.configured_gateway_service_delCatalogScope.delete Delete the Configured Gateway Service object by name or ID 
 apiconnect.configured_gateway_service_createSpaceScope.create Create a Configured Gateway Service object 
 apiconnect.configured_gateway_service_clearSpaceScope.delete Clear the Configured Gateway Service objects
This account is necessary so that management operations that are associated to a service can connect to vCenter Server to perform the operations on the service.

To prevent outages and connection problems, if you change the user ID, password, or password expiration settings for this user account, ensure that you also update the information in the associated service.

The user ID for this account is in the format <service_name>-<truncated service_uuid>@test.local or <service_name>-<truncated service_uuid>@example-domain.local. For example, the user ID that the Veeam® service uses to connect to vCenter Server to perform scheduled backups is Veeam-<Veeam_uuid>@test.local.

The <service_name> together with the <service_uuid> truncates to 20 characters.
* VMware resources for vCenter Server instances (V1.9 and later)

If the status of the vCenter Server instance is Available, you can modify the VMware virtual data center, cluster, switches, port groups, and customer Network File System (NFS) datastore names from the VMware vSphere Web Client.

Review the following restrictions:



* Do not change the vCenter Server instance name and the vCenter Server virtual machine name.
* Do not change the name of the management datastore from its default value. The default value is vsanDatastore for VMware vSAN™ instances and management-share for NFS instances.
* Do not change the names and do not delete any of the management subnets that are created for the vCenter Server instances.
* Do not change the name of the network uplinks that are created during provisioning.
* Do not rename or remove NSX-T components. These operations might generate add and remove failures or delays. The NSX-T components with the names that are documented in [Naming conventions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-nsx-t-designnsx-t-design-naming) are used when automation adds or removes hosts, clusters, and services.
All-in-one deployment 

An automated deployment and configuration of a single virtual machine (VM) that hosts all the RiskForesight™ application components. This deployment model is suitable for small deployments, up to 100 assets with 7 - 30 days of indexing. The details of the “all-in-one” VM and the additional Remote Collector VM are shown in the following tables.

All-in-one VM

Remote collector VM



Table 1. All-in-one VM parameters

 Parameter                         Value                                                                                                                                

 Type                              Base                                                                                                                                 
 VM qty                            1                                                                                                                                    
 vCPU                              16                                                                                                                                   
 RAM                               32 GB                                                                                                                                
 Disk                              80 GB                                                                                                                                
 OS                                CentOS 7                                                                                                                             
 Installed application components  UI, App, Plug-ins, Central collector, Index datastore, Messaging datastore, Relational datastore, Index datastore, Remote collector
vCenter needs the values separated for mount path, server and folder. You can use the following commands to get the required values:

echo "Server : "$(echo $VMWARE_DATASTORE01_TARGET01_MOUNTPATH | awk -F: '{print $1}')

echo "Folder : "$(echo $VMWARE_DATASTORE01_TARGET01_MOUNTPATH | awk -F: '{print $2}')
5. Use the Server and Folder values when configuring the datastore in vCenter.







 Step 2: Attach IBM Cloud VPC File share as a Datastore for a Compute Cluster in vCenter 

In the vSphere Client object navigator, browse to a host, a cluster, or a data center.



1. From the right-click menu, select Storage > New Datastore.
2. Select NFS as the datastore type and specify an NFS version as NFS 4.1.
3. Enter the datastore parameters: Datastore name, Folder and Server. With NFS 4.1, you can add multiple IP addresses or server names if the NFS server supports trunking, IBM Cloud uses multiple IPs behind the provided FQDN. The ESXi host uses these values to achieve multipathing to the NFS server mount point.
4. On Configure Kerberos authentication selection, select Don't use Kerberos authentication.
5. On Host Accessibility, select all hosts on your cluster.
6. Review the configuration options and click Finish.



The following parameters were used in this example.

General
Name: Datastore-VPC-NFS-01
Type: NFS 4.1

NFS settings
Server: fsf-fra0251a-fz.adn.networklayer.com
Folder: /nxg_s_voll_mz02b7_7e070ef6_12f5_4794_9077_953ba53dde82
Access Mode: Read-write
Kerberos: Disabled
To use the client-get-signed-url action in the cloud-object-storage package, you must bind your IBM Cloud Object Storage service credentials to the action.



* To bind service credentials to all actions in the package, use the service bind command in the CLI.
* To bind service credentials to individual actions, complete the following steps in the console.







 Binding service credentials in the console 



1. From the [Actions page](https://cloud.ibm.com/functions/actions), click cloud-object-storage package.
2. Next, click the client-get-signed-url action, then click Parameters.
3. Click Add to enter a new parameter. Note that parameters must be entered as key and value pairs.
4. For Parameter Name, enter the key __bx_creds.
5. For Default Value, paste in the service credentials JSON object from the IBM Cloud Object Storage service instance that you created earlier.
6. Repeat the steps for each action that you want to use.







 Binding service credentials in the CLI 

Bind the credentials from the IBM Cloud Object Storage instance you created to the package. You can include the --keyname flag to bind specific service credentials. For more information about binding services, see [Service commands](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_service).

ibmcloud fn service bind cloud-object-storage cloud-object-storage --keyname <service_key>

Verify that the package is configured with your IBM Cloud Object Storage service instance credentials.

ibmcloud fn package get <namespace_ID>cloud-object-storage parameters

You still need to pass the bucket and endpoint values during action invocation. Or, you can bind these parameters to the package or an action. To do this, see [Setting default parameters for a package or action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_param_bind).
This can be verified with the vSAN Health Service by clicking Home > Hosts and Clusters, then select the vSAN Cluster. Click the Monitor tab, vSAN and then click Health. Review the Test Results.
* No active resync at the start of the upgrade process by clicking Home > Hosts and Clusters, then select the vSAN Cluster and click the vSAN tab and then click Resync Components. The Resync components count should be 0. Some resync activity is expected during the upgrade process, as data needs to be synchronized following host restarts.



* vSphere ESXi host preparation - When you move a host into maintenance mode in a vSAN cluster, you have three options to choose:



* No data migration - If you select this option, vSAN does not evacuate any data from this host. If you power off or remove the host from the cluster, some virtual machines (VMs) might become inaccessible.
* Ensure availability - If you select this option, vSAN allows you to move the host into maintenance mode faster than Full data migration and allows access to the VMs in the environment.
* Full data migration



* Exit maintenance mode and resync - When the vSphere ESXi host is upgraded and moved out of maintenance mode, a resync occurs. You can see this through the VMware vSphere Web Client. Ensure this is complete before you move onto the next host. A resync is occurring as the host that is updated can now contribute to the vSAN datastore again. It is vital to wait until this resync is complete to ensure that there is no data loss.
* After starting a vSAN Cluster upgrade:



* Do not attempt to upgrade a cluster by introducing new versions to the cluster and migrating workloads.
* If introducing new hosts, ensure that they are of the same initial version and upgrade them along with the rest of the cluster.
* If you are adding or replacing disks during an upgrade, ensure that they are formatted with the appropriate legacy on-disk format version, if applicable.
* Therefore, certain vSAN behavior changes are controlled by the on-disk format it is important that newer on-disk format versions are not introduced into a mixed-version cluster.









 Upgrade the vCenter Server Appliance
Considerations about changing vCenter Server artifacts 

Changing users, resources, or subnets that are reserved for IBM Cloud® for VMware Solutions can impact management operations.

Do not edit the global permissions of the ic4v-vCenter group in the Users and Groups page on the VMware vSphere® Web Client. Such changes include changing the username, deleting the user, or changing its password. Use the root host user ID. The ic4vroot host user ID is created for IBM use only.



 automation ID 

The automation ID is a user account that is used by the automated operations that are provided in the VMware Solutions console.

Users and passwords for the automated operations in the console must not be changed because the console operations that depend on those credentials might fail.





 Service-specific user accounts 

Each service creates an internal user account in VMware vCenter Server®. This account is necessary so that management operations that are associated to a service can connect to vCenter Server to perform the operations on the service.

To prevent outages and connection problems, if you change the user ID, password, or password expiration settings for this user account, ensure that you also update the information in the associated service.

The user ID for this account is in the format <service_name>-<truncated service_uuid>@test.local or <service_name>-<truncated service_uuid>@example-domain.local. For example, the user ID that the Veeam® service uses to connect to vCenter Server to perform scheduled backups is Veeam-<Veeam_uuid>@test.local.

The <service_name> together with the <service_uuid> truncates to 20 characters.





 VMware resources for vCenter Server instances (V1.9 and later) 

If the status of the vCenter Server instance is Available, you can modify the VMware virtual data center, cluster, switches, port groups, and customer Network File System (NFS) datastore names from the VMware vSphere Web Client.

Review the following restrictions:



* Do not change the vCenter Server instance name and the vCenter Server virtual machine name.