vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Determining your organization architecture 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

You can use the following two organization architectures.



* Single-organization: Consider this architecture if you require the same set of users to access resources that are available anywhere in the organization.
* Multi-organization: Consider this architecture if you require isolation between different environments.





 Single-organization versus multi-organization 

In a single-organization environment, the infrastructure resources are shared by different areas of the company. Whereas, in a multi-organization environment the infrastructure resources are not shared.

Both organization architectures support the following principles:



* Boundary enforcement for apps, projects, or both.
* Authorization to manage resources that are granted by user role.



You can then define multiple spaces that are based on different lines of business (LOB), the delivery phases, specific projects, apps, user permissions, or a combination of these components.

To implement a multi-organization architecture you can define organizations that correspond to different LOBs, delivery phases, specific projects, user permissions, or a combination of these components. You can then define multiple spaces that are based on apps or projects that are delivered by the same department in the company.





 Organization considerations 

When you implement a single-organization architecture, the organization includes all of the cloud resources, services, and apps that you use to develop, manage, and deploy cloud apps. In IBM Cloud Public, the organization provides segregation between accounts and is available across all regions.

When you implement a multi-organization architecture, organizations provide the first level of boundary enforcement and abstraction that you can use to control and define what can be done and by whom. Design each organization around the different LOBs, the delivery phases, the roles of the users, specific projects, or a combination of these components.

The number of organizations that you require depends on multiple factors:



* The level of granularity that you require within your organization to manage quotas and control costs.
* The level of security that you must enforce in your different environments.
The IBM Cloud Provider for Terraform supports IaaS (bare metal, virtual machine, network services, etc.), CaaS (Kubernetes Service and Kubernetes clusters), PaaS services, and serverless (Cloud Functions and Code Engine) resources.





 Step 2: Write scripts to automate the deployment 

As you start describing your infrastructure-as-code, it is critical to treat files you create as regular code. Thus, store them in a source control management system. Over time this will bring benefits such as using the source control review workflow to validate changes and continuous integration to automatically deploy infrastructure changes.

[This Git repository](https://github.com/IBM-Cloud/multiple-environments-as-code) has all the configuration files needed to set up the environments defined earlier. You can clone the repository to follow the next sections detailing the content of the files.

git clone https://github.com/IBM-Cloud/multiple-environments-as-code

The repository is structured as follow:



List of folders in the repository and their description

 Directory Description 

 [terraform](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform) Home for the Terraform files 
 [terraform/global](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform/global) Terraform files to provision resources common to the three environments 
 [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

!
Learning about Hyper Protect Virtual Servers architecture and workload isolation 

Review the following sample architecture for IBM Cloud® Hyper Protect Virtual Servers, and learn more about different isolation levels so that you can choose the solution that best meets the requirements of the workloads that you want to run in the cloud.



 Hyper Protect Virtual Servers architecture 

Zoom

![Hyper Protect Virtual Servers architecture](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_architecture-overview.svg)

Figure 1. Hyper Protect Virtual Servers architecture overview

The Hyper Protect Virtual Servers architecture is divided into two major areas:



1. The Z as a Service (ZaaS) infrastructure as shown in Figrure 1 is used to host the Hyper Protect Virtual Servers. This infrastructure is deployed as multi-zone regions, where each region consists of three zones. In every region, you can deploy virtual servers on one of the many IBM LinuxONE systems available. These systems can be reached by way of SSH over the public network.
2. The second part of the picture shows the Hyper Protect Virtual Servers Management stack. The key component is the Hyper Protect Virtual Servers service broker, which is used to create and manage your virtual servers. You can use the IBM Cloud catalog to interact with this component to provision a virtual server. After that you can use the Hyper Protect Virtual Servers dashboard to view details about the virtual server you created.







 Hyper Protect Virtual Servers workload isolation 

As shown in Figure 2, the IBM LinuxONE systems which are used for the Hyper Protect Virtual Servers are partitioned into several Logical Partitions (LPARs). A host system, which is protected by the IBM Secure Service Container technology is installed on each partition. IBM Secure Service Container technology provides protection against insider threats, for example, IBM Cloud administrators. Protection achieved by the following features:



* The host system supports interactions for administrators by way of well-defined encrypted REST APIs with only a limited set of secure configuration options. No other connection is available. For example, SSH is not available.
[Creating a resilient three-tier highly available infrastructure VPC in multiple regions with Terraform](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-create-three-tier-resilient-vpc-mzr)Creating a resilient three-tier highly available infrastructure VPC in multiple regions 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-11-18



[Creating a resilient three-tier highly available infrastructure VPC with Autoscale by using Terraform](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-create-three-tier-resilient-vpc-autoscale)Creating a resilient three-tier highly available infrastructure VPC with Autoscale by using 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 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.
[Architecture of Public frontend and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution40-vpc-public-app-private-backend/Architecture.png)

Figure 1. Architecture diagram of the tutorial

The configuration also includes [a bastion host](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-secure-management-bastion-server) acting as a jump server allowing secure connection to instances provisioned without a public IP address:

Zoom

![Architecture of Bastion Host](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution47-vpc-secure-management-bastion-server/ArchitectureDiagram.png)

Architecture of Bastion Host

While provisioning the resources, you will also deploy applications on the virtual server instances. When deploying applications in the cloud, software can originate from different sources:



1. The file system of a local workstation - using tools like Terraform to create the required infrastructure or Ansible, ssh and scp to install and configure software on the virtual server instances;
2. IBM mirrors to update the operating systems or to install supported packages;
3. Internet or intranet software repositories.



Zoom

![Architecture diagram showing the different sources to install software from](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution49-vpc-app-deploy/ArchitectureDiagram.png)

Architecture diagram showing the different sources to install software from

You will explore how to consume these different sources.
Creating a resilient three-tier highly available infrastructure VPC across multiple regions 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](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

To create resources with Terraform, you use Terraform configuration files that describe 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 run to create the resources. You can review the execution plan, change it, or run the plan. When you change your configuration, Terraform on IBM Cloud can determine what changed and create incremental execution plans that you can apply to your existing IBM Cloud resources.



 What is created 

A VPC is a private space in IBM Cloud where you can run an isolated environment with custom network policies. The variables that you define are used by the scripts to provision the virtual private cloud infrastructure resources for you. The default values in the scripts are used to create these resources in two different multi-zone regions:



 RESOURCE NAME REGION1 REGION2 TOTAL 

 Cloud Object Storage Instance 01 <br><br> * <br><br><br> 01 
 Cloud internet Service 01 <br><br> * <br><br><br> 01 
 Transit Gateway 01 <br><br> * <br><br><br> 01 
 Subnet Gateway 01 <br><br> * <br><br><br> 01 
 VPC 01 01 02 
 Subnets 04 04 08 
 Bastion VSI 01 01 02 
 App VSI 05 05 10 
 web VSI 05 05 10 
 Database VSI 
 Floating IP 01 01 02 



The scripts use variables to specify your information, OS, Auto scale, and Cloud Object Storage:



* API and ssh key
DC 

See [data center](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2439906).





 dedicated cloud 

A private cloud computing environment that provides infrastructure with single-tenant hardware. See also [borderless](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx8439189).





 deployable architecture 

Cloud automation for deploying a common architectural pattern that combines one or more cloud resources that is designed for easy deployment, scalability, and modularity. See also [module](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2030595).





 deployment 

A process that retrieves the output of a build, packages the output with configuration properties, and installs the package in a pre-defined location so that it can be tested or run. See also [stage](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2067189).





 DevOps 

A software methodology that integrates application development and IT operations so that teams can deliver code faster to production and iterate continuously based on market feedback.





 DevSecOps 

A methodology that integrates security practices with the software development and operations lifecycle. The goal of the merge is to prioritize the balance of development speed and security.





 dictionary 

A collection of words that can be used to pre-annotate documents. A new annotation is created for each word in the document text that matches a term in the dictionary. A machine learning model can be configured with one or more independent dictionaries, which are typically domain-specific, such a dictionary for pharmaceuticals and a dictionary for wealth management. See also [lemma](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2763345), [surface form](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3271760).





 dictionary pre-annotator 

A component that identifies mentions in text that match a specific set of words.
Scenario 3 - deploying in multiple zones with IBM Cloud Load Balancer 

You can also deploy your application in multiple zones by using only IBM Cloud Load Balancer rather than a combination of IBM Cloud Internet Services and IBM Cloud Load Balancer. This deployment scenario is less ideal, but is more cost-effective. You should consider this method only for less critical and less sensitive applications, such as internal applications.

Zoom

![Multiple-zone deployment.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/multi-zone-lb.svg)

Figure 5. Deploying in multiple zones with IBM Cloud Load Balancer





 Reference 

For more IBM Cloud high availability content, see:



* [Cloud reliability and disaster recovery architecture](https://www.ibm.com/garage/method/practices/run/cloud-platform-for-ha).
* [Application-level high availability](https://www.ibm.com/cloud/architecture/architectures/resilience/overview).
* [Deploying server pools and origins in a single region](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-pools-origins)
* [Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-auto-scale).
* [Deploying critical applications with IBM Cloud MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-multi-zone-resiliency) using the IBM Cloud console.
* Configuration and script files for 3-tier applications are available on the [vpc-ha-iac GitHub repository](https://github.com/IBM-Cloud/vpc-ha-iac).
[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. You might need to refer to your vendors’ supported methods of replication for the tiers, depending on the software components in your architecture.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2021-06-25



[Architecture for a resilient infrastructure for a single availability zone](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ref-arch-saz)Architecture for a resilient infrastructure for a single availability zone
Fast Path of IBM Cloud for VMware 

This page is a collection of shortcuts to the documentation sections for each offering, excluding general information that applies to all offerings, such as SAP Sizing.

Use the links in this section to quickly access relevant documents that you are already familiar with.



 Learn 

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



* [IBM Cloud Classic Infrastructure environment introduction](https://cloud.ibm.com/docs/sap?topic=sap-classic-env-introduction)



Certified Infrastructure-as-a-Service for SAP HANA database server is available in many variations, each with different capabilities and sizes to fit many different SAP workload scenarios. For more information:



* [Infrastructure certified for SAP - VMware Software-Defined Data Center](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offeringsiaas-vmware)



The following is an overview of the SAP-certified profiles with IBM Cloud Bare Metal servers for SAP HANA and SAP NetWeaver. For more information:



* [VMware SSDC certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-vmware)
* [VMware SDDC certified profiles for SAP NetWeaver](https://cloud.ibm.com/docs/sap?topic=sap-nw-iaas-offerings-profiles-vmware)
* [Compute Profiles of SAP-certified VMware on Classic Infrastructure](https://cloud.ibm.com/docs/sap?topic=sap-compute-os-design-considerationscompute-vmware)



Your business and functional requirements determine the SAP solutions powered by the SAP HANA Database Server or SAP NetWeaver Application Server, and therefore determine how your applications are run in the available infrastructure. For more information:
* Adobe Document Services (ADS) for SAP
* SAP Process Orchestration (PO) - Process Integration (PI)
* SAP Landscape Management (LaMa)
* SAP Secure Logon Server (SLS)
* AnyDB - IBM Db2
* AnyDB - Microsoft SQL Server
* AnyDB - SAP MaxDB
* AnyDB - SAP ASE
* ...more







 Supported SAP Development Applications 



* SAP Cloud Platform (including SAP Cloud Connector)







 SAP-certified Infrastructure-as-a-Service (IaaS) offerings 

The IBM Cloud SAP-Certified IaaS gives you the flexibility to run your SAP workloads in the IBM Cloud when you need them, where you need them with over 60 IBM data centers worldwide. You can quickly address issues such as:



* Rapidly expanding and contracting capacity (as needed)
* Migrating SAP workloads to the cloud
* Supplementing existing on-premises virtualized infrastructure architectures.



The IBM Cloud® for SAP portfolio primarily consists of five offerings:



1. IBM Cloud Bare Metal
2. IBM Cloud Bare Metal with Intel Optane DC Persistent Memory
3. IBM Cloud Virtual Servers
4. IBM Power Virtual Servers (complementary offering from IBM Power Systems, with connection through IBM Cloud)
5. IBM Cloud for VMware



More information on the these Infrastructure offerings within the IBM Cloud® for SAP portfolio, see [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings).

These offerings are spread across two primary infrastructure environments, and one separated environment that uses IBM Power technologies:



* [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.
* [Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-redhat-arch)
* [IBM Cloud® for VMware Solutions SDDC architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-arch)
* [IBM Cloud networking and infrastructure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-sddc-infra)
In [this other tutorial, we've introduced best practices to organize users, teams and applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-users-teams-applicationsusers-teams-applications) and a sample scenario. The sample scenario considers three environments, Development, Testing and Production. How to automate the creation of these environments? What tools could be used?



 Objectives 



* Define a set of environments to deploy
* Write scripts using the IBM Cloud CLI and Terraform to automate the deployment of these environments
* Deploy these environments in your account



Zoom

![Architecture Diagram](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution26-plan-create-update-deployments/architecture.svg)

Architecture diagram



1. A set of Terraform files are created to describe the target infrastructure as code.
2. An operator uses terraform apply to provision the environments.
3. Shell scripts are written to complete the configuration of the environments.
4. The operator runs the scripts against the environments.
5. The environments are fully configured, ready to be used.







 Step 1: Overview of the available tools 

All of the operations will be done in a bash shell and making use of terraform and ibmcloud commands. You will find instructions to download and install these tools for your operating environment in the [Getting started with tutorials](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorials) guide.

To avoid the installation of these tools you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console.

With ibmcloud and its plugins, you can automate the creation and configuration of your cloud resources. Virtual Servers, Kubernetes clusters, Cloud Functions, Code Engine, and services, you can provision all of them from the command line.