vania-janet/multiturn-rag-retrieval-data huggingface dataset:
About Citrix DaaS for IBM Cloud 

Citrix DaaS for IBM Cloud® is a streamlined process for experienced administrators and service providers to create a dedicated (Citrix DaaS) service environment at one of our global data centers. This solution provides flexibility, control, and saves you time in building out your virtual apps and desktops solution. If you are invested in virtual desktop infrastructure (VDI), you understand the complexity of hosting and managing VDI entirely on-premises. The offering is purposefully built for a better VDI experience in the cloud.

The solution is integrated with the Citrix DaaS service deployment model, which shifts the management of core components to Citrix so you can focus on managing your applications and desktops. IBM Cloud creates the Citrix Cloud Connectors and other compute, networking, and storage components that are required to host your applications and desktops and connects the IBM Cloud resource location to Citrix Cloud. You manage the infrastructure components after provisioning, including the Active Directory and Virtual Delivery Agents (VDAs).



 Provisioning Citrix DaaS on Classic Infrastructure option 

You can provision Citrix Hypervisor on Bare Metal servers or VMWare. For more information about provisioning on Classic infrastructure, see [Provisioning Citrix DaaS on IBM Cloud Classic infrastructure](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-provisioning-cvad-classic).

Zoom

![Architecture diagram.](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/citrix-daas/images/CitrixArchDiagram.svg)

Figure 1. Citrix DaaS for IBM Cloud Classic architecture diagram





 Provisioning Citrix DaaS on Virtual Private Cloud option 

You can provision Citrix DaaS on Virtual Private Cloud.
About IBM Cloud Direct Link 

IBM Cloud® Direct Link offerings provide connectivity from an external source into a customer's IBM Cloud private network. Direct Link can be viewed as an alternative to a traditional site-to-site VPN solution, which is designed for customers that need more consistent, higher-throughput connectivity between a remote network and their IBM Cloud environments.

The IBM Cloud Direct Link service is a routed, OSI Layer-3 service. It offers a direct connection to the IBM Cloud private network backbone, with low latency and speeds up to 5 Gbps.

For increased flexibility in creating this Layer-3 connectivity, IBM Cloud Direct Link enables customers to use:



* Dual IP for remote hosts
* Tunneling for BYOIP



You can also bind a direct link to transit gateways so that there is a secure connection to on-prem networks and IBM Cloud resources connected through the transit gateways.



 Direct Link offerings 

Currently, two types of connections are available: Direct Link Dedicated and Direct Link Connect.



 Direct Link Connect 

Offers private access to your IBM Cloud infrastructure and to any other clouds linked to your service provider through your local IBM Cloud data center. This option is perfect for creating multi-cloud connectivity in a single environment. IBM connects customers to the IBM Cloud private network, using a shared bandwidth topology. As with all Direct Link products, you can add global routing that enables private network traffic to all IBM Cloud locations.





 Direct Link Dedicated 

Allows customers to terminate a single-tenant, fiber-based cross-connect into the IBM Cloud network. This offering can be used by customers with colocation premises that are next to IBM Cloud PoPs and data centers, as well as network service providers that deliver circuits to customer on-premises or other data centers.







 Using AS prepends to influence route preference 

This use case pertains to both Direct Link Connect and Direct Link Dedicated offerings.

Adding one or more autonomous system (AS) numbers at the beginning of an AS path is called AS prepending. You can use this technique to make a route less preferable to the BGP router by increasing the length of the AS path. For example, you might want route redundancy, but don't want traffic going through both routes at the same time.
IBM Cloud Framework for Financial Services - Control Requirements 

[IBM Cloud for Financial Services™](https://www.ibm.com/cloud/financial-services) is designed to build trust and enable a transparent public cloud ecosystem with the features for security, compliance, and resiliency that financial institutions require. Financial institutions can confidently host their mission-critical applications in the cloud and transact quickly and efficiently. With a large partner ecosystem of independent software vendors (ISVs), Software as a Service (SaaS), and fintech partners, IBM Cloud for Financial Services offers a new generation of cloud for the enterprise. Financial institutions can now deploy on public cloud to enable innovation and deliver new outstanding customer experiences, while managing stringent industry regulations for sensitive data and complex workloads.

The IBM Cloud Framework for Financial Services™ provides a comprehensive set of control requirements designed to help address the security requirements and regulatory compliance obligations of financial institutions and cloud best practices. The cloud best practices include a shared responsibility model across financial institutions, application providers, and IBM Cloud.

The technology-agnostic control requirements defined in the framework were built by the industry for the industry. The framework contains 565 control requirements that span 7 focus areas and 21 control families. The control requirements were initially based on [NIST 800-53 Rev 4](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls/release-search!/800-53?version=4.0) and have been enhanced based on feedback from leading industry partners.

See [IBM Cloud Framework for Financial Services - Control Requirements](https://cloud.ibm.com/media/docs/downloads/framework-financial-services/IBM_Cloud_Framework_for_Financial_Services_-_Control_Requirements_v1.1.0.xlsx) for a spreadsheet of the control requirements.

See [Getting started with IBM Cloud for Financial Services](https://cloud.ibm.com/docs/framework-financial-services) for reference architectures and prescriptive implementation guidance to help you build solutions on IBM Cloud that meet the control requirements.
* [Direct Link Exchange on Classic](https://cloud.ibm.com/docs/direct-link?topic=direct-link-about-ibm-cloud-direct-linkdirect-link-exchange-solution)





 The Direct Link Connect on Classic solution 

Common use cases: The Connect solution enables customers to use an NSP to deliver connectivity to IBM Cloud locations. This offering typically provides connectivity at a reduced cost because the physical connectivity from IBM Cloud to the NSP is already in place, which is shared among other customers.

Zoom

![Direct Link Connect](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Connect.png)

Figure 1. Direct Link Connect

Termination location: IBM Cloud point of presence (PoP).

Typical deployment time: 5 - 10 days after circuit reaches the exchange. Deployment time can possibly be 30 - 60 days overall, depending on your location and requirements when you order a circuit from an NSP or carrier.

Cross-connect details: Physical cross-connects for the secure Direct Link Connect interconnect are maintained between IBM Cloud and the Connect provider. Customers request a "Virtual Circuit" from the Cloud Connect provider, which establishes logical connectivity to IBM Cloud, after the customer is interconnected to the Cloud Connect provider.

Port speed options: Select 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps.

Approximate latency: Latency is approximately 1.5 ms within the local area (data centers with the same three-letter prefix, such as DAL, AMS, MEL). See [Looking Glass](http://lg.softlayer.com/) for live PoP-to-PoP (P2P) location latency measurements.

IBM colocation services: None.

Redundancy: IBM Cloud does not provide redundancy as part of the product.
Exploring IBM Cloud load balancers 

IBM Cloud offers several load balancing solutions to choose from. The following table compares the load balancing solutions to help you choose the one that's right for you. To learn more about the individual offering, click its name in the table.



A comparison of IBM's load balancer offerings
This table lists all of IBM's load balancer offerings, and provides links to their documentation.

 [IBM Cloud® Load Balancer](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-getting-started) [Citrix NetScaler](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-getting-started) VPX/MPX (Standard) [Citrix NetScaler](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-getting-started) VPX/MPX (Platinum) 

 Public VIP ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) 
 Private VIP !
One of the benefits of the PER solution is that it makes it easier for a Power Systems Virtual Server user to access other IBM Cloud services, such as IBM Cloud DNS, NTP, and Cloud Object Storage. You can connect to these services without having to use proxies or virtual routers, as the PER solution includes a Network Address Translation (NAT) device that simplifies the access process.

The following network architecture diagram explains how the PER is integrated into the IBM Cloud environment:

Zoom

![Power Edge Router network architecture diagram](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/per-network-arch-diag.svg)

Figure 1. Power Edge Router network architecture diagram

The network traffic in a PER environment can flow in the following two ways:



* Accessing classic infrastructure through Transit Gateway.



* 1 - Traffic from ACI tenants is forwarded to the PER.
* 2 - PER forwards the traffic to classic infrastructure services that use Transit Gateway



* Accessing cloud services that can access each other's resources.



* 1 - Traffic from ACI tenants is forwarded to the PER.
* 3 - Traffic from PER is forwarded to the NAT services with Service Gateway routers for conversion of destination addresses to ADN and CSE networks.
* 4 - The converted traffic from NAT is forwarded to PER.
* 2 - Traffic from PER is now forwarded to IBM Cloud PPRs for final delivery.





The automation of ACI, PER, and NAT Services provisioning in IBM data centres is designed to simplify network integration and accelerate connection time for IBM Power Systems Virtual Server users in the IBM Cloud.



 Considerations when using PER 



* You cannot create a cloud connection or a VPN connection in a PER workspace.
* Currently, you can only choose DAL10 as the datacenter to create a PER workspace.
* 6 hosts (bare metal servers) each running Intel Xeon Gold 5218 with 192GB RAM
* 5TB of NFS storage





IBM Cloud for VMware Solutions provides different offerings to address different client needs and the [offering comparison chart](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-inst_comp_chart) details the differences.





 Architecture 

The following architecture represents the pattern this deployment journey is based on:

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/architecture.jpg)





 Next Steps 

The next step on the deployment journey is:



* [Understanding Network Flows](https://cloud.ibm.com/docs/vmware-classic-journey?topic=vmware-classic-journey-vmware-onboarding-network-flows)
Cross-connect details: IBM Cloud provides a Letter of Authorization (LOA) that a customer uses to order fiber Ethernet (single-mode fiber only, either 1Gig-LX or 10Gig-LR optics) that runs from a customer cage or provider cage to the IBM Cloud CFA termination point, which will be tied down to the cross-connect router (XCR) infrastructure. The media must be a 1310 nm wavelength optic.

Port speed options: Select 1 Gbps, 2 Gbps, 5 Gbps, or 10 Gbps.

Approximate latency: Latency is approximately 1.5 ms within the local area (data centers with the same three-letter prefix, such as DAL, AMS, MEL). See [Looking Glass](http://lg.softlayer.com/) for live PoP-to-PoP (P2P) location latency measurements.

IBM colocation services: None.

Redundancy: IBM Cloud does not provide redundancy as part of the product. To establish redundant connectivity, customer must acquire two connections on diverse cross connect routers (XCRs) and configure BGP on each Direct Link on Classic connection as they prefer. Examples include options such as: prefer Lowest MED, prefer highest local-preference, or prefer shorter AS paths.

Local and global routing options: The default routing option is Local routing. It provides access to data centers within the same market as the Direct Link PoP (denoted, for example, as DAL, AMS, or MEL). The Global routing option is required as an add-on to connect your IBM Cloud resources to other IBM Cloud resources in data centers outside the local market. It provides a way to share workloads between IBM Cloud resources (for example Dallas to Ashburn, or Dallas to Frankfurt).







 The Direct Link Dedicated Hosting on Classic solution 

The Direct Link Dedicated Hosting on Classic solution provides connectivity similar to Dedicated on Classic, but the connection point is next to an IBM Cloud data center, which improves latency for higher performance use cases. IBM Cloud offers various customizable colocation services with this solution, with simple pricing.

Common use cases: Best for working with non-standard compute technologies, for dedicated storage requirements, or for using existing IT investments.

Zoom

!
Exploring firewalls 

IBM Cloud® offers several firewalls to choose from. The following table compares the firewall solutions to help you choose the one that's right for you. To learn more about the individual offering, click its name in the table.

All instances of the FortiGate Security Appliance 1 Gbps are deprecated. Existing instances can be used until they are no longer supported. Use one of the following available firewall options to get our latest security capabilities on IBM Cloud. For migration information, see [Migrating FortiGate Security Appliance 1Gbps](https://cloud.ibm.com/docs/fortigate-1g?topic=fortigate-1g-migration-overview).



Table 1: A comparison of IBM's firewall offerings
This table shows all of IBM's firewall offerings, and provides links to their documentation.

 [Security Groups](https://cloud.ibm.com/docs/security-groups?topic=security-groups-getting-started) (VSI only) [IBM Cloud Juniper vSRX Standard](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-started) [Virtual Router Appliance](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-getting-started) [FortiGate Security Appliance 10 Gbps](https://cloud.ibm.com/docs/fortigate-10g?topic=fortigate-10g-getting-started) [FortiGate Security Appliance 1 Gbps](https://cloud.ibm.com/docs/fortigate-1g?topic=fortigate-1g-getting-started) [Hardware Firewall](https://cloud.ibm.com/docs/hardware-firewall-shared?topic=hardware-firewall-shared-getting-started) [Cloud Internet Services](https://cloud.ibm.com/docs/cis?topic=cis-getting-started) 

 Stateful Packet Inspection !
Deployment Journey Overview 

IBM Cloud for VMware Solutions makes it simpler for your organization to capitalize on the tremendous value of the cloud. The solution provides a path to migrate VMware workloads to the IBM Cloud while using existing tools, technologies and skills from your on-premises environment. The information contained within this document is meant to serve as a technical guide for starting with a new IBM Cloud towards a fully configured VMware instance.

Welcome to the Deployment Journey for VMware on IBM Cloud! Use the sidebar on the left to navigate between the journey points.



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/intro/journeymap-1.png)





 Assumptions 

The deployment journey will be assuming the following scenario. Please note that while your circumstance may not be exactly identical, you will still benefit from the overall journey steps and concepts covered in this guide.



* The goal is to deploy VMware workload on IBM Cloud.
* VMs will need to be able to access the Internet (source NAT) as well as certain VMs will need to be directly accessible from the Internet (destination NAT).
* Already familiar with Juniper networking technology on-premises, and wishes to do the same on IBM Cloud. So a vSRX Gateway device will be used.
* An initial non-production environment to be provisioned:



* A single VMware instance (cluster)
* vSphere 7.0 with NSX-T
* 6 hosts (bare metal servers) each running Intel Xeon Gold 5218 with 192GB RAM
* 5TB of NFS storage





IBM Cloud for VMware Solutions provides different offerings to address different client needs and the [offering comparison chart](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-inst_comp_chart) details the differences.





 Architecture
Release notes for Citrix DaaS for IBM Cloud 

Use these release notes to learn about the latest updates to Citrix DaaS for IBM Cloud® that are grouped by Date. Release notes are available for a minimum of three years.



  15 September 2022 

Rebranding
:   This is the initial release of the rebranded Citrix DaaS for IBM Cloud, formerly Citrix Virtual Apps and Desktops on IBM Cloud;reg;.
:   If you are using bookmarks to access the documentation, you should update them to the new product name path.





  25 August 2022 

Log Analysis
:   Added consolidated logging.





  7 July 2022 

Volume worker
:   Added Volume Worker, which is used for distributed identity disk creation with large machine catalogs.





  8 June 2022 

Dedicated host
:   Added dedicated host options for the control plane.





  25 May 2021 

Virtual private Cloud
:   Added support for IBM Cloud Secrets Manager on VPC.





  26 July 2021 

VMware
:   Added support for VMware ESXi Hosts.





  26 April 2021 

Active Directory
:   Added Active Directory topologies. Can now host AD in IBM Cloud, on-premises, or hybrid.





  25 March 2021 

Introducing Citrix DaaS
:   Citrix DaaS for IBM Cloud is a streamlined process for experienced administrators and service providers to create a dedicated Citrix Virtual Apps and Desktops (Citrix DaaS) service environment at one of our global data centers. This solution provides flexibility, control, and saves you time in building out your virtual apps and desktops solution. If you are invested in virtual desktop infrastructure (VDI), you understand the complexity of hosting and managing VDI entirely on-premises. The offering is purposefully built for a better VDI experience in the cloud.
This layer requests resources and orchestrates the lower layers from a user interface or application programming interface (API). VMware Aria Automation enables cloud automation on the IBM Cloud. For more information, see [IBM Cloud for VMware Solutions VMware Aria Automation 7.2 Solution Architecture](https://www.ibm.com/cloud/architecture/files/IBM_Cloud_for_VMware_Solutions_VRA_Architecture_v1.pdf).

For more information about how this architecture can be extended with Chef integration, see [IBM Cloud for VMware Solutions VMware Aria Automation 7.2 Chef Integration](https://www.ibm.com/cloud/architecture/files/IBM_Cloud_for_VMware_Solutions_VRA_Chef_Integration_Architecture.pdf).
* Service Management Layer - This layer focuses on the full lifecycle of the IT environment and is typically implemented at the enterprise level combining inputs from all the silos of IT Operations and technologies. This layer has traditionally been, architected on IT Service Management (ITSM) frameworks such as the IT Infrastructure Library (ITIL) and ISO/IEC 20000, which are a framework of best practices for delivering IT services through the processes and stages of the IT service lifecycle. At a product level, ITSM is typified by a centralized workflow management system for handling incidents, service requests, problems, changes, and knowledge connected to a configuration management database.
* UI
* Terraform







 Automating SAP S/4HANA on 3-tier IBM Cloud® VPC with Terraform and Ansible 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud VPC infrastructure resources so that you can rapidly build complex, cloud environments. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and other Intel technologies.

You can use Terraform scripts to create a single-tier VPC and create the SAP and SAP HANA in a distributed architecture on the bastion server that you create. Creating the bastion server is a prerequisite for all IBM SAP VPC automated solutions. The automation scripts use the VPC information that you provide and then call the Ansible playbook to create the SAP architecture on the specified VPC.

You have three deployment methods to choose from:



* Terraform scrits run from the CLI on your bastion server
* Catalog Tile user interface accessed from the IBM Cloud Catalog
* IBM Cloud® Schematics user interface accessed from the menu on your cloud dashboard.





 SAP Solution implemented 

SAP S/4HANA is an ERP system from SAP's ERP software product line. The software is based on the innovative SAP HANA database technology and was launched as the fourth product generation in 2015. Users can choose between the SAP S/4HANA Cloud and On-Premise solution.

An ERP system is used for demand-oriented business resource planning. It is used to control processes and to link departments and functional areas in a meaningful way. Individual modules include applications for accounting, sales, production, and marketing. More complex tasks in customer or supply chain management can also be done by ERP software. As the successor to the core product SAP ECC, SAP S/4HANA was presented as the intelligent ERP system of the new generation. Thanks to modern technologies, the Software as Service (SaaS) version is designed to help companies standardize processes and make the leap to digitalization.

While previous SAP ERP solutions support the most common databases, SAP S/4HANA uses exclusively the SAP HANA in-memory database developed by SAP. This in-memory database offers users the greatest technical benefit and they benefit from increased performance.