vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Understanding high availability and disaster recovery for Cloud Functions 

Learn about the high availability features of the IBM Cloud® Functions and design your resources to meet the availability requirements that your business and customers need.

High availability is a core discipline in an IT infrastructure to keep your resources healthy and your app workloads up and running, even after a partial or a full site failure. The main purpose of high availability is to eliminate potential points of failure in an IT infrastructure.

Regions and service level
: All IBM Cloud general availability (GA) services have a Service Level Agreement of 99.99% availability. Cloud Functions is a GA service that is offered in six regions: US South, US East, EU Central, Tokyo, UK South, and Sydney. Each location uses different availability zones for redundancy. If all the availability zones in a location fail, the Cloud Functions service for that location becomes unavailable.
: Cloud Functions is available only on the public cloud.

Who is responsible to set up high availability for my resources?
: Your global strategy is important, and you are responsible for understanding your configuration, customization, and usage of the service to best leverage the capabilities of IBM Cloud. For more information, see the topic [How does IBM Cloud ensure zero downtime?](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime)
: While Cloud Functions is responsible to ensure that your namespace information is available, backed up, and replicated across multiple regions so that information can be recovered after a failure, Cloud Functions does not set up high availability for any IBM Cloud resources that are used by Cloud Functions. Instead, you must understand the high availability options that each resource offering provides to implement the right level of availability for your needs.

See [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud. You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).

The following sections contain information about high availability, disaster recovery for Cloud Functions as well as HIPAA-related considerations.
Configuring Event Notifications 

You can use the IBM Cloud® Event Notifications service to receive information about critical events that occur in your IBM Cloud® account. You can filter and route event notifications from IBM Cloud services like Toolchains, Monitoring, Security and Compliance Center, and Secrets Manager to communication channels like PagerDuty, Slack, email, SMS, push notifications, webhook, Microsoft® Teams, ServiceNow, and IBM Cloud Functions.

Before you configure an Event Notifications tool integration, make sure that you provision an instance of the [Event Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-instance) service.

By connecting a toolchain to an Event Notifications service instance, the Event Notifications tool integration enables the toolchain and its associated tool integration instances to send events to any of the destinations that are supported by the Event Notifications service.

Make sure that the selected Event Notifications service instance has an [IAM authorization policy](https://cloud.ibm.com/iam/authorizations/grant) that allows the toolchain to send events to this service instance. For more information about granting authorization with the Event Notifications service instance, see [Why am I denied permission to integrate an Event Notifications instance?](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-troubleshoot-integrate).

Configure Event Notifications to send critical events from toolchains and tool integration instances:



1. If you have a toolchain and are adding this tool integration to it, from the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps. On the Toolchains page, click the toolchain to open its Overview page. Alternatively, on your app's Overview page, on the Continuous delivery card, click View toolchain.
Customize the JRE 

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

Apps run in a Java runtime environment (JRE) that is provided and configured by the Liberty buildpack. The Liberty buildpack also makes it possible to configure the JRE version or type, customize the JVM options, or overlay the JRE functions.



 IBM JRE 

By default, apps are configured to run with a lightweight version of the IBM® JRE. This lightweight JRE is stripped down to provide core, essential function with a much reduced disk and memory footprint. For more information about the contents of the lightweight JRE, see [Small Footprint JRE](http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.lnx.80.doc/user/small_jre.html).

IBM JRE version 8 is used by default. The Liberty buildpack also includes the latest OpenJ9 11 JRE as an alternate JRE. Use the JBP_CONFIG_IBMJDK environment variable to specify an alternative JRE. For example, to use the latest OpenJ9 JRE provided by the Liberty buildpack set the following environment variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"

The version property can be set to a version range. There are two supported version ranges: 1.8.+ and 11.+. For best results, use Java 8.





 OpenJDK 

Optionally, apps can be configured to run with OpenJDK as the JRE. To enable an app to run with OpenJDK set the JVM environment variable to openjdk. For example, using the IBM Cloud command line tool, run the command:
* 30 minutes
* 2022-06-29



[Develop and deploy an app by using IBM Cloud Satellite](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-satellite)Develop and deploy an app by using IBM Cloud Satellite

In this tutorial, you learn how to create an open toolchain by using IBM Cloud® Continuous Delivery and deploy your app on Satellite. You also learn how toolchains are implemented in the Continuous Delivery service and how to develop and deploy a simple web application (app) by using toolchains.

Satellite Creating apps

+3

Red Hat OpenShift on IBM Cloud,Kubernetes service,Continuous Delivery



* 30 minutes
* 2022-10-06



[Using Hyper Protect Crypto Services with Unified Key Orchestrator to manage keys in Key Protect on Satellite](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-uko-satellite)Using Hyper Protect Crypto Services with Unified Key Orchestrator to manage keys in Key Protect on Satellite

IBM Cloud Satellite provides you with flexibility and scalability to bring your own infrastructures to IBM Cloud. You can run IBM Cloud services anywhere including on your on-prem data centers and other cloud providers. With IBM Cloud Satellite, you can connect your multiple environments to implement distributed cloud solutions to help your enterprise hybrid cloud transformation. Key Protect on Satellite allows you to fully control your encryption keys by using your on-prem hardware security module (HSM). Hyper Protect Crypto Services with Unified Key Orchestrator enables you to manage keys in various key management systems, including Key Protect on Satellite, from a single pane of glass.

Hyper Protect Crypto Services Key Protect

+3

Satellite,IBM Cloud Databases,Activity Tracker hosted event search



* 2 hours
* 2023-06-27



[Attaching bare metal hosts to a location](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-bare-metal)Attaching bare metal hosts to a location

You can attach bare metal hosts to your Satellite location.
Set preferences to [receive emails about platform notifications](https://cloud.ibm.com/docs/overview?topic=overview-uiemail-prefsl), and monitor the [IBM Cloud status page](https://cloud.ibm.com/status?selected=announcement) for general announcements. 
 Firmware updates Provide firmware updates for multiple crypto units in a sequential manner with no impact to running workloads. Perform tasks as usual. 
 Connecting to third-party cloud Provide error messages when access to the third-party keystores does not work. Contact affected third-party cloud service provider to resolve access or connection issues. 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion. You and IBM share responsibilities for keeping Hyper Protect Crypto Services service components at the latest version. You are responsible for change management of your application data.



Table 2. Responsibilities for change management

 Task IBM responsibilities Your responsibilities 

 Applications Provide major, minor, and patch version updates for Hyper Protect Crypto Services interfaces. Use the [API](https://cloud.ibm.com/apidocs/hs-crypto), [CLI](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-cli-plugin-hpcs-cli-plugin), or console tools to perform updated functions. 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access. You and IBM share responsibilities for controlling access to your Hyper Protect Crypto Services instances and resources. You are responsible for identity and access management to your application data.



Table 3. Responsibilities for identity and access management

 Task IBM responsibilities Your responsibilities 

 User management IBM does not have access to your resources but provides you with the ability to restrict user access to resources. Depending on your needs, restrict access to resources and service functionality by using Cloud IAM access policies.
Configuration options 

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

A variety of options are available for configuring the sdk-for-nodejs buildpack.



  NPM scripts 

NPM provides a scripting facility allowing you to run scripts, including pre-installation and post-installation scripts which are applied before and after your node_modules are installed. See [npm-scripts](https://docs.npmjs.com/misc/scripts) for complete details.





  Cache behavior 

IBM Cloud® maintains a cache directory per node app, that is persisted between builds. The cache stores resolved dependencies so they are not downloaded and installed every time the app is deployed. For example, suppose myapp depends on express. Then the first time myapp is deployed the express module is downloaded. On subsequent deployments of myapp, the cached instance of express is used. The default behavior is to cache all node_modules installed by NPM and bower_components installed by bower.

Use the NODE_MODULES_CACHE variable to determine whether or not the Node buildpack uses or ignores the cache from previous builds. The default value is true. To disable caching set NODE_MODULES_CACHE to false, for example via the IBM Cloud command line:

ibmcloud cf set-env myapp NODE_MODULES_CACHE false

Note that node_modules that are included in your app are not cached.

You can use a cacheDirectories array in your top-level package.json file to achieve fine grained control over what modules are cached. When the cacheDirectories element is present in the package.json file only those modules which are in the cacheDirectories array will be cached. In the following example only node_modules and bower_components are cached.

{
"cacheDirectories": ["node_modules","bower_components"],
...
}
* [Organizing IBM Cloud accounts and resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organization)







 IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



Rules for AC-5 in IBM Cloud for Financial Services v1.2.0 profile

 Requirement ID Rules 

 AC-5 (c) <br><br> * Check whether permissions for API key creation are limited and configured in IAM settings for the account owner<br> * Check whether App ID Cloud Directory users aren't able to update their own accounts<br> * Check whether IAM roles are used to create IAM policies for IBM resources<br> * Check whether IAM users are attached to at least one access group<br> * Check whether App ID Cloud Directory users aren't able to self-sign up to applications<br> * Check whether App ID user profile updates from client apps is disabled<br><br><br> 







 NIST supplemental guidance 

Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes, for example: (i) dividing mission functions and information system support functions among different individuals and/or roles; (ii) conducting information system support functions with different individuals (e.g., system management, programming, configuration management, quality assurance and testing, and network security); and (iii) ensuring security personnel administering access control functions do not also administer audit functions.
See [Deploy from Red Hat Marketplace](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-deploy-ocp-rhm) to learn more.
* Is it possible to deploy blockchain nodes to multiple clouds from a single blockchain console?

You cannot currently deploy blockchain nodes to multiple hosted cloud providers. However, you can use your console to operate a distributed multicloud network by importing nodes deployed by using consoles on other clouds.
* How can I find what version of the IBM Blockchain Platform that I am running?

View the Support page by clicking the question mark icon ![Support link icon](https://cloud.ibm.com/images/support-link.png) in the upper right corner of the page. The IBM Blockchain Platform version is visible under the page heading.
* How do I get the latest Fabric version and Fabric functionalities on my IBM Blockchain Platform network?

Depending on the contents of a Fabric release and IBM Blockchain Platform, it might only be necessary to upgrade nodes to get access to the latest features. However, often it is necessary to update channel configurations with the latest capabilities in order to get access to the latest Fabric features. In these cases, it is important to upgrade components and channels in a particular order:



1. Upgrade nodes to the latest Fabric versions. Note that nodes are always backward compatible with earlier versions and earlier capabilities. For more information about upgrading nodes, see [Upgrading to a new version of Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade).
2. Update channels with any new channel capabilities. If you update capabilities to a capability level (such as 2.0) before upgrading nodes to the Fabric version corresponding to a capability, the node may crash. For more information, see [Capabilities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-capabilities).
See [Deploy from Red Hat Marketplace](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-deploy-ocp-rhm) to learn more.
* Is it possible to deploy blockchain nodes to multiple clouds from a single blockchain console?

You cannot currently deploy blockchain nodes to multiple hosted cloud providers. However, you can use your console to operate a distributed multicloud network by importing nodes deployed by using consoles on other clouds.
* How can I find what version of the IBM Blockchain Platform that I am running?

View the Support page by clicking the question mark icon ![Support link icon](https://cloud.ibm.com/docs/images/support-link.png) in the upper right corner of the page. The IBM Blockchain Platform version is visible under the page heading.
* How do I get the latest Fabric version and Fabric functionalities on my IBM Blockchain Platform network?

Depending on the contents of a Fabric release and IBM Blockchain Platform, it might only be necessary to upgrade nodes to get access to the latest features. However, often it is necessary to update channel configurations with the latest capabilities in order to get access to the latest Fabric features. In these cases, it is important to upgrade components and channels in a particular order:



1. Upgrade nodes to the latest Fabric versions. Note that nodes are always backward compatible with earlier versions and earlier capabilities. For more information about upgrading nodes, see [Upgrading to a new version of Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade).
2. Update channels with any new channel capabilities. If you update capabilities to a capability level (such as 2.0) before upgrading nodes to the Fabric version corresponding to a capability, the node may crash. For more information, see [Capabilities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-capabilities).
The Spectrum LSF cluster can be deployed on IBM Cloud by using the IBM Cloud catalog, Schematics CLI, or the Schematics APIs. If you want to deploy your cluster by using the CLI or API, review the prerequisites for your interface of choice:



* [Setting up the IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-setting-up-cli)
* [Setting up the IBM Cloud Schematics API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-setting-up-api)



After you've created and gathered your information and reviewed any additional prerequisites for your interface of choice, you are ready to begin [Creating a workspace](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-creating-workspace).
: Explore [IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-faqs) to extend the flexibility and scalability of IBM Cloud into your on-premises, edge, or other cloud provider environments.





 Can I automate my infrastructure deployments? 

If you want to run your app in multiple clusters, public and private environments, or even multiple cloud providers, you might wonder how you can make your deployment strategy work across these environments.

You can use the open source [Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-startedgetting-started) tool to automate the provisioning of IBM Cloud infrastructure, including Kubernetes clusters. Follow along with this tutorial to [plan, create, and update deployment environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-plan-create-update-deploymentsplan-create-update-deployments). After you create a cluster, you can also set up the [IBM Cloud Kubernetes Service cluster autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpc) so that your worker pool scales up and down worker nodes in response to your workload's resource requests.





 What kind of apps can I run? Can I move existing apps, or do I need to develop new apps? 

Your containerized app must be able to run on the supported operating system, RHEL 7 . You also want to consider the statefulness of your app. For more information about the kinds of apps that can run in IBM Cloud Kubernetes Service, see [Planning app deployments](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapp_types).

If you already have an app, you can [migrate it to IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploymigrate_containerize).
Getting help and support 

If you have problems or questions about IBM Cloud® Functions, you can get help by joining the IBM Cloud® Functions community in Slack, asking questions through a forum, or opening an IBM Cloud support case.



*  To see whether IBM Cloud is available, [check the IBM Cloud status page](https://cloud.ibm.com/status?selected=status).
*  Review the forums to see whether other users ran into the same issue. When you use the forums to ask a question, tag your question so that it is seen by the IBM Cloud development teams.



*  If you have technical questions about developing functions with IBM Cloud® Functions, post your question on [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud-functions) and tag your question with ibm-cloud-functions.



*  See [Getting help](https://cloud.ibm.com/docs/get-support) for more details about using the forums.
*  Contact IBM Support by opening a case. To learn about opening an IBM support case, or about support levels and case severities, see [Contacting support](https://cloud.ibm.com/docs/get-support).



When you report an issue, include your activation ID. To get an activation ID, run ibmcloud fn activation list.
(https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploydeploy_objects)
* [What type of Kubernetes objects can I make for my app?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployobject)
* [What if I want my app configuration to use variables? How do I add these variables to the YAML?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployvariables)
* [How can I make sure that my app has the correct resources?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployresources)
* [How can I add capabilities to my app configuration?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploycapabilities)
* [How can I add IBM services to my app, such as Watson?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployservices_ibm)



* [Planning highly available deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployhighly_available_apps)



* [How can I increase the availability of my app?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployincrease_availability)
* [How can I scale my app?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployscale)



* [Versioning and updating apps](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployupdating)



* [How can I organize my deployments to make them easier to update and manage?]