vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The features include such attributes as part of speech, lexical stress, word-level prominence, and positional features such as the position of the syllable or word in the sentence.

The DNNs are trained on natural human speech to predict the acoustic features of the audio. This modular approach has the advantage of enabling fast and easy training, as well as independent control of each component. Once the base networks are trained, they can then be adapted to new speaking styles or voices for branding and personalization purposes.

Neural voices produce speech that is crisp and clear, with a very natural-sounding and smooth audio quality. For more information about the service's neural voice technology, see



* The documentation [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices)
* The research paper [High quality, lightweight and adaptable Text to Speech using LPCNet](https://arxiv.org/abs/1905.00590)
* The research paper [Transplantation of Conversational Speaking Style with Interjections in Sequence-to-Sequence Speech Synthesis](https://arxiv.org/abs/2207.12262)







 Concatenative synthesis 

All concatenative voices, also referred to as standard voices, were deprecated as of 2 December 2020. The following information is maintained for general information purposes only. For more information about the deprecation of the concatenative voices, see the [2 December 2020 service update](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-release-notestext-to-speech-2december2020) in the release notes for IBM Cloud.

Concatenative synthesis relies on an inventory of acoustic units from a large synthesis corpus to produce output speech for arbitrary input text. It is based on the following pipeline of processes. These processes facilitate an efficient, real-time search over this inventory of units followed by a post-processing of the units.



* Acoustic model - This model consists of a decision tree that is responsible for generating candidate units for the search.
--secret-group GROUP
: Secret group ID of the IBM Cloud Secret Manager instance where the secrets are persisted. To get a secret group ID, see the [Secrets Manager CLI reference](https://cloud.ibm.com/docs/secrets-manager-cli-plugin?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-groups-command).

Example:

ibmcloud oc ingress instance default set --cluster --cluster a111aaa11a1aaaaaaa1 --crn crn:v1:staging:public:secrets-manager:eu-gb:a/1a11a1a111aa11aa111aa1a1111aa1a1:1aaa1a1a-aaaa-11aa-1a11-a11aaa1a11a1:secret:a1a11a11-111a-11a1-aa11-11aaa1a11a11 --name my-secret-manager --namespace default --secret-group 90e059dd-d04e-a32b-010f-4d303b9050b8





 ibmcloud oc ingress instance default unset 

Virtual Private Cloud

Classic infrastructure

Remove a Secrets Manager instance as the default instance.

If no default instance is set, your secrets are only written directly to the cluster and are not written to any Secrets Manager instance.

ibmcloud oc ingress instance default unset --cluster CLUSTER --crn CRN --name NAME [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--crn
: Required. The CRN of the IBM Cloud Secret Manager instance.

--name NAME
: Required. The name of the Secret Manager instance.

-q
: Optional: Do not show the message of the day or update reminders.

Example:
"type": "application/vnd.ibm.secrets-manager.secret.group+json",
"updated_at": ""
}
]
},
"warnings": null
}







 Get a secret group 

Use this command to get the details of a secret group.

vault read [-format=FORMAT] auth/ibmcloud/manage/groups/SECRET_GROUP_ID



 Prerequisites 

You need the [Reader service role](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam) to get the details of a secret group.





 Command options 

-format
: Prints the output in the format that you specify. Valid formats are table, json, and yaml. The default is table. You can also set the output format by using the VAULT_FORMAT environment variable.





 Examples 

Get the details of a specific secret group in JSON format.

vault read -format=json auth/ibmcloud/manage/groups/9c6d20ad-779e-27c5-3842-2a20b19abfcf





 Output 

The command returns the following output:

{
"request_id": "ab6b22d9-8e42-d23f-31d8-a4865b5a40e7",
"lease_id": "",
"lease_duration": 0,
"renewable": false,
"data": {
"created_at": "2020-10-05T17:43:49Z",
"description": "A group of secrets.",
"id": "9c6d20ad-779e-27c5-3842-2a20b19abfcf",
"name": "my-secret-group",
"type": "application/vnd.ibm.secrets-manager.secret.group+json",
"updated_at": ""
},
"warnings": null
}







 Update a secret group
"serial_number": "38:eb:01:a3:22:e9:de:55:24:56:9b:14:cb:e2:f3:e3:e2:fb:f5:18",
"validity": {
"not_after": "2023-10-05T11:49:42Z",
"not_before": "2022-06-27T11:58:15Z"
},
"version_custom_metadata": {
"custom_version_key": "custom_version_value"
}
}
],
"total_count": 1
}

The downloaded property indicates whether the data for each secret version was already read or accessed. If the payload_available field has a value of true, it means that you're able to access or [restore the secret data of that version](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-version-history&interface=uirestore-secret-api). For more information about the required and optional request parameters, check out the [API reference](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2).

You can store metadata that is relevant to the needs of your organization with the version_custom_metadata request parameter. The custom metadata of your secret is stored as all other metadata, for up to 50 versions, and you must not include confidential data. For more information about the required and optional request parameters, check out the [API reference](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2).





 Updating secret versions metadata in the UI 

You can update the metadata of a specific version of a secret by using the Secrets Manager UI.

To update the metadata of a secret version, complete the following steps.



1. In the console, click the Menu icon !
1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root Scored 1 Pass IBM 
 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive Scored 1 Pass IBM 
 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 Scored 1 Pass IBM 







 1.2 API server 



Section 1.2 API server benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 1.2.1 Ensure that the --anonymous-auth argument is set to false Not Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-411ibm-remediations-and-explanations-411) IBM 
 1.2.2 Ensure that the --basic-auth-file argument is not set. Scored 1 Pass IBM 
 1.2.3 Ensure that the --token-auth-file parameter is not set. Scored 1 Pass IBM 
 1.2.4 Ensure that the --kubelet-https argument is set to true. Scored 1 Pass IBM 
 1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate. Scored 1 Pass IBM 
 1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate. Scored 1 Pass IBM 
 1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow Scored 1 Pass IBM 
 1.2.8 Ensure that the --authorization-mode argument includes Node Scored 1 Pass IBM 
 1.2.9 Ensure that the --authorization-mode argument includes RBAC Scored 1 Pass IBM 
 1.2.10 Ensure that the admission control plug-in EventRateLimit is set Not Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-411ibm-remediations-and-explanations-411) IBM
1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root Scored 1 Pass IBM 
 1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive Scored 1 Pass IBM 
 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 Scored 1 Pass IBM 







 1.2 API server 



Section 1.2 API server benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 1.2.1 Ensure that the --anonymous-auth argument is set to false Not Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-412ibm-remediations-and-explanations-412) IBM 
 1.2.2 Ensure that the --basic-auth-file argument is not set. Scored 1 Pass IBM 
 1.2.3 Ensure that the --token-auth-file parameter is not set. Scored 1 Pass IBM 
 1.2.4 Ensure that the --kubelet-https argument is set to true. Scored 1 Pass IBM 
 1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate. Scored 1 Pass IBM 
 1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate. Scored 1 Pass IBM 
 1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow Scored 1 Pass IBM 
 1.2.8 Ensure that the --authorization-mode argument includes Node Scored 1 Pass IBM 
 1.2.9 Ensure that the --authorization-mode argument includes RBAC Scored 1 Pass IBM 
 1.2.10 Ensure that the admission control plug-in EventRateLimit is set Not Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-412ibm-remediations-and-explanations-412) IBM
To see the Kubernetes LoadBalancer service UID, run kubectl get svc myloadbalancer -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC NLB name.

The VPC NLB name has a format kube-<cluster_ID>-<kubernetes_lb_service_UID>. To see your cluster ID, run ibmcloud oc cluster get --cluster <cluster_name>. To see the Kubernetes LoadBalancer service UID, run oc get svc myloadbalancer -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC NLB name.

Do not rename any VPC NLBs that are created automatically for LoadBalancer services. If you rename a VPC NLB, IBM Cloud Kubernetes Service automatically creates another VPC NLB for the LoadBalancer service.

ibmcloud is load-balancers

In the following example CLI output, the VPC NLB that is named kube-bh077ne10vqpekt0domg-046e0f754d624dca8b287a033d55f96e is created for the Kubernetes LoadBalancer service:

ID Name Created Host Name Is Public Listeners Operating Status Pools Private IPs Provision Status Public IPs Subnets Resource Group
To see the Kubernetes LoadBalancer service UID, run oc get svc myloadbalancer -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC ALB name.

The VPC ALB name has a format kube-<cluster_ID>-<kubernetes_lb_service_UID>. To see your cluster ID, run ibmcloud oc cluster get --cluster <cluster_name>. To see the Kubernetes LoadBalancer service UID, run oc get svc myloadbalancer -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC ALB name.

Do not rename any VPC ALBs that are created automatically for LoadBalancer services. If you rename a VPC ALB, Red Hat OpenShift on IBM Cloud automatically creates another VPC ALB for the LoadBalancer service.

ibmcloud is load-balancers

In the following example CLI output, the VPC ALB that is named kube-bsaucubd07dhl66e4tgg-1f4f408ce6d2485499bcbdec0fa2d306 is created for the Kubernetes LoadBalancer service:

ID Name Family Subnets Is public Provision status Operating status Resource group
r006-d044af9b-92bf-4047-8f77-a7b86efcb923 kube-bsaucubd07dhl66e4tgg-1f4f408ce6d2485499bcbdec0fa2d306 Application mysubnet-us-south-3 true active online default
6. If you created a public LoadBalancer service, curl the hostname of the Kubernetes LoadBalancer service that is assigned by the VPC ALB that you found in step 4. Example:
To see the Kubernetes LoadBalancer service UID, run oc get svc myloadbalancer -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC NLB name.

Do not rename any VPC NLBs that are created automatically for LoadBalancer services. If you rename a VPC NLB, Red Hat OpenShift on IBM Cloud automatically creates another VPC NLB for the LoadBalancer service.

ibmcloud is load-balancers

In the following example CLI output, the VPC NLB that is named kube-bh077ne10vqpekt0domg-046e0f754d624dca8b287a033d55f96e is created for the Kubernetes LoadBalancer service:

ID Name Created Host Name Is Public Listeners Operating Status Pools Private IPs Provision Status Public IPs Subnets Resource Group
06496f64-a689-4693-ba23-320959b7b677 kube-bh077ne10vqpekt0domg-046e0f754d624dca8b287a033d55f96e 8 minutes ago 1234abcd-us-south.lb.appdomain.cloud yes 95482dcf-6b9b-4c6a-be54-04d3c46cf017 online 717f2122-5431-403c-b21d-630a12fc3a5a 10.241.0.7 active 169.63.99.184 c6540331-1c1c-40f4-9c35-aa42a98fe0d9 00809211b934565df546a95f86160f62
6. Access the IP address of the Kubernetes LoadBalancer service that you found in step 4 and your app port in the format <external_IP>:<app_port>.
7.
nodeAnalyzer:
nodeAnalyzer:
deploy: true
apiEndpoint: API_ENDPOINT
benchmarkRunner:
deploy: false
kspmCollector:
apiEndpoint: API_ENDPOINT
Show more

Where



* CLUSTER_NAME is the name of the cluster where you are deploying the agent.
* SERVICE_ACCESS_KEY is the Workload Protection instance access key.
* INGESTION_ENDPOINT is the instance's ingestion endpoint. For example, ingest.us-east.security-compliance-secure.cloud.ibm.com
* API_ENDPOINT is the intance's API endpoint. For example, us-east.security-compliance-secure.cloud.ibm.com







 Step 4. Install the helm chart 

To deploy the agent, the Secure components, or both, you must install the sysdig/sysdig-deploy chart and use the variables yaml file that you configured in the previous step.

Run the following command to install the agent by using the helm chart:

helm install -n ibm-observe sysdig-agent sysdig/sysdig-deploy -f agent-values-monitor-secure.yaml

Run the following command to install the agent by using the helm chart and the variables yaml file:
Allow users to create apps or audit your cluster activity by [assigning cluster access](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms). To see specific permissions and actions that you can grant users, see the [user access permissions reference](https://cloud.ibm.com/docs/containers?topic=containers-access_reference).





Need help? Check out [Troubleshooting clusters and masters](https://cloud.ibm.com/docs/containers?topic=containers-debug_clusters) and [Troubleshooting worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).





 Manage the network 

Review the following optional topics to manage the network connectivity of your cluster components and connections to other networks. For example, you might need to connect the workloads in your cluster to workloads in another private network. Or, you might return to this section later if you need to make more portable IP addresses available for load balancer services that expose apps in your cluster.



* Connections to other networks and workloads:



* Set up VPN connectivity between your [classic cluster](https://cloud.ibm.com/docs/containers?topic=containers-vpn) or [VPC cluster](https://cloud.ibm.com/docs/containers?topic=containers-vpc-vpnaas) and remote network environments, other VPCs, and more.
* To route responses from your cluster back to your on-premises network in VPN solutions that preserve the request source IP address, add [custom static routes](https://cloud.ibm.com/docs/containers?topic=containers-static-routes) to worker nodes for on-premises subnets.



* Subnets, service endpoints, and VLANs:
New environment variables used in IBM Cloud Pak for Data documentation
: Most commands in the Speech to Text for IBM Cloud Pak for Data documentation have been updated to use a common set of environment variables. The documentation provides a script to automatically export the environment variables before you run installation, upgrade, and administration commands. After you source the script, you can copy most commands from the documentation and run them without making any changes.

The environment variables that the script defines include the following:



* ${PROJECT_CPD_INSTANCE} identifies the project where you plan to install IBM Cloud Pak for Data and the Speech services.
* ${PROJECT_CPD_OPS} identifies the project for the IBM Cloud Pak for Data platform operator.
* ${PROJECT_CPFS_OPS} identifies the project for the IBM Cloud Pak for Data foundational services.



For more information about using the environment variables, see [Best practice: Setting up install variables](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=installing-best-practice-setting-up-install-variables).

The ttsVoiceMarginalCPU property is no longer documented
: The ttsVoiceMarginalCPU property has been removed from the documentation for the Speech services custom resource. The property manages the tradeoff between concurrency and speech synthesis speed. The default value of 400 ensures a reasonable balance for most customers and maintains real-time synthesis.

New German next-generation multimedia model
: The service now offers a next-generation multimedia model for German: de-DE_Multimedia. The new model is generally available. It does not support low latency. It does support language model customization and grammars as generally available functionality.

For more information about all available next-generation models and their customization support, see



* [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)
* [Customization support for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-supportcustom-language-support-ng)
untaint Do not mark a resource as tainted. 
 state An advanced state management command to write sub commands to remove or move rm && mv. 





 Commands 

The Commands API executes one or group of Terraform commands by using the JSON file for your workspace command requirements. The access control such as plan, apply, destroy, or refresh are applicable for Commands API. Select your region where the workspace is created, and use the following syntax to run the commands API.

Syntax

ibmcloud schematics workspace commands --id WORKSPACE_ID --file FILE_NAME

Command options



Schematics Terraform commands flags

 Flag Required / Optional Description 

 --id or -i Required The unique ID of the workspace where you want to run the commands. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --file or --f Required Path to the JSON file containing the list of Terraform commands. 



Sample payload of Test.JSON file:

{
"commands": [
{
"command": "state show",
"command_params": "data.template_file.test",
"command_name": "Test1",
"command_desc": "Showing state",
"command_onerror": "continue"
},
{
"command": "taint",
"command_params": "null_resource.sleep",
"command_name": "Test2",
"command_desc": "Marking taint",
"command_onerror": "continue"
},
{
"command": "untaint",
"command_params": "null_resource.sleep",
"command_name": "Test3",
"command_desc": "Marking untaint",
"command_onerror": "continue"
},
{
"command": "state list ",
"command_params": "",
* [Terraform commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencetf-cmds)



* [Commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencecmds)



* [Terraform state file commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-file-cmds)



* [ibmcloud schematics state pull](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-pull)
* [ibmcloud schematics workspace state show](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-show)
* [ibmcloud schematics workspace state mv](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-wks_statemv)
* [ibmcloud schematics workspace state rm](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-wks_staterm)



* [Workspaces commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-commands)



* [ibmcloud schematics workspace action](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-action)
9. You can update the snapshot space for the new volume to add more, less, or no snapshot space.
10. You can select the OS Type to be different than the original volume or to stay the same.
11. You can specify IOPS or IOPS Tier for the new volume if you want to. The IOPS designation of the original volume is set by default. Available Performance and size combinations are displayed.



* If your original volume is 0.25 IOPS Endurance tier, you can't make a new selection.
* If your original volume is 2, 4, or 10 IOPS Endurance tier, you can move anywhere between those tiers for the new volume.



12. Check the box if you read and agreed to the terms and conditions.
13. Click Create to continue.



After you click Create, the order confirmation window appears. When you close the window, you return to the resources list. You can go back to your list of Block Storage for Classic volumes to click the newly provisioned duplicate. The volume details section displays information such as Duplicate Type, a link to the parent volume's details page and the name of the snapshot that was used to create the duplicate.







 Creating a duplicate LUN from the SLCLI 

The commands that are described in the article are part of the SLCLI. For more information about how to install and use the SLCLI, see [Python API Client](https://softlayer-python.readthedocs.io/en/latest/cli/).

To create an independent duplicate Block Storage for Classic volume, you can use the following command.

 slcli block volume-duplicate --help
Usage: slcli block volume-duplicate [OPTIONS] ORIGIN_VOLUME_ID

Options:
-o, --origin-snapshot-id INTEGER
ID of an origin volume snapshot to use for
duplcation.
-c, --duplicate-size INTEGER Size of duplicate block volume in GB. If
no size is specified, the size of the origin
volume will be used.
Potential Sizes:
[20, 40, 80, 100, 250, 500, 1000, 2000,
On the Git Repos and Issue Tracking User Settings dashboard, from the menu, click your avatar and select Edit profile. Click Account. On the Account page, in the Change username section, find your Git Repos and Issue Tracking username. Your username is also displayed as the first segment of the URL for any personal Git repos that you create.
6. Use your Git Repos and Issue Tracking username and personal access token to authenticate with your Git repo from an external Git client.



To learn more, see [Personal access tokens](https://us-south.git.cloud.ibm.com/help/user/profile/personal_access_tokens.md).





 Creating an SSH key 

To create an SSH key, see [Generate an SSH key pair](https://us-south.git.cloud.ibm.com/help/user/ssh.mdgenerate-an-ssh-key-pair). Accessing your repositories with SSH authentication might require more configuration for proxies and firewalls.

To learn more, see [Use SSH keys to communicate with GitLab](https://us-south.git.cloud.ibm.com/help/user/ssh.html).





 Verifying host key fingerprints 

The first time that you connect to a server by way of Git over SSH, the Git client prompts you to accept the host key fingerprint of the server. You can use the following host key fingerprints to verify SSH connections with the IBM Cloud Git Repos and Issue Tracking servers. Proceed with the connection only if the host key fingerprint matches the specified value for the server that is provided in the following code snippets.

au-syd.git.cloud.ibm.com:
ECDSA:
SHA256:oUpjbxJ+UVIlBvcdcKuprZ0JEtCWkTu1yFTdfFHoEF8
MD5:ca:34:27:f1:49:fd:b4:9d:e8:ce:d2:7b:99:a1:dd:98