vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker//images/scenario_enterprise.svg)](https://cloud.ibm.com/docs/atracker?topic=atracker-scenariosscenarios-3)[![Global events](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker//images/scenario_global.svg)](https://cloud.ibm.com/docs/atracker?topic=atracker-scenariosscenarios-4)[![Data lake scenario](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker//images/scenario_datalake.svg)](https://cloud.ibm.com/docs/atracker?topic=atracker-scenariosscenarios-5)



* Forward your activity event data to IBM Cloud Object Storage for IBM Cloud Financial Services compliance. See [Financial Services (FS) Validated scenario](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-scenarios&interface=cliscenarios-1).
* Improve data residency compliance by keeping data at-rest within specific locations such as the EU-managed locations. See [EU-managed account scenario](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-scenarios&interface=cliscenarioss-2).
* Consolidate Activity Tracker Event Routing data to the account and region of your primary operations. You can also route auditing events to multiple locations.
Data centers overview 

When you select a data center, you want to keep latency to a minimum. So, you typically select a data center location that is closest to where your workloads are located. If you see a location that has multiple selections, these data centers are part of a multi-zone region (MZR). MZRs make sure that you have high availability and capacity within these regions.

For more information about resources and locations, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).

Availability of data centers differs for bare metal servers and virtual server instances.
Table 7. EVC mode settings for vCenter Server instances and clusters

 Bare metal server CPU model vSphere 6.7<br><br>[10] vSphere 7.0 

 Skylake EVC is set to Intel® Broadwell Generation. Skylake is not supported. 
 Cascade Lake For the management cluster, EVC is not set. For all other clusters, EVC is set to Intel Skylake Generation. EVC is set to Intel Cascade Lake Generation. 







 Related links 



* [Build numbers and versions of VMware ESXi and ESX (2143832)](https://kb.vmware.com/s/article/2143832)
* [Build numbers and versions of VMware vCenter Server (2143838)](https://kb.vmware.com/s/article/2143838)
* [Enabling Jumbo Frames on virtual switches](https://kb.vmware.com/s/article/1038827)
* [IBM Cloud for VMware Solutions Protection data sheet](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=236C87407E7411E6BA51E79BE9476040)
* [vCenter Server overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [Planning vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
3. Select the log-analysis-kp Key Protect service.
4. Click Start streaming data.





You now see the status Queued for your topic. It may take up to 5 minutes until the streaming job is fully dispatched and up and running. You will see the status switch to Running at that point. In the context menu, you find a new option called View stream landing configuration.





 Using kcat with Event Streams 

The streaming job is currently idle and awaiting messages. In this section, you will configure the tool [kcat](https://github.com/edenhill/kcat) to work with Event Streams. kcat allows you to produce arbitrary messages from the terminal and send them to Event Streams. Below the Kafka message feed will be persisted in your data lake on IBM Cloud Object Storage .



1. Either [install kcat](https://github.com/edenhill/kcat) on your machine or use it via Docker.
2. Change into a new directory and create a text file named kcat.config with the following contents. The value for bootstrap.servers is the comma-separated list of brokers from the es-for-log-analysis service credentials created earlier in the Event Streams service without any quotes, brackets, or newline characters.

bootstrap.servers=<value of property kafka_brokers_sasl in your credentials>
sasl.mechanism=PLAIN
security.protocol=SASL_SSL
sasl.username=token
sasl.password=<value of property password in your credentials>
3. If you installed kcat, run the following command:

kcat -F kcat.config -P -t webserver

If you use Docker, run:

docker run -v ${PWD}:/bdla -w /bdla -it --network=host edenhill/kcat:1.7.0 -F kcat.config -P -t webserver

The command will connect as event producer to the topic webserver. Remember the command for later.
The VMware Regulated Workloads offering includes a secure-by-default architecture that follows IBM's unique policy controls framework, provides continuous compliance monitoring, and offers the highest level of data encryption (FIPS 140-2 Level 4). For VMware Regulated Workloads, only VMware vSphere 7.0 Update 1a is supported.

VMware Solutions Dedicated - VMware vSphere 7.0 Update 1a support
: You can order vSphere 7.0 Update 1a with your VMware vCenter Server with NSX-T instances and VMware vSphere with NSX-T clusters. vSphere 7.0u1a introduces the following support and enhancements.



* Smaller instance footprint with support for converged management and workload cluster. vSphere 6.7 and NSX-T require eight hosts when using vSAN storage and five hosts when using NFS storage. vSphere 7.0u1a enables a footprint of four hosts when using vSAN storage and three hosts when using NFS storage.
* Full support for the HTML5 vSphere Web Client
* Support for Intel Cascade Lake EVC level
* The enhanced VMware vSphere Lifecycle Manager (LCM)
* Enhancements to VMware vSphere Distributed Resource Scheduler (DRS) and VMware vSphere vMotion
* Security enhancements that include multi–factor authentication (MFA) and vSphere Trust Authority (vTA)



vSphere 7.0u1a is the exclusive basis for IBM Cloud® for VMware Regulated Workloads and is available for Cascade Lake and SAP-certified bare metal servers only.

vSphere 7.0u1a currently does not support 25 Gb uplink speed or High performance with Intel Optane for vSAN storage. Support for these features is planned for a future release. Additionally, vSphere 7.0u1a does not support single-node instances.

VMware Solutions Dedicated - vSAN storage for vSphere 7.0 Update 1a
: A warning message might be displayed when you log in to vCenter Server through the vSphere Web Client.
Use a dedicated host to carve out a single-tenant compute node for IBM Cloud VPC. For more information, see [Creating dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances)





 12 March 2021 

New profiles
: The Balanced, Compute, and Memory profile families now include three new profiles with 64, 96, and 128 vCPUs. Profiles with 64 or more vCPUs are deployed exclusively on 2nd generation Intel Xeon Platinum 8260 (Cascade Lake) running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz.

VPN for VPC
: For high-security standards, VPN now supports SHA-512 authentication and Diffie-Hellman Group 19.
: Gateway private IP addresses are now visible for gateway members.





 05 March 2021 

Instance resize (Beta)
: Beta users can now resize a virtual server instance by selecting a different profile to assign to the instance. Profiles are a combination of instance attributes, such as the number of vCPUs, amount of RAM, network bandwidth, and more that define the size and capablilities of the virtual server instance. For more information, see [Resizing an instance (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance).

Snapshots for VPC (Beta)
: Select Beta users can now create snapshots of their block storage boot and data volumes attached to a running virtual server instance. These snapshots can be used to create new volumes, which function like the original volume. For more information, see [About Snapshots for VPC (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).

UI enhancement
: When creating or editing a VPN policy (IKE or IPsec), a new authentication option is available, SHA512. Additionally, a new Diffie-Hellman key exchange group is supported: group 19.







 February 2021 



 25 February 2021 

Dedicated hosts
Locations and providers 

View details about the IBM Cloud data centers where Direct Link Dedicated and Connect offering are available.



 Direct Link Dedicated locations 

The following table provides details about the IBM Cloud data centers where Direct Link Dedicated is available. Choose a tab to see locations for Americas, APAC, and EMEA.

Americas

APAC

EMEA



Table 1. Direct Link Dedicated - Americas

 IBM Location Code Location Type Meet Me Room Operator Operator Site Code 

 Chicago 1 PoP Equinix CH4 
 Dallas 3 PoP 1 Equinix DA1 
 Dallas 4 PoP 2 Digital Realty DFW14 
 Dallas 10 DC(AZ1) QTS IRV 
 Dallas 12 DC(AZ2) Digital Realty DFW18 
 Dallas 13 DC(AZ3) CyrusOne Carrollton - Frankford 
 Denver 1 PoP Coresite DE1 
 Miami 1 PoP TERREMARK MI1 
 Montreal 3 DC Colo-D MON03 
 New York City 2 PoP Equinix NY4 
 New York City 3 PoP Equinix NY4 
 San Jose 2 PoP Equinix SV1 
 San Jose 3 DC Digital Realty SJC31 
 San Jose 4 DC Infomart SJC1 
 São Paulo 1 DC(AZ1) Digital Realty (Ascenty) SAO01 
 São Paulo 2 PoP Equinix SP4 
 São Paulo 3 PoP ODATA SAO03 
 São Paulo 4 DC(AZ2) ODATA SAO04 
 São Paulo 5 DC(AZ3) ASCENTY SAO05 
 Seattle 2 PoP Digital Realty (The Westin Building) WBX 
 Toronto 1 DC(AZ1) Digital Realty TOR01 
 Toronto 2 PoP Cologix TOR02 
 Toronto 3 PoP Equinix TOR03 
 Toronto 4 DC(AZ2) Server Farm TOR04 
 Toronto 5 DC(AZ3) Digital Realty TOR05 
 Washington DC 2 PoP 1 Equinix DC2 
 Washington DC 4 DC(AZ1) Digital Realty IAD38 
 Washington DC 5 PoP 2 Coresite DC2 
 Washington DC 6 DC(AZ2) Raging Wire VA2 
 Washington DC 7 DC(AZ3) Sabey Sabey Intergate.Ashburn
* NSX-V clusters with 25 Gb uplink speed support only a deployment size of FortiGate-VM16.







 FortiGate Virtual Appliance on the Security and Compliance Readiness Bundle 

On the Security and Compliance Readiness Bundle, you can install FortiGate Virtual Appliance on the gateway cluster.



* You can install FortiGate Virtual Appliance on gateway clusters with a 10 Gb or 25 Gb uplink speed.
* With a 10 Gb uplink speed, you can select a deployment size from FortiGate-VM02 up to FortiGate-VM32. The FortiGate-VM32 deployment size requires Cascade Lake 5218 or higher.
* With a 25 Gb uplink speed, you can install FortiGate-VM16 or FortiGate-VM32. The FortiGate-VM32 deployment size requires Cascade Lake 5218 or higher.







 FortiGate Virtual Appliance on Regulated Workloads 

For Regulated Workloads, you can install FortiGate Virtual Appliance on the gateway cluster. You can deploy the service on a single-zone (new or existing) or multizone (existing only) instance.



* You can install FortiGate Virtual Appliance on gateway clusters with a 10 Gb or 25 Gb uplink speed.
* With a 10 Gb uplink speed, you can install FortiGate-VM16 on Cascade Lake 4210.
* With a 25 Gb uplink speed, you can install FortiGate-VM16 or FortiGate-VM32. The FortiGate-VM32 deployment size requires Cascade Lake 5218 or higher.









 Considerations when you install FortiGate Virtual Appliance 

Review the following considerations before you install the FortiGate Virtual Appliance service:



* The FortiGate VMs are deployed on the management cluster or gateway cluster.
* If you want to deploy FortiGate-VM16 or FortiGate-VM32, it is recommended that you consider deploying on a gateway cluster instead of a management cluster because of resource requirements. For more information about Fortinet® sizing, see [FortiGate-VM on VMware ESXi data sheet](https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/FortiGate_VM_ESXi.pdf).
Dual Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H2.3000) HANA and NetWeaver 56 2.7 3 TB Up to 12 Drivers 
 Quad Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H4.3000) HANA and NetWeaver 112 2.7 3 TB Up to 24 Drivers 
 Quad Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H4.6000) HANA and NetWeaver 112 2.7 6 TB Up to 24 Drivers 







 Number of bare metal servers 



* For NFS storage, you can order 2-59 servers. However, for production workloads, a minimum of 3 servers is recommended.
* For vSAN™ storage, you can order 4-59 servers.
* All servers that you order have the same configuration.









 Storage settings 

Storage settings are based on your selection of IBM Cloud bare metal server configuration and the storage type.

You can add NFS storage shares to an existing vSAN or NFS cluster.



 vSAN storage 

Specify the following vSAN options.



 Size for vSAN capacity disks 

Select an option for the capacity disks that you need.





 Number of vSAN capacity disks 

Specify the number of capacity disks that you want to add.





 Size for vSAN cache disks 

Review the Size for vSAN cache disks value.





 Number of vSAN cache disks 

Review Number of vSAN cache disks. The value depends on whether you checked the High performance with Intel Optane box.





 Enable vSAN deduplication and compression 

vSAN storage depends on the number of servers and your total disk capacity, and the use of deduplication and compression.

The amount of storage reduction from deduplication and compression depends on many factors, including the type of data stored and the number of duplicate blocks. Larger disk groups tend to provide a higher deduplication ratio.
: The user interface is updated with various messages and tooltips, and provides the following enhancements:



* The Instance configuration name field is changed to a side panel. You can manage your configuration templates from a list of saved configurations in the side panel.
* The checkbox Select a different cluster location is changed to a switch, for consistency with other similar UI options.
* The SAP-certified Cascade Lake selections (NetWeaver and HANA) are merged into a single option for a more streamlined user experience when you choose the CPU model for your servers.
* The procedure to [set up your environment for your first order](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklistcompleting_checklist-procedure) is simplified.







 3 May 2023 

Madrid data centers available
: (Updated on 22 June 2023) The IBM Cloud data centers Madrid 02, Madrid 04, and Madrid 05 are now available for deployment.

Bring Your Own License (BYOL) no longer available
: BYOL is now disabled in the Licensing section for VMware vCenter Server® instances, VMware vSphere clusters, adding hosts and clusters, and vRealize Operations and Log Insight service.

VMware NSX-T 4.0.1.1 manual upgrade
: VMware NSX-T™ version 4.0.1.1 is now available if you want to upgrade your existing NSX-T instances manually. All newly deployed VMware NSX-T instances are still provisioned with NSX-T version 3.2.0.1.

Updates to VMware vCenter Server instances and VMware vSphere clusters
: The following upgrades are applied to newly deployed instances, clusters, and hosts.



* VMware vCenter Server Appliance 7.0 Update 3k (build 21290409)
* VMware vSAN Witness 7.0 Update 3c (build 19193900)



Veeam 12 availability
: Veeam® Backup and Replication 12 (Veeam 12) is now available for deployment with VMware vCenter Server, Cyber Recovery, and VMware Regulated Workloads offerings.
AC-4 (5) - Embedded Data Types 



  Control requirements 

AC-4 (5) - 0
:   The information system enforces [Assignment: organization-defined limitations] on embedding data types within other data types.





  Additional IBM Cloud for Financial Services specifications 



*  This control is required for ISVs.







  NIST supplemental guidance 

Embedding data types within other data types may result in reduced flow control effectiveness. Data type embedding includes, for example, inserting executable files as objects within word processing files, inserting references or descriptive information into a media file, and compressed or archived data types that may include multiple embedded data types. Limitations on data type embedding consider the levels of embedding and prohibit levels of data type embedding that are beyond the capability of the inspection tools.
* 25 Gb, which is available only for specific pods and data center locations. The following table shows the available locations for the 25 Gb uplink speed.



Asia-Pacific

Europe

NA East



Table 1. Available locations for 25 Gb uplink speed

 Geography Data center Pod 

 Asia-Pacific TOK02 02 
 Asia-Pacific TOK04 01 
 Asia-Pacific TOK05 01 







 Networking type 

Select either Public and private network or Private network only for the gateway cluster.





 Related links 



* [Network interface](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-network-interface)
* [Procedure to order Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure)
Management cluster (multizone VMware instance only) 

New deployments of VMware Regulated Workloads multizone instances are no longer supported. You can still add or delete clusters, add or delete ESXi servers or NFS storage, and add or remove services for existing multizone instances.



 Cluster name 

The primary (management) cluster name is set to mcv-xx-management by default. You can also specify a new management cluster name, which must meet the following requirements.



 Management cluster name requirements 



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* The management cluster name must start with a lowercase alphabetic character.
* The management cluster name must end with a lowercase alphabetic or numeric character.
* The maximum length of the management cluster name is 10 characters.
* The management cluster name must be unique within the regulated workload instance.









 Cluster type 



* For Management-optimized, you get a Cascade Lake server with 20 cores, 2.2 GHz, and 384 GB RAM.
* For Customizable consolidated, you can choose the Cascade Lake server and RAM size according to your needs.







 Hosts per site 

Choose the number of management hosts to be deployed in two availability zones. The hosts are deployed and scaled in pairs (one per site) to ensure appropriate failover capacity. You can order 3 - 20 servers per site.





 vSAN configuration 



* For Management-optimized, you get two vSAN™ capacity disks 1.9 TB SSD.
* For Customizable consolidated, you can choose the type and number of capacity disks according to your needs.







 Estimated resources available per cluster 

Review the estimated resources available per cluster.





 Networking 

Specify the networking type and uplink speed.



 Networking type 

The networking type is set to Private network only by default.





 Uplink speed 

The uplink speed provides two options:



* 10 Gb, which is selected by default.
* 25 Gb, which is available only for specific pods and data center locations. The following table shows the available locations for the 25 Gb uplink speed.



Asia-Pacific

Europe

NA East



Table 1.
[This diagram shows a geography that contains data center buildings that host a multizone region (MZR)](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/mzr.svg)

Figure 1. Multizone region (MZR)

The following table lists the IBM Cloud MZRs that fall into this category and the region, zone, and data center codes for each one.

Americas

Europe

Asia Pacific



Table 1. MZRs in North and South America
Use the buttons before the table to change the context of the table. The column headers identify the data centers located in the specific geographical area.

 Location Region Zone Data center 

 Dallas us-south us-south-1 <br>us-south-2 <br>us-south-3 DAL10 <br>DAL12 <br>DAL13 
 Sao Paulo br-sao br-sao-1 <br>br-sao-2 <br>br-sao-3 SAO01 <br>SAO04 <br>SAO05 
 Toronto ca-tor ca-tor-1 <br>ca-tor-2 <br>ca-tor-3 TOR01 <br>TOR04 <br>TOR05 
 Washington DC us-east us-east-1 <br>us-east-2 <br>us-east-3 WDC04 <br>WDC06 <br>WDC07 







 Single campus MZRs 

Single campus MZRs contain three availability zones in different sections of the same building or within multiple buildings on a campus where the power, cooling, networking, and physical security dependencies overlap but are not identical between any two availability zones. This setup ensures a level of continuous availability and survivability of any one system outage, planned or unplanned.

SLAs are maintained because the infrastructure is set up in a concurrently maintainable fashion so that a single failure does not affect all three zones in the same campus. This setup is ideal for services that support local users as it reduces latency or to support disaster recovery workloads.
Environment data refers to data that is associated with a specific location. For example, dallas-dev, dallas-prod, frankfurt-prod, or frankfurt-staging. To delete the environment data, complete the following steps:



1. Go to Manage Data > Quality Data.
2. Select Environment data.
3. Select the environment that has the data that you want to delete
4. Click Delete.







 Deleting application data 

Application data is all of the data that is associated with a certain app that is attached to a toolchain. To delete the environment data sets, complete the following steps:



1. Go to Manage Data > Quality Data.
2. Select Application data.
3. Select the app that has the data you want to delete, and click Delete.







 Deleting branch data for an application 

Branch data for an application is the data that is associated with a specific repo of an application. For example, the master branch or staging repo.



1. To delete the environment data, go to Manage Data > Quality Data.
2. Select Branch data for an application.
3. Select the app and the branch that has the data you want to delete.
4. Click Delete.









 Deleting a DevOps Insights tool integration 

To delete the DevOps Insights tool integration, you must delete DevOps Insights from your toolchain. To delete DevOps Insights from your toolchain, complete the following steps to delete the tool integration by using the console, with the API, or with Terraform.



 Deleting a DevOps Insights tool integration by using the console 



1. Click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps.
2. On the Toolchains page, select your toolchain.
3.