vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information about IBM Cloud availability zones, data centers, and Points of Presence (PoPs), see the [global regions, availability zones, and data centers map](https://www.ibm.com/cloud/data-centers/datacentermap).





 Compute Resources 

Two types of compute resource can be deployed in IBM Cloud VPC Infrastructure environment:



* Intel Virtual Server Instances (VSIs)
* Intel Bare Metal Servers



These compute resources are offered in different profiles that define CPU and RAM combinations.

For more information, see [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings).





 Networking 

The IBM Cloud VPC infrastructure network, is robust, secure, and flexible; powered by the latest in networking hardware, with the best networking capabilities. It allows definable isolation and creation of a network within the cloud.



Table 1. Networking component layers overview

 IBM Cloud VPC Infrastructure network 

 Global 
 Resource Group 
 Region 
 VPC 
 Availability zone (with address prefix) 
 Subnet 



Every IBM Cloud® Virtual Private Cloud is created for a region, and spans multiple availability zones.

When you deploy a VPC in an availability zone, an [address prefix](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-addressing-plan-design) is used for that specified zone.

Each VPC Zone (and the address prefix) contains one or more subnets. You can define each subnet manually by choosing the IP range and the subnet mask, or you can choose the number of IP addresses needed. A newly created compute resource is deployed into this subnet and can also be attached to further subnets.



 Networking connectivity 

[IBM Cloud® Virtual Private Cloud network overview](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpc) demonstrates the connectivity for the environment. Issues with network connectivity can cause delays for your project if you do not plan properly, regardless of how you plan to use your system.
It is hosted on dedicated hardware, such as a bare metal server, and either onsite at the company's office (or across offices) or by a cloud provider. A private cloud can be accessed from anywhere.

A hybrid cloud includes resources that combine the aspects of both public and private clouds. It is hosted both onsite at a company's office (or across offices) and by a cloud provider. A hybrid cloud can be accessed from anywhere.





 Next steps 

To continue, see [Planning your infrastructure](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-planning-2).
Expansion of an environment can be accomplished by buying more IBM Cloud Dedicated IBM Cloudant 1.6 TB Capacity parts, which can be used to expand the IBM Cloudant cluster in multiples of three database nodes. Customers can also choose to have multiple separate IBM Cloudant environments rather than expanding a single environment.





 Locations and tenancy in a Dedicated environment 

The IBM Cloudant Dedicated environment within an IBM Cloud Dedicated environment is on hardware that is designated for sole use by the IBM Cloud Dedicated customer. The customer can provision one or more instances of IBM Cloudant on the specific environment, and each instance of IBM Cloudant shares the underlying hardware resources that make up the IBM Cloudant environment.





 Security, encryption, and compliance 

All plans are provided on servers with [at rest](https://en.wikipedia.org/wiki/Data_at_rest) disk encryption. Access is over the public network connection and encrypted by using HTTPS. For more detail, see [Security](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-securitysecurity). IP allowlisting is available upon request to IBM Cloudant Support and applies to the whole IBM Cloudant environment, and not at the instance level.

The plan also offers [Compliance Certification](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-compliancecompliance).

[HIPAA](https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act) compliance is available upon request, so request HIPAA compliance during the purchase process with an IBM sales representative.





 High availability, disaster recovery, and backup 

To provide high availability (HA) and disaster recovery (DR) within a data center, all data is stored in triplicate across three separate physical servers in a cluster. When available, you can provision accounts in multiple locations, then use continuous data replication to provide HA/DR across data centers. IBM Cloudant data isn't automatically backed up, but supported tools are provided to handle backups.
IBM Power Systems Infrastructure environment introduction 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

An Infrastructure-as-a-Service (IaaS) environment consists of many components - primarily compute, storage, and network from a specified region (such as the US) and a designated site location (also referred to as zone, which is a data center site).



 Deployment and management 

IBM Power Systems Virtual Server is an IBM Power Systems enterprise Infrastructure-as-a-service (IaaS) offering.

These IBM Power Systems Virtual Servers are physically located with low-latency connectivity to the IBM Cloud Classic Infrastructure or VPC Infrastructure. In the data centers, the Power Systems Virtual Servers are separated from the rest of the IBM Cloud servers with separate networks and direct-attached storage. This infrastructure design enables Power Systems Virtual Servers to maintain key enterprise software certification and support as its architecture is identical to certified on-premises infrastructure. The internal networks are fenced but have connectivity options to the rest of environments and services on IBM Cloud.

IBM Power Systems Infrastructure offerings (such as IBM Power Systems Virtual Server) are deployed using the [IBM Power Infrastructure console available through IBM Cloud](https://cloud.ibm.com/catalog/services/power-systems-virtual-server).

Alternatively, you can create and manage deployments with any of the following methods:



* IBM Power Infrastructure plug-in for IBM Cloud CLI
* IBM Power Infrastructure API calls with an IBM Cloud API key
* [Terraform Provider for IBM Cloud](https://cloud.ibm.com/docs/terraform) with an IBM Cloud API key



For more information, see [Managing IBM Power Systems Virtual Servers (IAM)](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-resources-and-users).





 Locations - Data centers 

With data centers across North and South America, Europe, Asia, and Australia, you can provision IBM Power Infrastructure resources where (and when) you need them.

You can choose from multiple data centers globally.

Each data center with IBM Power Infrastructure uses a separate enterprise-grade network which is connected using IBM Cloud Direct Link to the IBM Cloud global private network, making data transfers faster and more efficient anywhere in the world.
Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud VPC infrastructure resources so that you can rapidly build complex, cloud environments. The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. For more information about Terraform on IBM Cloud, see Terraform on IBM Cloud getting started tutorial.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 30 minutes
* 2021-06-30



[Creating a resilient three-tier highly available infrastructure VPC with Terraform](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-create-three-tier-resilient-vpc)Creating a resilient three-tier highly available infrastructure VPC with Terraform

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud VPC infrastructure resources so that you can rapidly build complex, cloud environments. The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. For more information about Terraform on IBM Cloud, see Terraform on IBM Cloud getting started tutorial.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 30 minutes
* 2021-06-30



[Creating a three-tier highly available architecture on an IBM Cloud VPC](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-create-three-tier-architecture)Creating a three-tier highly available architecture on an IBM Cloud VPC

This tutorial describes the three-tiered architecture of an application that is rehosted on IBM cloud. The tutorial outlines the steps to implement a Highly Available solution in the IBM Cloud VPC infrastructure that spans multiple availability zones in one region. The strategies can differ and vary depending upon your application (web, app, and DB) and the redundancy necessary at each level. The tutorial provides a few guidelines for setting up a three tier OLTP application. Wherever possible, guidelines are provided on infrastructure, security, and operations.
[terraform/per-environment](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform/per-environment) Terraform files specific to a given environment 
 [terraform/roles](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform/roles) Terraform files to configure user policies 





 Heavy lifting with Terraform 

The Development, Testing and Production environments pretty much look the same.

Zoom

![Diagram showing the deployment environment](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution26-plan-create-update-deployments/one-environment.svg)

One environment deployed into a resource group

They all share the same type of resources, but differ by the allocated capacity and the access rights. For this tutorial, only a VSI will be deployed in each environment, no cluster will be deployed. The Terraform files reflect this with a global configuration to provision common resources and a per-environment configuration, using Terraform workspaces, to provision the environment-specific resources:

Zoom

![Using Terraform workspaces](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution26-plan-create-update-deployments/terraform-workspaces.png)

Using Terraform workspaces





 Global Configuration 

Under the [terraform/global](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform/global) directory, you find the Terraform scripts to provision common resources. It could be an instance of IBM Cloud Activity Tracker Event Routing (this tutorial won't create such instance).
Checks can be automated. Results are directly compared against defined controls, can be exported and integrated into a customized dashboard. Read how to [get started with Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started) for the first steps.





 Isolate runtime environments, networks traffic and data 

One of the fundamental principles of Cloud Computing is the sharing of resources. This could be from the sharing of a machine (i.e., the sharing of applications by many users who are running on the same computer) to just sharing the data center and parts of the infrastructure. In the following, you learn how you can isolate runtime environments, network traffic and stored data to increase application security.



 Use dedicated resources and virtual private clouds 

To isolate application runtime environments and related services, you can provision dedicated machines and enterprise-level service plans. Typically, entry-level, lower-priced plans run on shared infrastructure in a multi-tenant mode. The more advanced plans utilize dedicated environments and provide greater physical separation of data. Here are some considerations for some compute options.

Look into running virtual servers or Kubernetes Service on [IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/vpc-ext) to benefit from isolation of compute and network resources.

Check out the tutorials on [how to deploy isolated workloads across multiple locations and regions](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-multi-region) and [how to securely access remote instances using a bastion host](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-secure-management-bastion-server) to get started with IBM Cloud® Virtual Private Cloud.

Evaluate the use of [Hyper Protect Virtual Servers](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-overview) to run workloads in secure service containers.

When working with database systems, consider using service plans with dedicated resources or services with enhanced security.
* [IBM Cloud Classic Infrastructure environment](https://cloud.ibm.com/docs/sap?topic=sap-classic-env-introduction). The original environment and network, formerly known as the Softlayer network.
* [IBM Cloud VPC Infrastructure environment](https://cloud.ibm.com/docs/sap?topic=sap-vpc-env-introduction). The latest environment and network, with the newest technologies and networking capabilities.
* [IBM Power Systems Infrastructure environment](https://cloud.ibm.com/docs/sap?topic=sap-power-env-introduction). The environment maintained by IBM Power Systems built of IBM Power enterprise components, which has links to either Classic Infrastructure and VPC Infrastructure.



Our documents provide detailed considerations and information for building your SAP environments at each layer for all offerings. However, if you are interested in quickly finding the information related specifically to one of the IaaS offerings, then you may consider using the Fast Path Site Maps for [Intel Bare Metal](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-intel-bm), [Intel Virtual Servers](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-intel-vs-gen2), [IBM Power Virtual Servers](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-power-vs) and [VMware SDDC](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-vmware-sddc).



 Certifications summary 



* SAP S/4HANA (AnyPremise edition), which uses SAP HANA scale-up
* SAP BW/4HANA, which uses SAP HANA scale-up
* SAP BW/4HANA, which uses SAP HANA scale-out
Deployment of specific workload types Almost anything that can be containerized, web apps, event-driven serverless functions, micro-services, batch jobs [Types of typical workloads being moved to IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-strategy) <br>[Use cases](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_intro) <br>Can integrate IBM Cloud Code Engine with IBM Cloud Kubernetes Service. [Types of typical workloads being moved to Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-strategy) <br>[Use cases](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_intro) 
 "Push your code" from local disk developer experience Yes Yes Yes 
 Complete cluster management experience through the IBM Cloud Kubernetes Service automation tools (API, CLI, console) No - IBM Cloud Code Engine is a multi-tenant service based on Kubernetes, and therefore only namespace-scoped operations are allowed (not entire cluster management) Yes Yes 
 Worldwide availability in single and multi-zones Multi-zone Regions Yes Yes 
 Access to all IBM Cloud services Yes Yes Yes 
 Can additional persistent storage be attached to application containers? No Yes Yes 
 Isolation through IBM Cloud Virtual Private Cloud (VPC) Yes Yes Yes 
 Free level of service [Yes, free tier available, that re-sets every month](https://www.ibm.com/cloud/code-engine/pricing) [Yes, free limited cluster](https://cloud.ibm.com/docs/containers?topic=containers-cs_ov) No 
 Latest community Kubernetes distribution Yes. IBM Cloud Code Engine is built on IBM Cloud Kubernetes Service. Yes Partially. Support is as close as possible to the latest major version.For example, right now OpenShift 4.10 is on Kubernetes 1.23, but we offer OpenShift 4.9 right now, which is on Kubernetes 1.22.
Introduction to the architecture framework 

Cloud architecture can be thought of as a multi-dimensional matrix that considers application workloads, cloud deployment models, service management, and design aspects to provide a basis for cloud computing architectural designs that align with business drivers and requirements.

In addition, when architecting cloud solutions, consideration needs to be given to items such as:



*  Resiliency and service availability
*  Data privacy
*  Performance and scale
*  Distributed storage
*  Management
*  Interoperability and integration



Evaluating options and designing a suitable architecture for comprehensive enterprise cloud solutions can be a daunting task. The use of an architecture framework can assist in enhancing the ability to design optimum cloud computing solutions.



  What is the architecture framework? 

The architecture framework is a structured, technology agnostic, enterprise architecture approach, inspired by the technology layer of the [TOGAF](https://www.opengroup.org/togaf) model. It can be used as a guide to provide a consistent approach to architect hybrid, multi-cloud end-to-end solutions based on your requirements.

The architecture framework defines a technology- and cloud-provider-agnostic taxonomy of "aspects" and "domains" that can be used to develop reference solutions or patterns for specific platforms or applications on any target cloud deployment, be it private cloud, public cloud, hybrid cloud, or multi-cloud.

Aspect
:   Aspects are architectural areas that need to be considered for any enterprise solution. Some aspects are associated with nonfunctional requirements like security and resiliency. Each aspect can have one or more domains.

Domain
:   Domains are common capabilities or similar technology functions within an aspect. For example, Enterprise Connectivity and Load Balancers are considered networking technologies.

Component
:   Components are product offerings that can be used to satisfy the solution requirements. The component options depend on the target cloud deployment and cloud provider. For example, Direct Link 2.0 and VPC VPN Gateways are Enterprise Connectivity components on the IBM Cloud.
You might not even have a data center, but rather an edge location that meets the minimum hardware requirements, such as three racks at one of your company's local sites.

Supported bare metal servers
: You can use a supported bare metal server as a host attached to your Satellite location, including IBM Cloud® Bare Metal Servers for Classic. For more information, see [Bare Metal Server requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-bare-metalsetup-bare-metal).

Non-IBM cloud provider
: You can use a cloud provider of your choice, such as [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), or [Alibaba Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-alibaba).

IBM Cloud
: You can use [IBM Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-ibm) for testing purposes. While you can use other IBM Cloud virtual servers, such as Virtual Servers for VPC for test environments, the only supported IBM Cloud infrastructure to use in Satellite for production environments is IBM Cloud® Bare Metal Servers for Classic that is running Red Hat CoreOS.





 Plan for a multizone location 

In your infrastructure provider, identify a multizone location that meets the latency requirements.

Multizone
: Your location must have at least three zones that are physically separate so that you can spread out hosts evenly across the zones to increase [high availability](https://cloud.ibm.com/docs/satellite?topic=satellite-ha). For example, your cloud provider might have three different zones within the same region, or you might use three racks with three separate networking and power supply systems in an on-prem environment.

Latency between IBM Cloud and the location
You will learn how to implement those common sharing scenarios, either manually or fully automated with Terraform.



 Objectives 



* Understand the benefits of sharing resources across accounts
* Learn about different techniques to share resources across accounts







 Resource sharing overview 

It is not unusual to find multiple applications access and use the same resource or parts of it. One example is when applications and compute environments have to live on the same corporate network. Another scenario is that security logs are collected in central storage. In a microservice architecture, it requires us to configure services to access and use external resources. In turn, the shared resources must authorize access, and the network between them is configured to support such collaboration, but not more.

Some typical use cases of resource sharing are:



* Central management of security-related infrastructure. Monitor security from a dedicated account, and aggregate security logs in a single place. Manage all encryption keys in central key management systems (KMS).
* Coordination of network addresses and subnets. Applications and compute environments need to fit into the same network and require sharing of address ranges and domain names.
* Central management of resources for disaster recovery, including backup services like [IBM Cloud Backup for Classic](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-started). Applications and their services may be designed for high availability, but additional centrally organized resources might be available to fall back to in the worst case. This includes holding multiple resource copies available worldwide, e.g., stored in [replicated Object Storage buckets](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-replication-overview).
* Control costs by sharing more expensive services where possible. Not every development project needs to have all services deployed as dedicated instances. Often, it is enough to share service instances - within accounts or across. Even for production environments, service instances might be shared depending on their cost/value factor and technical feasibility.