vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Status change You can view the latest volumes-clone request status by using the [get volumes-clone detail](https://cloud.ibm.com/apidocs/power-cloudpcloud-v2-volumesclone-get) request or the [get volumes-clone list](https://cloud.ibm.com/apidocs/power-cloudpcloud-v2-volumesclone-getall) request. When the volumes-clone request is initiated, the initial status is set to Starting. When the group snapshot is created, the request status changes to Available. The start action of the volumes-clone request is synchronous and when the API call returns to the client, the volumes-clone request status changes to Available unless an error occurs. If an error occurred during the start action, the status of the volume-clone request changes to Failed. The reason for failure is specified in the error that is returned with the start action response. The prepared snapshot data is removed so that you can clone the same set of volumes again. If you cancel the start action of a volumes-clone request, status of the volumes-clone request changes to Cancelling. You can cancel a volumes-clone request when the volumes-clone request is in the Available state.
* Output The volumes-clone request is updated to view the current status.







 3. Execute the volumes-clone request 

Performs the remaining execution action to create the cloned volumes from the available group snapshot. As a best practice, you must manually unquiesce the VM before you initiate the execute action of a volumes-clone request.



* Requirements The volumes-clone request must be in the available status.
* Status change If the execute action of a volumes-clone request is initiated, the initial status is set to Executing. When the execute action is completed successfully, the request status changes to Completed. If an error occurs during the volume cloning process, any artifacts that are created by the cloning process are removed. The group snapshot is returned to the Available state so that you can retry the execute action. If you cancel the execute action of a volumes-clone request, status of the volumes-clone request is changed to Cancelling.
Normal Created 102s service-controller Created Configuration "myapp"
Normal Created 102s service-controller Created Route "myapp"

Instances:
Name Revision Running Status Restarts Age
myapp-00001-deployment-699c45ddd-c25rm myapp-00001 1/2 Terminating 0 102s







 Application status 

The following table shows the possible status that your application might have.



Table 1. Application status

 Status Description 

 Deploying The application is deploying. Deployment time includes the time before the app is scheduled as well as time to download images over the network, which can take a while. 
 Ready The application is deployed and ready to use. 
 Ready (with warnings) The deployment of a new application revision failed, but the original deployment is available. 
 Failed The application deployment terminated, and at least one instance terminated in failure. The instance either exited with nonzero status or was terminated by the system. 
 Unknown For some reason, the state of the application cannot not be obtained, typically due to an error in communicating with the host.
: Change log documentation is available for version [4.8.15_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484815_1532),[4.7.34_1537_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474734_1537), [4.6.48_1561_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464648_1561), and [3.11.524_1609_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311524_1609).





 22 October 2021 

IBM Cloud Object Storage plug-in.
: [Version 2.1.6](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog) is released.





 19 October 2021 

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for versions 0.49.3_1745_iks and 1.0.3_1730_iks.





 18 October 2021 

New troubleshooting topic
: See [Why does my cluster master status say it is approaching its resource limit?](https://cloud.ibm.com/docs/openshift?topic=openshift-master_resource_limit).

IBM Cloud HPCS Router add-on
: The [IBM Cloud HPCS Router add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) version 4.5 is deprecated.

OpenShift Data Foundation
* Status change If the execute action of a volumes-clone request is initiated, the initial status is set to Executing. When the execute action is completed successfully, the request status changes to Completed. If an error occurs during the volume cloning process, any artifacts that are created by the cloning process are removed. The group snapshot is returned to the Available state so that you can retry the execute action. If you cancel the execute action of a volumes-clone request, status of the volumes-clone request is changed to Cancelling. You can cancel a volumes-clone request, when the volumes-clone request is in the Executing state.

A volumes-clone request is considered complete when the status of the volumes-clone request is changed to one of the Completed, Failed, or Cancelled state.
* Output The volumes-clone request is updated to view the current status.





 Additional volumes-clone APIs that can be used with volumes-clone requests 



* Get details of a volumes-clone request

This API request returns detailed information about the status of the volume-clone request such as the list of source volumes that are getting cloned and the list of cloned volumes when the execute action is successfully completed.
* Get a list of all volumes-clone requests

The API request provides a list of all volumes-clone requests and the latest status for each request. The detailed information about the source volumes or cloned volumes is not provided.
* Cancel a volumes-clone request

This API request removes the group snapshot. If the volumes-clone request is in the Executing state, any artifacts that are created by the clone operation process are removed. If you cancel the volumes-clone request, initial status of the volumes-clone request is set to Cancelling and then it is changed to Cancelled state when all the clean-up work is completed successfully.
* Delete a volume-clone request

When a volumes-clone request is not required any longer, you can call the volumes-clone delete API to remove the data. You can delete a volumes-clone request only when the request status is in one of the finalized statuses: Completed, Failed, or Cancelled state.











 Restoring a snapshot 

The restore operation restores all of the volumes that are part of a VM snapshot back to the source disks.
IBM Cloud File Storage for Classic plug-in and monitor configuration N/A N/A Added a pod memory limit. 
 IBM Cloud RBAC operator 08ce50e 8882606 Updated image for [CVE-2020-13777](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13777) and to use Go version 1.13.12. 
 Kubernetes v1.18.4 v1.18.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.6). The update resolves CVE-2020-8559 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6249915)). 
 Kubernetes configuration N/A N/A The Kubernetes API server audit policy configuration is updated to include auditing the scheduling.k8s.io API group and the tokenreviews resource. 
 Kubernetes Dashboard v2.0.1 v2.0.3 See the [Kubernetes Dashboard release notes](https://github.com/kubernetes/dashboard/releases/tag/v2.0.3). 
 OpenVPN server 2.4.6-r3-IKS-131 2.4.6-r3-IKS-222 Removed the deprecated comp-lzo compression configuration option and updated the default cipher that is used for encryption. 
 Operator Lifecycle Manager 0.14.1 0.14.1-IKS-1 Updated image for [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). 







 Change log for worker node fix pack 1.18.6_1520, released 20 July 2020 

The following table shows the changes that are in the worker node fix pack 1.18.6_1520.
Securing your data in IBM Cloud Foundry 

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).

To ensure that you can securely manage your data when you use IBM® Cloud Foundry, it is important to know exactly what data is stored and encrypted and how you can delete any stored personal data.



  How your data is stored and encrypted in IBM Cloud Foundry 

IBM Cloud Foundry does not store customer or application user data. Data related to IBM Cloud Foundry apps is stored encrypted in IBM Cloud® object storage using a key defined by IBM Cloud Foundry.





  Deleting your data in IBM Cloud Foundry 

When an app is deleted from IBM Cloud Foundry the app and any associated data stored in IBM Cloud Foundry is deleted. All app data should be deleted when the app is deleted unless there is an error during the app deletion. In the case of an error any remaining data will be cleaned up by Cloud Foundry during [automatic cleanup](https://docs.cloudfoundry.org/concepts/architecture/cloud-controller.htmlautomatic-clean).





  Restoring deleted data for IBM Cloud Foundry 

An app that was deleted from IBM Cloud Foundry cannot be restored. If you need to restore a deleted app, redeploy the app.
Connection information for applications, devices, and gateways 

IBM Watson® IoT Platform is deprecated. As of 30 April 2023, only subscribers on paid plans will be able to deploy new instances. The service will be fully withdrawn on 1 December 2023. Any instances that still exist on 1 December 2023 will be deleted. For more information, see [the deprecation details](https://cloud.ibm.com/docs/IoT?topic=IoT-deprecation).

This IBM Cloud® documentation collection pertains to the IBM Watson® IoT Platform Lite pricing plan and includes basic getting started information, API references, and general troubleshooting information. For the full Watson IoT Platform feature documentation, see the [Watson IoT Platform product documentation ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/overview.html) on IBM Knowledge Center. More information about the various plans can be found in [Watson IoT Platform service plans](https://cloud.ibm.com/docs/services/IoT?topic=IoT-plans_overviewplans_overview).

You can connect applications, devices, and gateways to IBM Watson® IoT Platform by using the MQTT protocol. You can also use the HTTP REST API to connect devices to Watson IoT Platform.



 Client connection information 

For more information about how to connect devices, applications, and gateway clients to your Watson IoT Platform instance, see the corresponding topics in the Watson IoT Platform product documentation.



* [Application development ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/applications/app_dev_index.html)
* [Device development !
Database mirroring was deprecated in SQL Server 2012, however, is still referenced in SQL 2019 documentation, refer to [Database mirroring in SQL Server](https://docs.microsoft.com/en-us/sql/connect/ado-net/sql/database-mirroring-sql-server?view=sql-server-ver15). It is discussed here for completeness of migration methods, however, carefully research this approach if you want to employ it in your migration.

Database mirroring in SQL Server allows you to keep a copy, or mirror, of a SQL Server database on a standby server. Mirroring ensures two separate copies of the data always exist. Compared to log shipping, database mirroring is a little more complicated to get set up, and it has more restrictions. Database mirroring is easier to set up if both servers in the partnership are in the same Windows Domain, but if this is not the case, you can use certificates for your endpoint authentication. The basic steps for migration include:



* Configure database mirroring.
* At the required cut-over time, stop the applications that are using the principal databases on the primary server.
* Make sure each database is in a synchronized state.
* Fail over each mirrored user database.
* Remove the mirroring partnership.
* Redirect the applications to the new database server.
* Decommission the original server.







 Log shipping 

SQL Server log shipping can be configured at the database level and in a specified time period, the SQL Server transaction log backup will be taken and copied to the destination server and be restored. Transaction logs contain a log of all the transactions happening in a SQL Server database. The SQL Server instance from which the transaction log backup is shipping from is called the primary and the SQL Server instance where the transaction log backup is being shipped to is called the secondary. Before configuring log shipping, the database must be in full recovery model or bulk-logged mode.

The SQL Server transaction log backup settings allows addressing to a network path and backup job scheduler can be defined to run a backup job, by default, the setting is to run a backup job every 15 minutes.
The Purge API for purging a single file is deprecated. For efficiency, it is recommended to use [Multiple file Purge](https://cloud.ibm.com/docs/CDN?topic=CDN-cdn-api-referenceapi-for-multiple-file-purge) instead.



 Container class for Purge 

class SoftLayer_Container_Network_CdnMarketplace_Configuration_Cache_Purge
{
/
* @var string
/
public $path;

/
* @var string
/
public $status;

/
* @var string
/
public $saved;

/
* @var string
/
public $date;
}
Show more





 createPurge 

Create a single file purge.



* Parameters:



* uniqueId - The unique ID of the mapping to which the Purge is created.
* path - Path of the Purge to be created.



* Return - a collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Cache_Purge



--------------------





 getPurgeHistoryPerMapping 

Returns the Purge history for a CDN based on the uniqueId and saved status. (By default, the value of saved is set to UNSAVED.)



* Parameters:



* uniqueId - The unique ID of the mapping for which retrieve Purge history.
* saved - Return Purges that were SAVED or UNSAVED.



* Return - a collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Cache_Purge



--------------------





 saveOrUnsavePurgePath 

Updates the status of the Purge path entry to indicate whether that Purge path should be saved. Creates a new saved Purge if a Purge path is saved. Deletes a saved Purge record if the path is unsaved.



* Parameters:



* uniqueId - The unique ID of the mapping to which the Purge belongs.
: The default Certificate Manager instance for your cluster is now named in the format kube-crtmgr-<cluster_ID>.





 22 March 2021 

Ingress updates
: Updated the [nginx-ingress build to 2466 and the ingress-auth build to 982](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for the Red Hat OpenShift on IBM Cloud Ingress image.





 17 March 2021 

Deprecated events to be replaced for Activity Tracker
: To align with event auditing standards across IBM Cloud, the following cluster events are deprecated and are replaced in 30 days on 16 April 2021 by new events.



* containers-kubernetes.account.create
* containers-kubernetes.account.delete
* containers-kubernetes.account.get
* containers-kubernetes.account.update
* containers-kubernetes.cluster.config
* containers-kubernetes.cluster.create
* containers-kubernetes.cluster.delete
* containers-kubernetes.cluster.update
* containers-kubernetes.credentials.ready-to-use
* containers-kubernetes.logging-config.create
* containers-kubernetes.logging-config.delete
* containers-kubernetes.logging-config.refresh
* containers-kubernetes.logging-filter.create
* containers-kubernetes.logging-filter.delete
* containers-kubernetes.logging-filter.update
* containers-kubernetes.logging-autoupdate.changed
* containers-kubernetes.masterlog-retrieve
* containers-kubernetes.masterlog-status
* containers-kubnertes.cluster.rbac.update
* containers-kubernetes.service.create
* containers-kubernetes.service.delete
* containers-kubernetes.subnet.add
* containers-kubernetes.subnet.create
: The default Certificate Manager instance for your cluster is now named in the format kube-crtmgr-<cluster_ID>.





 23 March 2021 

Istio add-on
: [Version 1.8.4 of the Istio managed add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog184) is released.





 22 March 2021 

Ingress ALB change log
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for updates to the Kubernetes Ingress and IBM Cloud Kubernetes Service Ingress images.





 17 March 2021 

Deprecated events to be replaced for Activity Tracker
: To align with event auditing standards across IBM Cloud, the following cluster events are deprecated and are replaced in 30 days on 16 April 2021 by new events.



* containers-kubernetes.account.create
* containers-kubernetes.account.delete
* containers-kubernetes.account.get
* containers-kubernetes.account.update
* containers-kubernetes.cluster.config
* containers-kubernetes.cluster.create
* containers-kubernetes.cluster.delete
* containers-kubernetes.cluster.update
* containers-kubernetes.credentials.ready-to-use
* containers-kubernetes.logging-config.create
* containers-kubernetes.logging-config.delete
* containers-kubernetes.logging-config.refresh
* containers-kubernetes.logging-filter.create
* containers-kubernetes.logging-filter.delete
* containers-kubernetes.logging-filter.update
* containers-kubernetes.logging-autoupdate.changed
* containers-kubernetes.masterlog-retrieve
* containers-kubernetes.masterlog-status
Kind Node.js version Description Change log 

 nodejs:16 [16.x](https://nodejs.org/docs/latest-v16.x/api/) By default, all Node.js actions are executed in a version 16 environment. [CHANGELOG.md](https://github.com/ibm-functions/runtime-nodejs/blob/master/nodejs16/CHANGELOG.md). 
 nodejs:12 [12.x](https://nodejs.org/docs/latest-v12.x/api/) Deprecated [CHANGELOG.md](https://github.com/ibm-functions/runtime-nodejs/blob/master/nodejs12/CHANGELOG.md). 
 nodejs:10 [10.x](https://nodejs.org/docs/latest-v10.x/api/) Deprecated [CHANGELOG.md](https://github.com/ibm-functions/runtime-nodejs/blob/master/nodejs10/CHANGELOG.md). 
 nodejs:8 [8.x](https://nodejs.org/docs/latest-v8.x/api/) Deprecated [CHANGELOG.md](https://github.com/ibm-functions/runtime-nodejs/blob/master/nodejs8/CHANGELOG.md). 





 Migrating from Node.js 12 to Node.js 16 



Table 2. Migrating details from Node.js 12 to Node.js 16

 Package Details 

 cloudant The @cloudant/cloudant SDK package in the nodejs:12 runtime is deprecated and has been replaced with @ibm-cloud/cloudant in nodejs:16. This is a major change and will cause incompatibilities, which might cause your action to fail. If your action uses @cloudant/cloudant consider migrating to @ibm-cloud/cloudant.
* Disabled - The user does not have access to any permissions or subscriptions on the account, including [customer portal](https://control.softlayer.com/) and VPN. If set to disabled by another user on the account, this status can be manually selected and changed at any time.
* VPN Only - The user has access to only VPN connectivity and cannot access the [customer portal](https://control.softlayer.com/). This status can be manually selected or changed at any time.
* Inactive - The user hasn't used the [customer portal](https://control.softlayer.com/) or VPN in the last 60 days (system-generated status).
* cancel_pending - An administrator on the account cancelled this user and the cancellation is being processed. (system-generated status).







 How do I set up SSL VPN? 

SSL VPN is a quick-access connection that connects you to our private network directly for non-production use. For detailed instructions about setting up SSL VPN, see [Getting started with SSL VPN](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-started).





 Are there open-source alternatives to SSL VPN? 

Yes, you can set up [WireGuard](https://www.wireguard.com/) or [OpenVPN](https://openvpn.net/) servers on IBM Cloud, and build your own VPN tunnels from on-premises to IBM Cloud.





 What is the process of installing MotionPro on Windows, Mac, or Linux? 



1. Uninstall your current version of MotionPro (if applicable).
2. Restart your system.
3. Download and install the latest version of MotionPro.
The status of a newly-created custom resolver is initially Critical because the resolver location is not yet enabled. The status changes to Healthy after the resolver location changes to Up.

The following status definitions apply to the resolver locations:



* Up - when the resolver location is functioning.
* Down - when the resolver location is not functioning.



The following status definitions apply to the custom resolver:



* Healthy - when all resolver locations are Up, the status is Healthy.
* Degraded - when there is more than one resolver location, and one is Up but another is Down, then the status changes to Degraded.
* Critical - when all resolver locations are Down, the status changes to Critical.







 Custom resolvers limits 

The following limits exist for the custom resolvers feature:



* Each VPC can have a maximum of one custom resolver.
* Each custom resolver can have a maximum of three locations, either within the same subnet or in different subnets.
* Each custom resolver can have a maximum of 10 forwarding rules.
* You cannot delete the subnet used for the custom resolver.
* You must manually add rules to your security groups to allow traffic from your virtual server instance to the resolver location virtual server instance.
Persistent storage that is dynamically provisioned with a non-retaining storage class can be removed by deleting the PVC.







 Static provisioning 

If you have an existing persistent storage device in your IBM Cloud infrastructure account, you can use static provisioning to make the storage instance available to your cluster.

Static provisioning is a feature that is native to Kubernetes and that allows cluster administrators to make existing storage devices available to a cluster. As a cluster administrator, you must know the details of the storage device, its supported configurations, and mount options.

To make existing storage available to a cluster user, you must manually create the storage device, a PV, and a PVC.

The following image shows how to statically provision file storage in a cluster. This sample flow works similar with other storage types, such as block storage.

Zoom

![Sample flow to statically provision file storage in a cluster, as described in the following list.](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/cs_storage_static-01.svg)

Figure 1. Sample flow to statically provision file storage in a cluster



1. The cluster admin gathers all the details about the existing storage device and creates a persistent volume (PV) in the cluster.
2. Based on the storage details in the PV, the storage plug-in connects the PV with the storage device in your IBM Cloud infrastructure account.
3. The cluster admin or a developer creates a PVC. Because the PV and the storage device already exist, no storage class is specified in the PVC.
4. After the PVC is created, the storage plug-in tries to match the PVC to an existing PV. The PVC and the PV match when the same values for the size, IOPS, and access mode are used in the PVC and the PV. When PVC and PV match, the status of the PVC and the PV changes to Bound. You can now use the PVC to mount persistent storage to your app.