vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[delete-voice-model](https://cloud.ibm.com/apidocs/text-to-speechdelete-a-custom-model) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id Delete a custom model. 
 [get-voice-model](https://cloud.ibm.com/apidocs/text-to-speechget-a-custom-model) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id Get a custom model. 
 [list-voice-models](https://cloud.ibm.com/apidocs/text-to-speechlist-custom-models) Action username,password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, language List custom models. 
 [update-voice-model](https://cloud.ibm.com/apidocs/text-to-speechupdate-a-custom-model) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id, name, description, words Update a custom model. 
 [add-word](https://cloud.ibm.com/apidocs/text-to-speechadd-a-custom-word) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id, word, translation, part_of_speech Add a custom word.
Reloading a software version 

You can reload a version of your software in your private catalog to update the version based on your current repository. When you reload a version, you revert it to its default state when you first imported the software.



  Reloading an unpublished version 

To update a version of your software that isn't published to the catalog, you must reload the version from your source repository and validate it.



1.  In the IBM Cloud console, click Manage > Catalogs > Private catalogs.
2.  Select the private catalog where your product is located.
3.  Select your product.
4.  Select the version of the software you would like to reload.
5.  Open the Actions menu and select Reload version.
6.  Click Reload version.
7.  Configure and validate your software.



Configuration and validation steps vary based on the type of software.





  Reloading a published version 

To update a published version of your software, you must create a draft, reload the version from your source repository, validate, and merge the changes.



1.  In the IBM Cloud console, click Manage > Catalogs > Private catalogs.
2.  Select the private catalog where your product is located.
3.  Select your product.
4.  Select the version of the software that you want to reload.
5.  Open the Actions menu and select Edit to create a draft of your original version.
6.  In the draft version, open the Actions menu and select Reload version.
7.  In the Reload version panel, click Reload version.
8.  Configure and validate your software.

Configuration and validation steps vary based on the type of software.
9.  Open the Actions menu and select Merge changes.
10. Click Merge to update your original version.
19 May 2023 

Updates to English next-generation Medical telephony model
: The English next-generation Medical telephony model has been updated for improved speech recognition:



* en-WW_Medical_Telephony



Added support for French and German on new improved next-generation language model customization
: Language model customization for French and German next-generation models was recently added. This service update includes further internal improvements.

For more information about improved next-generation customization, see



* [February 27, 2023 service update](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notesspeech-to-text-27february2023)
* [Improved language model customization for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-customizationcustomLanguage-intro-ng)



Defect fix: Custom words containing half-width Katakana characters now return a clear error message with Japanese Telephony model
: Defect fix: Per the [documentation](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-corporaWords-ngwordLanguages-jaJP-ng), only full-width Katakana characters are accepted in custom words and the next generation models now show an error message to explain that it's not supported. Previously, when creating custom words containing half-width Katakana characters, no error message was provided.

Defect fix: Japanese Telephony language model no longer fails due to long training time
: Defect fix: When training a custom language model with Japanese Telephony, the service now effectively handles large numbers of custom words without failing.





 2 May 2023 

New procedure for upgrading a custom model that is based on an improved next-generation model
: Two approaches are now available to upgrade a custom language model to an improved next-generation base model. You can still modify and then retrain the custom model, as already documented.
How do I troubleshoot an error when deploying a model? 

You try to deploy a custom model, but it fails with an error if you exceed a machine learning model limit.

  What’s happening 

When you try to deploy your custom model, the following error appears in a dialog: “owner exceeds allowable model limit”

  How to fix it 

To resolve the error, you must reduce the number of models by either undeploying or deleting a model.

If you want to undeploy a model or find a model ID, view the Deployed Models page. See [Undeploying models](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-publish-mlpm-um).

If the model does not show on the Deployed Models page, list the models in your Natural Language Understanding instance, and then delete the model with the [Natural Language Understanding API](https://cloud.ibm.com/apidocs/natural-language-understandingdeletemodel).



1.  Use list models method to get model id(s)
2.  Use delete model method with model id



If you see an error message other than this one, check Cloud Status for any service outages, then go to Support Center for more options to get help.
"customization_id": "63f5807f-a4f2-5766-914e-7abb1a84fe97",
"owner": "297cfd08-330a-22ba-93ce-1a73f454dd98",
"created": "2016-07-15T18:12:31.743Z",
"name": "Test Two",
"language": "en-US",
"description": "Second customization test",
"last_modified": "2016-07-15T18:23:50.912Z"
}
]
}
Show more

The created and last_modified times for the first model are the same because it has yet to be updated. The times for the second model are different, indicating that it has been changed since its initial creation. The information does not include the custom entries defined for the models.





 Updating a custom model 

To update information about a custom model, use the POST /v1/customizations/{customization_id} method. You specify the updates as a JSON object. In addition to modifying its name and description, you can also use this method to add or update word/translation pairs in the model. You cannot change a model's language once it is created.

The following example updates the name and description of a custom model. An empty JSON array is sent with the words parameter to indicate that the model's entries are to remain unchanged.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/json" --data "{"name":"Test Update", "description":"Customization test update", "words":[]}" "{url}/v1/customizations/{customization_id}"

IBM Cloud Pak for Data
Databases for Elasticsearch indexes are only compatible with the same version or plusOne version from the release on which they are created. Only an explicit reindex operation updates an index to the current database version.







 Upgrading in the UI 

You can upgrade to a new version when [restoring a backup](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-dashboard-backups&interface=uirestore-backup) from the Backups tab of your Deployment Overview. Clicking Restore on a backup brings up a dialog box where you can change some options for the new deployment. One of them is the database version, which is auto-populated with the versions available for you to upgrade to. Select a version and click Restore to start the provision and restore process.

To upgrade from Elasticsearch 7.9/7.10 to version 7.17, you must change your plan from Standard to Enterprise. Change your plan by clicking Restore on the Provisioning page on the backup you want to restore, then select 7.17 from the dropdown menu.





 Upgrading through the CLI 

When you upgrade and restore from backup through the IBM Cloud CLI, use the provisioning command from the resource controller.

ibmcloud resource service-instance-create <service-name> <service-id> <service-plan-id> <region>

The parameters service-name, service-id, service-plan-id, and region are all required. You also supply the -p with the version and backup ID parameters in a JSON object. The new deployment is automatically sized with the same disk and memory as the source deployment at the time of the backup.

ibmcloud resource service-instance-create example-es-upgrade databases-for-elasticsearch standard us-south -p '{
Until you re-create the custom language models, speech recognition requests that attempt to use the custom models fail with HTTP error code 400.

You need to re-create custom language models that you created based on the following versions of next-generation models:



* For the en-AU_Telephony model, custom models that you created from en-AU_Telephony.v2021-03-03 to en-AU_Telephony.v2021-10-04.
* For the en-GB_Telephony model, custom models that you created from en-GB_Telephony.v2021-03-03 to en-GB_Telephony.v2021-10-04.
* For the en-US_Telephony model, custom models that you created from en-US_Telephony.v2021-06-17 to en-US_Telephony.v2021-10-04.
* For the en-US_Multimedia model, custom models that you created from en-US_Multimedia.v2021-03-03 to en-US_Multimedia.v2021-10-04.



To identify the version of a model on which a custom language model is based, use the GET /v1/customizations method to list all of your custom language models or the GET /v1/customizations/{customization_id} method to list a specific custom language model. The versions field of the output shows the base model for a custom language model. For more information, see [Listing custom language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageLanguageModelslistModels-language).

To re-create a custom language model, first create a new custom model. Then add all of the previous custom model's corpora and custom words to the new model. You can then delete the previous custom model. For more information, see [Creating a custom language model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-languageCreate).

Updates to multiple next-generation models for improved speech recognition
Complete the update.



1. [ATTACH] Baseline, select the previously created baseline.
2. Select Baseline and [REMEDIATE].



7. Remediate each host in turn. After remediation, ensure to pull the host out of maintenance mode.



If the upgrade process fails immediately and the host cannot enter maintenance mode error message is displayed, shut down the Zerto ZVAs and try again. The ZVRA VMs automatically start as each server comes out of remediation. For more information about continuing Zerto replication during the upgrade process, see [How to Place a Host with an Associated VRA into Maintenance Mode](https://www.zerto.com/myzerto/knowledge-base/how-to-place-a-host-with-an-associated-vra-into-maintenance-mode/).





 Updating vCenter Server and ESXi host licenses 

After you upgrade the vCenter Server and ESXi hosts to vSphere 7, you must update the licenses on the vCenter Server and the ESXi hosts. If you have a vSAN cluster, you must update the vSAN license. Contact [IBM Cloud for VMware Solutions Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) to obtain the new licenses for vSphere 7.



 Procedure to update the vCenter Server license 

Complete the following steps from the vCenter Server user interface.



1. Select Administration menu > Licensing > Licenses.
2. From the Licenses page, click + Add New Licenses.
3. Enter the new vCenter Server 7.0 license key in the New Licenses field. Then, enter a name for the license and click OK.
4. From the Assets page, select the vCenter instance under VCENTER SERVER SYSTEMS and click Assign License. Then, select the new license and click OK.
5. From the Licenses page, find the license with the product name VMware vCenter Server 6 Standard and click Remove Licenses.







 Procedure to update ESXi host licenses 



1. From the Licenses page, click + Add New Licenses.
For example, you can update commands such as pip/pip3 for discovering Python packages that require a later pip version.

The following example shows how to use the cra-custom-script to update the pip version:

!/usr/bin/env bash

if [ "${PIPELINE_DEBUG:-0}" == 1 ]]; then
trap env EXIT
env | sort
set -x
fi

python3 -m pip install --upgrade pip

If your Dockerfile uses an image from a private Docker registry, you can use the cra-custom-script-path parameter to authenticate to a private Docker registry before you run Code Risk Analyzer and to allow Code Risk Analyzer to pull this image for scanning.

The following example shows how to use the cra-custom-script to authenticate to the ibmcloud container registry:

!/usr/bin/env bash

if [ "${PIPELINE_DEBUG:-0}" == 1 ]]; then
trap env EXIT
env | sort
set -x
fi

ibmcloud cr login





 Debugging the Code Risk Analyzer in DevSecOps 

To help with debugging, you can run the Code Risk Analyzer locally as a command-line interface (CLI) on your own local machine. For information about running the ibmcloud cra bom-generate command to generate a BOM file, see [Bill of Materials (BOM)](https://cloud.ibm.com/docs/cli?topic=cli-cra-cli-pluginbom-generate-command). After you generate the BOM file, use the ibmcloud cra cve command to list any vulnerabilities. For more information about running the ibmcloud cra cve command, see [Vulnerability scan](https://cloud.ibm.com/docs/cli?topic=cli-cra-cli-pluginvulnerability-command).

Make sure that the run-cra task does not contain any errors.
To migrate to next-generation models, you must remove features that aren't supported by next-generation models from your speech recognition requests. You can also consider using features such as low latency and character insertion bias that are available only with next-generation models.

For example, the following speech recognition request uses the profanity_filter, redaction, and word_alternatives_threshold parameters with the previous-generation en-US_NarrowbandModel:

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary @{path_to_file}audio-file.flac "{url}/v1/recognize?model=en-US_NarrowbandModel&profanity_filter=true&radaction=true&word_alternatives_threshold=0.50"

Only the word_alternatives_threshold parameter is not supported by next-generation models. To use the equivalent next-generation en-US_Telephony model, you simply change the value that you pass with the model query parameter and eliminate the word_alternatives_threshold parameter:

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary @{path_to_file}audio-file.flac "{url}/v1/recognize?model=en-US_Telephony&profanity_filter=true&radaction=true"





 Step 3: Re-create any custom language models that you use 

You must re-create any custom language models that are based on previous-generation models by basing them on the equivalent next-generation models. This requires that you create a new custom language model and add your corpora, grammars, and custom words from the old model to the new model.

In general, next-generation models do not rely as heavily on custom language models. They use a different approach to transcription that minimizes the need for language model customization.

Next-generation models do not support custom acoustic models. Because of how the models transcribe audio, acoustic model customization is not necessary.
Update your cluster to at least [version 1.24](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_124) as soon as possible.



 Update before master 

The following table shows the actions that you must take before you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.23

 Type Description 

 Unsupported: CoreDNS wildcard queries via Kubernetes plugin CoreDNS no longer supports wildcard DNS queries via the Kubernetes plugin. Applications using such queries must be updated to use an alternative DNS query method. 
 Kubernetes service IP advertisement over BGP If you are using Calico's [Kubernetes Service IP Advertisement over BGP feature](https://www.tigera.io/blog/advertising-kubernetes-service-ips-with-calico-and-bgp/), you need to [add the service IP CIDRs that you want to advertise to the default BGP configuration resource](https://docs.tigera.io/archive/v3.21/reference/resources/bgpconfig). In previous releases, the entire service IP range was advertised by setting an environment variable in the calico-node daemonset. 







 Update after master 

The following table shows the actions that you must take after you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.23

 Type Description 

 Operator Lifecycle Manager (OLM) install no longer managed OLM is no longer installed nor managed by IBM. Existing installs are unchanged and no longer managed after the update. If you are using the OLM components then you must manage updates. If unused, you may [uninstall the OLM components](https://cloud.ibm.com/docs/containers?topic=containers-ts-delete-olm). Refer to the [open source documentation](https://olm.operatorframework.io/) for information on available resources including how to install a new instance of OLM on your cluster.
To update, use the following command:

ibmcloud plugin update

To view installed plug-ins and versions, use the following command:

ibmcloud plugin list



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





 NETWORK COMMANDS 

The following section provides information about CLI commands for network services.





 Flow logs 



 ibmcloud is flow-log-create 

Create a flow log.

ibmcloud is flow-log-create --bucket STORAGE_BUCKET_NAME --target TARGET_IDOrName [--target-type vpc | subnet | instance | nic] [--vpc VPC] [--in IN] [--name NAME] [--active TRUE | FALSE] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is flow-log-create --bucket bucket-name --target 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479
* ibmcloud is flow-log-create --bucket bucket-name --target 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-flow-log
* ibmcloud is flow-log-create --bucket bucket-name --target 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-flow-log --active false
* ibmcloud is flow-log-create --bucket bucket-name --target 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-flow-log --output JSON
* ibmcloud is flow-log-create --bucket bucket-name --target my-vpc --target-type vpc --name my-flow-log
You append the new variable to the cpd_vars.sh script, and source the script to use the variable in your environment. For more information, see Information you need to complete this task in [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing), or refer to any of the upgrade topics for the Speech services.

Defect fix: The Swedish telephony and Italian multimedia models are now available
: Defect fix: The Swedish telephony (sv-SE_Telephony) and Italian multimedia (it-IT_Multimedia) models are now available for installation. Previously, they were not available.

Defect fix: Improved training time for next-generation custom language models
: Defect fix: Training time for next-generation custom language models is now significantly improved. Previously, training time took much longer than necessary, as reported for training of Japanese custom language models. The problem was corrected by an internal fix.

Defect fix: Grammar files now handle strings of digits correctly
: Defect fix: When grammars are used, the service now handles longer strings of digits correctly. Previously, it was failing to complete recognition or returning incorrect results.

Defect fix: Dynamically generated grammar files now work properly
: Defect fix: Dynamically generated grammar files now work properly. Previously, dynamic grammar files could cause internal failures, as reported for integration of Speech to Text with IBM Watson® Assistant. The problem was corrected by an internal fix.

Defect fix: Smart formatting for US English dates is now correct
: Defect fix: Smart formatting now correctly includes days of the week and dates when both are present in the spoken audio, for example, Tuesday February 28. Previously, in some cases the day of the week was omitted and the date was presented incorrectly. Note that smart formatting is beta functionality.

Defect fix: Update documentation for speech hesitation words for next-generation models
: Defect fix: Documentation for speech hesitation words for next-generation models has been updated. More details are provided about US English and Japanese hesitation words. Next-generation models include the actual hesitation words in transcription results, unlike previous-generation models, which include only hesitation markers.
Ubuntu packages N/A N/A Updates to installed Ubuntu packages including apt for [CVE-2019-3462](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3462) and [USN-3863-1](https://ubuntu.com/security/notices/USN-3863-1). 







 Change log for 1.12.4_1534, released 21 January 2019 

The following table shows the changes that are in the patch 1.12.3_1534.



Changes since version 1.12.3_1533

 Component Previous Current Description 

 IBM Cloud Provider v1.12.3-91 v1.12.4-118 Updated to support the Kubernetes 1.12.4 release. 
 Kubernetes v1.12.3 v1.12.4 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.12.4). 
 Kubernetes add-on resizer 1.8.1 1.8.4 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.4). 
 Kubernetes dashboard v1.8.3 v1.10.1 See the [Kubernetes dashboard release notes](https://github.com/kubernetes/dashboard/releases/tag/v1.10.1). Update resolves [CVE-2018-18264](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18264). 
 GPU installer 390.12 410.79 Updated the installed GPU drivers to 410.79. 







 Change log for worker node fix pack 1.12.3_1533, released 7 January 2019
Updating variables with Schematics API 



1. To update variables by using the IBM Cloud® Schematics Python APIs, create two Python files, and provide a name of your choice for those files, for example, schematics_variables_update.py and schematics_env_class.py.
2. Copy and paste the schematics_variables_update.py and schematics_env_class.py Python example code requests to the respective Python files.
3. Copy and paste the [config.json template file](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-update-variablestemplate-file) to a JSON file, for example config.json.
4. Change the following parameters as part of the request:



* Provide the workspace ID w_id generated in both the following functions: schematic_obj.get_workspace(w_id="<w_id>) and schematic_obj.update_variables(w_id="<wi_id>").



5. Make sure to update the required parameters, such as api_key, ibm_customer_number, remote_allowed_ips, ssh_key_name, and zone in the config.json file.
6. Run the Python script by using python3 to update the variables in the Schematics workspace in the IBM Cloud.



Note: The following parameters might not be required in config.json as the Schematics update variables API uses the workspace ID w_id to update the variables against that workspace.

{
  "name": "Schematic Dev Workspace",
  "type": [
    "terraform_v0.13.7"
  ],
  "location": "us-south",
  "description": "Schematic Dev Workspace",
  "tags": [],
  "template_repo": {
    "url": "<GitHub repo URL>",