vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Activation: 'docTrigger' (db6de778bb084366ade778bb08036685)

"{"statusCode":0,"success":true,"activationId":"23e0a17bebd3486ca0a17bebd3186c8d","rule":"<namespace_ID>/docRule","action":"<namespace_ID>/docSequence"}"
] ! ! !
2. Verify that the file was updated to include the shade value by invoking the read action. Replace <database> name with the name of your database.
ibmcloud fn action invoke /_/myCloudant/read --blocking --result --param dbname <database_name> --param id color

Example output

{
"_id": "color",
"_rev": "3-6845b04618338f717676f16edf32a78f",
"name": "blue",
"shade": "indigo"
}
<-- </ol> --><-- </section "id="section-cloudant_test_sequence" "> --><-- <section "id="section-cloudant_next" "> --> Next steps with IBM Cloudant database Now that you are listening for changes to a document in your IBM Cloudant database, you can trigger Slack notifications for the changes by using the /whisk.system/slack package]whisk.system_slack_ package] ! ! ! ! !
[Input tab](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/input_tab_only_execute.png)

Figure 1. Input tab

More stage trigger options are available for stages that use the Git repository input type. For example, you can choose to run jobs automatically for Git events on the chosen branch. When you choose this trigger type, you must select one or more of the following event types:



* When a commit is pushed triggers when a push is made to the selected repo branch.
* When a pull/merge request is opened or updated triggers when a pull request or merge request is opened or edited.
* When a pull/merge request is closed triggers when a pull request or merge request is closed, even without an associated commit.



Zoom

![Input tab triggers](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/input_tab_only_triggers.png)

Figure 2. Input tab triggers

If you select the When a pull/merge request is opened or updated checkbox, the status of the pipeline is returned to the Git repo. When a pull request or merge request triggers your pipeline, an inline status check is displayed on the page. A status check is displayed for each of the stages that are run in your pipeline, and links to the logs and history for each stage are provided. As the status check runs, it updates from pending to either successful or failed. If your pipeline contains multiple stages, each stage reports its status in the check list.

This status feedback is also supported by the IBM hosted GitLab Community Edition tool for merge requests.

You can also restrict merging based on the results of the status checks by using Git branch protection rules. After a branch protection rule is created, all merging is blocked until all of the required status checks are successful.
To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The cluster is being deleted and cluster infrastructure is being dismantled. You can't access the cluster.





 Deploy failed 

Review the following description of the Deploy failed cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The deployment of the Kubernetes master can't be completed. You can't resolve this state. Contact IBM Cloud support by opening an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).





 Deploying 

Review the following description of the Deploying cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The Kubernetes master is not fully deployed yet. You can't access your cluster. Wait until your cluster is fully deployed to review the health of your cluster.





 Normal 

Review the following description of the Normal cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

All worker nodes in a cluster are up and running. You can access the cluster and deploy apps to the cluster. This state is considered healthy and does not require an action from you.

Although the worker nodes might be normal, other infrastructure resources, such as [networking](https://cloud.ibm.com/docs/containers?topic=containers-coredns_lameduck) and [storage](https://cloud.ibm.com/docs/containers?topic=containers-debug_storage_file), might still need attention. If you just created the cluster, some parts of the cluster that are used by other services such as Ingress secrets or registry image pull secrets, might still be in process.





 Pending 

Review the following description of the Pending cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.
^branch_[0-9]{3}_[a-z]$ More complex regex pattern to match topic names. 
 "topic1", "topic2" Full topic names. 
 "." Mirror all source topics. 
 "" (by Administration REST API) --none (by CLI) Mirror no source topics. 



Updating a topic selection replaces the current set of patterns.

You can also disable mirroring on previously enabled topics.

ibmcloud es mirroring-topic-selection-set --none

To selectively disable mirroring, re-apply the topic selection leaving out the topic that you want to disable. For example, when topic1, topic2, topic3 are currently being mirrored, the following command disables mirroring for topic2 but leaves the other two enabled.

ibmcloud es mirroring-topic-selection-set --select topic1,topic3





 Retrieving the topic selection 

You can retrieve the mirroring selection by using the following interfaces:

CLI:

ibmcloud es mirroring-topic-selection

REST API:

curl -s -X GET -H "Authorization: <bearer token>" <admin url>/admin/mirroring/topic-selection





 Retrieving the active topics 

You can retrieve the topics that are being actively mirrored by using the following interfaces:

CLI:

ibmcloud es mirroring-active-topics

REST API:

curl -s -X GET -H "Authorization: <bearer token>" <admin url>/admin/mirroring/active-topics







 Building mirroring aware applications 



 Producers 

We recommend producers to produce to local topics only, hence they should not require changes when they switch between clusters.





 Consumers 

Consumers should subscribe to and consume from both the local and remote topics. This can be done with one wild-carded subscription. For example, to consume from both accounting.invoice and accounting.invoice.<ALIAS>, use the subscription to accounting.invoice..

When you consume both local and remote topics, check if the application requires strict ordering.
The bigger the volume is, the longer it takes to convert it. Use the following command to check on the progress.

slcli block duplicate-convert-status <dependent-vol-id>

The following example shows the output that you can expect.

slcli block duplicate-convert-status 370597202
Username Active Conversion Start Timestamp Completed Percentage
SL02SEVC307608_74 2022-06-13 14:59:17 90

For more information about available command options, see [duplicate-convert-status](https://softlayer-python.readthedocs.io/en/latest/cli/block/block-duplicate-convert-status).





 Updating data on the duplicate from the parent volume with the API 

As time passes and the primary volume changes, the duplicate volume can be updated with these changes to reflect the current state through the refresh action. The refresh involves taking a snapshot of the primary volume and then, updating the duplicate volume by using the data from that snapshot.

A refresh incurs no downtime on the primary volume. However, during the refresh transaction, the duplicate volume is disabled and must be remounted after the refresh is completed.

The refresh process can be time-consuming. You might find that you have new data that you want to add to the duplicate before the running refresh is finished. If that's the case, you can make a second call to refreshDuplicate and specify the second, forceRefresh parameter as true to stop all ongoing and pending refresh transactions, and initiate a new refresh. If the second parameter is set to false or it is not specified, the call fails if another refresh is already in progress.

The force refresh process works only on independent volumes.



 REST API example 



* URL - https://USERNAME:APIKEY@api.softlayer.com/rest/v3.1/SoftLayer_Network_Storage/duplicateVolumeId/refreshDuplicate
* Type - POST
* Request body -

{
"parameters": [primaryVolumeSnapshotId, true OR false]
}







 SOAP API example
You can filter the list of unresolved IP addresses to show only Internal, External, Aliased, Unknown IP addresses or a combination of these.

Internal
: IP addresses that are found within the cluster.

External
: IP addresses that are not within the cluster.

Aliased
: IP addresses that have aliases associated with them.

Unknown
: IP addresses that cannot be determined to be Internal or External.





 Reviewing the topology 

You can use the Topology tab to see a graphical representation of the policy. The view is a high-level Kubernetes metadata view of pod owners, listening ports, service and labels. You can hover over items in the topology to see all the relevant details for entities and communications.

Zoom

![Example topology](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection/images/sample-topology.png)

Figure 1. Example topology

The color of topology items indicates the status.

Lines
: Black - The connection is resolved.

Red - The connection is not resolved. The communication is not included in the generated policy. To resolve the issue, use the [ingress and egress tabs](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-netsec_policyknp_coms) to include the connection.

Entities
: Blue - The workload is included.

Black - Indicates other services and deployments the included workload communicates with.





 Generating the policy file 

You can view the generated policy in yaml format on the Generated Policy tab.

Click Download Policy to download a copy of the generated policy to your local system.
Verify that the PVCs are used in your stateful set replica pods by listing the pods in your cluster and identifying the pods that belong to your stateful set.

kubectl get pods
4. Verify that your existing PVC is mounted to your stateful set replica. Review the ClaimName in the Volumes section of your CLI output.

kubectl describe pod <pod_name>

Example output

Name: nginx-0
Namespace: default
Node: 10.xxx.xx.xxx/10.xxx.xx.xxx
Start Time: Fri, 05 Oct 2022 13:24:59 -0400
...
Volumes:
myvol:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: myvol-nginx-0
...









 Changing the size and IOPS of your existing storage device 

If you want to increase storage capacity or performance, you can modify your existing volume.

For questions about billing and to find the steps for how to use the IBM Cloud console to modify your storage, see [Expanding File Share capacity](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacityexpandCapacity).



1. List the PVCs in your cluster and note the name of the associated PV from the VOLUME column.

kubectl get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
myvol Bound pvc-01ac123a-123b-12c3-abcd-0a1234cb12d3 20Gi RWX ibmc-file-bronze 147d
2. Retrieve the StorageType, volumeId, and the server of the physical File Storage for Classic that is associated with your PVC by listing the details of the PV that your PVC is bound to. Replace <pv_name> with the name of the PV that you retrieved in the previous step. The storage type, volume ID, and the server name are shown in the Labels section of your CLI output.
The Dashboard provides notifications and summary information about servers, backups, restores, and activity in your site. In the What’s new section, you can see the newest IBM Cloud® Backup for Classic Announcements along with unconfigured agent information. Such a IBM Cloud Backup for Classic agent can be configured by clicking the Configure Now link or by clicking the computers tab.

For more





 Computers 

On the Computers page, you can view server information, configure backup jobs, run jobs, and restore data. For more information about how to configure backupjobs, see [Configuring the backup agent and the backup schedule](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-startedconfigureagentschedule). For more information about how to run jobs, see [running your first backup job](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-startedrunfirstbackup). For more information about restoring data, see [Restoring data from a backup](https://cloud.ibm.com/docs/Backup?topic=Backup-simplerestore).





 Monitor 

On the Monitor page, you can view the most recent backup statuses for your jobs, monitor processes, and view logs. You can go from information on the Monitor page to related information on the Computers page or in the Logs window. If you click an online computer name or job name, you can view the computer’s record on the Computers page. If you click a job’s last backup status, you can view the job’s past logs in a separate window.
* UI
* CLI
* API
* Terraform







 Viewing file shares and mount targets 

View all file shares and mount targets in the UI, CLI, API, or Terraform. View details of a single file share or mount target.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 View file shares and mount targets in the UI 



 View all file shares in the UI 



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. The File Shares for VPC list page shows all file shares that are created in that zone. Overflow menu options are used to manage the file shares. The following table describes the information and actions on the list page.





Table 1. File shares list page.

 Field Value 

 Region Account region for the file share. Select a different region to see file shares for zones in that region. 
 Name The file share name. It can be the original file share or a replica file share. Click the name to see details about that file share. 
 Status For a list of statuses for file shares, see [File storage lifecycle states](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfile-storage-vpc-status). 
 Mount targets Number of mount targets that are associated with the file share. You can have one mount target per VPC per file share. 
 Size Size of the file share, in GBs. 
 Replication role Relationship to the source file share. "Replica of" indicates that the file share a replica of the source share, which is linked. "Source of" indicates that the share the source of the replica, which is linked.
An on-premises Veeam Backup and Replication Server connecting to IBM Cloud must validate the revocation status of the IBM Cloud for VMware Solutions SSL certificate that is provided by DigiCert. You must have admin privileges.



2. From your on-premises Veeam Backup and Replication Server, view Veeam Cloud Connect failover plans, perform failovers, or undo failovers from IBM Cloud.







 Procedure to access the Veeam Cloud Connect self-service portal from the virtual data center 

If you don't have access to your on-premises Veeam Backup and Replication Server, connect to the Veeam Cloud Connect self-service portal. From the portal you can view failover plans, perform failovers, or undo failovers from IBM Cloud.



1. Under Recommended services on the virtual data center details page, click Veeam Cloud Connect. The Veeam Cloud Connect self-service portal login is displayed.
2. Log in to the Veeam Cloud Connect portal.



You must add your organization name as a prefix to your User credential to log in to the Veeam Cloud Connect self-service portal. You can locate your organization name under the self-service portal access information under Veeam Cloud Connect Replication. For example, 8823e1828b208ef9380b3admin.

For more information about using Veeam Cloud Connect, see the [Veeam Cloud Connect User Guide](https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_user_guide.html?ver=100).







 Deleting Veeam backups 

Restore points are automatically removed from the Veeam self-service portal when you delete a virtual data center. For more information, see [Deleting virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_deletinginstance).

If you remove a VMware Cloud Director virtual data center from your account, all backups and restore points that are associated with the virtual data center are deleted and cannot be recovered.
For more information, see [Creating replica file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication&interface=ui). 







 View all file shares for a VPC in the UI 

You can see all file shares that have a mount target to a VPC by viewing the VPC details page.



1. Go to a VPC:



1. From the [file shares details page](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=clifs-view-single-share-ui), click the VPC link in the list of mount targets.
2. From the UI, go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > > Network > VPCs. Click the name of a VPC in the list.



2. On the VPC details page, scroll to File shares in this VPC.







 View mount target details in the UI 



1. Go to the list of all file shares. From the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. Click the name of a file share to see the details page.
3. Scroll to the Mount targets section to see the list of mount targets. The list contains the names and statuses of the mount target, and the VPC that the mount target belongs to.
4. Click the ellipsis (!
Why does the Ingress status show an ESSWS error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following example.

The secret status shows a warning (ESSWS).

  Why it’s happening 

There was an error when attempting to apply the secret to your cluster.

To view the specific error, run the ibmcloud oc ingress secret ls commands and review the Status column.

Error api_request_failed
:   There was an issue uploading the new certificate to the registered instance for the cluster. Verify the instance details using the ibmcloud oc ingress instance ls command.

Error secret_apply_failed
:   There was an issue applying the secret to your cluster. Follow the steps to [ensure your cluster control plane is healthy](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_masterreview-master-health).

Error namespace_not_found
:   The namespace for the secret is no longer found in the cluster. If you no longer need the secret for that namespace, you can remove it with the ibmcloud oc ingress secret rm command. Otherwise, recreate the namespace on the cluster.

If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The cluster is being deleted and cluster infrastructure is being dismantled. You can't access the cluster.





 Deploy failed 

Review the following description of the Deploy failed cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The deployment of the Kubernetes master can't be completed. You can't resolve this state. Contact IBM Cloud support by opening an [IBM Cloud support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).





 Deploying 

Review the following description of the Deploying cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The Kubernetes master is not fully deployed yet. You can't access your cluster. Wait until your cluster is fully deployed to review the health of your cluster.





 Normal 

Review the following description of the Normal cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

All worker nodes in a cluster are up and running. You can access the cluster and deploy apps to the cluster. This state is considered healthy and does not require an action from you.

Although the worker nodes might be normal, other infrastructure resources, such as [networking](https://cloud.ibm.com/docs/containers?topic=containers-coredns_lameduck) and [storage](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_storage_file), might still need attention. If you just created the cluster, some parts of the cluster that are used by other services such as Ingress secrets or registry image pull secrets, might still be in process.





 Pending 

Review the following description of the Pending cluster state.
For more information, see [Creating replica file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication&interface=ui). 







 View all file shares for a VPC in the UI 

You can see all file shares that have a mount target to a VPC by viewing the VPC details page.



1. Go to a VPC:



1. From the [file shares details page](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=terraformfs-view-single-share-ui), click the VPC link in the list of mount targets.
2. From the UI, go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > > Network > VPCs. Click the name of a VPC in the list.



2. On the VPC details page, scroll to File shares in this VPC.







 View mount target details in the UI 



1. Go to the list of all file shares. From the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. Click the name of a file share to see the details page.
3. Scroll to the Mount targets section to see the list of mount targets. The list contains the names and statuses of the mount target, and the VPC that the mount target belongs to.
4. Click the ellipsis (!