vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Currently 6 IP addresses in each subnet are allotted as overhead. The remaining IP addresses in the subnet are available to assign to instances that are provisioned in the instance group.

Ensure that you use a subnet size of 32 or greater. Using the same subnet for multiple instance groups can create capacity issues.





 How are instances balanced across subnets? 

Currently instances are provisioned at random to one of the instance group's subnets.





 What happens when I update an instance template? 

When the instance template that is used by an instance group is updated, all future instances that are created for the instance group use the new instance template. No changes are made to existing instances in the instance group.





 Can I update all instances in an instance group with a new instance template? 

You can update all of the instances in an instance group by deleting the existing memberships and applying a new instance template. For more information, see [Pausing auto scale to apply a new instance template](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-instance-grouppausing-for-maint).





 How do I add health checks? 

You can add health checking by associating a load balancer when you create your instance group. For more information about load balancers, see the following topics:



* [About IBM Cloud Application Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers-about).
* [About IBM Cloud Network Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers).



For more information about creating a load balancer, a load balancer pool, and configuring health checks, see the following topics:



* [Creating an IBM Cloud Application Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers)
To enact this good practice, complete the following steps.



1. Provision a VLAN in the same data center as the host and the File Storage for Classic device.
2. Provision a secondary private subnet to the new VLAN.
3. Trunk the new VLAN to the private interface of the host. This action momentarily disrupts the network traffic on the host while the VLAN is being trunked to the host.
4. Create a network interface.



* On the Linux® host, create a 802.11q interface. Choose one of the unused secondary IP address from the newly trunked VLAN and assign that IP address, subnet mask, and gateway to a new 802.11q interface.
* In VMware®, create a new VMkernel network interface (vmk) and assign the unused secondary IP address, subnet mask, and gateway IP from the newly trunked VLAN to the new vmk interface.



5. Add a new persistent static route on the host to the target NFS subnet.
6. Authorize the new IP to access the storage.
7. For mounting instructions, depending on your host's operating system, follow the appropriate link.



* [Accessing File Storage for Classic on Linux®](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinux)
* [Mounting File Storage for Classic in CentOS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingCentOS)
* [Mounting File Storage for Classic Volume on ESXi hosts](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-architectureguide)





* What performance latency can be expected from the File Storage for Classic?

Target latency within the storage is less than one ms. The storage is connected to compute instances on a shared network, so the exact performance latency depends on the network traffic during the operation.
* What happens to the data when File Storage for Classic Volumes are deleted?

IBM Cloud® File Storage for Classic presents file shares to customers on physical storage that is wiped before any reuse.
For more information, see [Configure IBM Cloud Function Channel](https://docs.sysdig.com/en/configure-ibm-cloud-functions-channel.html).
* For a Webhook notification channel, add the Webhook URL. Note: When an alert is triggered, the notification is sent as a POST in JSON format to your webhook endpoint. For more information, see [Configuring a Webhook channel](https://docs.sysdig.com/en/configure-a-webhook-channel.html). For example, IBM Cloud Security and Compliance Center Workload Protection can be integrated with ServiceNow using a custom webhook. To learn about configuring IBM Cloud Security and Compliance Center Workload Protection with ServiceNow, see [Configure ServiceNow](https://docs.sysdig.com/en/configure-servicenow.html).
* For a VictorOps notification channel, add the API Key and the Routing Key.
* For an OpsGenie notification channel, add the OpsGenie API key. Notice that you must configure in OpsGenie the integration with IBM Cloud Security and Compliance Center Workload Protection. For more information, see [Add IBM Cloud Security and Compliance Center Workload Protection} Integration in Opsgenie](https://docs.opsgenie.com/v1.0/docs/sysdig-cloud-integration).
* For an Amazon SNS Topic notification channel, add the SNS Topic.
* For a Microsoft Teams notification channel, add the Microsoft Teams URL.
* For a PagerDuty notification channel, first you must authorize IBM Cloud Security and Compliance Center Workload Protection to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Security and Compliance Center Workload Protection opens. Click either Authorize Integration or Sign In Using Your Identity Provider to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Security and Compliance Center Workload Protection notifications, then click Finish Integration.
These changes are required to remove deprecated event fields and support upcoming service enhancements for IBM Cloud Activity Tracker.
* How will the changes impact my environment? This change impacts the event fields that are returned in [IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-monitor_events) audit logs when you perform Key Protect actions. The change does not impact Key Protect operations. As a security or compliance admin, ensure that the removed and changed event fields do not affect your audit operations.







 25 February 2020 

Support for integrated services and resources
: You can now use Key Protect REST APIs to examine which root keys are actively protecting what data so that you can evaluate exposures based on your organization's security or compliance needs. For more information, see [View associations between root keys and IBM Cloud resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources). This extra feature is available only if a cloud service has enabled it as part of its integration with Key Protect. To learn if an [integrated service](https://cloud.ibm.com/docs/key-protect?topic=key-protect-integrate-services) supports key registration, refer to its service documentation for more information. Also, Key Protect enabled extra security measures to protect against the accidental or malicious deletion of keys.



* Key Protect now blocks the deletion of a root key that's actively protecting a cloud resource. To learn if a key is registered to cloud resource, you can [review the resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources) that are associated with the key.
* You can now [force deletion on a key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keysdelete-keys-force-delete) that's protecting a cloud resource.







 17 February 2020 

Key Protect announces additional roles
: Need to grant read-only access to keys?
* For a PagerDuty notification channel, first you must authorize IBM Cloud Security and Compliance Center Workload Protection to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Security and Compliance Center Workload Protection opens. Click either Authorize Integration or Sign In Using Your Identity Provider to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Security and Compliance Center Workload Protection notifications, then click Finish Integration. Select the escalation policy to use for IBM Cloud Security and Compliance Center Workload Protection incidents. Then, on the Notifications tab, confirm your PagerDuty account, your service name, and the service key. For more information, see [PagerDuty Notifications](https://docs.sysdig.com/en/docs/administration/administration-settings/notifications-management/set-up-notification-channels/pagerduty-notifications/).

To retrieve the required permissions automatically by clicking Auto-fetch, first you must authorize IBM Cloud Security and Compliance Center Workload Protection to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Security and Compliance Center Workload Protection opens. Click either Sign in or Sign In Using Your Identity Provider to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Security and Compliance Center Workload Protection notifications, then click Finish Integration. Select the escalation policy to use for IBM Cloud Security and Compliance Center Workload Protection incidents. Then, on the Notifications tab, confirm your PagerDuty Account, Service Key, and Service Name.
* For a Teams Email notification channel, select the name of the team to receive notifications.
* For an IBM Event Notifications channel you must first have an [IBM Cloud Event Notifications instance configured.](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-instance)

To configure the notification channel you need to specify the IBM Cloud Event Notifications instance name and specify your choice of a channel name.
When you select PagerDuty, a wizard to configure the integration with IBM Cloud Monitoring opens. Click either Authorize Integration or Sign In Using Your Identity Provider to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Monitoring notifications, then click Finish Integration. Select the escalation policy to use for IBM Cloud Monitoring incidents. Then, on the Notifications tab, confirm your PagerDuty account, your service name, and the service key. For more information, see [Add IBM Cloud Monitoring Integration in PagerDuty](https://docs.sysdig.com/en/docs/administration/administration-settings/notifications-management/set-up-notification-channels/pagerduty-notifications/).

To retrieve the required permissions automatically by clicking Auto-fetch, first you must authorize IBM Cloud Monitoring to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Monitoring opens. Click either Sign in or Sign In Using Your Identity Provider to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Monitoring notifications, then click Finish Integration. Select the escalation policy to use for IBM Cloud Monitoring incidents. Then, on the Notifications tab, confirm your PagerDuty Account, Service Key, and Service Name.
* For a Teams Email notification channel, select the name of the team to receive notifications.
* For an IBM Event Notifications channel you must first have an [IBM Cloud Event Notifications instance configured.](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-instance)

To configure the notification channel you need to specify the IBM Cloud Event Notifications instance name and specify your choice of a channel name. You will also indicate if the notification channel is enabled and when notifications should be sent, for example, when an alert is resolved. Notifications can be shared with one or all teams.
* The resource group that is associated with an instance
* The region where the instance is provisioned
* The instances that are configured to collect automatically platform logs
* The service plan of an instance



You can also view sources. If you select Add log sources for an instance, a new page opens where you can find instructions on how to configure logging agents to forward logs to this instance.

You might see the Add log sources disabled. When this happens, the information icon displays a message that suggests that you need a new ingestion key. Notice that the ingestion key has not been lost. If you created the instance through the CLI, but did not create a service key for that instance, then the ingestion key is not available through the Logging UI for the instance. To fix the problem and enable the Add log sources, complete 1 of the following steps:



* [Create a service key](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provisionprovision_cli_2).
* Follow the instructions given through the information icon. Click i > Got it > Generate your key.
See also [Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network?](https://cloud.ibm.com/docs/blockchain-sw-252?topic=blockchain-sw-252-ibp-v2-faqibp-v2-faq-interoperability).
* Can I migrate the blockchain components on my IBM Kubernetes service cluster to a Red Hat OpenShift cluster in IBM Cloud?

No. There is currently no way to migrate existing components to a new Red Hat OpenShift cluster in IBM Cloud.
* What happens when I delete my IBM Blockchain Platform service?

When you delete an IBM Blockchain Platform service instance, all of the blockchain CAs, peers, smart contract pods (if using peers deployed with a Fabric 2.x image; smart contracts deployed on peers using a Fabric 1.4.x image are located inside the peer container), and ordering nodes are deleted along with their associated storage. If you have exported any nodes to other consoles, make sure to reach out to the administrators of those consoles to let them know that those nodes are no longer functioning, because deleting them in your console does not automatically delete them in theirs.
* Can I use my existing Kubernetes cluster on IBM Cloud?

Your existing Kubernetes cluster works with the IBM Blockchain Platform if it satisfies the following conditions:



* It is running Kubernetes version v1.20 - v1.23.
* There are enough available resources in the cluster.



* What database do the peers use for their ledger?

You have the choice of either CouchDB or LevelDB when you configure your peer database. Because data is modeled differently in a Couch database than in a Level database, the peers in a channel must all use the same database type. See [LevelDB versus CouchDB](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-level-couch) to decide what is best for your business needs.
See also [Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network?](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-ibp-v2-faqibp-v2-faq-interoperability).
* Can I migrate the blockchain components on my IBM Kubernetes service cluster to a Red Hat OpenShift cluster in IBM Cloud?

No. There is currently no way to migrate existing components to a new Red Hat OpenShift cluster in IBM Cloud.
* What happens when I delete my IBM Blockchain Platform service?

When you delete an IBM Blockchain Platform service instance, all of the blockchain CAs, peers, smart contract pods (if using peers deployed with a Fabric 2.x image; smart contracts deployed on peers using a Fabric 1.4.x image are located inside the peer container), and ordering nodes are deleted along with their associated storage. If you have exported any nodes to other consoles, make sure to reach out to the administrators of those consoles to let them know that those nodes are no longer functioning, because deleting them in your console does not automatically delete them in theirs.
* Can I use my existing Kubernetes cluster on IBM Cloud?

Your existing Kubernetes cluster works with the IBM Blockchain Platform if it satisfies the following conditions:



* It is running Kubernetes version v1.24 - v1.26.
* There are enough available resources in the cluster.



* What database do the peers use for their ledger?

You have the choice of either CouchDB or LevelDB when you configure your peer database. Because data is modeled differently in a Couch database than in a Level database, the peers in a channel must all use the same database type. See [LevelDB versus CouchDB](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-level-couch) to decide what is best for your business needs.
ibmc-vpc-file-custom vpc.file.csi.ibm.io







 Updating the File Storage for VPC add-on 



1. Disable the add-on.

ibmcloud oc cluster addon disable vpc-file-csi-driver --version VERSION
2. Enable the newer version of the add-on.The add-on might take a few minutes to become ready.

ibmcloud oc cluster addon enable vpc-file-csi-driver --version VERSION







 Understanding your storage removal options 

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.

If you [dynamically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your PVC, PV, and the storage instance are automatically deleted when you delete the cluster. For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
* [ibm_cd_toolchain_tool_gitlab](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain_tool_gitlab)
* [ibm_cd_toolchain_tool_hostedgit](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain_tool_hostedgit)



* What type of authentication should I use to access GitHub repos from my toolchain?

Before you can use a repo integration, you must authorize it so that IBM Cloud can access your GitHub account by using one of the following authentication methods.



* IBM Cloud OAuth app: When you grant authorization by using the IBM Cloud OAuth App, you allow IBM Cloud to act as the authenticated user. You can also revoke permissions from the Oauth App.
* Personal Access Token: Use a Personal Access Token (PAT) to provide granular access to a specific user or repo. Authorizing with a PAT is recommended when you use Terraform or the API.



* Can DevOps Insights be installed and run in an on-premises environment?

DevOps Insights isn't available for an on-premises environment. It's only available in IBM Public Cloud.
* My Jenkins or Travis CI is running in an on-premises environment or in another public cloud. Can I still publish build records, test records, deployment records to DevOps Insights, and use quality gates?

Yes, it doesn't matter from where your pipeline tool is running.
* I am deploying my applications to on-premises environments or other public clouds. Can I publish build records, test records, deployment records to DevOps Insights, and use quality gates for these applications?

Yes, it doesn't matter where your applications are deployed.
* Why can't I see my app on the Quality Dashboard page?

For an application to show up in the Quality Dashboard page, it must have a build record for the selected branch, and at least one test record for that build.
For more information about the complete list of attributes, see the [CloudEvents specification](https://github.com/cloudevents/spec).

In Code Engine, when events are delivered to applications, the CloudEvent attributes appear as HTTP headers, prefixed with ce-. When events are delivered to batch jobs, the attributes appear as environment variables, prefixed with CE_ and the entire variable name is in uppercase.



 Example environment variables for an IBM Cloud Object Storage event that is sent to a job 

CE_DATA={"bucket":"mybucket","endpoint":"","key":"Notes.rtf","notification":{"bucket_name":"mybucket","content_type":"text/rtf","event_type":"Object:Delete","format":"2.0","object_length":"4642","object_name":"Notes.rtf","request_id":"b59727ee-9c4e-446a-9261-5616f6d1283b","request_time":"2021-04-13T20:10:37.631Z"},"operation":"Object:Delete"}
CE_ID=b59727ee-9c4e-446a-9261-5616f6d1283b
CE_SOURCE=https://cloud.ibm.com/catalog/services/cloud-object-storage/mybucket
CE_SPECVERSION=1.0
CE_TIME=2021-08-17T20:22:02.917Z
CE_TYPE=com.ibm.cloud.cos.document.delete







 What happens when I create a subscription?
If you are moving from v1.4.x to v2.x, you may have to update your smart contracts to conform to new smart contract lifecycle. For more information, see [Upgrading to a new version of Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2).





 I am currently using Hyperledger Fabric v1.4.x and want to move to IBM Blockchain Platform for IBM Cloud . Can I continue to use Raft? 

Yes. The IBM Blockchain Platform for IBM Cloud uses Raft consensus. All of the applications and smart contracts that you are using on Fabric v1.4.x are able to work on your IBM Blockchain Platform network. However, no mechanism exists to migrate your ledger data from one network to another. Instead, you can reinstall your smart contract packages on your IBM Blockchain Platform network. See also [Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network?](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-ibp-v2-faqibp-v2-faq-interoperability).





 Can I migrate the blockchain components on my IBM Kubernetes service cluster to a Red Hat OpenShift cluster in IBM Cloud? 

No. There is currently no way to migrate existing components to a new Red Hat OpenShift cluster in IBM Cloud.





 What happens when I delete my IBM Blockchain Platform service? 

When you delete an IBM Blockchain Platform service instance, all of the blockchain CAs, peers, smart contract pods (if using peers deployed with a Fabric 2.x image; smart contracts deployed on peers using a Fabric 1.4.x image are located inside the peer container), and ordering nodes are deleted along with their associated storage.