vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Learning about App Configuration architecture and workload isolation 

Learn about the IBM Cloud® App Configuration service architecture, the service dependencies, and how customer workloads are isolated from each other in App Configuration instances.



  App Configuration architecture 

IBM Cloud App Configuration service is offered in the regions: Dallas, Washington DC, London, and Sydney. Every region supported, has its own IBM Cloud Kubernetes Service cluster with several worker nodes. Each worker node runs several instances of App Configuration service components. Each region is fronted by a global load balancer and a web application firewall.

App Configuration service persists tenant data in highly available database. A single regional database is used to store the data of all tenants in that particular region.

The data is stored across multiple zones in each region for high availability. Data that is stored is encrypted and persisted in a database cluster that is spread across availability zones. All databases connections use TLS/SSL encryption for data in transit.

Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/arch.png)

Figure 1. IBM Cloud App Configuration architecture

The Feature server component provides the API interface to the App Configuration service.

The data store component stores all configuration, metrics, instance details, and environments data.

The App Configuration UI is the front-end component, which can be used to manage the configuration data.

Analytics server component collects the usage metrics for configuration data and stores it to the data store at instance level.





  App Configuration workload isolation 

Each regional deployment of the IBM Cloud® App Configuration serves multiple tenants that are identified by the IBM service instance.



*  The IBM Cloud App Configuration service in a region is a multi-tenant highly available service.
*  The configuration data that is collected and processed by the IBM Cloud App Configuration service is associated with the service instance that is created by a tenant. This configuration data is not visible to the other service instances by virtue of this association.
*  Data for all tenants is colocated in the same data store and segmented by the tenant-specific instance guid. Retrieval of tenant-specific data is enforced by access control policies.
For more information about the different features of each version and what is supported by VMware®, see [NFS Protocols and ESXi](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html).







 Step 2: Submitting your Order 

When you're ready to submit your order, you can place it in the [Console](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-orderingFileStorageorderingFileStorageUI), from the [SLCLI](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-orderingFileStorageorderingthroughCLI), the [IBMCLOUD CLI](https://cloud.ibm.com/docs/cli?topic=cli-sl-file-storage-servicesl_file_volume_order) or with [Terraform](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-orderingFileStorageorderingthroughTerraform). For more information about provisioning File Storage for VMware® deployments, see the [architecture guide](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-architectureguide).





 Step 3: Connecting and configuring your new storage 

When your provisioning request is complete, authorize your hosts to access the new storage and configure your connection. Depending on your host's operating system, follow the appropriate link.



* [Mounting File Storage for Classic on Red Hat Linux®](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinux)
* [Mounting File Storage for Classic in CentOS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingCentOS)
Understanding cloud maintenance operations 



 Types of maintenance operations that affect your virtual server instances 



 Host and dedicated host maintenance 

IBM Cloud® performs periodic maintenance on the server hosts and dedicated hosts that run virtual servers. This maintenance upgrades the software on the underlying hypervisor, update the firmware on the systems, or other security and performance updates. In general, users don't experience any issues during these upgrades. Modifications that require host maintenance are applied with no or little impact to running services in most cases. Scenarios can occur where the user is involved during maintenance operations, which are discussed in the [Possible impacts to virtual server instances during maintenance operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenancemaintenance-impacts) section.

Most updates are done transparently to the host and the virtual servers that run on those hosts do not see any disruption. Nondisruptive changes can occur multiple times per week or even daily if necessary, all without impacting the user experience.





 Data center maintenance 

IBM Cloud® also performs periodic data center maintenance upgrades. Users don't generally experience any issues during data center maintenance. Examples of this maintenance can be updates to the network, power infrastructure, or server hardware in a data center. Most maintenance is performed without impact to the user’s workloads. Some infrequent scenarios can occur where the user might need to be involved during those operations, which are discussed in the following section.







 Possible impacts to virtual server instances during maintenance operations 

Some changes can require a secure live migration of a virtual server to update the hypervisor or host. These changes can be a firmware update, an event where the hypervisor kernel cannot be live patched, or load balancing. The regular live migration process is nondisruptive and use of dedicated hosts and virtual servers is not interrupted.

When nondisruptive live migration occurs, the virtual server experiences a brief pause of around 10 seconds, and in some cases up to 30 seconds. You are not notified in advance of nondisruptive migration. The virtual server instance is not restarted as part of this process.

In cases where a disruptive migration is required, you are notified 30 days in advance of the scheduled migration.
* no matter the environment, all clusters will tend to look the same,
* it is easier to control who has access to a specific cluster,
* it gives flexibility in the update cycles for deployments and underlying resources: When there is a new Kubernetes version, it gives you the option to update the Development cluster first, validate your application then update the other environment,
* it avoids mixing different workloads that may impact each other such as isolating the production deployment from the others.



However, often not all of that properties are needed and the use of fewer resources is desired. Then, another approach is to use [Kubernetes namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) in conjunction with [Kubernetes resource quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/) to isolate environments and control resource consumption. The following diagram shows a non-production and a production resource group with a Kubernetes cluster in a VPC each. The non-production cluster has a development and testing namespace, the production cluster a production namespace.

Zoom

![Diagram showing separate Kubernetes namespaces to isolate environments](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution20-users-teams-applications/multiple-environments-with-namespaces.svg)

Use separate Kubernetes namespaces to isolate environments





 Setup delivery pipeline 

When it comes to deploying to the different environments, your continuous integration / continuous delivery pipeline can be setup to drive the full process:



* continuously update the Development environment with the latest and greatest code from the development branch, running unit tests and integration tests on the dedicated cluster;
* promote development builds to the Testing environment, either automatically if all tests from the previous stages are OK or through a manual promotion process. Some teams will use different branches too here, merging the working development state to a stable branch as example;
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

Deploying your application across the availability zone in a multiple-zone region provides the highest resiliency, 4 9's. However, there are scenarios where deploying across the zones is not wanted, such as needing the latency to be minimal or the application is deemed not critical.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2022-06-22



[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed.
Using cookbooks for VMware deployments 

VMware® administrators can quickly realize cost-effective hybrid cloud characteristics by deploying into the IBM Cloud® enterprise-grade global cloud. vSphere workloads and catalogs can be provisioned onto VMware® vSphere environments within the IBM Cloud data centers without modifying VMware® VMs or guests. These deployments are made possible by using a common vSphere hypervisor and management and orchestration platform. vSphere implementations also can use other components of the VMware® vCloud Suite – vCloud Automation Center, vCenter Operations Management Suite, vSAN, vCloud Network & Security, Site Recovery Manager, vCenter Orchestrator, and NSX.

The core objective of the VMware® cookbook series is to assist vSphere administrators with the deployment of VMware® vSphere environments within an IBM Cloud infrastructure. The cookbooks are not intended to train you how to administer vSphere. For more information about administering vSphere, see [VMware® Education](https://www.vmware.com/learning.html).

IBM Cloud has several specific capabilities that give VMware® administrators the flexibility to consume bare metal instances and network, storage, and backup and recovery constructs in a self-service manner. You can then use these constructs to deploy fully functional vSphere implementations, which can be built to extend or replace on-premises vSphere implementations (VMware@Home).

The following guides are intended for experienced vSphere administrators. Some topics that are covered, consider that the reader has basic deployment skills to install and configure vSphere and vCenter.



* [Build a Single Site VMware® Environment](https://cloud.ibm.com/docs/virtualization?topic=virtualization-advanced-single-site-vmware-reference-architecture) You, as the vSphere administrator, are walked through the steps of building your environment, including the use of either Endurance or Performance Block Storage or QuantaStor.
See the following list for the types of third-party software that you can currently add to the catalog:



* Helm charts on Kubernetes and Red Hat OpenShift on IBM Cloud clusters
* Terraform templates
* OVA images deployed on VMware Solutions Dedicated - vCenter Server
* Virtual server images with Terraform deployed on VPC infrastructure or Power Systems Virtual Server
* Operators with a TGZ file from GitHub or GitLab repositories
* Operator bundles from Red Hat OpenShift registries



* What account do I use to onboard my software?

Use your IBM Cloud account to onboard software to the catalog. In some cases an IBM representative, with their own account, might be helping you with the onboarding process. If you want the representative to access your software in your test environment, you can add them to your account. For more details, see [Inviting users to an account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv).
* What's the difference between onboarding an Operator from my repository and onboarding an Operator from Red Hat?

One major difference is the packaging format. You can review the following example formats:



* Node-RED Operator: [https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz](https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz)
* Operator bundle from a Red Hat OpenShift on IBM Cloud registry: For an example, select the Akka Cluster Operator from the list of available Operators in the Certified repository.



* Can I update an Operator that was onboarded from the Red Hat registry?

Yes, see the following links for more information:



* [Adding a new version of software](https://cloud.ibm.com/docs/sell?topic=sell-add-version-software).
* [Reloading a software version](https://cloud.ibm.com/docs/sell?topic=sell-software-reload).
[Host system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqshost-reqs)



* [Computing characteristics](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-compute)
* [Red Hat CoreOS (RHCOS) packages and other machine configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-packages-rhcos)
* [Red Hat Enterprise Linux (RHEL) packages and other machine configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-packages)



[Host storage and attached devices](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-storagereqs-host-storage)

[Host network requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network)



* [Networking configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network-config)
* [Host network bandwidth](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network-bandwidth)
* [Network gateways and interfaces](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network-interface)
* [Inbound connectivity requirements for Satellite hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network-firewall-inbound)
* [Exposing the app service](https://cloud.ibm.com/docs/containers?topic=containers-appapp-service)
* [Configmaps for container environment variables](https://cloud.ibm.com/docs/containers?topic=containers-appconfigmap)
* [Secrets for container environment variables](https://cloud.ibm.com/docs/containers?topic=containers-appsecret)
* [Persistent volumes for container storage](https://cloud.ibm.com/docs/containers?topic=containers-apppv)



* [Complete example deployment YAML](https://cloud.ibm.com/docs/containers?topic=containers-appyaml-example)
* [Packaging apps for reuse in multiple environments with Kustomize](https://cloud.ibm.com/docs/containers?topic=containers-appkustomize)



[Deploying Kubernetes-native apps in clusters](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appdeploy_app)



* [Launching the Kubernetes dashboard](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appcli_dashboard)



* [Launching the Kubernetes dashboard from the IBM Cloud console](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appdb_gui)
* [Launching the Kubernetes dashboard from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appdb_cli)



* [Deploying apps with the Kubernetes dashboard](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appapp_ui)
* [Deploying apps with the CLI](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appapp_cli)
The command returns the following output:

App Configuration instance being used is - App_Configuration_Instance_1 (GUID - 123)









 ibmcloud ac environment list 

You can list all environment, by using the command:

ibmcloud ac environment list [--expand EXPAND] [--sort SORT] [--tags TAGS] [--include INCLUDE] [--limit LIMIT] [--offset OFFSET]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--offset OFFSET (optional)
: Used for pagination. The number of records to skip.

--tags TAGS (optional)
: Filter based on the tags.

--sort SORT (optional)
: Sort the details based on the specified attribute.

--expand EXPAND (optional)
: Expanded view of the item.

--include INCLUDE (optional)
: Include feature and property details in the response.





 Example 

To list all environments, run the following command:

ibmcloud ac environment list



 Output 

The command returns the following output:

name environment_id
Prod Environment prodEnvironment
Dev environment devEnvironment









 ibmcloud ac environment create 

You can create an environment, by using the command:

ibmcloud ac environment create {--file FILE-PATH | --name NAME [--environment_id ENVIRONMENT_ID] [--description DESCRIPTION] [--tags TAGS] [--color_code COLOR_CODE]}



 Command options 

--name NAME
: Environment name. Required field - input either as a flag or from file.

--environment_id ENVIRONMENT_ID (optional)
: Environment ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION (optional)
: Description of the environment. Optional field - input either as a flag or from file.

--tags TAGS (optional)
: Tags associated with the environment. Optional field - input either as a flag or from file.
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,High availability and resiliency for infrastructure



* 60 minutes
* 2021-06-24



[Architecture for a resilient infrastructure for a single availability zone](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ref-arch-saz)Architecture for a resilient infrastructure for a single availability zone

Deploying your application across the availability zone in a multiple-zone region provides the highest resiliency, 4 9's. However, there are scenarios where deploying across the zones is not wanted, such as needing the latency to be minimal or the application is deemed not critical.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 60 minutes
* 2022-06-22



[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed.
Depending on the selected region, you can choose bare metal servers with various CPU and memory sizes.





 Step 3: Ordering a VMware as a Service instance 

You must specify the following settings when you order a VMware as a Service instance.

These configurations are used to order a new VMware cluster for running the target workload:



* Instance name
* Resource group
* Cluster name
* Location (geography, region, and data center)
* Host profile and quantity
* Attached Network File Storage (NFS) performance tiers and amount of storage in each tier



After you specify all configurations, validate the cost and submit the instance order.





 Other operations 



* [Viewing your VMware as a Service instance](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
* [Adding and deleting hosts](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-host-adding-deleting)
* [Adding and deleting storage](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-storage-adding-deleting)
* [Adding virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-adding)
* [Viewing and deleting virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-view-delete)
* [Deleting your VMware as a Service instance](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-deleting)
Deployment topology 

The VMware virtual data center topology deploys your VMware vCenter Server® in a single-zone data center.



  Related links 



*  [Service prerequisites](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-serv-prereq)
*  [Procedure to order VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-procedure)
*  [VMware Regulated Workloads reference architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-archi-overview)