vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Environment tab](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/multiple-env-tab.png)

Environment tab





 Using your environments 

You can use extra environments in your development and test process before you deploy an assistant for customer use.

Add extra environments to match your existing test-to-deploy process. For example, you might name and use five environments in a scenario like this:



Example

 Environment Used for 

 Draft Conversation authors build actions and test as they work 
 Review Conduct an initial content review with stakeholders 
 Test Test assistant content on a configured channel 
 Staging Use a staging website to test assistant content and channel configurations 
 Live Deploy for customer use 





 Access control to environments 

You can control who can work in each environment. Each environment has an ID that you can use in IBM Cloud Identity and Access Management (IAM) and set access by resource. For more information on access control, see [Managing access with Identity and Access Management](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-access-controlaccess-control-iam). For more information on settings, see [Environment settings](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-multiple-environmentsenvironment-settings).







 Publishing content to an environment 

For more information, see [Publishing your content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish).

To publish new changes from the draft environment to an environment:



1. If changes are available to publish, click Publish.
2. Enter a description of the version.
3. Choose an environment.
4. Click Publish.



To publish an existing version to an environment:



1. On the Environments page, click the environment tab.
2. In Resolution Methods, click Switch version.
3.
Learning about Code Engine architecture and workload isolation 

IBM Cloud® Code Engine is the IBM Cloud platform that unifies container images, 12-factor-apps, functions, and batch jobs as a one-stop-shop. It's a multi-tenant system that consists of three major building blocks: A control plane, a (set of) shard (or shards), and a routing layer. The control plane and the shards are realized as separate multi-zone Kubernetes clusters. The following diagram gives a graphical overview of the architecture.

Zoom

![Code Engine architecture diagram](https://cloud.ibm.com/docs-content/v1/content/ad5f41087138b4b1bb795e3b5b0661ac5a105cbd/codeengine/images/codeengine-architecture.svg)

Figure 1. Code Engine architecture diagram

Code Engine is based on IBM Cloud Kubernetes Service clusters and depends on the components and workload isolation of the IBM Cloud Kubernetes Service. For more information, see [IBM Cloud Kubernetes Service VPC cluster architecture](https://cloud.ibm.com/docs/containers?topic=containers-service-archarchitecture_vpc).

All components are managed and owned by IBM and run in the IBM Cloud account. Each cluster is running in its own VPC and separated from other clusters.

The Code Engine control plane runs the components that are shared among all Code Engine users and make the Kubernetes cluster a true multi-tenant system. The control-plane consists of four microservices that are deployed on it.



Table 1. Code Engine control-plane microservices

 Component Purpose 

 Resource broker Creates and deletes Code Engine project resources in the IBM Cloud resource controller and requests the placement of the project on a shard. 
 Project placement controller Selects a shard and requests the creation, deletion, and isolation of the project on the shard. 
 API server Provides the target information (KUBECONFIG file) for the selected project. It also performs IAM access policy checks and writes audit records.
* [Learning about CIS architecture and workload isolation](https://cloud.ibm.com/docs/cis?topic=cis-compute-isolation)
* [Securing your data in CIS](https://cloud.ibm.com/docs/cis?topic=cis-mng-data)
* [Auditing events for CIS](https://cloud.ibm.com/docs/cis?topic=cis-at_events)
* [IAM and Activity Tracker actions by API](https://cloud.ibm.com/docs/cis?topic=cis-at_iam_CIS)
* [Managing security and compliance with CIS](https://cloud.ibm.com/docs/cis?topic=cis-manage-security-compliance)



* [Setting up Terraform for CIS](https://cloud.ibm.com/docs/cis?topic=cis-terraform-setup-cis)



* Reference



* [CIS API](https://cloud.ibm.com/apidocs/cis)
* CLI reference



* [CIS CLI change log](https://cloud.ibm.com/docs/cis?topic=cis-cli-change-log)
* [CIS CLI reference](https://cloud.ibm.com/docs/cis?topic=cis-cis-cli)



* [Terraform](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cis)
* CIS use cases



* [Accessing your Cloudant database through CIS](https://cloud.ibm.com/docs/cis?topic=cis-access-cloudant-through-cis)
* [Edge functions use cases](https://cloud.ibm.com/docs/cis?topic=cis-edge-functions-use-cases)



* [Understanding your responsibilities when using CIS](https://cloud.ibm.com/docs/cis?topic=cis-responsibilities-cis)
Subnets and IPs docs 

IBM has three types of subnets (Primary, Secondary, and Global IP), with each subnet providing IP addresses to resources in different ways.

 Developer tools 

[Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/subnet)

 Recommended content 

[Getting started with subnets and IPs Get started setting up subnets and IPs.](https://cloud.ibm.com/docs/subnets?topic=subnets-getting-started)[About subnets and IPs Learn specific terminology for the types, and uses, of subnets. Knowing their intended use helps you understand how best to use them in your cloud infrastructure.](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ips)[Ordering secondary subnets and global IP addresses Secondary subnets provide additional, independent IP addresses for your compute resources and are available until canceled.](https://cloud.ibm.com/docs/subnets?topic=subnets-order-subnets)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>!
For more information, see [Deploying Red Hat OpenShift on IBM Cloud resources across clusters with Satellite configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig). 







 Satellite location components 

A location is a representation of an environment in your on-premises data center that you want to bring IBM Cloud services to so that you can run workloads in your own environment. You create the location based on at least three separate zones of your backing infrastructure environment, and attach host machines from across these zones in your infrastructure to the location. The [Satellite console](https://cloud.ibm.com/satellite/locations) provides a single pane of glass to manage the workloads that run across the infrastructure in your locations. For more information, see [Planning your infrastructure environment for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plan) and [Setting up Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).



 Infrastructure 



 Satellite location-underlying infrastructure 

You are responsible for providing the underlying infrastructure components in your on-premises data center that the Satellite location uses. These components include:



* Virtual and bare metal servers
* Virtual storage
* Virtual network
* Hypervisor
* Physical servers and memory
* Physical storage
* Physical network and devices
* Facilities and data centers







 Satellite infrastructure components 

The following table describes Satellite infrastructure components that run on top of the underlying infrastructure that you provide.



Table 4. Overview of the Satellite location infrastructure components
Overview of the Satellite location infrastructure components

 Infrastructure components Description 

 Hosts Hosts are machines that reside in your infrastructure provider, across at least three separate zones, and must [meet the minimum host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). After attaching the hosts to a Satellite location, you assign the hosts to the Satellite clusters to provide the computing power to run your application workloads.
* [Cloud Shell](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-getting-started)*
* [Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage)*
* [Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started)*
* [Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started)*
* [Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started)
* [Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)*
* [Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-getting-started)*
* [Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started)*
* [Hyper Protect DBaaS for MongoDB](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-mongodb)*
* [Hyper Protect DBaaS for PostgreSQL](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-postgresql)
* [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-getting-started-tutorial)*
* [Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-security)*
* [Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adoptionadoption_acc_settings)*
Getting started with virtualization 

You can use the virtualization solution to run multiple virtual machines in a single dedicated environment within IBM Cloud® Classic Infrastructure. Virtual machines that run on the IBM Cloud network can integrate with other physical and virtual devices on the network and can be managed through both the console and API. Running virtual machines on the IBM Cloud proprietary architecture and automated platform offers high levels of stability suitable for enterprise-level virtualization, and virtualization on a smaller scale.



Table 1. Getting started with Virtualization

 Get started 

 __ 1. For more information about virtualization options, see [Citrix XenServer](https://cloud.ibm.com/docs/virtualization?topic=virtualization-what-is-citrix-xenserver-), [Hyper-V](https://cloud.ibm.com/docs/virtualization?topic=virtualization-what-is-hyper-v-), [Virtuozzo](https://cloud.ibm.com/docs/virtualization?topic=virtualization-what-is-virtuozzo-), and [VMware](https://cloud.ibm.com/docs/vmware?topic=vmware-vmware-getting-started). 
 __ 2. [Set up a hypervisor](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-hypervisor). [Setting up a virtual machine Network](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-virtual-machine-network) is an important part of this process. 
 __ 3.
Learning about IBM Cloud for Education Applications Lab architecture and workload isolation 

IBM Cloud for Education Applications Lab architecture describe its components and how customers' workloads are isolated.



  IBM Cloud for Education Applications Lab Architecture 

The following image shows the components can be managed by you. All virtual machines (VM) are accessed by VM's public IP address. You can choose one of desired secure protocol to access, such as SSH and RDP.

![workflow Isolation](https://cloud.ibm.com/docs-content/v1/content/b6c5dbb443b797203b2824b05472cac5ae8635da/cloud-for-education/isolation.png)





  IBM Cloud for Education Applications Lab Workload Isolation 

Your workloads are running inside your own VM. Strong isolation among VMs are enfored by hypervisor. VM can be only accessed by VM's public IP address, and your username and random password is used to perform authentication.
Service and infrastructure availability by location 

IBM Cloud® makes it easier for you to implement, host, and scale services, infrastructure, and apps so you can focus on your application logic and application design. IBM Cloud's global network of locations provides three tiers of regions:

multizone regions(MZR),single-campus multizone regions, anddata centers. To achieve low application latency, deploy your apps in a region near your customers. For details about the available IBM Cloud regions and data centers for specific products, review the following sections.

IBM provides SDKs and APIs for all services that are general availability. Check out the reference docs in the [API & SDK reference library](https://cloud.ibm.com/docs?tab=api-docs).

Not all services and infrastructure are available for purchase in every IBM Cloud location.



 Services 

Some services are available to purchase in a location, but that service's data might be hosted in a different location. The following table shows the services that are provided by IBM. For the full list of resources that are available, see the [catalog](https://cloud.ibm.com/catalog) in the IBM Cloud console.

Services that are hosted globally create resources that operate across multiple locations. For example, with IBM Cloud Object Storage, you can choose to deploy data in a single data center, or even a combination of locations by selecting the endpoint where your application sends REST API requests. For more information about the global network of locations, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).

Americas

Europe

Asia Pacific



Table 1. Service availability - Americas
Use the buttons for the countries to change the context of the table. This table has row and column headers. The row headers identify the service. The column headers identify where that service is located. To understand where a service is located in the table, navigate to the row, and find the for the location you are interested in.

 Service Dallas Washington DC Toronto Sao Paulo 

 API Connect !
[Setting up virtualization on a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-location)Setting up virtualization on a Satellite location

You can set up your Bare Metal Servers to use Red Hat OpenShift virtualization in your Satellite location. By using virtualization, you can provision Windows or other virtual machines on your Bare Metal Servers in a managed Red Hat OpenShift space.

Satellite



* 2023-06-19



[AWS, Azure, GCP, and OCI workloads to IBM Cloud VPC migration with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-cloud-rackware)AWS, Azure, GCP, and OCI workloads to IBM Cloud VPC migration with RMM

The RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming from other cloud service providers (AWS, Azure, GCP, and OCI (bare metal)) to IBM Cloud® virtual server instance migration, which allows the adoption of the existing capabilities of IBM Cloud. Its intuitive GUI allows you to move the OS, application, and data from other cloud service providers to IBM Cloud VPC instances.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 45 minutes
* 2022-11-23



[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
Core <br><br> * [VPC infrastructure services](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment)[1]<br><br><br> <br><br> * [Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-cli)<br><br><br> 
 Containers <br><br> * [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-cli)<br> * [Container Registry](https://cloud.ibm.com/docs/container-registry-cli-plugin?topic=container-registry-cli-plugin-containerregcli)<br><br><br> <br><br> * [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-cli)[2]<br> * [Container Registry](https://cloud.ibm.com/docs/container-registry-cli-plugin?topic=container-registry-cli-plugin-containerregcli)<br><br><br> 
 Networking <br><br> * [VPC infrastructure services](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment)<br> * [Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-cli-plugin-dl-cli)<br> * [Transit Gateway](https://cloud.ibm.com/docs/tg-cli-plugin?topic=tg-cli-plugin-transit-gateway-cli)<br><br><br>
[Deploying server pools and origins in a single region](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-pools-origins)Deploying server pools and origins in a single region

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),Building infrastructure



* 2021-06-10



[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



[Microsoft Hyper-V VM to IBM Cloud VPC migration with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-vmware-vsi)Microsoft Hyper-V VM to IBM Cloud VPC migration with RMM

The RackWare Management Module (RMM) solution simplifies the overall migration process of moving the operating system, applications, and data from Microsoft Hyper-V VM to IBM Cloud® Virtual Servers for Virtual Private Cloud. The migration can occur either over the public or private interface of the compute resource. The only requirement is that RMM is able to access both the source and target server over SSH.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1
At that point you can decide to evaluate all the technologies or to jump to one of the specific standalone sections like [Terraform](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-app-deployvpc-app-deploy-terraform) or [Ansible](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-app-deployvpc-app-deploy-ansible).



 Objectives 



* Understand operating system software provided by IBM.
* Utilize manual steps for updating the operating system software and installing new software.
* Understand how to use the IBM Cloud CLI, Terraform and Ansible to automate the provisioning of resources and software installation.



In this tutorial, you will deploy the configuration introduced in another 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). You will provision a frontend server accessible from the public Internet talking to a backend server with no Internet connectivity.

Zoom

![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

!
The CE_SERVICES environment variable contains information that you can use to interact with a service instance. This environment variable points to a JSON object that contains key value pairs. These key value pairs represent each type of service that is bound to your application. The key is the name of the service type, such as cloud-object-storage, and the value is an array of credentials for bound service instances of that type.

The following example illustrates a CE_SERVICES variable:

{
"appid": [
{
"credentials": {
"apikey": "xxxxxx",
"appidServiceEndpoint": "https://us-south.appid.test.cloud.ibm.com",
"clientId": "abcdabcd-xxxxxxxx",
"discoveryEndpoint": "https://us-south.appid.test.cloud.ibm.com/oauth/v4/xxxxxxxx/.well-known/openid-configuration",
"iam_apikey_description": "Auto-generated for key crn:v1:staging:public:appid:us-south:a/abcdabcd719f45b98a931f6e20db1bd8:xxxxxxxx:resource-key:abcdabcd-xxxxxxxx",
"iam_apikey_name": "ce-service-access-abcd",
"iam_role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
"iam_serviceid_crn": "crn:v1:staging:public:iam-identity::a/abcdabcd719f45b98a931f6e20db1bd8::serviceid:ServiceId-6d7087e5-0611-4240-9e46-af8a4c15cba4",
* [vCenter Server overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [Architecture pattern for multisite NSX-T topologies](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-arch-pattern-overlays-multi-site)
* [Multisite configuration for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_multisite)