vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Management Network: One network interface is dedicated to the Management network. This secure out-of-band network is accessible via an IBM managed VPN. It is used by IBM Cloud staff for maintenance and administration purposes such as firmware updates, OS reloads, power-cycle or other IPMI functions like keyboard, video, mouse control (KVM over IP).



For the MAS Dedicated Service each client is provisioned with their own application instance and dedicated namespace(s). The IBM MAS-Dedicated team will provision and configure all necessary underlying infrastructure and components.

IBM Cloud Data Centers are SOC compliant and have full hardware redundancy implemented for all servers. All data centers have an N1 redundant power and cooling infrastructure, including backup power generators. All servers have redundant power supplies, NICs and use SAN based RAID storage.

The following diagrams show a high level overview of the architecture for each individual client instance.

Zoom

![MAS-Dedicated Architecture](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Architecture.png)

Figure 1. MAS-Dedicated Architecture on IBM CLoud

Zoom

![MAS-Dedicated Architecture AWS](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Architecture-AWS-Single-Tenant.png)

Figure 1. MAS-Dedicated Architecture on AWS





 MAS-Dedicated Architecture Highlights 



* MAS MS customers are required to have two (2) environments provisioned by default: (1) PROD and (1) NON-PROD
* All clients will be provisioned in their own application instance using dedicated namespace(s)
* IT Administration for the PROD and NON-PROD environments is solely managed by IBM's MAS-Dedicated operations team
* Clients can access PROD and NON-PROD systems via browser based URL
"direct":{
"mex01":"s3.direct.mex01.cloud-object-storage.appdomain.cloud"
}
},
"sjc04":{
"public":{
"sjc04":"s3.sjc04.cloud-object-storage.appdomain.cloud"
},
"private":{
"sjc04":"s3.private.sjc04.cloud-object-storage.appdomain.cloud"
},
"direct":{
"sjc04":"s3.direct.sjc04.cloud-object-storage.appdomain.cloud"
}
},
"mil01":{
"public":{
"mil01":"s3.mil01.cloud-object-storage.appdomain.cloud"
},
"private":{
"mil01":"s3.private.mil01.cloud-object-storage.appdomain.cloud"
},
"direct":{
"mil01":"s3.direct.mil01.cloud-object-storage.appdomain.cloud"
}
},
"par01":{
"public":{
"par01":"s3.par01.cloud-object-storage.appdomain.cloud"
},
"private":{
"par01":"s3.private.par01.cloud-object-storage.appdomain.cloud"
},
"direct":{
"par01":"s3.direct.par01.cloud-object-storage.appdomain.cloud"
}
},
"sng01":{
"public":{
"sng01":"s3.sng01.cloud-object-storage.appdomain.cloud"
},
"private":{
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/checkmark-icon.svg) 
 Development or Test environment ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/checkmark-icon.svg) 
 Production environment ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/checkmark-icon.svg) 



** The default configuration for a Standard Kubernetes cluster on IBM Cloud is a 4 CPU x 16 GB RAM cluster that includes three zones with three worker nodes each. You can scale up or down, by selecting a smaller or larger configuration, according to your needs.

The IBM Blockchain Platform deployer attempts to spread peers, ordering nodes, and CA replica sets across different worker nodes but cannot guarantee that it will happen due to resource limitations. You can also use the IBM Blockchain Platform APIs or the blockchain console to deploy peers or ordering nodes to specific zones in order to ensure that they are resilient to a zone failure.
(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. For more information about provisioning on Virtual Private Cloud infrastructure, see [Provisioning Citrix DaaS for IBM Cloud® on Virtual Private Cloud](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-provisioning-cvad-vpc).

Zoom

![Architecture diagram.](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/citrix-daas/images/2vpc-deployment.png)

Figure 2. Citrix DaaS for IBM Cloud VPC architecture diagram



 Dedicated Host Control Plane 

The standard dedicated host option for Citrix DaaS on VPC provisions the control plane components (active directory, cloud connectors, and custom image VSI) onto public hosts and the VDAs to the dedicated hosts.

Zoom

![Dedicated Host standard deployment diagram.](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/citrix-daas/images/dedicated-deployment-std.png)

Figure 3. Dedicated Host standard deployment

With the shared dedicated option, the control plane is also provisioned to the dedicated hosts.

Zoom

![Dedicated Host shared deployment diagram.]
* [Alibaba Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-alibaba)
* [Amazon Web Services (AWS)](https://cloud.ibm.com/docs/satellite?topic=satellite-aws)
* [Google Cloud Platform (GCP)](https://cloud.ibm.com/docs/satellite?topic=satellite-gcp)
* [Microsoft Azure](https://cloud.ibm.com/docs/satellite?topic=satellite-azure)
* [IBM Cloud for tests](https://cloud.ibm.com/docs/satellite?topic=satellite-ibm)
* [Setting up the Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane)
* [Sizing your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizing)



* Managing hosts and locations



* [Attaching hosts to your location](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts)
* [Assigning hosts to worker pools](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hosts)
* [Setting up a Satellite location with remote workers](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-multi-infra)
* [Updating Satellite location control plane hosts ](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-location)
* [Updating hosts that are assigned as worker nodes ](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workers)
* [Copying a location](https://cloud.ibm.com/docs/satellite?topic=satellite-location-copy)
* [Configuring an HTTP proxy for your Satellite hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-config-http-proxy)
"ams03":"s3.direct.ams03.cloud-object-storage.appdomain.cloud"
}
},
"che01":{
"public":{
"che01":"s3.che01.cloud-object-storage.appdomain.cloud"
},
"private":{
"che01":"s3.private.che01.cloud-object-storage.appdomain.cloud"
},
"direct":{
"che01":"s3.direct.che01.cloud-object-storage.appdomain.cloud"
}
},
"mon01":{
"public":{
"mon01":"s3.mon01.cloud-object-storage.appdomain.cloud"
},
"private":{
"mon01":"s3.private.mon01.cloud-object-storage.appdomain.cloud"
},
"direct":{
"mon01":"s3.direct.mon01.cloud-object-storage.appdomain.cloud"
}
},
"mex01":{
"public":{
"mex01":"s3.mex01.cloud-object-storage.appdomain.cloud"
},
"private":{
"mex01":"s3.private.mex01.cloud-object-storage.appdomain.cloud"
},
"direct":{
"mex01":"s3.direct.mex01.cloud-object-storage.appdomain.cloud"
}
},
"sjc04":{
"public":{
"sjc04":"s3.sjc04.cloud-object-storage.appdomain.cloud"
},
"private":{
"name": "remote_cidr_blocks",
"secure": false,
"value": ""169.252.0.0/18"]",
"type": "",
"description": ""
},
{
"name": "ibm_customer_number",
"secure": false,
"value": "12345",
"type": "",
"description": ""
},
{
"name": "compute_cluster_gui_username",
"secure": false,
"value": "admin",
"type": "",
"description": ""
},
{
"name": "compute_cluster_gui_password",
"secure": false,
"value": "P@ssw0rd",
"type": "",
"description": ""
},
{
"name": "storage_cluster_gui_username",
"secure": false,
"value": "admin",
"type": "",
"description": ""
},
{
"name": "storage_cluster_gui_password",
"secure": false,
"value": "P@ssw0rd",
"type": "",
"description": ""
},
{
"name": "storage_cluster_key_pair",
"secure": false,
"value": "scale-hpcc-key",
"type": "",
"description": ""
},
{
"name": "compute_cluster_key_pair",
"secure": false,
"value": "scale-hpcc-key",
"type": "",
"description": ""
}
],
"has_githubtoken": true
Deployment model 

IBM Cloud® Data Engine's Deployment Model corresponds to a public service with public endpoints. It is the publicly shared multi-tenant deployment model for IBM Services, and as such, this model is not dedicated. The service is accessed through public endpoints. Both, the control and data plane of the service, are shared across tenants.



 Tenant isolation models  Tenant domain isolation  Endpoint isolation  Compute isolation      Storage isolation                                        Network isolation       

 Shared data plane        Service account          Public endpoint     Shared physical hosts  Shared physical storage devices, shared access endpoint  Service virtual network 



Zoom

![Deployment model.](https://cloud.ibm.com/docs-content/v1/content/9fbd9f26e0f1e4aaa38411d9a81ad7bc6897624d/sql-query/images/deployment_model_a.svg)

Figure 1. Deployment model
* Ordering your server as private-only
* Using the console or the OS after the server is provisioned



Alternatively, the server can be attached to a public VLAN and private VLAN that is associated with a Gateway Appliance. In this arrangement, the server has a DMZ with a public network facing VLAN and private network facing VLAN.





 Networking subnets 

In Classic Infrastructure, the VLAN has different types of Subnets. The following information is a summary of [Getting started with subnet and IPs on Classic Infrastructure](https://cloud.ibm.com/docs/subnets?topic=subnets-getting-started) and [About subnets and IP on Classic Infrastructure](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ips).

Different types of subnets in Classic Infrastructure:



1. Public and Private Primary Subnet



* Auto-assigned when provisioning resources (for example, Bare Metal) into a Public and Private VLAN
* [Primary subnets have limitations](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsprimary-subnets)



2. Public and Private Secondary Portable Subnet



* Appends new subnet to Public and Private VLAN
* Provides IP addresses for assignment to any resource within a VLAN, can assign Portable IP to multiple resources as a Floating IP
* Enables connection to multiple resources from a single Portable IP



3. Public Secondary Static Subnet



* Appends new subnet to Public VLAN
* Provides IP addresses for assignment to one resource within a VLAN (that uses the existing Primary IP or Portable IP of the resource as the "routing endpoint")
* Enables connection to one resource by using any of the Static IPs plus the original Primary IP or Portable IP.



4. Public Secondary Global Subnet also known as Global IP addresses



* Appends single Internet-accessible IP from IBM Cloud private backbone to any VLAN worldwide
Compute hosts that are in the same data center or with the same cloud provider are often connected to the same power, network, and storage server. If one of these components experiences an outage, all compute hosts that are connected to the same component might be affected by the outage. To ensure that your compute hosts continue to run, plan to isolate your compute hosts as much as possible and not to share the same power, network, or storage devices. 
 Spread hosts across physical locations. To account for a data center or cloud provider outage, you can spread your compute hosts across different physical locations. Keep in mind that compute hosts can only be in different physical locations if they still meet the networking speed and latency requirements that are defined in the [minimum host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). 





 Example for a high availability setup in an on-premises data center 

The following image shows a high availability setup of your control plane worker nodes within an on-premises data center. All compute hosts are on a separate rack to ensure that power, network, and storage devices are not shared. Because all compute hosts are located in the same data center, the requirements for networking speed and latency between the hosts are met.

Zoom

![High availability setup for an on-premises data center.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/sat_control_plane_ha_onprem.svg)

Figure 3. High availability setup for an on-premises data center.





 Example for a high availability setup in a public cloud provider 

The following image shows a highly available setup for compute hosts that are in a public cloud provider. All virtual machines are hosted on a separate physical machine that is dedicated to you only. To ensure further isolation and availability, all compute hosts are spread across multiple availability zones within the same metro. Because the availability zones belong to the same metro, the requirements for networking speed and latency between the hosts are met.

Zoom

!
System context 

Although IBM Cloud® for VMware® Regulated Workloads is a self-contained design, some external dependencies exist. IBM Cloud for VMware Regulated Workloads is designed without the use of IBM Cloud shared offerings such as VSIs and shared storage offerings.

Zoom

![IBM Cloud for VMware Regulated Workloads context](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vrw-context.svg)

Figure 1. IBM Cloud for VMware Regulated Workloads context

Connections between the on-premises environment, CSP (Cloud Service Provider), CHP (Cloud Hosting Provider), and IBM Cloud traverse the internet and are required to use IBM Cloud Direct Link, IPsec, or other secure protocol.



* IBM Cloud Account administrator - manages the SaaS provider's IBM Cloud account through the IBM Cloud portal. The IBM Cloud administrator is the only administrator who can add or remove hosts or services from the cloud account.
* IBM Cloud for VMware Regulated Workloads administrator - manages the virtualized environment for the IBM Cloud for VMware Regulated Workloads instances. The IBM Cloud for VMware Regulated Workloads administrator manages all compute, storage, and network resources that are used by the client applications. For simplicity, the administrator who is illustrated is a collection of multiple administration roles. Separation of duties might require dedicated virtualization, network, and security administrator roles.
* User (SaaS consumer) - uses the resources available in the IBM Cloud for VMware Regulated Workloads instances to run their applications. The SaaS consumer has no access to the management plane.
* IBM Cloud data centers - supply the needed racks, cooling, and power to support the vSphere hosts used to build out the regions of the IBM Cloud for VMware Regulated Workloads.
* IBM Cloud network services - enable the connection of the IBM Cloud for VMware Regulated Workloads to the internet (disabled by default).
Depending on the business requirements and risk acceptance, the primary decision for any Cloud IaaS running SAP workloads which Cloud Tenancy model to use:



* Single-Tenant infrastructure, dedicated compute resources that are accessed with a private logical network within the Cloud provider network backbone that uses:



* Bare Metal
* Virtual Servers on Dedicated Hosts
* VMware SDDC



* Multi-Tenant infrastructure, shared compute resources that are accessed with a private logical network within the Cloud provider network backbone that uses Virtual Servers



After you decide on the Cloud Tenancy model that meets your business and IT risk needs, the focus is then on sizing and throughput requirements:



* Output of your [SAP Sizing activities](https://cloud.ibm.com/docs/sap?topic=sap-sizingsizing-methodology)
* Benchmark metric "SAPS", which demonstrates the total transactional throughput of the Infrastructure



More information that compares different Infrastructure types is in [Comparing the different SAP-certified IaaS offerings](https://cloud.ibm.com/docs/sap?topic=sap-overviewiaas-offerings-compare-summary) with more detail under [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings/docs/sap?topic=sap-iaas-offerings). All SAPS benchmarks are listed for each Profile under each Infrastructure type that is offered in the IBM Cloud® for SAP portfolio.





 SAP HANA considerations 

The SAP S/4HANA business application is affected by multiple [SAP HANA Database Server design considerations](https://cloud.ibm.com/docs/sap?topic=sap-hana-design-considerations).

SAP S/4HANA is considered a "Mixed Workload", as the business application primarily does Transactional processing (OLTP), but SAP S/4HANA also does Analytical processing (OLAP) through SAP S/4HANA Embedded Analytics.

During SAP Sizing, decision making, and Infrastructure selection, SAP S/4HANA is often considered as OLTP only. This representation is not a fully accurate view of the business application, but serves as the closest representation for use with SAP Benchmarks information.
Satellite Storage [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesincident-and-ops) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitieschange-management) [Workload provider](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesiam-responsibilities) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiessecurity-compliance) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesdisaster-recovery) 
 Satellite-enabled services [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesincident-and-ops) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitieschange-management) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesiam-responsibilities) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiessecurity-compliance) [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesdisaster-recovery) 
 Operating System Workload provider [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitieschange-management) Workload provider [Shared](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiessecurity-compliance) Workload provider 
 Virtual and bare metal servers On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Virtual storage On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider
WDC07 IBM Power VS SL-WDC07-IBMPOWERLAASLITE-1-1 <br>SL-WDC07-IBMPOWERLAASLITE-1-2 SL-WDC07-IBMPOWERLAASLITE-2-1 <br>SL-WDC07-IBMPOWERLAASLITE-2-2 
 DAL10 IBM Power VS SL-DAL10-IBMPOWERLAASLITE-1-1 <br>SL-DAL10-IBMPOWERLAASLITE-1-2 SL-DAL10-IBMPOWERLAASLITE-2-1 <br>SL-DAL10-IBMPOWERLAASLITE-2-2 
 DAL12 IBM Power VS IBM POWER VS-CLOUD EXCHANGE SL-DAL12-1-1 <br>IBM POWER VS-CLOUD EXCHANGE SL-DAL12-1-2 <br>xPowerVS-DAL12-10G-NOGRE-1-1 <br><br>[9] IBM POWER VS-CLOUD EXCHANGE SL-DAL12-2-1 <br>IBM POWER VS-CLOUD EXCHANGE SL-DAL12-2-2 <br>xPowerVS-DAL12-10G-NOGRE-1-2 <br><br>[10] 
 DAL13 IBM Power VS SOFTLAYER-IBMPOWERIAASLITE-1-1 <br>SOFTLAYER-IBMPOWERIAASLITE-1-2 <br>xPowerVS-DAL13-10G-NOGRE-1-1 <br><br>[11] SOFTLAYER-IBMPOWERIAASLITE-2-1 <br>SOFTLAYER-IBMPOWERIAASLITE-2-2 <br>xPowerVS-DAL13-10G-NOGRE-1-2 <br><br>[12]
"us-east":"s3.private.us-east.cloud-object-storage.appdomain.cloud"
},
"direct":{
"us-east":"s3.direct.us-east.cloud-object-storage.appdomain.cloud"
}
},
"eu-gb":{
"public":{
"eu-gb":"s3.eu-gb.cloud-object-storage.appdomain.cloud"
},
"private":{
"eu-gb":"s3.private.eu-gb.cloud-object-storage.appdomain.cloud"
},
"direct":{
"eu-gb":"s3.direct.eu-gb.cloud-object-storage.appdomain.cloud"
}
},
"eu-de":{
"public":{
"eu-de":"s3.eu-de.cloud-object-storage.appdomain.cloud"
},
"private":{
"eu-de":"s3.private.eu-de.cloud-object-storage.appdomain.cloud"
},
"direct":{
"eu-de":"s3.direct.eu-de.cloud-object-storage.appdomain.cloud"
}
},
"jp-tok":{
"public":{
"jp-tok":"s3.jp-tok.cloud-object-storage.appdomain.cloud"
},
"private":{
"jp-tok":"s3.private.jp-tok.cloud-object-storage.appdomain.cloud"
},
"direct":{
"jp-tok":"s3.direct.jp-tok.cloud-object-storage.appdomain.cloud"
}
},
"jp-osa":{
"public":{
"Dallas":"s3.dal.us.cloud-object-storage.appdomain.cloud",
"Washington":"s3.wdc.us.cloud-object-storage.appdomain.cloud",
"San Jose":"s3.sjc.us.cloud-object-storage.appdomain.cloud"
},
"private":{
"us-geo":"s3.private.us.cloud-object-storage.appdomain.cloud",
"Dallas":"s3.private.dal.us.cloud-object-storage.appdomain.cloud",
"Washington":"s3.private.wdc.us.cloud-object-storage.appdomain.cloud",
"San Jose":"s3.private.sjc.us.cloud-object-storage.appdomain.cloud"
},
"direct":{
"us-geo":"s3.direct.us.cloud-object-storage.appdomain.cloud",
"Dallas":"s3.direct.dal.us.cloud-object-storage.appdomain.cloud",
"Washington":"s3.direct.wdc.us.cloud-object-storage.appdomain.cloud",
"San Jose":"s3.direct.sjc.us.cloud-object-storage.appdomain.cloud"
}
},
"eu":{
"public":{
"eu-geo":"s3.eu.cloud-object-storage.appdomain.cloud",
"Amsterdam":"s3.ams.eu.cloud-object-storage.appdomain.cloud",
"Frankfurt":"s3.fra.eu.cloud-object-storage.appdomain.cloud",
"Milan":"s3.mil.eu.cloud-object-storage.appdomain.cloud"
},
"private":{