vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To view the virtual server instance details by using the CLI, use the ibmcloud is instance command. Specify the ID or name of the virtual server instance that you want to view by using the INSTANCE variable.

ibmcloud is instance INSTANCE





 Viewing instance details using the API 

You can view the virtual server instance details in your IBM Cloud VPC by using the API.

The following example displays the virtual server instance details for instance profile with a profile name of version=2021-06-22&generation=2.

curl -X GET "https://us-south.iaas.cloud.ibm.com/v1/instance/profiles/$profile_name?version=2021-06-22&generation=2" -H "Authorization: $iam_token"

For more information, see the [Retrieve an instance profile](https://cloud.ibm.com/apidocs/vpcget-instance-profile) in the Virtual Private Cloud API documentation.





 Adjusting bandwidth allocation using the UI 

You can adjust the allocation of your instance's total bandwidth between network bandwidth and storage bandwidth using the UI.

To adjust the bandwidth of an instance:



1. Navigate to a virtual service instance.
2. Select Bandwidth allocation.
3. On the Edit bandwidth allocation screen, adjust the value for Storage bandwidth. You can increase the bandwidth allocated for your block storage boot and attached data volumes. For information about how storage bandwidth is allocated, see [Bandwidth allocation for block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-bandwidth).



After you set storage bandwidth, network bandwidth is automatically adjusted so the total bandwidth of the instance equals the displayed Total bandwidth value. The value for Network bandwidth or Storage bandwidth cannot be set less than 500 Mbps.

To view the new bandwidth allocation, you must either stop and start the instance, or detach and reattach secondary volumes.





 Adjusting bandwidth allocation using the CLI 

You can adjust the allocation of your instance's total bandwidth between network bandwidth and storage bandwidth using the CLI.
By using your own SendGrid account to send your Cloud Directory emails, you have full control. You can decide how the emails are sent, use your own domain name, and define your sender details. With custom email settings, you can reduce the chances of an email getting filtered as spam while also furthering brand recognition for your application.

A direct connection to your email provider can help you to get information about individual messages such as the number of people that open the emails and which messages were not delivered. You can also see overall statistics that you can use to better manage your email campaigns.

Don't have a SendGrid account? [Sign up](https://signup.sendgrid.com/).



1. Go to the Cloud Directory > Email templates > Email settings page of the service dashboard.
2. Select SendGrid. The information that you need to input appears.
3. In SendGrid API key, enter your API key.
4. Configure your Sender details.



1. In From, enter the email address that you want users to receive your emails from.
2. In Sender name, enter the name that you want associated with the "From" email.
3. In Reply-to, enter the email address where you want to receive any replies that someone might have to the email.



5. Click Test to try your configuration with a test email.
6. Click Save to enable your configuration.







 Customizing your email provider 

By defining your own custom extension point to send your Cloud Directory emails, you have full control. You can decide how the emails are sent, use your own domain name, and define your sender details. With custom email settings, you can reduce the chances of an email getting filtered as spam while also furthering brand recognition for your application.

A direct connection to your email provider can help you to get information about individual messages such as the number of people that open the emails and which messages were not delivered. You can also see overall statistics that you can use to better manage your email campaigns.



 Configuring a custom provider with the GUI
Coveo search extension setup 

You can use [Coveo](https://www.coveo.com) to create and manage source documents. The [Coveo Search API](https://docs.coveo.com/en/52/build-a-search-ui/use-the-search-api) can issue search queries on an index. It is a configurable search that you can customize based on your use case. You can access Coveo search through an extension to your assistant.

To set up the extension for Coveo search:



 Add an API key 

In the Coveo Administration Console, add an API key. For detailed instructions, see [Add an API Key](https://docs.coveo.com/en/1718/manage-an-organization/manage-api-keysadd-an-api-key) in the Coveo documentation. Ensure that the API key is set to enable search and to allow Execute queries.





 Download the OpenAPI specification 

Download the OpenAPI specification file: [coveo.openapi.json](https://github.com/watson-developer-cloud/assistant-toolkit/blob/master/integrations/extensions/starter-kits/coveo/coveo.openapi.json). You use this file to add the extension to your assistant.

The OpenAPI specification defines the following method:



* GET /rest/search/v2: Search for content in a set of sources or documents.



For more information about the endpoints, see [Perform a Query](https://docs.coveo.com/en/1445/build-a-search-ui/perform-a-query) in the Coveo documentation.





 Create and add extension 



1. In your assistant, on the Integrations page, click Build custom extension and use the OpenAPI specification file to build a custom extension. For general instructions on building any custom extension, see [Building the custom extension](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-build-custom-extensionbuilding-the-custom-extension).
2.
On IBM Cloud VPC, RSA is the default SSH key type. You can select to change the key type to Ed25519. The Ed25519 SSH key type enables a slightly higher performance benefit because it can give the same level of security as the RSA SSH key type with a smaller key. You can create virtual server instances and bare metal servers with a mix of RSA and Ed25519 SSH keys.



* For Windows or VMware images, you must use the RSA SSH key type. The Ed25519 SSH key type can't be used with Windows or VMware images.
* For Linux images, the Ed25519 SSH key type can be used only if the SSH server for the operating system supports that key type.



In the CLI, you can specify which type of key by using the --key-type option. You can't create SSH keys within the CLI, you can import only an existing SSH key. The default --key-type is RSA. If you try to import a Ed25519 SSH key and don't specify the ed25519 key type, the process fails.

--key-type ed25519





 SSH key types: RSA and Ed25519 in the API 

IBM Cloud® Virtual Private Cloud supports two different types of public SSH keys.



* RSA
* Ed25519



On IBM Cloud VPC, RSA is the default SSH key type. You can select to change the key type to Ed25519. The Ed25519 SSH key type enables a slightly higher performance benefit because it can give the same level of security as the RSA SSH key type with a smaller key. You can create virtual server instances and bare metal servers with a mix of RSA and Ed25519 SSH keys.



* For Windows or VMware images, you must use the RSA SSH key type. The Ed25519 SSH key type can't be used with Windows or VMware images.
* For Linux images, the Ed25519 SSH key type can be used only if the SSH server for the operating system supports that key type.
For more information, see [Creating virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli).





 Toggle the auto-deletion of boot volumes attached to an instance using the API 

By default, a boot volume created as part of provisioning a virtual server instance is deleted when the instance is deleted. If an existing boot volume is attached as part of provisioning a virtual server instance, the volume is preserved by default when the instance is deleted. You can control this by specifying the delete_volume_on_instance_delete property when [creating the instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) or updating the [boot volume attachment](https://cloud.ibm.com/apidocs/vpc/latestupdate-instance-volume-attachment). For more information, see [Creating virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=api).





 Viewing instance details using the UI 

You can view a summary of all instances on the Virtual server instances page. You can access the details page for an instance clicking an individual instance name to view details and make changes. From the instance details page, you can also view the associated network interface, access its subnet, toggle the auto-delete setting, and reserve or release a floating IP address.





 Viewing instance details using the CLI 

You can view the virtual server instance details in your IBM Cloud VPC by using the command-line interface (CLI).

To view the virtual server instance details by using the CLI, use the ibmcloud is instance command. Specify the ID or name of the virtual server instance that you want to view by using the INSTANCE variable.

ibmcloud is instance INSTANCE





 Viewing instance details using the API 

You can view the virtual server instance details in your IBM Cloud VPC by using the API.

The following example displays the virtual server instance details for instance profile with a profile name of version=2021-06-22&generation=2.
"custom_metadata": {
"anyKey": "anyValue
"},
"certificate": "certificate",
"private_key": "private_key",
"description": "Description of my imported certificate.",
"labels": [
"dev","us-south"
],
"name": "example-imported-certificate",
"secret_group_id": "default",
"secret_type": "imported_cert",
"version_custom_metadata": {
"anyKey": "anyValue"
}
}

The command outputs the ID value of the secret, along with other metadata. For more information about the command options, see [ibmcloud secrets-manager secret-create](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-create-command).





 Importing certificates with the API 

You can import certificates programmatically by calling the Secrets Manager API.

The following example shows a query that you can use to import an existing certificate. When you call the API, replace the ID variables and IAM token with the values that are specific to your Secrets Manager instance.

You can store metadata that are relevant to the needs of your organization with the custom_metadata and version_custom_metadata request parameters. Values of the version_custom_metadata are returned only for the versions of a secret. The custom metadata of your secret is stored as all other metadata, for up to 50 versions, and you must not include confidential data.

You can import certificate files that are in the .pem format. Be sure to [convert your PEM files to single-line format](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-troubleshoot-pem) so that they can be parsed correctly by the Secrets Manager API.

curl -X POST
Activity Tracker events 

Use the IBM Cloud® Activity Tracker service to track how users and applications interact with IBM Cloud® Data Engine.

The IBM Cloud Activity Tracker service records user-initiated activities that change the state of a service in IBM Cloud®. For more information, see [Getting started with Activity Tracker](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-getting-started).

You can use the Data Engine service to query Activity Tracker archive files that are stored in an Object Storage bucket in your account. For more information, see [Searching archive data by using the Data Engine service](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-sqlquery).

You can search activity tracker events with Data Engine.



  List of events 

The following table lists the actions that generate an event:



 Actions                                   Description                                                                                                 

 sql-query.sql-job.create                  An SQL query was submitted.                                                                                 
 sql-query.sql-job.list                    List of jobs was retrieved.                                                                                 
 sql-query.sql-job.get                     Details of a job were retrieved.                                                                            
 sql-query.sql-job.disable                 An SQL query streaming job was stopped.                                                                     
 sql-query.catalog-table.list              List of catalog tables was retrieved.                                                                       
 sql-query.catalog-table.get               Details of a catalog table were retrieved.                                                                  
 sql-query.sql-job.disable                 An SQL query streaming job was stopped.                                                                     
 sql-query.sql-job.notify                  An SQL query streaming job can't process all messages before it is rolled out of the EventStreams topic.    
 sql-query.catalog-table-partition.list    List of partitions of a table was retrieved.
If you have a stateful app such as a database, you can create stateful sets that use block storage to store your app's data. Alternatively, you can use an IBM Cloud database-as-a-service and store your data in the cloud.

What do I need to be aware of when adding block storage to a stateful set?
: To add storage to a stateful set, you specify your storage configuration in the volumeClaimTemplates section of your stateful set YAML. The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your block storage that you want to provision. However, if you want to include labels in your volumeClaimTemplates, Kubernetes does not include these labels when creating the PVC. Instead, you must add the labels directly to your stateful set.

You can't deploy two stateful sets at the same time. If you try to create a stateful set before a different one is fully deployed, then the deployment of your stateful set might lead to unexpected results.

How can I create my stateful set in a specific zone?
: In a multizone cluster, you can specify the zone and region where you want to create your stateful set in the spec.selector.matchLabels and spec.template.metadata.labels section of your stateful set YAML. Alternatively, you can add those labels to a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass) and use this storage class in the volumeClaimTemplates section of your stateful set.

Can I delay binding of a PV to my stateful pod until the pod is ready?
: Yes, you can [create a custom storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storagetopology_yaml) for your PVC that includes the [volumeBindingMode: WaitForFirstConsumer](https://kubernetes.io/docs/concepts/storage/storage-classes/volume-binding-mode) field.

What options do I have to add block storage to a stateful set?
FAQs: Hyper Protect Crypto Services Standard Plan 

Read to get answers for questions about IBM Cloud® Hyper Protect Crypto Services Standard Plan.



  How many keys can be stored in a Hyper Protect Crypto Services service instance? 

A Hyper Protect Crypto Services service instance can hold a maximum of 5000 keys.





  How many key rings can be created for a Hyper Protect Crypto Services service instance? 

There is a KMS key ring limit of 50, but there is no GREP11 keystore limit. However, you can create as many as five keystores, including KMS key rings and EP11 keystores, free of charge. Each additional key ring or EP11 keystore is charged with a tiered pricing starting at $225 USD per month. For more information about pricing, see [the pricing sample](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-faq-pricingfaq-how-charge-hpcs).





  Can I add or remove crypto units after I provision a service instance? 

Yes, you can request to add or remove crypto units by raising support tickets in the IBM Cloud® Support Center. For detailed instructions, see [Adding or removing crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-units).





  Is there a Service Level Agreement (SLA) specifically for Hyper Protect Crypto Services? 

Yes, you can find the [SLA](https://www-03.ibm.com/software/sla/sladb.nsf/sla/bm-8506-01) for detailed terms.
You can even remove -A by adding "ForwardAgent yes" to .ssh/config.





 How many worker nodes can I deploy in my Spectrum Symphony cluster through this offering? 

Before deploying a cluster, it is important to ensure that the VPC resource quota settings are appropriate for the size of the cluster that you would like to create (see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas)).

The maximum number of worker nodes that are supported for the deployment value worker_node_max_count is 500 (see [Deployment values](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-deployment-values)). The worker_node_min_count variable specifies the number of worker nodes that are provisioned at the time that the cluster is created, which will exist throughout the life of the cluster. The delta between those two variables specifies the maximum number of worker nodes that can either be created or destroyed by the Symphony Host Factory auto-scaling feature.

The Spectrum Symphony offering supports both bare metal worker nodes and Spectrum Scale storage nodes. The following combinations of values are supported:



* If worker_node_type is set as baremetal, a maximum of 16 bare metal nodes are supported.
* If spectrum_scale_enabled is set to true and storage_type is set as persistent, a maximum of 10 bare metal nodes are supported.



For more information, see [Deployment values](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-deployment-values).

When creating or deleting a cluster with many worker nodes, you might encounter VPC resource provisioning or deletion failures. In those cases, running the Schematics apply or destroy operation again might result in the remaining resources being successfully provisioned or deleted. If you continue to see errors, see [Getting help and support](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-getting-help-and-support).
The space manager can also view the number of instances, service bindings, and resource use for each application in the space. 
 Developer Space developers can create, delete, and manage applications and services within the space. Some of the managing tasks include deploying apps, starting or stopping apps, renaming an app, deleting an app, renaming a space, binding or unbinding a service to an application, viewing the number or instances, service bindings, and resource usage for each application in the space. In addition, the space developer can associate an internal or external URL with an application in the space. 
 Auditor Space auditors have read-only access to all information about the space, such as information about the number of instances, service bindings, and resource use for each application in the space. 



Users that are assigned the manager or developer space role can access the VCAP_SERVICES environment variable. However, a user that is assigned the auditor role can't access VCAP_SERVICES.





 Updating Cloud Foundry access 



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. Select the name of the user that you want to assign access.
3. Select Cloud Foundry.
4. From the row for the organization that you want to manage access for, select the Actions![List of actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) menu and you can click one of three choices:



* Remove user from the organization
* Edit organization role
* View organization details









 Adding a user to an organization 

If you are the manager of an organization that the user is not yet a member of, you assign the user to that organization.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. From the row for the user that you want to assign access, click the Actions icon !
The space manager can also view the number of instances, service bindings, and resource use for each application in the space. 
 Developer Space developers can create, delete, and manage applications and services within the space. Some of the managing tasks include deploying apps, starting or stopping apps, renaming an app, deleting an app, renaming a space, binding or unbinding a service to an application, viewing the number or instances, service bindings, and resource usage for each application in the space. In addition, the space developer can associate an internal or external URL with an application in the space. 
 Auditor Space auditors have read-only access to all information about the space, such as information about the number of instances, service bindings, and resource use for each application in the space. 



Users that are assigned the manager or developer space role can access the VCAP_SERVICES environment variable. However, a user that is assigned the auditor role can't access VCAP_SERVICES.





 Updating Cloud Foundry access 



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. Select the name of the user that you want to assign access.
3. Select Cloud Foundry.
4. From the row for the organization that you want to manage access for, select the Actions![List of actions icon](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public/includes/icons/action-menu-icon.svg) menu and you can click one of three choices:



* Remove user from the organization
* Edit organization role
* View organization details









 Adding a user to an organization 

If you are the manager of an organization that the user is not yet a member of, you assign the user to that organization.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. From the row for the user that you want to assign access, click the Actions icon !