vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Adding a vSphere ESXi host For more information, see [Adding ESXi servers to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers). 
 Removing a vSphere ESXi host For more information, see [Removing ESXi servers from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_removingservers). 
 Bare metal server firmware patching For more information, see [What if my bare metal server has out-of-date firmware?](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-faqwhat-if-my-bare-metal-server-has-out-of-date-firmware-) 
 vSphere ESXi host patching For more information about using VMware Update Manager (VUM) to update not only vSphere ESXi hosts but a number of other vCenter Server instance components, see [VMware Update Manager introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-introvum-intro).
Configuring project-wide settings 

By using the Project settings pages in the console, you can review and configure settings that apply to a specific project. Learn how to work with project-wide integrations.



 What are project-wide integrations and why use them? 

Use the Integrations page in the console when you want to configure the project-wide settings in such a way that all users of the project can perform certain actions. With sufficient permissions, you can configure service binding operations or configure access to images in IBM Cloud Container Registry from a single page. If you don't have sufficient permissions to perform these actions, you can use these pages to help you understand the required permissions.

When you set project-wide settings with the Integrations page, Code Engine automatically sets up the necessary credentials so that Code Engine can perform service binding operations or access Container Registry for you, instead of using a personal user ID. You can view details about what Code Engine does for you when you configure service binding operations or configure access to Container Registry. These details include information about the service ID and its access policies, the API key, and secret.



* If you want to configure settings for service binding operations, see [Configuring service binding operations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrationsprojectintegration-sb).
* If you want to configure settings to control Code Engine managed registry access to IBM Cloud Container Registry, see [Configuring project-wide access to Container Registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrationsprojectintegration-cr).







 Configuring project-wide service binding operations 

Use the Integrations page in the console to configure settings for service binding operations so that all users of a specific project can create and delete bindings without having to assign all necessary privileges to their personal user IDs.

In Code Engine, service binding operations, which include creating, and deleting service bindings, are not performed with the identity of the user that is logged in.
* [Before you begin](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-smart-cardsrotate-master-key-smart-cards-prerequisites)
* [Rotating master keys using smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-smart-cardsrotate-master-key-smart-cards-steps)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-smart-cardsrotate-master-key-smart-cards-next)



[Rotating master keys by using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-cli-recovery-crypto-unitrotate-master-key-cli-recovery-crypto-unit)



* [Rotating master keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-cli-recovery-crypto-unitrotate-master-key-cli-recovery-crypto-unit-steps)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-cli-recovery-crypto-unitrotate-master-key-cli-recovery-crypto-unit-next)



[Rotating master keys by using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-master-key-cli-key-partrotate-master-key-cli-key-part)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-mechanismsnext-enable-mechanisms)







 Adding or removing crypto units 

[Adding or removing crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-unitsadd-remove-crypto-units)



* [Adding crypto units to an existing service instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-unitsadd-crypto-units)
* [Removing crypto units from an existing service instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-unitsremove-crypto-units)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-unitsadd-remove-crypto-units-next)







 Enabling or adding failover crypto units after you provision a service instance 

[Enabling or adding failover crypto units after you provision a service instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-add-failoverenable-add-failover)



* [Using the IBM Cloud CLI](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-add-failoverenable-add-failover-cli)
* [Using the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-add-failoverenable-add-failover-management-utilities)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-enable-add-failoverenable-add-failover-next)
Recovering from a regional disaster 

IBM Log Analysis is a highly available, multi-tenant, regional service. In this topic, you can learn more about Log Analysis's availability and disaster recovery strategies, what you need to plan for, and what you need to do if you need to recover from a regional disaster.



 Prereqs 



* Learn about your responsibilities in the event of a disaster. See [Disaster and recovery](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-shared-responsibilitiesdisaster-recovery).
* Learn about disaster recovery (DR). See [Overview](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-ha_dr_stepsha_dr_steps_ov).







 Planning for a DR scenario 

The steps in this section assume that you have a list of all IBM Log Analysis instances that are provisioned in a region per resource group; access reports for each instance; a current export of the logging configuration resources per instance; and a list of log sources per region that include information on the logging instance where logs are sent and how those logs are sent, for example, by configuring an agent. You should keep track of any agent versions too and any custom logging resources such as views, boards, screens, parsing templates that might be required to manage those logs.

Consider using access groups to manage permissions to work with logging instances. In the event of a DR situation, you can quickly add permissions for users and service IDs per access group and accelerate recovery time.



* To get the access report for an instance, go to the Observability UI, and in the Logging section, select 1 instance. Select the 3 dots icon and click Access report. Then, save it in a version control tool.

The report includes a list of users, access groups, and service IDs that have access to the selected resource. You must have the Administrator role on the selected resource to view the report.

You can download the report as CSV or as JSON.

Generate an access report everytime permissions to work with logging instances change in the account.

You can use terraform to manage IAM permissions.
In the IBM Cloud console, click Manage > Access (IAM), and select Access Groups.
2. Select the name of the access group that you want to create a rule for. This action opens the group Details page.
3. Select Dynamic rules.
4. Click Add rule.
5. Enter the information from your IdP that is dynamically provided for you on the Add rule page. The following list provides details for each required field.



You can think of an access group rule as a key:value pair. The key is what you add in the Add users when field, and the value is what you enter in the Values field.

For more information about the fields that are used to create dynamic rules, see [IAM condition properties](https://cloud.ibm.com/docs/account?topic=account-iam-condition-properties).





 Setting up rules by using Terraform 

Before you can set up rules by using Terraform, make sure that you have completed the following:



* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform. For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).



Dynamic rules are created by setting conditions that must be matched by the data that is configured within the IdP and passed in with a user's federated ID during login. You can add more than one condition for a rule. All conditions set in the rule must be met for a user to be added to an access group.

To create a rule by using Terraform, follow these steps:



1.
: The maximum number of web applications that you can create in a resource group.

Max Instances Per App
: The maximum number of instances of the same web application that you can create in a resource group.

Max App Instance Memory
: The maximum amount of memory allowed for each individual web application instance.

Total App Memory
: The maximum amount of memory allowed for each individual web application.

Max Service Instances
: The maximum service instances per resource group. Service instances are different from web application instances.



 Using the CLI to check your quotas 

If you're not sure what your resource group quotas are, you can check by using the IBM Cloud CLI. The CLI is the only way to check your account's resource group quotas. Before you can check your quotas, you need the [IBM Cloud CLI installed](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).

To check your quotas, type the following command into the CLI:

ibmcloud resource quotas

For more information about using the CLI to check your quotas, see [ibmcloud resource quotas](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_quotas).
If you are running a Java PKCS #11 application using the SunPKCS11 provider on the IBM Z (s390x) platform, make sure that you use the latest IBM Semeru JVM and specify the -Xjit:noResumableTrapHandler Java option when starting your application. You can download the latest s390x version of the IBM Semeru JVM by changing the Architecture filter field to s390x on the [IBM Semeru Runtime Downloads page](https://developer.ibm.com/languages/java/semeru-runtimes/downloads/?license=IBM).





 What's next 



* Check out the tutorial that shows how to

[use Hyper Protect Crypto Services PKCS #11 library for Oracle Database Transparent Database Encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-tde-pkcs11) to better understand the PKCS #11 library usage.
* Check out the

[PKCS #11 API reference](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-pkcs11-api-ref) for the detailed information about cryptographic functions.
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-prepare-management-utilitiesprepare-management-utilities-next)



[Initializing service instances with smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilitiesinitialize-hsm-management-utilities)



* [Before you begin](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilitiesinitialize-hsm-management-utilities-prerequisites)
* [Loading the master key from the smart cards](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilitiesload-master-key-management-utilities)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilitiesinitialize-crypto-utilities-management-utilities-next)



[Initializing service instances using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unitinitialize-hsm-recovery-crypto-unit)



* [Initializing service instances](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unitinitialize-hsm-recovery-crypto-unit-steps)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unitinitialize-hsm-recovery-crypto-unit-whats-next)
(https://cloud.ibm.com/docs/containers?topic=containers-access_webhooksaccess_webhooks_create_controllers)
* [What are the best practices for using webhooks?](https://cloud.ibm.com/docs/containers?topic=containers-access_webhookswebhook-best-practice)
* [What other types of apps use admission controllers?](https://cloud.ibm.com/docs/containers?topic=containers-access_webhooksaccess_webhooks-app-use-controllers)



* [Setting up admission controller webhooks](https://cloud.ibm.com/docs/containers?topic=containers-access_webhooksconfigure-webhooks-122)



* [I need help with a broken webhook. What can I do?](https://cloud.ibm.com/docs/containers?topic=containers-access_webhooksaccess_webhooks-help)



[Accessing private clusters by using the WireGuard VPN](https://cloud.ibm.com/docs/containers?topic=containers-cluster-access-wireguardcluster-access-wireguard)





 Managing the cluster and worker node lifecycle 

[Adding worker nodes and zones to clusters](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd_workers)



* [Adding worker nodes by resizing an existing worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersresize_pool)
* [Adding worker nodes in VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-add_workersvpc_pools)



* [Creating a new worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersvpc_add_pool)
[Retrieve your service and authentication credentials to work with keystores in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-uko-api).
2. Edit the connection to an external keystore by making a PATCH call to the following endpoint.

https://uko.<region>.hs-crypto.cloud.ibm.com:<port>/api/v4/keystores/<id>

Replace <id> with the ID of your keystore.

For detailed instructions and code examples about using the API method, check out the [Hyper Protect Crypto Services Unified Key Orchestrator API reference doc](https://cloud.ibm.com/apidocs/ukoupdate-keystore).







 What's next 



* To find out how to connect to an external keystore, check out [Connecting to external keystores](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-connect-external-keystores).
* To find out how to disconnect from an external keystore, check out [Disconnecting from external keystores](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-disconnect-external-keystores).
IBM Cloud Metrics Routing 

Use IBM Cloud Metrics Routing to configure how to route platform metrics in your IBM Cloud account.

 Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/metrics-router/metrics-router-v3)[CLI reference](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-metrics-router-cli)

 Recommended content 

[Understanding IBM Cloud Metrics Routing Learn about how to manage metrics by using IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-about)[Getting started with IBM Cloud Metrics Routing Use the IBM Cloud Metrics Routing CLI to configure your account to manage metrics.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-getting-started)[Planning your environment Plan how to configure the account to manage metrics.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-planning)[See what's new Read about the latest changes to IBM Cloud Metrics Routing. ](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-metrics-router-release-notes)

 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>!
When a job instance completes with a nonzero return code, Code Engine restarts the job instance. With Code Engine, you can specify to limit the number of retries to avoid restarting failed job instances.





 Running batch jobs 

Whether your code exists as source in a local file or in a Git repository, or your code is a container image that exists in a public or private registry, Code Engine provides a streamlined way for you to run your code as a job.

You can create and run batch jobs in Code Engine in the following ways:



* Run an existing container image. Create a job and provide a reference to your image to use when you submit the job. For an example, see [Create and run a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-startedfirst-job).
* Start with source code. If you are starting with source code that is located in a Git repository or on your local workstation, you can point to the location of your source and Code Engine takes care of building the image for you. See [Create a job from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-code) and [Create a job from local source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-local-source-code).



For more information, see [Working with jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan).





 Scaling 

A job in Code Engine (batch job) consists of one or more job instances. While job instances run independent of each other, they run the same code. Suppose you have a database with 100 records to analyze. You can run your job such that each job instance analyzes 10 records each. For example, the first job instance analyzes records 0 - 9, the second job instance can analyze records 10 - 19, and so on.
In this scenario, Code Engine builds an image from your private repository source with a Git repository secret that you provide, and then uploads the image to your container registry with the registry access that you provide.

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create a Git repository secret to access your source](https://cloud.ibm.com/docs/codeengine?topic=codeengine-code-repositories).
* [Create a registry secret so you can save your image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registry).





1. Create a build configuration to build an image from a private repo and specify the location of the image registry for the build output with a registry secret. With the build create command, specify the --image option to provide the location of the image registry, and specify the --registry-secret option to access the registry. For example, the following command creates a build configuration that is called helloworld-build-private that builds from the private Git repo https://github.com/myprivaterepo/builds, uses the buildpacks strategy and medium build size, and stores the image to us.icr.io/mynamespace/codeengine-helloworld by using the registry secret that is defined in myregistry.

Because the Git repo provided is private, access requires a Git repo secret. As a result, the --source that you specify must use the SSH protocol, such as git@github.com:myprivaterepo/builds.git. The value for --source must not use the http or https format.

In this example, the command uses the default medium build size.
Create a build configuration to build an image from source on your local workstation and let Code Engine automatically store and access the image. When you specify local as the value for -build-type, you can only target IBM Cloud Container Registry for the output of your local build. In this example, the command uses the default dockerfile strategy, and the default medium build size. By not specifying the location of the image registry or a registry secret, Code Engine pushes the build output to IBM Cloud Container Registry with automatic access.

ibmcloud ce build create --name build-local-dockerfile --build-type local
2. After you create the build, you must [run the build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-imagebuild-run-cli-local) with the CLI for source from a local directory (local).









 Creating a build configuration with the CLI (with local source and user-provided access to registry) 

In this scenario, Code Engine builds an image from your local source, and then uploads the image to your container registry with the registry access that you provide.

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create a registry secret so you can save your image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registry).





1. Create a build configuration to build an image from source on your local workstation and specify the location of the image registry for the build output with a registry secret. With the build create command, when you specify local as the value for --build-type, you can only target IBM Cloud Container Registry for the output of your local build. Specify the --image option to provide the location of the image registry, and specify the --registry-secret option to access the registry.