vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For VMware vSAN, it is configured by using an all–flash configuration. This design allows for several configuration options, including 2U and 4U chassis, various numbers of disks, and various disk sizes. All configurations use two vSAN disk groups, with one solid-state disk (SSD) for cache and one or more SSDs for capacity. All drives that are allocated for vSAN consumption are configured in single-disk RAID 0.

For more information about the supported configurations, see [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom).





 Shared File-level storage across hosts 

If you use shared file-level storage, a 2 TB NFS share is attached to the hosts that comprise the initial VMware cluster. This share, which is known as the management share, is used for management components, such as vCenter Server, Platform Services Controller, and VMware NSX.

The storage is attached by using the NFS v3 protocol at a 4 IOPS/GB level from IBM Cloud.

Zoom

![NFS shares that are attached to VMware deployment](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vcsv4radiagrams-ra-nfs-shares.svg)

Figure 4. NFS shares that are attached to VMware deployment

You can allocate and mount more file shares across all hosts for your workloads at the time of purchase or later within the console. You can select from the available IBM Cloud Endurance file storage capacity options and performance tiers in the corresponding IBM Cloud data center. All shares are attached by using the NFS v3 protocol. IBM Cloud Endurance file storage includes provider-managed encryption of data at rest (AES-256 encryption), and is backed up by all-flash storage.

The 10 IOPS/GB performance tier is limited to a maximum capacity of 4 TB.
Planning for migration 

To get the best results from your VPC migration, spend time analyzing your classic environment and learning how the VPC+ tool will handle different components of your environment. Use the following information to start planning your migration journey.



 Preparing for differences in classic and VPC environments 



Table 1. Review tasks

 Task Details 

 Review [quotas and service limits](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=vpc-quotas) Ensure that your IBM Cloud® classic infrastructure components that you are migrating are within the VPC quotas and service limits. 
 Review [migration considerations](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=wanclouds-vpc-plus-migration-considerations) Review information about specific infrastructure components. 
 Review [comparisons between infrastructure environments](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-compare-infrastructure) Some components of your classic infrastructure might not exist in VPC such as dedicated virtual servers, available server profiles, and IPv6 addressing. 
 Review [VPC pricing](https://www.ibm.com/cloud/vpc/pricing) Pricing might vary between IBM Cloud classic and VPC infrastructures. 







 Granting permissions and access 



Table 2. Permissions and access tasks

 Task Details 

 Permissions for classic and VPC Contact your account administrator for permissions. 
 Grant access between VPC Image Services and IBM Cloud Object Storage Grant this access if you want to migrate your primary boot volume, secondary volumes, and images from classic infrastructure. For more information, see [Granting access between services](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq). 







 Gathering IBM Cloud account information 



Table 3. Required IBM Cloud account information

 Account information Details 

 Username Create a username specifically for VPC+ Cloud Migration. In the IBM Cloud console, select Manage > Access (IAM) > Users. Select Users and then click Invite user, supplying the email address name of the user.
* The VPN route is pushed to your VPN client. If your VPN client already has a route with the same destination, the route "push" fails and the traffic cannot reach your VPN server. You must address the route conflict and then re-connect the VPN client. A common issue is if you add a VPN route with destination 0.0.0.0/0 on a split-tunnel-mode VPN server, and this route needs to be pushed to your VPN client. Typically, the VPN client already has a route with destination 0.0.0.0/0; therefore, this VPN route will conflict with your VPN client route. To avoid conflict, use a full-tunnel-mode VPN server, or remove the route 0.0.0.0/0 on your host.



No matter which tunnel mode you choose, you must use the API /vpn_servers/{id}/routes to define how the VPN server forwards the traffic from the VPN client. For example, if you want the internet traffic from the client to go through the VPN tunnel, a 0.0.0.0/0 route must be configured using the VPN service routes API.





 Supported VPN client software 

You must provide VPN client software for your users. The following client software versions are verified for use:



* For macOS Catalina and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-macos), OpenVPN Connect v2, and Tunnelblick 3.8.4
* Windows 8 and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-windows), OpenVPN Connect v2
* RHEL 7.x and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-linux), OpenVPN Connect v2, and OpenVPN command-line client (version 2.4.4 and later)
Deploying an Oracle database in IBM Power Systems Virtual Servers 

Learn how to deploy an Oracle database in a Power® Systems Virtual Server instance.

The following videos do not capture the latest updates to Power Systems Virtual Server. You might notice significant differences in functions between what is shown in the video and what's currently available.



  Modernizing an Oracle database 

For details, see this video on [deploying Oracle database in the Power Systems Virtual Server](https://ibm.biz/HybridOracleDBonPOWER9-Part1).





  Building a new Oracle environment from a custom AIX image 

For details on how to export a custom AIX image on-premises and redeploy it in the Power Systems Virtual Server to build a new Oracle environment, see this video on [building a new Oracle environment from a custom AIX image](https://ibm.biz/HybridOracleDBonPOWER9-Part2).
You might receive an email that's indicating that [maintenance](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance) is required on a system that is hosting your virtual server. Your virtual server might need to be migrated as part of the infrastructure [maintenance](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance).
* An unplanned host outage. The following actions apply if an unexpected host failure occurs:



* The virtual servers that were running on the host are stopped when the outage is detected.
* The virtual servers are automatically reassigned and restarted on a different compute host in the same multi-region zone.
* The virtual servers that are restarted use the same boot volume, and the same data volumes as the original virtual server.
* The virtual server that was restarted is assigned the same floating IP, static IP, and dynamic IP addresses on the new node.
* If the virtual server cannot be scheduled to run on another compute node, it is placed in a FAILED state.









 Can I use an encrypted image? 

Yes, you can encrypt a supported custom image with LUKS encryption and your own passphrase. For more information, see [Creating an encrypted custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-encrypted-custom-image). When your image is encrypted and imported to IBM Cloud VPC, you can use it to provision virtual server instances.





 Can I use my own license for a custom image that I create? 

Yes, for certain versions of Red Hat Enterprise Linux (RHEL) and Windows operating systems, you can bring your own license (BYOL) to the IBM Cloud VPC when you import a custom image. These images are registered and licensed by you. You maintain control over your license and incur no additional costs by using your license. For more information, see [Bring your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about).





 How does IBM handle maintenance?
Every location is securely connected to the IBM Cloud multizone region that manages your location by using the Satellite Link component. The link component runs in your control plane and is the main gateway for any communication between your Satellite location and IBM Cloud. If your Satellite location cannot communicate with the IBM Cloud multizone region anymore, your existing location workloads will continue to run, but you cannot make any configuration changes or roll out updates to the services and apps that run in your location.

For an overview of your options to make the Satellite control plane more highly available to prevent connectivity issues with your IBM Cloud multizone region, see [High availability for IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-ha).
* Does IBM support third-party and open source tools that I use with Satellite?

See the [IBM open source and third-party policy](https://www.ibm.com/support/pages/node/737271).
* Why can't I install extra software like vulnerability scanning tools on my host?

To add your own server as a host in your Satellite location, the host must meet certain [compute, storage, networking, and system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). These requirements specify the Red Hat software packages that must be installed on the Red Hat Enterprise Linux hosts. Other software packages that make modifications to the hosts, including vulnerability scanning tools such as McAfee or Qualys, cannot be installed on the hosts. But you can install read-only software such as OpenSCAP on the hosts before attaching them to your location.

The reasons that you cannot install extra software on the hosts relate to [IBM 's responsibilities](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilities) to manage multiple aspects of the Satellite hosts for you, such as installation, access, and maintenance.

Installation: The Satellite team tries to keep the host requirements to a minimal level so that many servers across infrastructure providers can meet the requirements to become Satellite hosts.
Step 4. Launch the web UI 

After you provision an instance of the IBM Cloud Security and Compliance Center Workload Protection service, and configure a monitoring agent for your node, you can view, monitor, and manage data through the service's web UI.

You launch the web UI within the context of the IBM Cloud Security and Compliance Center Workload Protection instance, from the IBM Cloud UI.

Complete the following steps to launch the monitoring UI:



1. Log in to your IBM Cloud account.

Click [IBM Cloud dashboard](https://cloud.ibm.com/login) to launch the IBM Cloud dashboard.

After you log in with your user ID and password, the IBM Cloud Dashboard opens.
2. In the navigation menu, select Resource List.
3. Select Security.

The list of instances that are available on IBM Cloud is displayed.
4. Select one instance. Then, click Open dashboard.

The Web UI opens.







 Step 5. Secure your environment 

See the following table for tasks that you can run to secure your environment:



Table 1. Tasks to secure your environment

 Action Descripion 

 [Integrate scanning into your CI/CD Pipeline](https://docs.sysdig.com/en/docs/sysdig-secure/scanning/integrate-with-cicd-tools/) You can integrate scanning into your CI/CD Pipeline to analyze images that are available on the CI/CD worker nodes. 
 [Configure a notification channel](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-notificationsnotifications_create) You can configure a notification channel to get notified about events, anomalies, or security incidents that require attention. 
 [Scan container images](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-scan_kube) You can scan container images for vulnerabilities, and other violations.
Creating a job from images in IBM Cloud Container Registry 

Create your job configuration that uses an image in IBM Cloud® Container Registry. You can create a job from the console or with the CLI.

Before you begin



* You must have an image in Container Registry. For more information, see [Getting started with Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started). Or, you can build an image from [repository source](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-code) or from [local source](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-local-source-code).
* Verify that you can access the registry. See [Setting up authorities for container registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registryauthorities-registry).



Interested in configuring your project such that all users of the project can store and access images in Container Registry without having to manually create registry secrets? With sufficient permissions, you can configure this default registry access on a per location (region) basis. If you don't have sufficient permissions to perform these actions, you can use this page to help you understand the required permissions. See [Configuring project-wide settings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrations).



 Creating a job that references an image in Container Registry with the console 

Create a job configuration that uses an image in Container Registry by using the Code Engine console.

Code Engine can automatically pull images from a Container Registry namespace in your account. To pull images from a different Container Registry account or from a private Docker Hub account, see [Create a job from images in a private registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-private).



1.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Code Engine ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 







 Container services 

IBM Cloud Container Registry
: IBM Cloud Container Registry generates platform services logs that are displayed in your logging instances. For informataion about the locations where the automatic collection of Container Registry service logs is enabled, see [Analyzing logs for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_logsregistry_logs_locations).

IBM Cloud Kubernetes Service
: You can choose the logging instance where you want to collect IBM Cloud Kubernetes Service service logs.

IBM Cloud Satellite
: You can monitor IBM Cloud Satellite® service logs through the logging instance that is configured with service platform logs in the same region that your Satellite location is managed from.

Red Hat OpenShift on IBM Cloud
: You can choose the logging instance where you want to collect Red Hat® OpenShift® on IBM Cloud® service logs.





 Database services 

The following tables list the locations where automatic collection of database service logs is enabled. You can monitor logs through the Log Analysis instance that is available in the same location as your database resources, if you enable 1 instance in this location to host service platform logs.
2. Click Project settings > Integrations.



2. If the status of Service binding operations is Configured, click Remove configuration to remove the operator secret. You are asked to confirm that you want to delete the operator secret.



When you receive a message that service binding operations are removed, the status for service binding operations is Not configured.

If you remove configured service binding operations from the Integrations page, any existing service bindings remain. This means that for existing service bindings, when you run applications, run new application revisions, or run jobs, the bound app or job uses the existing service bindings and their credentials. However, new service bindings cannot be created without sufficient permissions, and existing bindings cannot be deleted.

If the operator secret doesn't exist, it is automatically created when any one of the following scenarios is true.



* When the next service binding is created for the project (from the console or CLI).
* When you configure service binding operations from the Integrations page.
* When you run the project update command.









 Configuring project-wide access to Container Registry 

Use the Integrations page in the console to configure settings to set up and manage registry access to images in IBM Cloud Container Registry so that all users of a specific Code Engine project can store and access images in Container Registry without having to manually create registry secrets.

When you use project integrations to control your Code Engine managed access to Container Registry, Code Engine doesn't use the identity of the user that is logged in. Instead, Code Engine automatically creates registry access that is used specifically for accessing images in IBM Cloud Container Registry. With sufficient permissions, you can configure this default registry access on a per location (region) basis. For more information about Container Registry regions, see [IBM Cloud Container Registry regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions).



 What access permissions are required for Code Engine managed access to IBM Cloud Container Registry? 

The user of this Integrations page must have the following IBM Cloud® Identity and Access Management (IAM) access policies that are assigned to your user account to successfully configure registry access for all users of the project.
* Sao Paulo (br-sao)
* Sydney (au-syd)
* Tokyo (jp-tok)
* Toronto (ca-tor)
* Washington (us-east)



You can create a VPE gateway for your local Container Registry service only. For VPE gateways created after 11 November 2022, you can pull images from any other Container Registry region by using the public hostnames, such as uk.icr.io. For VPE gateways created before 11 November 2022, if you want to connect to IBM Cloud Container Registry in another region, you must enable classic access, see [Creating a classic access VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructurecreate-a-classic-access-vpc) and use private hostnames, such as private.uk.icr.io.





 Setting up a VPE for IBM Cloud Container Registry 

When you create a VPE gateway by using the CLI or API, you must specify the

cloud resource name (CRN)of the region that you want to connect to Container Registry. Review the following table for the available regions and CRNs to use to create your VPE gateway.

You can create VPE gateways in the following locations: ap-north, ap-south, br-sao, ca-tor, eu-central, jp-osa, uk-south, us-south, and us-east (global registry).



Table 1. Region availability and cloud resource names for connecting Container Registry over private IBM Cloud networks

 Registry region Cloud resource name (CRN) 

 ap-north crn:v1:bluemix:public:container-registry:jp-tok:::endpoint:jp.icr.io 
 ap-south crn:v1:bluemix:public:container-registry:au-syd:::endpoint:au.icr.io 
 br-sao crn:v1:bluemix:public:container-registry:br-sao:::endpoint:br.icr.io
You can view the value of retain-untagged for each retention policy by running the [ibmcloud cr retention-policy-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_list) command.

For more information, see [Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).





 30 April 2020 

ibmcloud cr image-prune-untagged command is available
: The ibmcloud cr image-prune-untagged command deletes all [untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_untagged) images in your Container Registry account.

For more information, see [ibmcloud cr image-prune-untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_image_prune_untagged) and [Clean up your namespaces by deleting untagged images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_images_untagged).





 16 April 2020 

You can use private network connections to securely route your data in Container Registry
: If you use cloud-based services for production workloads, you can use a secure private connection so that you ensure that you adhere to any compliance regulations. You can use IBM Cloud service endpoints to connect to IBM Cloud services over the private IBM Cloud network.

For more information, see [Securing your connection to Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_private) and [IBM Cloud Container Registry architecture and workload](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_architecture).

ibmcloud cr private-only command is available
: You can use the ibmcloud cr private-only command to prevent image pulls or pushes over public network connections for your account.
However, the build in Code Engine is not running on your local system, but instead in the Code Engine system. This build in Code Engine gives you several advantages.



1. You are not required to install software, such as Docker Desktop, locally.
2. You can use the resources that are provided by Code Engine. For example, you can take advantage of the speed of IBM Cloud to push and pull container registry images for you.
3. You can build your container image by using the [Buildpacks build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy) instead of Dockerfile, which detects your sources for various languages and automatically builds a container out of it.
4. If you have an image that was built with a non-Intel based processor, Code Engine can rebuild it for you.







 Why do images that are built by using a Code Engine buildpacks build show up in my container registry as being more than 15,000 days old? 

Buildpacks create [reproducible builds](https://buildpacks.io/docs/reference/reproducibility/) of container images. When the same sources are built with the same version of the build tool, then the produced image has the same identifier. The identifier of an image is based not only on the files that are inside the image, but also based on dates in the metadata of the image. Part of this metadata is the creation timestamp. The [Buildpacks community](https://buildpacks.io/community) set all these dates in the image metadata to a fixed timestamp in 1980 to achieve reproducibility.





 Why do images that are built with non-Intel processors not work with Code Engine? 

If you have an image that exists in a container registry and the image was built with a non-Intel based processor, Code Engine cannot run your container image. Code Engine uses Intel-based processing. You can build your own image if you use Intel processing (x86 processor). You can also choose to let Code Engine handle the build process for you.