vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Add to estimate - if you want to see how adding a replica impacts your monthly cost, click it. The monthly cost estimate is displayed. You can Review the estimate for more billing information and details or Clear the estimate and return to the Replica create page.









 Add replication to file share from the CLI 

Use the CLI to create a file share with replication, or update a file share to include replication.

As of 30 May 2023, you can use --mount-targets instead of -targets option. To see and use the updated option, set the feature environment variable IBMCLOUD_IS_FEATURE_FILESHARE_CHANGE_TO_MOUNT_TARGETS to true.

export IBMCLOUD_IS_FEATURE_FILESHARE_CHANGE_TO_MOUNT_TARGETS=true



 Create a file share with replication from the CLI 

Run the ibmcloud is share-create command and specify the following properties to define the replica share for a new file share:



* --replica-share-iops- The maximum input/output operation performance bandwidth per second for the file share; applicable for custom profile file share.
* --replica-share-name- Specify a name for the replica file share.
* --replica-share-profile- The profile the file share uses.
* --replica-cron-spec- The cron specification for the file share replication schedule.
* --replica-mount-target- TARGETS_JSON|@TARGETS_JSON_FILE, specify file share mount targets in JSON or in a JSON file.
* --replica-zone- The zone in which the replica file share is to be created. This zone must be a different zone in the same region as the source share.



Syntax:
For Frequency, the options are hourly, daily, weekly, monthly, or by cron-spec expression:



* For hourly, enter a value in the range 0 - 60 to specify exactly how many minutes past the hour, every hour, every day the replication is to start.
* For daily, specify the starting time in hours and minutes in Coordinated Universal Time. Enter a value between 00:00 and 23:59. For your convenience, the Coordinated Universal Time value is converted into your local time.
* For weekly, specify the days of the week you want replication to run and the start time in Coordinated Universal Time. Enter a value between 00:00 and 23:59.
* For monthly, choose a day 1 - 28. For the start time, enter a value between 00:00 and 23:59.
* If you specify a cron-spec expression, replications must be scheduled not less than 1 hour. Enter the replication frequency in cron-spec format: minute, hour, day, month, and weekday. For example, to replicate every day at 5:30 PM you need to enter 30 17 * * .



9. The encryption is inherited from the primary share. If you specified customer-managed encryption, the key management system is shown along with the root key. You can't encrypt a replica share with a different key.
10. In the side panel, you have multiple options.



* Apply a code - if you have a discount code, you can add it in the field.
* Create file share - when you're ready to create your replica share, click it.
* Get sample API call - if you want to get the curl command code to create the replica with these exact settings, click it.
* Add to estimate - if you want to see how adding a replica impacts your monthly cost, click it. The monthly cost estimate is displayed. You can Review the estimate for more billing information and details or Clear the estimate and return to the Replica create page.









 Add replication to file share from the CLI 

Use the CLI to create a file share with replication, or update a file share to include replication.

As of 30 May 2023, you can use --mount-targets instead of -targets option.
* [Install the Node Feature Discovery and NVIDIA GPU operators for your cluster version](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/getting-started.html).
* Verify that you can run GPU workloads by [deploying a sample job](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appgpu_app).



Master versions
: Master fix pack update change log documentation is available for Red Hat OpenShift [4.5.18_1521_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4518_1521), [4.4.29_1525_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4429_1525), [4.3.40_1546_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4340_1546), and [3.11.306_1573_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311306_1573_master).





 13 November 2020 

IBM Cloud Activity Tracker and IAM events
: Added [IAM actions and Activity Tracker events](https://cloud.ibm.com/docs/openshift?topic=openshift-api-at-iamks-ingress) for the Ingress secret, Ingress ALB, and NLB DNS APIs.





 9 November 2020 

New! Reduced and hourly billing is available for OCP licenses
: Now when you create worker nodes with the latest flavors, OCP license costs are billed at reduced rates as part of the worker node cost. You can check the new rates in the pricing estimate when you create a cluster or worker pool.
If you need a more detailed information on Gobal Replication Service, see [Global Replication Services Solution using IBM Power Virtual Server](https://cloud.ibm.com/media/docs/downloads/power-iaas/Global_Replication_Services_Solution_using_IBM_Power_Virtual_Server.pdf)





 Locations that support global replication service 

You can use the GRS location APIs to determine the locations that support storage replication and their mapped location. For more information, see [all disaster recovery locations supported by Power System Virtual Server](https://cloud.ibm.com/apidocs/power-cloudpcloud-locations-disasterrecovery-getall).

The following table shows the datacenter and their corresponding pool level detail that supports replication:



Table 1. Replication enabled datacenter and their supported storage pool

 Site 1 Site 2 

 Datacenter name WDC06 DAL12 
 Storage pool Tier3-Flash-2 <br>Tier3-Flash-1 <br>Tier1-Flash-1 Tier3-Flash-4 <br>Tier3-Flash-3 <br>Tier1-Flash-3 







 Pricing for Global replication service 

When you create a replicated-enabled volume, GRS creates the following four copies of volumes in the storage backend for the replication relationship:



* Master volume on primary site
* Master change volume on primary site to store changes
* Auxiliary volume on secondary site
* Auxiliary change volume on secondary site to store changes.



You are charged from the location where you create a replication-enabled volume. No charges for the auxiliary volume from the remote site.

The volume of size X GB is charged based on following two components:



* The master volume is charged 2x size based on its Tier under the existing part numbers for Tier 1 and Tier 3.
* Replication capability cost is charged $Y/GB under a new part number "GLOBAL_REPLICATION_STORAGE_GIGABYTE_HOURS" that is independent of volume tier.



Upon a site failure due to a catastrophe, metering is not available from the failed site. The auxiliary volumes are charged from remote site for its 2x size based on its tier. There is no replication capability cost for any replication-enabled volume.
For more information about hardware specifications, see [S922](https://www.ibm.com/downloads/cas/KQ4BOJ3N), and [E980 (Data centers other than Dallas and Washington)](http://www-01.ibm.com/support/docview.wss?uid=ssm1platformaix9080-M9S-vios-only). 
 Cores There is a core-to-vCPU ratio of 1:1. For shared processors, fractional cores round up to the nearest whole number. For example, 1.25 cores equals 2 vCPUs. 
 Memory Select the amount of memory for the Power Systems Virtual Server. If you choose to use more than 64 GBs of memory per core, you are charged a higher price. For example, when you choose one core with 128 GBs of memory, you are charged the regular price for the first 64 GBs. After the first 64 GBs (64 - 128 GBs), you are charged a higher price. 
 Boot image Select a version of the IBM-provided AIX or IBM i operating system stock image. You can also select Linux stock images for SAP HANA and SAP NetWeaver applications. For these SAP stock images it is mandatory to set an SSH key while creating the VM. You will be able to access the VM instance only via SSH after launch. However, it is recommended to set a password by using the passwd command during the first SSH access. By setting a password, you are able to access the instance in the UI console. You can also [deploy your own custom image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-image) of AIX, IBM i, or Linux. IBM also provides a community supported CentOS image under Linux operating system. However, IBM does not provide any support for this image. For CentOS support, see the [CentOS forum](https://forums.centos.org/) or [FAQ](https://forums.centos.org/app.php/help/faq) page.
Note that when smart contracts are installed on peers that run a Fabric v2.x image, the smart contract is launched in its own pod instead of a separate container on the peer, which accounts for the smaller amount of resources required on the peer.

While users of a free cluster must use default sizes for the containers associated with their nodes, users of paid clusters can set these values while the node is being created by clicking the Resource allocation box during the creation of their nodes. If this box is not checked, the default resource allocations, which can be seen below, will be used.

For cases when a user wants to minimize charges without stopping or deleting a node, it is possible to scale the node down to a minimum of 0.001 CPU (1 milliCPU). Note that the node will not be functional when using this amount of CPU.

While the figures in this topic endeavor to be precise, be aware that there are times when a node may not deploy even when it appears that you have enough space in your cluster. Make sure to reference your Kubernetes dashboard to see when components deploy and for error messages when they don't. In cases where a component doesn't deploy for a lack of resources, even if there seems to be enough space in the cluster, you will likely have to deploy additional cluster resources for the component to deploy.

The Resource allocation panel in the console provides default values for the various fields that are involved in creating a node. These values are chosen because they represent a good way to get started. However, every use case is different. While this topic provides guidance for ways to think about these values, it ultimately falls to the user to monitor their nodes and find sizings that work for them. Therefore, barring situations in which users are certain that they need values different from the defaults, a practical strategy is to use these defaults at first and adjust them later. For an overview of performance and scale of Hyperledger Fabric, which the IBM Blockchain Platform is based on, see [Answering your questions on Hyperledger Fabric performance and scale](https://www.ibm.com/blogs/blockchain/2019/01/answering-your-questions-on-hyperledger-fabric-performance-and-scale/).
Routing concepts 

Eliminate excess latency by analyzing and optimizing routing decisions across the global internet using real-time network connections. Reduce internet latency on average by 35% and connection errors by 27%.



  Smart Routing 

Route connections across the internet efficiently by avoiding packet loss, congestion, and outages.

Smart Routing optimizes the paths your data takes across the internet. Optimal paths are determined by analyzing latency and packet loss data collected from real-time network connections. Smart Routing uses this data to detect which transit providers are operating best between any two points on the planet.

The optimized route is different from the regular request path. It can take up to 24 hours to switch from the regular request path to the optimized route after you enable Smart Routing for your domain.





  Tiered Caching 

Increase cache hit ratios using concentrated connections to reduce requests to customer origins.

Tiered Caching reduces requests to customer origins and decreases the load on the origin server. Tiered Caching accomplishes this by first asking other PoPs if they have the requested data when a cache miss takes place. Customers see a performance increase because distances between our PoPs are typically shorter than the distances between PoPs and origins. By taking advantage of the cached data, customers benefit because of a decrease in the load on their origin server.

Tiered Caching also concentrates connections to origin servers so they come from a smaller number of PoPs. This allows fewer open connections going to the origin.
For more information, see [Using Netezza Performance Server as a data source](https://cloud.ibm.com/docs/netezza?topic=netezza-netezzakafkadatasourcekafka) and [Using Netezza Performance Server as a data sink](https://cloud.ibm.com/docs/netezza?topic=netezza-netezzakafkadatasinkkafka).







 Known issues 

datasource is a reserved keyword now. If you want to use datasource as an identifier, enclose it in double quotation marks ("datasource").

Example:

SYSTEM.ADMIN(ADMIN)=> create table t1 ( "datasource" int);
CREATE TABLE







 June 2022 

As of June 14, 2022, several fixes, and a stability patch for critical issues.



 Fixes 



* Fixed the issue with queries failing with error No such table exists on a second attempt.
* Fixed the issue with DBOS crashing while redumping modified plan to file.
* Fixed the issue with intermittent hangs.
* Fixed ERROR : unexpected error 12 that occurred when you ran merge queries dynamically through a stored procedure.
* Fixed the issue with memory leaks with stored procedures that occurred after the ENABLE_SPROC_HIST_LOGGING variable was enabled.
* Fixed the issue with postmaster crashing by compiling librest with Go 1.18.







 Known issues 



* If a large database backup to Azure Blob Storage with a single stream fails, update the number of streams to 16 and retry the backup.









 May 2022 

As of May 20, 2022, workload enhancements and network policies support is added.



 New features 



* Two new workload contours NC0 and NC3 are available for a wider range of configuration options for provisioning and scaling.
* Network policies support is added. You can control the set of the IP addresses and hostnames that your Netezza Performance Server database can connect to or can be connected from by using network policies.
If you selected Reserved, your vCPU model settings are based on your selection of Preconfigured or Customizable.

If you selected Preconfigured, you have the following options for allocated vCPU and RAM limits.



Table 1. Preconfigured vCPU and RAM options

 Size vCPU RAM 

 Small 64-cores 512 GB 
 Medium 128-cores 1024 GB 
 Large 256-cores 2048 GB 



If you selected Customizable, you can customize your reserved vCPU and RAM limits.

The vCPU maximum number is limited to the 40 cores with hyperthreading on each host. This limit allows for a maximum of 80 vCPU virtual machines.





 Recommended services 

The following services are preinstalled and ready to use in all virtual data centers. Service charges are incurred only if you choose to use the service.



* Veeam® Availability Suite and Veeam Cloud Connect Replication
* Zerto



For more information, see [Managing Veeam for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_veeam) and [Managing Zerto for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_zerto-portal).





 Summary 

Based on your selected configuration for the virtual data center, the estimated price is instantly generated and displayed in the Summary pane.

You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. The tool is useful if you want to estimate the price of the selected VMware Shared resources together with other IBM Cloud resources that you might consider purchasing.





 Procedure to order VMware Shared On-demand 



1. In the VMware Solutions console, click the VMware Shared card in the Platforms section.
2. On the Create tab of the VMware Shared page, select On-demand.
3. Enter the virtual data center name and select a resource group.
4. Select a deployment topology according to your needs.
5.
19 April 2018 

Bug fixes and performance improvements
: Added support for Japanese relations.
: Improved German keywords.
: Fixed a bug that caused incorrect entity mention text to be returned.
: Fixed a bug that could cause poor results for targeted sentiment.
: Fixed a bug that caused the returned analyzed_text to include characters that were not analyzed.





 5 April 2018 

Webpage improvements
: Improved webpage content fetching. If you use the url parameter to analyze webpages, you'll see better results, especially from webpages that use framesets and cookies.

Korean concept improvement
: Minor improvements to Korean concepts.







 16 March 2018 

Language support improvements
: Added support for German categories, relations, and semantic roles.
: A new relation type system is used for German relations. To view details, see the [Relation types (Version 2)](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-relation-types-version-2) page.
: Improved German keywords and sentiment.
: Added support for Japanese categories and concepts.
: Language detection improvements.
: Improved webpage cleaning.
: Improved French and German entities models. The models use a new entity type system. Check out the new entity types and subtypes on the [Entity types and subtypes (Version 2)](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-entity-types-version-2) page. When your application is compatible with the new type system, change the version date parameter in your requests to 2018-03-16 to use the new model. The following are the differences between the Version 1 type system and the Version 2 type system.



* New entity types:



* Date
* Duration
* Measure
* Money
* Number*
* Percent*
* PhoneNumber*
* Ordinal
* Time
* URL*



* Removed entity types:



* Anatomy
* Award
* Broadcaster
* Company
* Crime
* Drug
* HealthCondition
Adding a customer-managed remote gateway 

API Connect V10 Reserved deploys with the IBM DataPower API gateway by default. You can deploy additional DataPower API gateways, which you manage, for use with your Reserved instance.

API Connect V10 Reserved deploys with the IBM DataPower API gateway already configured. The gateway hosts published APIs and provides the API endpoints used by client applications. The gateways also executes API proxy invocations to back-end systems and enforce API policies that manage client identification, security, and rate limiting. This default gateway is managed by IBM.

You might want to deploy additional API Gateways for your Reserved instance; for example, to distribute API endpoints for different purposes. Any gateways that you deploy are considered remote because they are external to your Reserved service. You are responsible for deploying and managing your remote gateway.

To register a remote API Gateway with your Reserved instance, click the Download Gateway tile on the administration Home page, and complete the following steps:

Step 1: Download - Select your environment and download the package.

Step 2: Install - Select your environment to see the installation instructions for the gateway.

Step 3: Configure - Follow the instructions in [Adding remote gateways in V10 Reserved](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.install.doc/ri_gwy_intro.html) to set up certificates and configure the new gateway.

Step 4: Register - Click the link to register the new gateway with your API Connect Reserved instance. For instructions, see [Registering a gateway with V10 Reserved](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.install.doc/ri_gwy_reg.html)

After the gateway is registered, it is available for use in your Reserved service. You can manage the gateways availability to users as explained in [Managing gateways](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-ri-mng-gwy).
FAQs: VMware 



  How is VMware licensed? 

When you deploy ESX through the IBM Cloud® catalog, VMware Service Provider Program licensing (VSPP) automatically enables. On deployment, a default user 'ibmvmadmin' is added to the ESX server for data collection. Do not delete this default user. VSPP charges for RAM that is reserved and used for all “powered on” virtual machines (not “per socket” like a standard host license).





  How is VMware vSphere licensed? 

When you deploy vSphere, VMware Service Provider Program licensing (VSPP) automatically enables. On deployment, a default user 'ibmvmadmin' is added to the Host for vSphere administration and integration services.





  What license level is enabled when you deploy vSphere from the IBM Cloud® catalog? 

Enterprise Plus, the highest vSphere license level.





  Can I create an isolated private VMware cloud? 

Yes, you can deploy bare metal systems and install any supported hypervisor (including VMware ESX) on these hosts. You can also deploy virtual machines by using the native management tools. By default, systems are deployed in VLANs for segmentation and networking components (such as gateways, routers, and firewalls) and are used to create almost any topology.





  Can I deploy VMware components directly from the IBM Cloud® catalog? 

Yes, you have two options:



1.  Select and deploy the ESX hypervisor automatically with a monthly bare metal system. You can also deploy vCenter management automatically with a virtual machine or bare metal system (Windows only).
2.  Deploy a bare metal host with a free-operating system, such as CentOS, and then install ESX manually by using Remote Console and virtual media access of the host. You can then install vCenter Server manually or deploy the VMware vCenter Server Appliance that operates on Linux.
Why can't I communicate with the IBM Cloud service from my virtual server instance? 

To communicate with the IBM Cloud® server, your endpoint gateway must be configured correctly.

  What’s happening 

Cannot communicate with the IBM Cloud service.

  Why it’s happening 

This issue can be due to multiple causes.

  How to fix it 

If you are unable to communicate with the IBM Cloud service from your virtual server instance, follow these steps:



1.  Verify that the service instance is valid (not deleted).
2.  Check all reserved IP addresses that are associated with the endpoint gateway and make sure they are valid IP addresses. For more information, see [Associated reserved IP shows address 0.0.0.0](https://cloud.ibm.com/docs/vpc?topic=vpc-troubleshoot-reserved-ip).
3.  Verify that the service can be reached by using the reserved IP address instead of the URL, assuming one was provided by the service. For more information, see [Virtual server instance can access a service by using the reserved IP, but cannot access the service's URL](https://cloud.ibm.com/docs/vpc?topic=vpc-troubleshoot-cannot-access-url).
4.  Verify that connectivity to cloud service endpoints is functional - host google.com 161.26.0.10. If the connection fails, open an IBM Support case.
5.  Verify that network ACLs are defined on the virtual server instance (or reserved IP) subnet that prevents communication between the two.