vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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.



 Objectives 



* Setting up resilient single availability zone VPC environment for the application
* Setting up scheduling script for regular backups







 Architecture 

Zoom

![Architecture diagram.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-deploying-critical-apps-SAZ.png)

Architecture Diagram



1. Provision 4 subnets (mgmt, web, app, and db)
2. Provision security groups
3. Provision placement groups for web and app
4. Provision virtual server instances



1. Bastion server in mgmt subnet and generate an SSH Key
2. Provision virtual server instances in the corresponding tiers with security groups



5. Deploy a public load balancer and a private load balancer between tiers in each of availability zones.
6. Setup service IDs and deploy the script on the bastion server. For more information, see [Taking snapshot backups for your 3-Tier applications for SAZ](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-snapshot-backups-3-tier-applications-saz).







 Before you begin 



* Check permissions for VPC
* Generate SSH Keys from your workstation to connect to the bastion server







 Step 1: Create a VPC 

To create your own IBM Cloud VPC in region 1, complete these steps:



1. Go to the VPC overview page and click Get Started.
2. Select Create.
3.
Select a Satellite location to use for your compute environment.
4. Select the zones and worker nodes per zone for your compute environment. For more information about zones, see [Plan for a multizone location](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-multizone).
5. Select a region. For Beta, you must select eu-de.
6. Name your compute environment.
7. Click Create.



After your compute environment is set up, you can create a project and start deploying apps and running jobs.

Even though CLI commands are available for projects, apps and jobs, you must use the UI for these tasks when you select a project from a Satellite compute environment.





 Creating a project in a compute environment 

When you create a project, it is automatically selected as the current context. Note that you must create your project from the UI as you cannot select your compute environment from the CLI. To create a project in a compute environment, follow these steps.



1. From the [Projects page on the Code Engine console](https://cloud.ibm.com/codeengine/projects), click Create.
2. Select Satellite as your platform.
3. Choose a location to deploy the project.
4. Enter a name for the project. The name must be unique for all your projects within the specified location.
5. Choose the resource group where you want to create the project.
6. Click Create.



After your project is created, you can start deploying apps and running jobs in your Satellite location.





 Why doesn't my compute environment create? 



1. Verify that you set up service-to-service access. [Follow the steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-authority) to set it up. Because Code Engine continuously polls Satellite for the assigned location, as soon as you set up service-to-service access, the compute environment creation process continues.
2.
](https://cloud.ibm.com/docs/virtualization)Virtualization for Classic ServiceContainers[Container Registry](https://cloud.ibm.com/docs/Registry)Container Registry Service[Kubernetes service](https://cloud.ibm.com/docs/containers)Kubernetes service Service[Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift)Red Hat OpenShift on IBM Cloud ServiceDatabases[Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant)Cloudant Service[Databases For Elasticsearch](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-getting-started)Databases For Elasticsearch Service[Databases For EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-getting-started)Databases For EnterpriseDB Service[Databases For MongoDB](https://cloud.ibm.com/docs/databases-for-mongodb?topic=databases-for-mongodb-getting-started)Databases For MongoDB Service[Databases For MySQL](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-getting-started)Databases For MySQL Service[Databases For PostgreSQL](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-getting-started)Databases For PostgreSQL Service[Databases
* Tutorial: [Best practices for organizing users, teams, applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-users-teams-applicationsusers-teams-applications)
* [How to deploy isolated workloads across multiple locations and regions](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-multi-region)
* [Public front end and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-public-app-private-backend),
* [Network Function Virtualization](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vnf)
* [Private hub and spoke with transparent VNF and spoke-to-spoke traffic](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vnf-ha)
VMware licensing options 

VMware® administrators can quickly realize cost-effective hybrid cloud characteristics by deploying into an IBM Cloud® enterprise-grade global cloud. A key differentiator is that vSphere workloads and catalogs can be provisioned onto VMware vSphere environments within IBM Cloud® data centers without modifying VMware VMs or guests. These deployments are made possible by using a common vSphere hypervisor and management or orchestration platform.

In addition to offering the vSphere Enterprise Plus license, IBM Cloud® offers monthly licensing for vCenter, NSX, vRealize, vSAN, and Site Recovery Manager (SRM).



 VMware vSphere 

VMware vSphere is a bare metal virtualization OS platform that abstracts processor, memory, storage, and networking resources to create multiple virtual servers on a single physical server. Multiple physical servers can be clustered together to create a private cloud.

The following user interfaces are available for VMware vSphere.



* vCenter Clients
* VMware API
* VMware CLI





 VMware vSphere features 

VMware vSphere offers the following features.



* vMotion live migration
* High availability
* Fault tolerance
* Replication
* Nvidia GRID vGPU virtualization
* Workload capacity optimization
* Distributed Resources Scheduler (DRS)
* Thin provisioning
* Network I/O control









 VMware vCenter 

VMware vCenter helps you centralize the management of the compute resources within each vSphere host. You can manage vSphere hosts individually, but placing them under the vCenter control enables the following capabilities.

The following user interfaces are available for VMware vCenter.



* Web Client
* Thick Client
* VMware API
* VMware CLI





 VMware vCenter features 

VMware vCenter offers the folliwing features.



* Centralized control and visibility for all aspects within managed vSphere hosts and guest virtual machines.
* Provides a window interface view through the vCenter web client for compute network and storage management.
* Proactive Optimization.
[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



* 2021-06-10



[Deploying critical applications with IBM Cloud MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-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.
Region and data center locations for resource deployment 

IBM Cloud® has a resilient global network of locations to host your highly available cloud workload. You can create resources in different locations, such as a region or data center, but with the same billing and usage view. You can also deploy your apps to the location that is nearest to your customers to achieve low application latency. IBM Cloud provides three tiers of regions:

multizone regions,single-campus multizone regions, anddata centers.



 Regions 

Multizone regions (MZRs) are composed of three or more zones that are independent from each other to ensure that single failure events affect only a single zone. MZRs provide low latency (< 2-milliseconds latency) and high bandwidth (> 1000 Gbps) connectivity across zones. For

GAservice rollout, see the [Service rollout policy](https://cloud.ibm.com/docs/overview?topic=overview-service-rollout).

The advantage of an MZR is that it provides consistent cloud services across different zones, better resiliency, availability, higher interconnect speed between data centers for your resources. These features can be critical to your applications. Deploying the application in an MZR rather than a different deployment location (data centers, either physical or logical) is that you can increase the availability from 99.9% to 99.99% when deployed over three zones.

IBM® offers two types of multizone regions. The underlying infrastructure in both types provides the same SLA.



 Multizone regions (MZR) 

MZRs offer the highest level of redundancy and availability because it uses three separate sites within a region.

Zoom

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

Figure 1. Multizone region (MZR)
Now, one of the advantages of this idea of a location is it really provides a tremendous flexibility. IBM Cloud Satellite is built on top of Kubernetes and OpenShift as the common infrastructure abstraction that we use to allow you to consume cloud services in any infrastructure. And by using OpenShift as that abstraction layer, we can support a variety of infrastructures underneath a Satellite location. You can bring your own custom infrastructure in your data center, physical or virtual servers. You can use your account on another public cloud like Amazon, or Azure, or Google - and consume that infrastructure, and arrange it into a location that’s used by IBM Cloud for running cloud services. Now, since those locations those services and applications, are managed by IBM Cloud, we, of course, need a connection back to the cloud to help us manage those things - and that connection is provided by a component called “Satellite Link”. And the idea of Satellite Link is to give you the transparent visibility to all the data that’s flowing back and forth between the cloud and that location, and to give you control over what applications and resources are exposed in those locations. So, these two ideas, of location and link, provide the fundamental new concepts that Satellite introduces to IBM Cloud to give you the power of services anywhere. We’re also going to provide some optimized solutions. Fully integrated rack systems, both from IBM and from partners, and as-a-service infrastructure capabilities where we can run the entire stake for you from hardware through infrastructure and up into the platform and SaaS applications. And so, you can consume infrastructure either with what you have, you can build new environments, or you can run multi-cloud environments across IBM Cloud and other public cloud providers. So, those are kind of the core ideas in Satellite: locations and link allow us to extend our cloud catalog services to any location, giving you the power of cloud, and the power of IBM Cloud, anywhere in the world that you need it. All you need is some Linux infrastructure and IBM does the rest. Thanks a lot.





 What are Satellite locations, hosts, and so on? 

Before you get started, become familiar with some key terms for Satellite. Afterward, you can test your knowledge and [!take a quiz](https://ibm.biz/BdPUqR)
Containers <br><br>[4] <br><br> * [Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-containers-openshift)<br> * [IBM Cloud® Container Registry](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-containers-registry)<br><br><br> 
 Networking - VPC infrastructure <br><br> * [IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc)<br> * [IBM Cloud® Application Load Balancer for VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-alb)<br> * [IBM Cloud® Virtual Private Network (VPN) for VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-vpn)[5]<br> * [IBM Cloud® DNS Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-dns-services)<br> * [IBM Cloud® Virtual Private Endpoints for VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-aboutservices-networking-vpe)<br><br><br>
Creating an advanced single-site VMware reference architecture 

The reference architecture is intended for provisioning an environment that uses shared storage, VMware High Availability (HA) and vSphere Distributed Resource Scheduler (DRS), and an IBM Cloud gateway or firewall. Advanced single-site VMware reference architecture is suitable for most production deployments that can be scaled as workload dictates and can replace an on-premises implementation or extend into a hybrid IT scenario.



 VMWare environment overview 

The advanced representative VMware environment that is outlined, consists of one data center that manages two separate clusters: management and capacity. The configuration can be set up by using a single four node cluster that depending on requirements. The management cluster contains the following virtual machines (VMs) that are used for managing the infrastructure:



* VMware vCenter Server 5.5 or 6.0 Appliance
* Microsoft Windows 2012 R2 Standard with Active Directory and Domain Name System (DNS) roles



The capacity cluster contains the resources and infrastructure that are needed to create and run VMs. For networking, the environment consists of three private, internal VLANs, and a single, public VLAN that is used for external communication. Table 1 specifies the VLAN types and VLAN names are used throughout the environment.



Table 1. Primary VLANs

 VLAN Type VLAN Name Description 

 Primary Private Management Assigned to manage and access the physical ESXi hosts and virtual servers. 
 Primary Private Storage Assigned to manage and access the shared storage that is attached to each ESXi host. 
 Primary Private VM Access Assigned to virtual machines that run on each ESXi host. 
 Primary Public Public Assigned to virtual machines or other devices that require access from the public network. 



For shared storage, you can use OS Nexus QuantaStor, a single-tenant shared storage server, or IBM Cloud Endurance or Performance storage services. In either case, the shared storage device is used to store the VMs on both the management and capacity clusters. For more information about storage options, see [IBM Cloud storage solutions](https://www.ibm.com/cloud/storage).

The storage environment is configured to support NFS volumes.



 Before you begin 



* Navigate to your console's device menu.
* Single site VMware vCenter Server® instance - An automated provisioning offering that deploys hardware and software in a defined pattern. After initial deployment, you must add capacity and additional services to a number of automated workflows as needed. For more information, see [vCenter Server overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview). The types of vCenter Server instances include:



* Regulated Workloads. For more information, see [VMware Regulated Workloads overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-overview).
* VMware Security and Compliance Readiness Bundle. For more information, see [Security and Compliance Readiness Bundle overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-scb-overview).



* Multisite or location vCenter Server instance - The vCenter Server offering can be deployed in multiple locations to create a multisite or location vCenter Server instance. The vCenter Server multisite deployment pattern is two or more instances that are deployed into a common root domain and single sign-on domain with vCenters in Enhanced Link Mode. Each site or location has its own NSX-T instance. For more information, see [Multisite configuration for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_multisite).



The vCenter Server multizone offering is now deprecated. For more information, see [vCenter Server multizone BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-mcv-archi-bom).
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 critical applications with IBM Cloud MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-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,High availability and resiliency for infrastructure



* 45 minutes
* 2021-09-03



[Setting up a Red Hat OpenShift for HPC cluster](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-setting-up-red-hat-openshift-hpc-cluster)Setting up a Red Hat OpenShift for HPC cluster
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. You might need to refer to your vendors’ supported methods of replication for the tiers, depending on the software components in your architecture.



 Architecture diagram 

This diagram shows the 3-tier architecture that you create with the tutorial.

Zoom

![Two different types of bare metal deployment.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/3_tier_tut.png)

Architecture Diagram

You must have full administrative privileges for managing the VPC resources. For more information about user permissions in a VPC, see [[Getting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).





 Step 1: Create VPC 

Create a VPC named vpcname-region1. For more information, see [Deploying critical applications with IBM Cloud MZR - Step 1: Create a VPC](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-multi-zone-resiliencycreate-vpc-mzr)





 Step 2: Create Subnets 

Create the following subnets:



1. vpcname-zone1web-subnet
2. vpcname-zone2web-subnet
3. vpcname-zone1mt-subnet
To list all of your resource groups, run ibmcloud resource groups. Optional.

-t TAG
: Use tags to organize your resources. Tags are visible account-wide. Optional. Multiple tags are permitted, for example, -t tag1 -t tag2.

-e ENV-CONFIG
: Specify environment variables if you are using a self-provided image. You must specify the variables in your registration definition first. You can set one or more environment variables as key value pairs by using the -e flag, for example, -ibmcloud hpvs instance-update CRN -i latest -e k1=v1 -e k2='v2 v3'. Environment variable names can have a maximum length of 64 characters and can be numbers, chars, and underscore. Environment variable values can have a maximum length of 12288.

--outbound-only
: If this parameter is set, only outbound connections are allowed from your Hyper Protect Virtual Server instance. Use the internal IP address to connect to this Virtual Server from other Virtual Servers created by the same IBM Cloud account in the same region.

For example: