vania-janet/multiturn-rag-retrieval-data huggingface dataset:
name: 'networkZoneId',
value: '76921bd873115033bd2a0909fe081b45',
};

// RuleContext
const ruleContextModel = {
attributes: [ruleContextAttributeModel],
};

// ResourceAttribute
const resourceAttributeModel = {
name: 'accountId',
value: '12ab34cd56ef78ab90cd12ef34ab56cd',
};

// Resource
const resourceModel = {
attributes: [resourceAttributeModel],
};

const params = {
ruleId: 'testString',
ifMatch: 'testString',
contexts: [ruleContextModel],
resources: [resourceModel],
description: 'this is an example of rule',
enforcementMode: 'disabled',
};

contextBasedRestrictionsService.replaceRule(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});





 Updating network zones 

You can modify the list of allowed locations where an access request can originate. A set of one or more network locations can be specified by IP addresses (individual addresses, ranges, or subnets), VPCs, or service references. You can update a network zone that is used in a rule, or integrate the new updated network zones into your rules later.



1. In the IBM Cloud console, click Manage > Context-based restrictions, and select Network zones.
2. Select the Actions icon !
<br>Alternative path <br>Upgrade the instance by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, provision a new vCenter Server instance with NSX-T and vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).<br><br><br> <br><br> * Broadwell and Skylake servers are not supported.<br> * Add-on services to upgraded instance are not supported.<br> * Conversion of vSphere switching from N-VDS to VDS is not supported.<br><br><br> 
 VMware vSphere Server (VSS) Preferred path <br>Consider provision vSphere bare metal server and deploy a new [VSS bare metal server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverview) or a bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview).
Static route add-on change log 

For deployment steps, see the [managed static route add-on](https://cloud.ibm.com/docs/containers?topic=containers-static-routes) docs.

For steps on updating the static route add-on, see [Updating managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons).

To view a list of add-ons and the supported cluster versions, run the following command or see the [Supported cluster add-ons table](https://cloud.ibm.com/docs/containers?topic=containers-supported-cluster-addon-versions).

ibmcloud ks cluster addon versions



  Version 1.0.0 



  Change log for 1.0.0_649, released 8 September 2021 



*  Uses apiextensions.k8s.io/v1 instead of apiextensions.k8s.io/v1beta1.
<br>Alternative path <br>Self-upgrade by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, you must provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).<br><br><br> <br><br> * Broadwell and Skylake servers are not supported.<br> * Add-on services to upgraded instance are not supported.<br><br><br> 
 vCenter Server (VCS) with NSX-T instances with vSphere V6 Preferred path <br>Provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview). <br>Alternative path <br>Upgrade the instance by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, provision a new vCenter Server instance with NSX-T and vSphere V7 and migrate workloads.
Best practices for application development 

Information previously contained on this page has been refreshed and merged into the [Creating Applications tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-app). For the most up to date recommendations, refer to that tutorial.
vCenter Server (VCS) with NSX-T instances with vSphere V6 Preferred path <br>Provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview). <br>Alternative path <br>Upgrade the instance by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, provision a new vCenter Server instance with NSX-T and vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).<br><br><br> <br><br> * Broadwell and Skylake servers are not supported.<br> * Add-on services to upgraded instance are not supported.<br> * Conversion of vSphere switching from N-VDS to VDS is not supported.<br><br><br> 
 VMware vSphere Server (VSS) Preferred path <br>Consider provision vSphere bare metal server and deploy a new [VSS bare metal server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverview) or a bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview).
Known limitations for IBM Cloud Juniper vSRX 

There are some limitations to be aware of when using IBM Cloud® Juniper vSRX.



* Due to incompatible networking elements, the Juniper vSRX solution is not available as follows:



* 10 Gbps version in WDC01
* 1G and 10G High Availability versions in: DAL05, SJC01, and WDC01



* Only IBM Cloud certified versions of vSRX are supported. The list of supported versions can be found [here](https://cloud.ibm.com/docs/vsrx?topic=vsrx-vsrx-versions).
* There is no support to upgrade from Standalone to High Availability mode.
* There is no support to downgrade from High Availability to Standalone mode.
* There is no support to upgrade from 1G to 10G or downgrade from 10G to 1G.
* Only the latest IBM Cloud certified vSRX release is available for new orders and upgrades. Requests for older IBM Cloud certified vSRX releases should be made through an IBM Support ticket. Limitations for upgrading and downgrading can be found in [Upgrading the vSRX](https://cloud.ibm.com/docs/vsrx?topic=vsrx-upgrading-the-vsrx).
* Older Juniper vSRX gateways were deployed with Linux Bridge based networking virtualization. This virtualization can achieve only limited throughput and never line-rate throughput. Most deployments of vSRX 18.4 and later leverage SR-IOV, which provides improved throughput.
* Older Juniper vSRX gateways were deployed with a 60-day evaluation license, which might cause the kernel to generate error messages even when another (valid) license is on the system. Remove any 60-day evaluation licenses to avoid this issue. To do so, follow these steps:



1. Log in to your vSRX gateway device.
2. Enter CLI mode by running the command cli at the console prompt.
3. Run the following command to get the license identifier:

show system license

Output is similar to the following:

License usage:
vCenter Server (VCS) with NSX-V instances with vSphere V6 Preferred path <br>Provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview). <br>Alternative path <br>Self-upgrade by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, you must provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).<br><br><br> <br><br> * Broadwell and Skylake servers are not supported.<br> * Add-on services to upgraded instance are not supported.<br><br><br> 
 vCenter Server (VCS) with NSX-T instances with vSphere V6 Preferred path <br>Provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview).
The Canary release deployment strategy is the slowest to move from a previous release to a current release of the software that is being deployed. Canary deployments allow organizations to test two different software versions side by side in production.



 Before you begin 

Before you start this tutorial, make sure that you have the following resources in place:



* An [IBM Cloud account](https://cloud.ibm.com/registration), with a Standard plan. For more information about working with your IBM Cloud account, see [Setting up your IBM Cloud account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started) and [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
* A provisioned VPC infrastructure. Based on the type of deployment strategy that you want to use, click one of the following links to create an IBM Cloud® Schematics workspace. This workspace generates and applies the Terraform plan to create the VPC, the virtual server instances, and the Load Balancer that are required to run and access the app.

[!
You can't revert your managed Istio add-on to a previous version. If you want to revert to an earlier minor version, you must uninstall your add-on and then reinstall the add-on by specifying the earlier version.



1. Review the current version of your Istio add-on.

kubectl get iop managed-istio -n ibm-operators -o jsonpath='{.metadata.annotations.version}'
2. Review the available Istio add-on versions.

ibmcloud ks addon-versions
3. Review the changes that are in each version in the [Istio add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog).
4. If you are upgrading from version 1.11 to version 1.12 and your Istio components were provisioned at version 1.10 or earlier:



1. Run the command to get the details of your mutating webhook configurations.

kubectl get mutatingwebhookconfigurations

Example output.

NAME WEBHOOKS AGE
istio-sidecar-injector 5 32m
2. In the output, find the istio-sidecar-injector and review the WEBHOOKS column. If there are 5 or more webhooks, run the following command to delete the additional webhooks.

kubectl delete mutatingwebhookconfigurations istio-sidecar-injector && kubectl rollout restart deploy addon-istio-operator -n ibm-operators

Example output.

mutatingwebhookconfiguration.admissionregistration.k8s.io "istio-sidecar-injector" deleted
3. Check that the additional webhooks were deleted. Get the details of your mutating webhook configurations and verify that there are 4 istio-sidecar-injector webhooks.

kubectl get mutatingwebhookconfigurations
VMware vSphere Server (VSS) Preferred path <br>Consider provision vSphere bare metal server and deploy a new [VSS bare metal server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverview) or a bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview). <br>Upgrade your VMware vSphere servers by using [the upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Broadwell servers, provision new servers as this server type is not supported by vSphere V7.<br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers.<br><br><br> <br><br> * Broadwell and Skylake servers are not supported.<br><br><br> 
 Roll-your-own (classic bare metals servers) Preferred path <br>Consider provision vSphere bare metal server and deploy a new bare metal server or a bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview).<br><br><br><br> * Provision a new bare metal server with VMware ESXi V7.<br> * Swap out the ESXi V6 servers.<br> * Reload OS image with ESXi V7.
](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_lbargument-reference)<br> * Update protocol and connection limit argument for [ibm_is_lb_listener](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_lb_listenerargument-reference)<br> * Update protocol and connection limit argument for [ibm_is_lb_listener](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_lb_listenerargument-reference)<br> * Support mode argument and status, created_at, members attributes for [ibm_dl_gateway](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/dl_gatewayargument-reference)<br> * Update the arguments and attributes for [ibm_is_vpn_gateway_connection](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpn_gateway_connectionattribute-reference)<br><br><br>
[version 2.x](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/2-x_Pill.png)*[Channel application capabilities and peer Fabric images are 2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2)
* ![version 1.4][version 1_.4Channel application capabilities are 1.4 and peer Fabric images are 1.4 or 2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14)



* Fabric v2.0 introduced a new distributed process to manage the lifecycle of a smart contract that allows for decentralizing the governance of smart contracts on a channel. Whenever possible, it is recommended that customers should move to using the new smart contract lifecycle to avoid any interruption of service in later upgrades when Fabric no longer supports the v1.4 process for installing and instantiating smart contracts.
To develop new applications for IBM Blockchain Platform v2.5.4, using the latest v2.4 Hyperledger Fabric Gateway peer service and API are recommended, as documented in [Running a Fabric Application](https://hyperledger-fabric.readthedocs.io/en/release-2.4/write_first_app.html). However, for existing applications developed for IBM Blockchain Platform v2.5.2 and earlier, no migration is required— your existing applications will continue to run on v2.5.4. In addition, the prior [Hyperledger Fabric v2.2](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/developing_applications.html) (and earlier) development methods, using the legacy SDKs (both high-level and low-level programming models), remain supported for new applications in IBM Blockchain Platform v2.5.4 and Fabric v2.4.

Although legacy applications will continue to run on v2.5.4, upgrading development methods to use the v2.4 Fabric Gateway API as soon as possible is recommended.





 Fabric Peer Gateway documentation 

For details on developing new applications for Hyperledger Fabric v2.4 networks, refer to the [v2.4 Fabric Gateway](https://hyperledger-fabric.readthedocs.io/en/release-2.4/write_first_app.html) documentation. The documentation includes v2.4 [Fabric Gateway samples](https://github.com/hyperledger/fabric-gateway/tree/main/samples), [connection details](https://hyperledger-fabric.readthedocs.io/en/release-2.4/write_first_app.htmlfirst-establish-a-grpc-connection-to-the-gateway), and related client application development topics.





 Connecting to the Fabric Gateway peer service 

A client application that uses the v2.4 Fabric Gateway peer service needs to specify the connection details for the target peer.
}'
Show more





 Creating a mount target for an existing share 

The following examples compare how to create a mount target for an existing file share before and after the 2023-05-30 versioned change. The path of the API request is different before and after the change.

This request creates a target for an existing file share, specifying API version 2023-05-29 or earlier. The path of the API includes /targets.

curl -X POST "$vpc_api_endpoint/v1/shares/$share_id/targets?version=2023-05-29&generation=2&maturity=beta" -H "Authorization: Bearer $iam_token" -H 'Content-Type: application/json' -d '{
"name": "target-3",
"vpc": {
"id": "6e01bc24-4a6e-4a0c-a1bd-4caa0c8159e7"
}
}'

This request creates a mount target for an existing file share, specifying API version 2023-05-30 or later. The path of the API includes /mount_targets.

curl -X POST "$vpc_api_endpoint/v1/shares/$share_id/mount_targets?version=2023-05-30&generation=2&maturity=beta" -H "Authorization: Bearer $iam_token" -H 'Content-Type: application/json' -d '{
"name": "mount-target-4",
"vpc": {
"id": "549192f1-d238-42bd-8657-b6034a08f04e"
}
}'





 Updating a file share mount target 

The following examples compare how to make a request to update a file share mount target before and after the 2023-05-30 versioned change. The path of the API request is different before and after the change.

This request updates a mount target, specifying API version 2023-05-29 or earlier. The path of the API includes /targets.
- Mounts /etc/os-release or /etc/lsb-release as read only. - Mounts /etc/kubernetes instead of /etc or /usr/libexec/kubernetes to install the FlexVolume binary. - Mounts /usr/local/bin instead of /usr/local to install the s3fs binary.





 Change log for version 2.1.18, released 14 July 2022 



* Updates the UBI Image to 8.6-854
* Resolves [CVE-2022-29824](https://nvd.nist.gov/vuln/detail/CVE-2022-29824), [CVE-2021-40528](https://nvd.nist.gov/vuln/detail/CVE-2021-40528), [CVE-2022-22576](https://nvd.nist.gov/vuln/detail/CVE-2022-22576), [CVE-2022-27774](https://nvd.nist.gov/vuln/detail/CVE-2022-27774), [CVE-2022-27776](https://nvd.nist.gov/vuln/detail/CVE-2022-27776), [CVE-2022-27782](https://nvd.nist.gov/vuln/detail/CVE-2022-27782), [CVE-2022-25313](https://nvd.nist.gov/vuln/detail/CVE-2022-25313), [CVE-2022-25314] ([https://nvd.nist.gov/vuln/detail/CVE-2022-25314](https://nvd.nist.gov/vuln/detail/CVE-2022-25314))
* Updates Golang to 1.18.3







 Change log for version 2.1.17, released 28 June 2022 



* Updates the UBI to 8.6-751.1655117800
Upgrading to a newer version of R1Soft 

IBM tries to have the latest software available for provisioning or through OS reload. However, if you need a version newer than what IBM offers, you need to get the latest from R1Soft.

You need to verify with R1Soft that your license is valid with newer versions of the software.
Currently, there isn't a migration path from Direct Link on Classic offerings to the new IBM Cloud Direct Link. You must order a Direct Link Dedicated or Direct Link Connect connection.





 Learn more 

If you require a diverse and redundant Direct Link on Classic deployment, review the [Models for diversity and redundancy document](https://cloud.ibm.com/docs/direct-link?topic=direct-link-models-for-diversity-and-redundancy-in-direct-link).

If you require a diverse, redundant, or multi-cloud deployment for Direct Link Connect on Classic or Direct Link Exchange on Classic, you can review the [Alternatives document](https://cloud.ibm.com/docs/direct-link?topic=direct-link-alternatives-for-your-ibm-cloud-direct-link-deployment).
<br><br> * [ibm_atracker_route](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/atracker_route)<br> * [ibm_atracker_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/atracker_settings)<br> * [ibm_atracker_target](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/atracker_target)<br><br><br> <br><br> * [ibm_atracker_endpoints](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/atracker_endpoints)<br> * [ibm_atracker_routes](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/atracker_routes)<br> * [ibm_atracker_targets](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/atracker_targets)<br><br><br> 







 App Configuration 



 Resources Data sources
List of Move and Migrate SAP workloads approaches

 Move and Migrate SAP workloads approach Description Common Usage Downtime Pre/Post Migration Work Data Transfer 

 Heterogeneous System Copy that uses SWPM Move or Re-Platform to different CPU Architecture, OS, or database. Uses System Copy Export/Import of SWPM Commonly used to change database server in preparation for more significant move; for example, move to SAP HANA DB with a Classical Migration approach Yes Significant preparation and post processing required. System Copy Export dump 
 Homogeneous System Copy that uses SWPM (Only option for System Copies that are running SAP HANA DB) Move or Re-Platform to more to newer OS or database version. Cannot be used to move between CPU Architecture or Endianness. Uses SAP Database Backup with SWPM. Move to new SAP HANA target, or to move to new OS target with existing AnyDB. Also used to create fresh sandboxes of an existing system (with or without Logical System Name change). Yes. Some reduction in downtime possible depending on preparation, change freeze, and delta change sync (of log files) in failover to target Less preparation than heterogeneous System Copy; moderate to significant post processing required depending on scenario (in most cases, the Logical System Name is changed, for example, BDLS) SAP Database Backup 
 SAP HANA System Replication (HSR) with replicated database mirror on cloud Secondary failover site is hosted on cloud HA and DR scenarios Yes minimal, depends on design and failover factors (for example, cost-optimised or performance) Using SAP Landscape Management (LaMa), set up and execution can be automated Log or memory shipping; SYNCMEM, FULLSYNC, SYNC, or ASYNC modes 
 System Relocation that uses SAP LaMa to orchestrate move Physically or virtually relocate running or shutdown instances. Uses SAP LaMa. Cannot relocate SAP HANA DB MDC Tenants. Moving individual SAP instances to new infrastructure landscape that is already set up. Yes minimal, running systems have downtimes as they are stopped, unprepared, then prepared and started Using SAP LaMa, relocation can be automated Package network transfer that uses LaMa or LaMa adapter for VMware