vania-janet/multiturn-rag-retrieval-data huggingface dataset:
28 July 2022 



* Added extensive content for the new [IBM Cloud Satellite® reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-about) as well as deployment and configuration guidance for that architecture. During this process, there were numerous organizational changes that were made due to the overlap between the IBM Cloud Satellite® reference architecture and the IBM Cloud VPC reference architecture.
* Enabled link to spreadsheet of [control requirements](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-aboutframework-control-requirements) in IBM Cloud Framework for Financial Services.
* Added article [Deploy infrastructure as code for reference architectures](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deploy-infrastructure-as-code) about Terraform automation for IBM Cloud for Financial Services.
* Enhanced content on IBM Cloud® Security and Compliance Center and IBM Cloud for Financial Services profile. See [Compliance monitoring](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-monitoring-compliance).
* Added [site map](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-sitemap).
* Made many editorial updates.







 17 March 2022 



* Clarify guidance around using IBM Cloud Financial Services Validated services depending on whether you are a financial institution or technology vendor. Add guidance about using IBM Cloud Activity Tracker Event Routing in regions where event routing is not available.







 03 February 2022 



* Added information on an approved variation of the VPC reference architecture to allow public internet access to the workload VPC. Added related tutorials on setting up a virtual network firewall in a new edge/transit VPC.







 14 October 2021 



* Revamped [Best practices for software as a service](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practices). Added clarifications and detail.
Backing up and restoring data 

Data on Block Storage for VPC is secured across redundant fault zones in your region. To manually back up your data, use the Kubernetes oc cp command.

You can use the oc cp[command](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commandscp) to copy files and directories to and from pods or specific containers in your cluster

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).

To back up or restore data, choose between the following options:

Copy data from your local machine to a pod in your cluster.

oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath>

Copy data from a pod in your cluster to your local machine.

oc cp <namespace>/<pod>:<pod_filepath>/<filename> <local_filepath>/<filename>

Copy data from your local machine to a specific container that runs in a pod in your cluster.

oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath> -c <container>





 Storage class reference 

For more information about pricing, see [Pricing information](https://cloud.ibm.com/vpc-ext/provision/vs).

Storage classes that have retain in the title have a reclaim policy of Retain. Example: ibmc-file-retain-bronze. Storage classes that don't have retain in the title have a reclaim policy of Delete. Example: ibmc-file-bronze.



 10 IOPs tier 

Name
: ibmc-vpc-block-10iops-tier
: ibmc-vpc-block-retain-10iops-tier
: ibmc-vpc-block-metro-10iops-tier
: ibmc-vpc-block-metro-retain-10iops-tier
Use flow logs to collect, store, and present the Internet Protocol (IP) traffic flowing to and from networks within your VPC. For more information, see [About flow logs (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-flow-logs).

UI enhancement
: Create a new subnet directly from the page where you create a new instance.







 April 2020 



 22 April 2020 

New Frankfurt region
: The Frankfurt region endpoint (eu-de) is now in service at http://eu-de.iaas.cloud.ibm.com. For more information, see [Endpoint URLs](https://cloud.ibm.com/apidocs/vpcendpoint-url) in the IBM Cloud VPC API. See also [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region).





 17 April 2020 

Documentation correction
: IBM Cloud interprets volume capacity units in gibibytes, but the API documentation used gigabytes. This issue is now resolved in the documentation.





 03 April 2020 

Load balancer for VPC update
: Access load balancer monitoring metrics (throughput, active connections, connection rate) using [IBM Cloud Monitoring](https://cloud.ibm.com/docs/vpc?topic=vpc-monitoring-metrics).

The following cipher suites are supported for load balancer HTTPS listeners:



* TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
* TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Backing up and restoring data in Cloud Pak for Data 

Use the following procedures to back up and restore data in your IBM Watson® Discovery for IBM Cloud Pak® for Data instance.

IBM Cloud Pak for Data

This information applies only to installed deployments.

You use the same set of backup and restore scripts to back up and restore data in any of the supported upgrade paths. The backup script stores the version number of the service with data to back up from the existing deployment. The restore script detects the version of the service that is installed on the new IBM Cloud Pak for Data deployment, and then follows the appropriate steps to restore data to the detected version.

The following table lists the upgrade paths that are supported by the scripts.



Supported upgrade paths

 Version in use Version that you can upgrade to 

 4.6.0 4.6.5 
 4.5.x 4.6.0 
 4.0.x 4.6.0 
 2.2.1 4.6.0 



If you are upgrading from 4.x to 4.6.x, a simpler way to complete the upgrade is described in the following topics:



* [Upgrading Watson Discovery from Version 4.6](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-upgrade-v46.html).
* [Upgrading Watson Discovery from Version 4.5.x](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-upgrade-v45.html).
* [Upgrading Watson Discovery from Version 4.0.x](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-upgrade-v4.html).



If you use IBM Cloud Pak for Data Red Hat OpenShift APIs for Data Protection (OADP) backup and restore utility to back up and restore an entire cluster to 4.6, a few extra steps are required.
See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log28-march-2023).







 24 May 2022 



 For all version dates 

Backup for VPC. Accounts with special approval to preview this feature can now [create](https://cloud.ibm.com/apidocs/vpc-betacreate-backup-policy-plan) up to four plans for backup policies. You can now also [update](https://cloud.ibm.com/apidocs/vpc-betaupdate-backup-policy-plan) and [delete](https://cloud.ibm.com/apidocs/vpc-betadelete-backup-policy-plan) existing plans, and [add backup plans](https://cloud.ibm.com/vpc-betacreate-backup-policy) to existing policies. You can use one of the new deletion_trigger sub-properties to specify a custom backup deletion policy. For more information, see [Managing backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-manage&interface=api).

Backup policies now also include information about [backup policy jobs](https://cloud.ibm.com/apidocs/vpc-betalist-backup-policy-jobs). A [backup policy job](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs&interface=api) is automatically created each time a backup has to be created or deleted to meet the backup policy's settings. For more information, see [Backup for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).

The backup API is now generally available, with the exception of the backup jobs API, which remains in beta. See the [Change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log21-june-2022).
: Added how to [add IBM Cloud tags to existing clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workerscluster_tags).

VPC security groups
: [Modify the security group rules](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-security-group)for VPC Gen 2 clusters to allow traffic requests that are routed to node ports on your worker nodes.





 3 February 2020 

Version change log
: Red Hat OpenShift master fix pack [3.11.161_1539_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311161_1539) and worker fix pack [3.11.161_1540_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311161_1540).







 January 2020 



 30 January 2020 

Ingress ALB change log
: Updated the [nginx-ingress image build to 625](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).





 27 January 2020 

Back up and restore File and Block storage
: Added steps for deploying the [ibmcloud-backup-restore Helm chart](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesibmcloud-backup-restore).





 22 January 2020 

Changing VLANs
: After you [change your worker node VLAN connections](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_network_clusterchange-vlans), you can now [move router services across VLANs](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routesmigrate-router-vlan-classic).

Storage utilities
"user_tags": [
"env:test",
"env:prod"
]
}'

When the user tags are matched with a backup policy, a backup is triggered based on the backup plan schedule. For more information, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create).





 Editing fast restore zones in the UI 

Use the following steps to edit the zones where fast restore clones are stored by using the UI. You can add or remove zones as needed.



1. Select a snapshot from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-view&interface=uisnapshots-vpc-view-list-ui).
2. From the overflow menu, click Edit fast restore.
3. From the side panel, select or deselect the zones for fast restore in your region. Review the billing update based on your selection.
4. Click Save. You're returned to the [snapshots details page](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-view&interface=uisnapshots-vpc-view-snapshot-ui). The Fast restore section shows the new zone initially with a pending status.



Fast restore information is updated when you refresh. Zone information is updated to show enabled or disabled, depending on your changes.





 Creating a snapshot clone for fast restore from the CLI 

To create a zonal copy of a snapshot, issue the ibmcloud is snapshot-clone-create command with the snapshot ID and the zone or zones where you want to create copies. The following command example creates the fast restore clone of r138-4463eb2c-4913-43b1-b9bf-62a94f74c146 in the eu-de-3 zone.
However, only one copy of the backup snapshot can exist in each region.







 Next steps 

Review [best practices](https://cloud.ibm.com/docs/vpc?topic=vpc-backups-vpc-best-practices) for creating a backup policy and the [planning checklist](https://cloud.ibm.com/docs/vpc?topic=vpc-backups-vpc-planning). Afterward, you can [create backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan).
Release notes 

Use the release notes to learn about the latest changes to the documentation for the IBM Cloud for Financial Services®.

Looking for IBM Cloud status, platform release notes, security bulletins, or maintenance notifications? See [IBM Cloud status](https://cloud.ibm.com/status?selected=status).



 30 April 2023 



* Updated [Infrastructure as Code (IaC) article](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deploy-infrastructure-as-code) to point at new deployable architectures.







 24 April 2023 



* Removed recommendation that limited deployments to a subset of available multizone regions.







 31 March 2023 



* Integrated references to supplemental guidance for [enterprise account architecture](https://cloud.ibm.com/docs/enterprise-account-architecture?topic=enterprise-account-architecture-about) for large enterprises.







 03 March 2023 



* Updated list of multizone regions which are IBM Cloud for Financial Services Validated to include Toronto (ca-tor) and Sydney (au-syd).







 23 January 2023 



* Updated list of services which are designated as IBM Cloud for Financial Services Validated to include IBM Cloud Security and Compliance Center, IBM Cloud® Continuous Delivery, IBM Cloud® Secrets Manager, and IBM Cloud® Client Virtual Private Network (VPN) for VPC.







 30 September 2022 



* Added contextual links into [IBM Cloud Framework for Financial Services - Control Requirements](https://cloud.ibm.com/docs/framework-financial-services-controls) to make it easier to understand how the control requirements related to implementation guidance.







 24 August 2022 



* Fixed a couple of links and addressed some formatting issues.







 28 July 2022 



* Added extensive content for the new [IBM Cloud Satellite® reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-about) as well as deployment and configuration guidance for that architecture. During this process, there were numerous organizational changes that were made due to the overlap between the IBM Cloud Satellite® reference architecture and the IBM Cloud VPC reference architecture.
* [13 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb1323)



* IBM Cloud Object Storage plug-in version 2.2.9 is available.
* Worker node fix packs 4.8.57_1589_openshift, 4.9.54_1575_openshift, 4.10.51_1555_openshift, and 4.11.26_1542_openshift.



* [10 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb1023)



* New troubleshooting doc for how to recover after deleting a portable subnet in Classic clusters.



* [9 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb0923)



* Block Storage for VPC add-on version 5.1.



* [8 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb0823)



* Cloud Image Key Synchronizer add-on version 1.0.0_1329.



* [2 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb0223)



* Istio add-on 1.14



* [1 February 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-feb0123)



* Persistent VPC load balancers
* Customized VPC load balancer health checks
Migration considerations 

Microsoft SQL Server database supports a number of methods to migrate existing SQL Server databases to IBM Cloud VPC. This documentation does not go into depth on migration, but discusses a number of methods to allow you to choose one or more methods based on your requirements and subsequent assessment.



* Native SQL Server backup/restore.
* Transactional replication.
* Database mirroring.
* Log shipping.
* Always On availability groups.
* Always On distributed availability groups.



Considerations other than the movement of data are required in a migration such as:



* Recreating SQL Jobs on the new server.
* Recreate logins on the new server.
* Data encryption.
* Recovery options during replication.
* Quantity of data to be transmitted.
* Features available in current software versions and editions.





 Native SQL Server backup/restore 

Microsoft SQL Server databases support native backup and restore operations that use full and differential backup (.bak) files or differential restore and log restores. Using native .bak files is the simplest way to back up and restore SQL Server databases and a simple migration method for single or multiple databases in an instance. Full backups of the database on your existing server are taken and copied to an IBM Cloud Object Storage bucket. It is then restored, via a staging server with [s3fs](https://github.com/s3fs-fuse/s3fs-fuse) or [rclone](https://rclone.org/) and SMB\Samba share, on your SQL Server database instance virtual server in IBM Cloud VPC.





 Transactional replication 

Transactional replication enables changes to be transferred between one database and another. These changes can include; data, tables, stored procedures, views etc. The architecture consists of the following:



* Publisher - the primary database that publishes data.
* Subscriber - a secondary database that receives replicated data.
* Distributor - a server that stores metadata and transactions for transactional replication and is ideally a separate server to the publisher or subscriber.



The process works as follows:



* Transactional replication creates a snapshot of the objects and data in the publication database and sends it to the subscriber database.
Release notes for VMware as a Service 

Use these release notes to learn about the most recent updates to IBM Cloud® for VMware as a Service, including new features, component updates, usability enhancements, and bug fixes.



 2023 



 7 July 2023 

Veeam Backup and Replication availability
: The Veeam® Backup and Replication service is now available by default for deployment with new and existing VMware as a Service instances. Service charges are incurred only if you choose to include the service in your order. For more information, see [Managing Veeam for VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-veeam).

User interface updates and enhancements
: The user interface is updated and provides the following enhancements.



* The ordering flow for both VMware as a Service single-tenant Cloud Director sites and associated virtual data centers are now combined into a single ordering page.
* The VMware as a Service Resources page now provides two tabbed views. In the first tab, all virtual data centers in the account are displayed. In the second tab, all authorized Cloud Director sites are displayed with the associated virtual data centers.
* You can now access the VMware console from the virtual data center and Cloud Director site summary pages.
* The Add-on services tab is available on instance details pages to easily manage the Veeam Backup and Replication service.







 2 June 2023 

IBM Cloud data center availability
: (Updated on 30 June 2023) The Frankfurt region is now available to host your provider virtual data center. For more information, see [Planning the deployment](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-plan-deploytenant-plan-deploy-locations).

Accessing VMware as a Service REST APIs
: You can now access VMware as a Service APIs through the IBM Cloud Virtual Private Cloud.
* ibmcloud is snapshots --copies crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-fc2a25b9-1cca-4cee-a9c4-0f350d7923f5
* ibmcloud is snapshots --copies-remote-region us-south
* ibmcloud is snapshots --source-volume-remote-region us-south
* ibmcloud is snapshots --source-snapshot-remote-region us-south
* ibmcloud is snapshots --backup-policy-plan r134-7d36a9df-9512-496e-8ad0-054cb4dd854c --backup-policy r134-3f56e0fa-1cfb-4341-9e57-de2a6345e7b3
* ibmcloud is snapshots --backup-policy-plan bkp-plan-do-not-delete --backup-policy bkp-policy-do-not-delete
* ibmcloud is snapshots --source-snapshot r142-abb79ab7-d79d-4863-9678-123d1dffee06
* ibmcloud is snapshots --clones-zone-name us-south-2







 Command options 



* --volume: ID, name, or CRN of the source volume.
* --tag: Tag for this resource.
* --source-image: ID, name, or CRN of the source image.
* --copies: ID, name, or CRN of the snapshot copies. Combination of these three types are not supported. Only passing either one of three types is supported.
* --copies-remote-region: Name of the snapshot copies remote region.
* --source-snapshot: ID or name of source snapshot.
: For more information, see the change logs: [4.11.13_1533_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10.41_1546_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410),[4.9.51_1566_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8.52_1581_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7.60_1590_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47).





 17 November 2022 

Block Storage for VPC add-on versions 4.4.13_1712 and 5.0.2_1713
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).





 16 November 2022 

Master fix pack 4.7.59_1589_openshift, 4.8.52_1580_openshift, 4.9.51_1565_openshift, 4.10.39_1545_openshift, and 4.11.12_1532_openshift.
new util.Attribute(ep11.CKA_CLASS, ep11.CKO_SECRET_KEY),
new util.Attribute(ep11.CKA_KEY_TYPE, ep11.CKK_AES),
new util.Attribute(ep11.CKA_VALUE_LEN, 128/8),
new util.Attribute(ep11.CKA_ENCRYPT, true),
new util.Attribute(ep11.CKA_DECRYPT, true),
);

const derived = [];

async.eachSeries([
{ PubKey: bob.PubKeyBytes, PrivKey: alice.PrivKeyBytes },
{ PubKey: alice.PubKeyBytes, PrivKey: bob.PrivKeyBytes }
], (data, cb) => {
const combinedCoordinates = util.getPubKeyBytesFromSPKI(data.PubKey);

client.DeriveKey({
Mech: {
Mechanism: ep11.CKM_ECDH1_DERIVE,
ParameterB: combinedCoordinates
},
Template: deriveKeyTemplate,
BaseKey: data.PrivKey
}, (err, data={}) => {
if (!err) {
derived.push(data);
}

cb(err);
});
}
Show more









 Protecting keys 

You can protect a key by wrapping it and then decrypt the key by invoking the unwrapping feature.



 WrapKey 

The WrapKey function wraps (encrypts) a key.

Enterprise PKCS #11 over gRPC

Enterprise PKCS #11

PKCS #11





 Description Binds to EP11 m_WrapKey, which is an implementation of PKCS #11 C_WrapKey. 
 Parameters message WrapKeyRequest { bytes Key = 1; bytes KeK = 2; bytes MacKey = 3; Mechanism Mech = 4; } message WrapKeyResponse { bytes Wrapped = 5; }
To generate a new DEK, omit the plaintext attribute. The service generates a random plain text (32 bytes), wraps that value, and then returns both the generated and wrapped values in the response. The generated and wrapped values are base64 encoded and you will need to decode them in order to decrypt the keys. 



Your wrapped data encryption key, containing the base64 encoded key material, is returned in the response entity-body. The response body also contains the ID of the key version that was used to wrap the supplied plain text. The following JSON object shows an example returned value.

{
"ciphertext": "eyJjaXBoZXJ0ZXh0IjoiYmFzZTY0LWtleS1nb2VzLWhlcmUiLCJpdiI6IjRCSDlKREVmYU1RM3NHTGkiLCJ2ZXJzaW9uIjoiNC4wLjAiLCJoYW5kbGUiOiJ1dWlkLWdvZXMtaGVyZSJ9",
"keyVersion": {
"id": "02fd6835-6001-4482-a892-13bd2085f75d"
}
}

If you omit the plaintext attribute when you make the wrap request, the service returns both the generated data encryption key (DEK) and the wrapped DEK in base64 encoded format.

{
"plaintext": "Rm91ciBzY29yZSBhbmQgc2V2ZW4geWVhcnMgYWdv",
"ciphertext": "eyJjaXBoZXJ0ZXh0IjoiYmFzZTY0LWtleS1nb2VzLWhlcmUiLCJpdiI6IjRCSDlKREVmYU1RM3NHTGkiLCJ2ZXJzaW9uIjoiNC4wLjAiLCJoYW5kbGUiOiJ1dWlkLWdvZXMtaGVyZSJ9",
"keyVersion": {
"id": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6"
}
}

The plaintext value represents the unwrapped DEK, and the ciphertext value represents the wrapped DEK and are both base64 encoded. The keyVersion.id value represents the version of the root key that was used for wrapping.

If you want Hyper Protect Crypto Services to generate a new data encryption key (DEK) on your behalf, you can also pass in an empty body on a wrap request. Your generated DEK, containing the base64 encoded key material, is returned in the response entity-body, along with the wrapped DEK.