vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2. You can use this feature for a backup and restore of a 3-tier application. Block storage snapshots can also be used to scale out a 3-tier system with minimal changes to your application.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 2021-06-25



[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-deploy-n-tier-app-saz)Deploying n-tier application with IBM Cloud single availability zone

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® for a single availability zone.The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. In this tutorial, you create your own VPC, then create subnets in one zone of the region, then you provision the virtual server instances.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 60 minutes
* 2021-12-14



[Deploying server pools and origins in a single MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-pools-origins)Deploying server pools and origins in a single MZR

Use this tutorial to deploy availability pools in a VPC for a single MZR. Creating server pools with origins provides your DevOps team with a staging environment so they can validate near-production ready code in parallel with an existing production environment.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+3

IBM Cloud Load Balancer,Cloud Internet Services (CIS),High availability and resiliency for infrastructure
Compute hosts in different edge or data centers





 5. Compute hosts, including Satellite control plane, are located in multiple edge or data centers 

In this example, the compute resources are located in multiple data centers or edge. The Satellite control plane is located in a single data center or edge, while the hosts required for your services are on separate data centers or edge.

Zoom

![Compute resources in different edge or data centers.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/topology-5.svg)

Figure 5. Compute hosts from nultiple, separate edge or data centers







 Use case: Edge clusters with centralized management in IBM Cloud 

This use case shows how to build a centralized management plane for your Satellite location inside IBM Cloud, while the managed Satellite clusters are on the edge, in any other data centers, or in third-party clouds.

Follow these steps to set up your Satellite location.



1. Create a Satellite location manually. See [Manually creating Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-locationslocation-create-manual).
2. Download the host attach script.
3. Provision the infrastructure hosts inside IBM Cloud with the attach script. See [Adding IBM Cloud hosts to Satellite manually](https://cloud.ibm.com/docs/satellite?topic=satellite-ibmibm-host-attach).
4. Provision the edge compute hosts for the Satellite clusters with the same attach script.
5. Confirm all your hosts from all providers are available and unassigned in the Satellite location.
6. Assign Satellite location control plane hosts. Use your hosts from IBM Cloud according to [Setting up the Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane).
7. Confirm that the Satellite location control plane is in a healthy state.
8.
* For shared microservices, a new VSI could be created with a new version and after verification DNS could be adjusted or the shared load balancer could be used to switch to the new version.







 Automation, Staging, and Development 



* For production the teams can each have their own [Schematics](https://cloud.ibm.com/schematics/overview) workspace. With Schematics, Terraform configurations can be executed directly in the cloud where state and output can be shared.
* The Terraform scripts can be adjusted to allow staging and development environments. Put these environments into new accounts.
* A continuous deployment environment can be constructed to move the code and environments through the development, staging and into production. Is roll back needed? How would this be accomplished?









 Conclusions 

The architecture of a system is influenced by the containment and ownership of cloud resources. It is important for architects from all aspects of the system contribute their concerns to the architecture. Each team needs the ability to control the resources they produce and release. Isolation will reduce the likelihood of problems and contain the blast radius when problems occur.





 Related content 



* Tutorial: [Best practices for organizing users, teams, applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-users-teams-applicationsusers-teams-applications)
* Tutorial: [Public frontend and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-public-app-private-backend),
* Tutorial: [Deploy a LAMP stack using Terraform](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-lamp-stack-on-vpc)
VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about more VPC overviews and VPC tutorials. For more information about VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).





 SAP products architecture on IBM Cloud VPC 

A [Virtual Private Cloud (VPC)](https://www.ibm.com/cloud/learn/vpc?mhsrc=ibmsearch_a&mhq=VPC) contains one of the most secure and reliable cloud environments for SAP applications within your own VPC with its included virtual server instances. This represents an Infrastructure as a Service (IaaS) within IBM Cloud that offers all of the benefits of isolated, secure, and flexible virtual cloud infrastructure from IBM. In comparison, the IBM Cloud classic infrastructure virtual servers offering uses virtual instances with native and VLAN networking to communicate to each other within a data center; however, the instances are restricted in one well-working pod by using subnet and VLAN networking as a gap scale up of virtual resources should rely between the pods. What’s new with IBM Cloud VPC is a network orchestrator layer concept that eliminates the pod boundaries and restrictions, so this new concept handles all the networking for every virtual instance running within VPC across regions and zones.





 1. Highly available system for SAP NetWeaver on IBM Cloud VPC 

In a highly available (HA) system, every instance can run on a separate IBM Cloud virtual server instance. The cluster HA configuration for the SAP application server consists of two virtual server instances, each of them located in the same zone within the region by using placement groups. Placement groups assure that both cluster resources and cloud resources are also located in different compute nodes as specified in the following placement groups section.

Zoom

![Figure 1.
[GPU](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilesgpu) Best for high-performance workloads. 



Some of these families are also available for IBM Cloud® Virtual Servers for Virtual Private Cloud. For more information, see [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc-on-classic-vsi?topic=vpc-on-classic-vsi-getting-started).



 Next steps 

After you review and decide upon your virtual server profile, it's time to provision your public virtual server. To get started, see [Provisioning public instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-ordering-vs-public).
* [Compute](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutrequired-services-compute)
* [Containers](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-containers)
* [Networking - VPC infrastructure](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-vpc)
* [Networking - Interconnectivity](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-interconnectivity)
* [Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-storage)
* [Security](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-security)
* [Logging and monitoring](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-logging-monitoring)
* [Integration](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutvpc-architecture-optional-services-integration)
* [Databases](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutvpc-architecture-optional-services-databases)



* [Reference architecture components](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutvpc-architecture-detailed-vsi-component-summary)
[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-deploy-n-tier-app-szr)Deploying n-tier application with IBM Cloud single availability zone

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® for a single availability zone. The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies. In this tutorial, you create your own VPC, then create subnets in one zone of the region, then you provision the virtual server instances.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2021-12-14



[Deploying critical applications with IBM Cloud MZR](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-multi-zone-resiliency)Deploying critical applications with IBM Cloud MZR

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® MZR. In this tutorial, you create your own VPC in region 1, then create subnets in two different zones of region 1, then you provision the virtual server instances. You create two availability zones and virtual server instances in each availability zone for UI, application, and db.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 45 minutes
* 2021-09-03



[Creating a three-tier highly available architecture on an IBM Cloud VPC](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-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.
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. Examples are [dedicated hardware plans for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicdedicated-hardware-plan) that offers HIPAA compliance or services like [Hyper Protect DBaaS for PostgreSQL](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-postgresql) and [Hyper Protect DBaaS for MongoDB](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-mongodb) which offer highly secure database environments for sensitive data.





 Secure and isolate network traffic 

In most cases, an application consists of the app itself and one or many (micro-) services. These services are typically reachable over the public internet, but can also be accessed on so-called [service endpoints](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview). To increase security by isolating network traffic, follow the [instructions to enable virtual routing and forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint).
[Isolated recovery environment network overview](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/veeam-cr-sa-sb-ire.svg)

Figure 1. Isolated recovery environment network overview

The previous diagram shows the networks that are associated with a consolidated cluster of the vCenter Server® instance that is used for an isolated recovery environment. The customer order is:



* A private network only vCenter Server® instance with gateway cluster and Juniper® vSRX firewalls.
* The Veeam service on a bare metal server.
* A bare metal server that runs Ubuntu 20.04 LTS.



When the IaaS is provisioned, the customer:



* Deletes the sample segments that created during the provisioning process.
* Keeps the workload T0 and T1.
* Does not change to the services T0.
* Creates a DMZ segment and provisions several Microsoft® Windows® Jump hosts and Linux® bastion hosts. These actions provide the cyberteam with access to the environment while providing isolation.
* Configures the vSRX:



* System services and local administrator access.
* Management services, such as NTP, DNS, SNMP, and syslog.
* Interfaces and zones.
* Address books, services, and security policies.
* NAT, routing, and VPN.



* Associates and routes-through the vCenter Server instance VLANs with the IBM Cloud® gateway devices, which are the ESXi hosts in the gateway cluster.



The vSRX security policies enable the objectives that are listed in the following table:



Table 1. vSRX security policies objectives

 Rule Name Sources Destinations Services Action 

 Allow access to DMZ Cyber Admins IPs DMZ subnets SSH, RDP Allow 
 Allow access to Instance Management DMZ Instance Management SSH, HTTPS, TCP-9392, DNS Allow 
 Allow Veeam access to production environment Veeam backup server IP Production vSphere management networks HTTPS Allow
Expand the tutorial 



 Other Considerations 



* The Application team is providing access to the application via a floating IP address. Consider connecting this to IBM Cloud Internet Services. It can manage the public DNS and provide security. [Deploy isolated workloads across multiple locations and zones](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-multi-region) has an example.
* The Application team can scale horizontally using a load balancer like the shared team.
* The shared team can add additional instances to the load balancer by adding instances to the shared/main.tf.
* The shared team could switch their implementation platform to Kubernetes.







 Continuous Delivery 



* Installation of software is currently done when the VPC instance is created. The delivery of new versions of software to production has not been considered. [Application Deployment to a Virtual Private Cloud with a DevOps Toolchain](https://www.ibm.com/cloud/blog/application-deployment-to-a-virtual-private-cloud-with-a-devops-toolchain) demonstrates one solution.
* For shared microservices, a new VSI could be created with a new version and after verification DNS could be adjusted or the shared load balancer could be used to switch to the new version.







 Automation, Staging, and Development 



* For production the teams can each have their own [Schematics](https://cloud.ibm.com/schematics/overview) workspace. With Schematics, Terraform configurations can be executed directly in the cloud where state and output can be shared.
* The Terraform scripts can be adjusted to allow staging and development environments. Put these environments into new accounts.
* A continuous deployment environment can be constructed to move the code and environments through the development, staging and into production. Is roll back needed? How would this be accomplished?









 Conclusions 

The architecture of a system is influenced by the containment and ownership of cloud resources. It is important for architects from all aspects of the system contribute their concerns to the architecture. Each team needs the ability to control the resources they produce and release.
About Terraform on IBM Cloud 

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud platform, classic infrastructure, and VPC infrastructure resources so that you can rapidly build complex, multitiered cloud environments, and enable Infrastructure as Code (IaC).



 How does Terraform on IBM Cloud work? 

[Terraform](https://www.terraform.io/) is an open source project that lets you specify your cloud infrastructure resources and services by using the high-level scripting HashiCorp Configuration Language (HCL). With HCL, you have one common language to declare the cloud resources that you want and the state that you want your resources to be in.

Let's say you want to spin up multiple copies of your cloud environment that uses a cluster of virtual servers, a load balancer, and a database server on IBM Cloud. You could learn how to create each resource, review the API or the commands that you need, and write a bash script to spin up these components. But it's easier, faster, and more orderly to use one language to declare all your requirements, document them in a configuration file, and let Terraform on IBM Cloud do it all for you.



 What is the IBM Cloud Provider plug-in? 

To abstract the APIs and complexity of the cloud resource provisioning and management process to the user, cloud providers create a plug-in for Terraform that contains the information for how to connect to the cloud provider and what APIs to call to work with a certain cloud resource. IBM's plug-in is called the IBM Cloud Provider plug-in for Terraform. The plug-in analyzes the resources that you specified and determines the order in which these resources must be provisioned, including any dependencies that must be considered.





 How does Terraform on IBM Cloud provision and manage cloud services? 

To use Terraform on IBM Cloud, you must create a Terraform configuration file that describes the IBM Cloud resources that you need and how you want to configure them. Based on your configuration, Terraform creates an execution plan and describes the actions that need to be executed to get to the required state. You can review the execution plan, change it, or simply execute the plan.
IBM Cloud® Power Virtual Servers (PowerVS) is a public cloud offering that an enterprise can use to establish its own private IBM Power computing environment on shared public cloud infrastructure. PowerVS is logically isolated from all other public cloud tenants and infrastructure components, creating a private, secure place on the public cloud. This deployable architecture provides a framework to build a PowerVS offering according to the best practices and requirements from the IBM Cloud.





 Components 



 VPC architecture decisions 



Table 1. VPC architecture decisions

 Requirement Component Choice Alternative choice 

 <br><br> * Ensure public internet connectivity<br> * Isolate most virtual instances to not be reachable directly from the public internet<br><br><br> Edge VPC service Create a separate VPC service where public internet connectivity is allowed to be configured 
 <br><br> * Provide infrastructure administration access<br> * Limit the number of infrastructure administration entry points to ensure security audit<br><br><br> Management VPC service Create a separate VPC service where SSH connectivity from outside is allowed 
 <br><br> * Provide infrastructure for service management components like backup, monitoring, IT service management, shared storage<br> * Ensure you can reach all IBM Cloud and on-premises services<br><br><br> Workload VPC service Create a separate VPC service as an isolated environment, without direct public internet connectivity and without direct SSH access 
 <br><br> * Allow customer to choose operating system from two most widely used commercial Linux operating system offerings<br> * Support new OS releases<br><br><br> Linux operating system Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise Server(SLES) 
 <br><br> * Create a virtual server instance that can act as an internet proxy server<br><br><br> Proxy server VPC instance Create a Linux VPC instance that can act as a proxy server. Preconfigure ACL and security group rules to allow public internet traffic over proxy that uses default proxy ports (3828) Configure application load balancer to act as proxy server manually
About virtual server instances for VPC 

IBM Cloud® Virtual Servers for Virtual Private Cloud is an Infrastructure-as-a-Service (IaaS) offering that gives you access to all of the benefits of IBM Cloud VPC, including network isolation, security, and flexibility.

With virtual server instances for VPC, you can quickly provision instances with high network performance. When you provision an instance, you select a profile that matches the amount of memory and compute power that you need for the application that you plan to run on the instance. Instances are available on the x86 architecture. After you provision an instance, you control and manage those infrastructure resources.



 How are virtual server instances for VPC different from other IBM virtual server offerings? 

In the IBM Cloud Virtual Servers for Classic infrastructure offering, instances use native subnet and VLAN networking to communicate to each other within a data center (and single pod). Using subnet and VLAN networking in one pod works well until you must scale up or have large virtual resource demands that require resources to be created between pods. (Adding appliances for VLAN spanning can get expensive and complicated!)

IBM Cloud VPC adds a network orchestration layer that eliminates the pod boundary, creating increased capacity for scaling instances. The network orchestration layer handles all of the networking for all virtual server instances that are within a VPC across regions and zones. With the software-defined networking capabilities that VPC provides, you have more options for multi-vNIC instances and larger subnet sizes.

To review and start deploying compute resources, see the following topics:



Table 1. Deployment options

 Deployment options Description 

 [Virtual Servers for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesprofiles) IBM Cloud Virtual Servers for VPC provide the advanced security of a private cloud with the agility and ease of a public cloud. Virtual servers for VPC offer the best network performance (up to 80 Gbps), best security, and fastest provisioning times.