vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Data is labeled by adding a customer_id of your choice (see restrictions in [How to label data](https://cloud.ibm.com/docs/discovery?topic=discovery-information-securitylabeling)) to the optional X-Watson-Metadata header. Discovery can then delete it by customer_id.

On any REST call, an optional header X-Watson-Metadata can be sent with semicolon separated field=value pairs, where currently only customer_id is persisted. By adding that customer_id in X-Watson-Metadata header, the request indicates that it contains data that belongs to this customer_id.

customer_ids are unique within a single Discovery instance. They are not unique per environment or collection. Do not include personal data in these IDs.

Experimental and beta features are not intended for use with a production environment and, therefore, are not guaranteed to function, as expected, when labeling and deleting data. Do not use experimental and beta features when implementing a solution that requires the labeling and deletion of data.





 Methods that support labeling data 

The following stored information can be deleted using a customer_id if the customer_id was specified when the information was originally added using the associated method:



* queries (/v1/environments/{environment_id}/collections/{collection_id}/query) Only when used with the passages or natural_language_query parameters
* events (/v1/events)
* documents (/v1/environments/{environment_id}/collections/{collection_id}/documents)
* notices (/v1/environments/{environment_id}/collections/{collection_id}/notices) Only ingestion notices are labeled.
* training data (/v1/environments/{environment_id}/collections/{collection_id}/training_data)



The following stored information is not explicitly labeled and cannot be deleted by specifying the customer_id. Personal Data is not supported in these fields.

Any string fields (including but not limited to name and description) of the following stored items:



* configurations
* collections
* environments







 Labeling data
: You can now select the Intel Xeon 8260 CPU when you provision a bare metal server. For more information, see [Bare metal server options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmbm-cascade-lake-support).







 February 2021 



 01 February 2020 

25 Gbps port space is now available
: You can now use 25 Gbps port speed on select Cascade Lake processor servers. For more information about 25 Gbps port speed, see the 25 Gbps port speed section of the Bare Metal Servers [Network options](https://test.cloud.ibm.com/docs/bare-metal?topic=bare-metal-network-options25-gbps-port-speed) topic.







 Aug 2020 



 12 August 2020 

Intel Xeon 6250 CPU
: You can now select the Intel Xeon 6250 CPU when you provision a bare metal server. For more information, see [Bare metal server options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmbm-cascade-lake-support).





 10 August 2020 

Custom images templates now available
: Image templates provide an imaging option for IBM Cloud® Bare Metal Servers. With Bare Metal Servers custom image templates, you can capture an image of a bare metal server to replicate its configuration with minimal changes in the order process. For more information, see [About bare metal custom image templates](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-getting-started-bm-custom-image-templates).







 July 2020 



 22 July 2020 

IBM Cloud Monitoring
: IBM Cloud Monitoring collects basic Classic infrastructure and VPC virtual server metrics such as CPU usage, disk usage, network traffic, and memory. These metrics are stored in IBM Cloud Monitoring. For more information, see [IBM Cloud Monitoring](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-monitoring-iaas).







 May 2020 



 18 May 2020 

NVM solid-state drives
* You are responsible to ensure that all VMware ESXi™ servers have proper firmware and drivers to support vSphere 7. Broadwell and SkyLake servers are not supported. Research and plan carefully for Cascade Lake servers.
* IBM Cloud supports only Cascade Lake bare metal servers for newly deployed vSphere 7 instances.
* If you add clusters or hosts to a vSphere 7 instance from the VMware Solutions console, only Cascade Lake bare metal servers are provisioned.
* After you upgrade, your existing clusters will continue to use N-VDS switches, which are deprecated by VMware. Support for N-VDS (NSX-T Virtual Distributed Switch) will be removed in a future VMware NSX-T™ release. Plan to migrate your workloads to a new vCenter Server with NSX-T instance with vSphere 7. For more information, see [NSX-V to NSX-T migration overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).
* If you are using VMware NSX-V, familiarize yourself with the product lifecycle for NSX-V from VMware and plan to migrate your workloads to vCenter Server with NSX-T instance. For more information, see [NSX-V to NSX-T migration overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).
* vCenter Server is designed to allow for a "rolling" upgrade. That is, virtual machine (VM) workloads that are currently functioning continue to function without an outage if you complete the following procedure. Enterprises must engage their change management policies to enable a structured and communicated upgrade and plan for contingencies. However, during the upgrade process of certain management functions, such as vCenter Server and NSX Manager, temporary outages of management functions, configuration changes, powering off and on VMs, might be impacted.







 Before you begin 

The time to complete the upgrade is unknown.
If No resource group available is displayed in this field, you currently do not have the permission to add the virtual data center to any resource group in this account. Contact the account owner to be assigned an Editor or Administrator role on a resource group in the account. For more information, see [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles).







 Deployment topology 



* Single-zone VMware virtual data center deploys your virtual data center in a single-zone data center.
* Multizone VMware virtual data center deploys your virtual data center across two availability zones in an IBM Cloud multizone region if a single-zone data center failure occurs.







 Data center location 

Select the IBM Cloud data center settings. For more information, see [IBM Cloud data center availability](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_planningshared_planning-dc-availability).



 Geography 

Select the region where your virtual data center instance is hosted.





 Site 

Select the IBM Cloud data center site where the virtual data center is hosted.





 Location 

Select the IBM Cloud data center where the virtual data center is hosted.







 Networking 

You must specify the following network settings for your virtual data center.



 Networking type 

Select either Private only or Public and private. Public networking is delivered through a generic routing encapsulation enablement tunnel system.







 Virtual data center capacity 

Virtual data center capacity is based on your selection of the On-demand or Reserved pricing plan.

If you selected On-demand, select the vCPU and RAM limits.

If you selected Reserved, your vCPU model settings are based on your selection of Preconfigured or Customizable.

If you selected Preconfigured, you have the following options for allocated vCPU and RAM limits.



Table 1. Preconfigured vCPU and RAM options

 Size vCPU RAM 

 Small 64-cores 512 GB 
 Medium 128-cores 1024 GB 
 Large 256-cores 2048 GB 



If you selected Customizable, you can customize your reserved vCPU and RAM limits.
Single data centers are not co-located with IBM Cloud services, such as IAM or Key Protect, and offer no resiliency in a site outage or destruction.

If a networking failure results in a partition where the data center is unable to access IAM, authentication and authorization information is read from a cache that might become stale. This cached data might result in a lack of enforcement of new or altered IAM policies for up to 24 hours.

Public

Private

Direct



Table 3. Single Data Center Endpoints

 Region Type Endpoint 

 ams03 Public s3.ams03.cloud-object-storage.appdomain.cloud 
 che01 Public s3.che01.cloud-object-storage.appdomain.cloud 
 mil01 Public s3.mil01.cloud-object-storage.appdomain.cloud 
 mon01 Public s3.mon01.cloud-object-storage.appdomain.cloud 
 par01 Public s3.par01.cloud-object-storage.appdomain.cloud 
 sjc04 Public s3.sjc04.cloud-object-storage.appdomain.cloud 
 sng01 Public s3.sng01.cloud-object-storage.appdomain.cloud 







 EU-Managed Endpoints 

The IBM Cloud Activity Tracker can archive to a bucket at specific IBM Cloud Object Storage instances. This table shows the EU-Managed locations of Object Storage instances for archiving events.



Table 4. EU-managed Endpoints

 Object Storage bucket location Resiliency City 

 ams03 Single Site Amsterdam 
 eu-de Regional Frankfurt 
 eu-gb Regional London 
 mil01 Single Site Milan 
 par01 Single Site Paris 
 eu-geo Cross Region Amsterdam, Frankfurt, Milan 







 Resource Configuration Endpoints 

Requests made using the Resource Configuration API are sent to a global endpoint, regardless of the bucket's location.



 Type Endpoint 

 Public config.cloud-object-storage.cloud.ibm.com/v1 
 Private config.private.cloud-object-storage.cloud.ibm.com/v1 
 Direct config.direct.cloud-object-storage.cloud.ibm.com/v1
{region}.databases.cloud.ibm.com/v5/ibm/deployments/{id}/allowlists/ip_addresses/{ipaddress} -H 'Authorization: Bearer <>'

When all entries in the allowlist are removed, the allowlist is disabled and all IP addresses are accepted by your deployment.







 Allowlist Cloud Databases in your Environment 

If you use allowlists to control connections in your environment, use the following IP lists to allowlist Cloud Databases deployments. We recommend you allowlist all of the subnet ranges for the entire region that your deployments live in.



 in-che List 



 Public Subnets 



Table 1. in-che Public Subnets

 Location Region Data center Subnet First IP 

 Chennai in-che che01 169.38.95.127/27 169.38.95.97 
 Chennai in-che che01 169.38.121.159/28 169.38.121.145 
 Chennai in-che che01 169.38.132.127/25 169.38.132.1 
 Chennai in-che che01 169.38.136.255/26 169.38.136.193 
 Chennai in-che che01 169.38.73.151/29 169.38.73.145 
 Chennai in-che che01 169.38.105.79/29 169.38.105.73 







 Private Subnets 



Table 2. in-che Private Subnets

 Location Region Data center Subnet First IP 

 Chennai in-che che01 10.162.8.127/26 10.162.8.65 
 Chennai in-che che01 10.163.20.127/25 10.163.20.1 
 Chennai in-che che01 10.162.115.103/29 10.162.115.97 
 Chennai in-che che01 10.162.132.79/29 10.162.132.73 









 ca-tor List 



 Public Subnets 



Table 3. ca-tor Public Subnets

 Location Region Data center Subnet First IP 

 Toronto ca-tor tor01 158.85.91.111/28 158.85.91.97
From the console, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) and select Classic Infrastructure.
3. Select Network > IP Management > VLANs.



The VLANs listing displays information about your VLANs, and it provides access to each VLAN, along with associated devices or subnets.



 Understanding pod versus data center selection 

The options for where to order a VLAN provide for different needs and constraints. This section summarizes reasons why you might select one option over another.

The Order by Pod option allows you to specify the exact pod (and thus router) where you require a VLAN. Use this option if you have a specific reason for the VLAN to exist in that pod. Reasons for this include using the VLAN with an existing Gateway Appliance or multi-VLAN Firewall. Typically, if you are ordering additional VLANs as part of a larger deployment scheme, you know what pod you want the VLANs in. If so, choose this option.

Use the Order by data center option when the location of the VLAN is less important. This option is best when you want to seed a location for which you will cluster other resources. If your deployments follow a network first strategy (as opposed to ordering servers first), using this option to establish your presence in a new data center provides the best experience. Your requested VLANs are fulfilled by any pod in the selected data center; set no expectations about which pod will be selected when choosing this option.

It's best to use the least specific location option available that fits your current need.





 Complex orders 

The portal ordering experience only provides for ordering a single VLAN configuration per order. A configuration consists of the desired network, location option, and quantity. While it is possible to order multiple VLAN configurations in a single order via the API, each configuration quantity is restricted to 1. This means that each VLAN configuration provided is fulfilled independently. Thus, if each configuration utilizes the data center location option, each VLAN can be assigned to different pods within that data center.





 A note about capacity
Release notes 

Use this release notes to learn about the latest changes to the IBM Cloud Data Security Broker documentation that are grouped by month.



  February 2023 

Review the release notes for February 2023.



  13 February 2023 





  Introducing IBM Cloud Data Security Broker Beta version 

IBM Cloud Data Security Broker is a complete data protection solution that secures sensitive data in enterprise databases by integrating with key management and databases to provide application-level encryption.

Following features are supported in the Beta version:



*  Data Encryption and Decryption
*  Data Masking
Data center consolidations 

As part of the data center modernization strategy for IBM Cloud®, several data centers are scheduled to consolidate.

IBM Cloud invests significantly in data center infrastructure. These investments include rolling out newer data centers and multizone regions (MZRs) designed to deliver a more resilient architecture with higher levels of network throughput and redundancy. For more information, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).

Part of this modernization strategy is to consolidate select data centers. As this transition approaches, help is available to assist you in your migration to modern data centers. For more information, see [Migrating resources to a different data center](https://cloud.ibm.com/docs/account?topic=account-migrate-data-center) or [FAQs for migrating resources to a different data center](https://cloud.ibm.com/docs/account?topic=account-faqs-dc-closure).

The following table shows the locations with the associated data centers that are set to close, and the recommended data centers to which you can migrate.



Table 1. Data centers or PODs that are closing in 2023

 Location Data Center to Close Recommended Data Centers Migration Deadline 

 Dallas DAL05 DAL10, DAL12, DAL13 04 April 2024 
 San Jose SJC01 SJC03, SJC04 or <br>DAL10, DAL12, DAL13 04 April 2024 
 Washington DC WDC01 WDC04, WDC06, WDC07 04 April 2024 



The following table describes important dates that you need to be aware of if you have services that run in the data centers that are set to close. You receive notifications if you have services in the data centers that are closing.



Table 2. Timeline for data center migration

 Date Data Center Migration Milestone 

 03 April 2023 Official announcement for all impacted customers in the following data centers: DAL05, SJC01, and WDC01 
 03 April 2023 Stop provisioning for new customers in the following data centers: DAL05, SJC01, and WDC01
"datapoints":

118.1668472290039,
1523984540
],

90.57628631591797,
1523984550
],

142.6778106689453,
1523984560
],

118.42487335205078,
1523984570
],

120.38044738769531,
1523984580
],

103.94148254394531,
1523984590
],

126.64134979248047,
1523984600
],

113.03324127197266,
1523984610
],

136.9058074951172,
1523984620
],

148.68711853027344,
1523984630
],

121.22771453857422,
1523984640
],

142.86459350585938,
1523984650
],

103.75953674316406,
1523984660
],

139.1707763671875,
1523984670
],

118.29866027832031,
1523984680
],

126.3541259765625,
1523984690
],

115.5962905883789,
1523984700
],

106.68751525878906,
1523984710
],

144.12387084960938,
1523984720
],

103.8598861694336,
1523984730
],

136.84429931640625,
1523984740
Migrating resources to a different data center 

IBM Cloud®'s investments in data center infrastructure includes rolling out newer data centers and multizone regions (MZRs) and closing older data centers that are unsuitable for upgrading.

For a current list of data centers, see [Locations for resource deployment ](https://cloud.ibm.com/docs/overview?topic=overview-locations).

For information, see [Data center closures](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).



  Migrating your resources 

To identify your impacted resources, take advantage of special offers, or learn about recommended configurations, use one of the following options to contact the IBM 24x7 Client Success team:



*  [Live chat](https://www.ibm.com/cloud/data-centers/?focusArea=WCP%20-%20Pooled%20CSM&contactmodule)
*  Phone: (US) 866-597-9687; (EMEA) +31 20 308 0540; (APAC) +65 6622 2231



To avoid any disruption to your service, please complete the following steps to migrate your resources from your current data center to your new location:



*  Restore your backup into a new database, in a new region. For more information, see [Managing backups](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups).
*  For an IBM Cloud® Databases for PostgreSQL deployment, you can deploy [Read Replicas](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-read-only-replicas) into a new region and turn that Read Replica into a stand-alone database.
Requirements and planning for VMware Shared 

Review the following requirements before you order your VMware Shared virtual data centers. Plan for your order by considering the IBM Cloud data center location, your workload capacity requirements, and services requirements.

Price calculations are automatically generated when you access the VMware Shared instance order page. Default selections for on-demand virtual data centers include public and private networking, 2000 vCPU, and 40960 RAM. Default selections for reserved virtual data centers include public and private networking, and customizable vCPU and RAM limits.



 IBM Cloud account requirements 

To order VMware Shared, you must have a Pay As You Go or Subscription IBM Cloud account. The cost of the resources that are ordered is billed to that IBM Cloud account.





 Virtual data center name requirements 

The virtual data center name must meet the following requirements:



* Maximum length is 128 characters.
* Only alphanumeric, dash (-), and underscore (_) characters are allowed.
* The name must be unique from active virtual data centers within your account. You can create a virtual data center that has the same name as a previously deleted virtual data center.







 IBM Cloud data center availability 

The VMware Shared deployment has strict requirements on the physical infrastructure. Therefore, you can deploy your virtual data centers only in IBM Cloud data centers that meet the requirements.

The following IBM Cloud data centers are available for VMware Shared deployment.

Europe

North America



Table 1. Available IBM Cloud data centers for deployment

 Geography Site Location vSAN support Multizone support 

 Europe Frankfurt Director 01 Frankfurt 02 None No 
 Europe Frankfurt Director 01 Frankfurt 04 None No 
 Europe Frankfurt Director 01 Frankfurt 05 None No 







 Services for VMware Shared instances 

The following preinstalled services are available for your virtual data center based on your needs.



* [Managing Veeam for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_veeam)
[BI.S4.NW192](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=8451&packageId=2640&itemId=13285) 32 64 192 GB 82,470 
 [BI.S4.NW384](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=8451&packageId=2642&itemId=13285) 32 64 384 GB 85,130 
 [BI.S4.NW768](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=8451&packageId=2644&itemId=13289) 40 80 768 GB 112,830 



See also [SAP Note 2414097 - SAP Applications on IBM Cloud Classic Infrastructure environment](https://launchpad.support.sap.com//notes/2414097).





 Understanding Bare Metal profile names 

The Bare Metal profile names are contextual and sequential, below uses an SAP HANA certified server as an example:



Table 2. Profile naming for SAP NetWeaver

 Profile name Naming convention component What it means 

 BI.S3.NW384 BI IBM Cloud Infrastructure 
 S3 Series 3 (processor generation) <br><br><br><br> * S3 is Intel Skylake/Kaby Lake<br> * S4 is Intel Cascade Lake<br><br><br> 
 NW NetWeaver-certified server 
 384 384 GB RAM 







 Profiles available on Hourly Consumption Billing 

The following Bare Metal servers are available on Hourly Consumption Billing:



* BI.S3.NW32
* BI.S4.NW192
* BI.S4.NW384
* BI.S4.NW768
However, the Administrative State option in the DataPower UI functions as an on/off switch for that particular client.
* Connection status polling for real-time connected and disconnected gateway status updates is not supported.
* Full certificate chains with destination-side TLS are not supported prior to DataPower version 7.5.1.0
* Cloud destinations are not supported prior to DataPower version 7.5.1.0
* The log level can't be changed to TRACE level
* The latest Secure Gateway Client version in DataPower is 1.8.5fp1, please check [here](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-client-installinstalling-datapower) for more information
Migrating resources to a different data center 

IBM Cloud invests significantly in data center infrastructure. These investments include rolling out newer data centers and multizone regions (MZRs) designed to deliver a more resilient architecture with higher levels of network throughput and redundancy.

Part of this modernization strategy is to close older data centers that are unsuitable for upgrading. As this transition approaches, help is available to assist you in your migration to modern data centers. For a list of the available data centers, see [Endpoints and storage locations](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-endpoints).

For additional information about data center closings, see [Withdrawal of support for some data centers](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).

To identify your impacted resources, take advantage of special offers, or learn about recommended configurations, use one of the following options to contact the IBM 24x7 Client Success team:



* [Live chat](https://www.ibm.com/cloud/data-centers/?focusArea=WCP%20-%20Pooled%20CSM&contactmodule) (Click 'Lets Talk' in the lower right corner)
* Phone: (US) 866-597-9687; (EMEA) +31 20 308 0540; (APAC) +65 6622 2231





 Migrating your resources 

To avoid any disruption to your service, please complete the following steps before any announced deadlines:



1. Identify your buckets in the data centers that are set to close through viewing your COS UI buckets page. Also, [Extended listing](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-list-buckets-extended) can be used for this purpose, as it will return 'LocationConstraint' values that indicate the location in addition to the storage class of a bucket.