vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Primitive program interfaces vary based on the type of task that you want to run on the quantum computer and the corresponding data that you want returned as a result. After identifying the appropriate primitive for your program, you can use Qiskit to prepare inputs, such as circuits, observables (for Estimator), and customizable options to optimize your job. For more information, see the appropriate topic:



* [Sampler](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-example-sampler)
* [Estimator](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-example-estimator)







 Next steps 



* Use the [Getting started guide](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-get-started) to create an instance and run your first job.
* Use Qiskit [tutorials](https://qiskit.org/documentation/tutorials.html) to learn how to create circuits with Qiskit.
* Watch the [Qiskit Runtime Tutorial video](https://www.youtube.com/watch?v=b9mdMye-iVk) for more information.
* View the [Qiskit Runtime API reference](https://cloud.ibm.com/apidocs/quantum-computing) to understand how to use cURL commands to work with your cloud service instance.
* Learn about [IBM Quantum Computing](https://www.ibm.com/quantum-computing/).
To use private network endpoints, the following account features must be enabled for your account:



* Virtual routing and forwarding (VRF)
* Service endpoints

Enabling service endpoints means that all users in the account can connect to private network endpoints.



You must first enable virtual routing and forwarding in your account, and then you can enable the use of IBM Cloud private service endpoints.



* To enable VRF, you create a support case.
* To enable service endpoints, you use the IBM Cloud CLI. For more information about how to enable your account, see [Enabling VRF and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint).







 Step 2. Setting a private endpoint 

After your account is enabled for VRF and service endpoints, you can configure a logging agent to connect to an IBM Log Analysis instance through the private network.

A service instance can have a private network endpoint, a public network endpoint, or both.



* A public network endpoint is a service endpoint on the IBM Cloud public network.
* A private network endpoint is a service endpoint that is accessible only on the IBM Cloud Private network.



The IBM Log Analysis service offers [private API endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api_private).





 Step 3. Configure your logging agent 

You can [configure the logging agent](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-logdna_agent) to use the private network by using a private endpoint as the ingestion URL.

What happens when you configure the logging agent to use a private endpoint?



* Private endpoints are not accessible from the public internet.
* All traffic is routed to the IBM Cloud Private network.
* Services like IBM Log Analysis are no longer served on an internet routable IP address.









 Limitations that use private endpoints 

The logging web UI is not supported on the private network.
You need to specify the right [roles and permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accessaccess-setup) to a user who controls the state file. For more information about Schematics service access roles and permissions for



* [Workspace Permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accessworkspace-permissions)
* [KMS permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accesskms-permissions)









 Best practices of managing Schematics Actions 



 What are the best practices that you must follow in creating an action for the Ansible template? 

Follow these practices in creating a Schematics action for the Ansible template.



* Check whether the location and the url endpoint are pointing to the same region when you create or update the Schematics Workspace. For more information about location and endpoint, see [Where is the information stored](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)?
* You cannot delete or stop a running job of your Schematics action. Wait for the job to complete, then change your settings, and click Check action, or Run action again.
* As the account owner or an authorized account administrator, you can assign IAM service access roles to your users. The IAM service access roles determine the actions that you can set on an IBM Cloud Schematics resource, such as a workspace or an action. To avoid assigning access policies to individual users, consider creating [IAM access groups](https://cloud.ibm.com/docs/account?topic=account-groups).







 How can you protect the access to actions and its data? 

As the account owner or an authorized account administrator, you can assign IAM service access roles to your users. The IAM service access roles determine the actions that you can set on an IBM Cloud Schematics resource, such as a workspace or an action.
QuantaStor for VMware Architecture Guide 

You can order and configure the OSNexus QuantaStor shared storage solution for a VMware ESXi 5 environment. Use the following information along with the [Advanced Single-Site VMware Reference Architecture](https://cloud.ibm.com/docs/virtualization?topic=virtualization-advanced-single-site-vmware-reference-architecture) cookbook to set up one of these storage options in your VMware environment.



 Before you begin 



* Navigate to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/bare-metal?topic=virtual-servers-navigating-devices).
* Ensure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Step 1: Ordering QuantaStor Shared Storage 

Before you place an order for storage, you need to determine the specifications that meet your capacity, performance, and redundancy requirements. This can include processor and chassis choice, QuantaStor license capacity, server RAM, type and number of data disk drives, type and number of cache disks, and networking configuration and other specifications. For more information about choosing the correct QuantaStor configuration in your environment, see [QuantaStor Solution Design Guide for Virtualization ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://wiki.osnexus.com/index.php?title=-_1._IBM_Cloud_QuantaStor_SAN/NAS_Storage_Servers).
Read and agree to the [Direct Link prerequisites](https://cloud.ibm.com/docs/dl?topic=dl-ibm-cloud-dl-prerequisites) and review Cloud Services [Terms](https://www.ibm.com/software/sla/sladb.nsf/sla/bm-8695-01). Then, click Create to complete your order.

If you want to add GB egress data to your estimate, click Add to estimate to calculate the cost. You can also click the About tab for links to Direct Link pricing tables and other helpful resources.



Complete your connection, using the following instructions.





 Completing the connection 

After you submit your Direct Link order, the Direct Link table indicates an LOA creation in progress connection status. Click the name of the connection to open its details page. Then, view the Actions section to see if you have any actions pending.

Here's how the process works:



1. IBM Cloud uploads a Letter of Authorization (LOA) containing a Connecting Facility Assignment (CFA) within 24 hours. In turn, the connection status changes to Waiting LOA review. At this time, you can click the corresponding buttons to preview and accept the LOA.
2. After accepting the LOA and downloading it, the connection status changes to Waiting completion notice upload. You must now take the LOA document to your carrier and get the completion notice ([Example](https://cloud.ibm.com/docs/dl?topic=dl-completion-notice-example)). To do so, you can:



* Supply the LOA/CFA to your colocation provider and have them order a cross connect and any required inter-campus connectivity.
* Supply the LOA/CFA to your service provider and have them order a third-party cross connect, as well as the circuit between your on-premises and the appropriate Meet Me Room.



IBM Cloud will not order a cross-connect on a customer's behalf.
3. After receiving the completion notice from your carrier, upload it. The completion notice must be in PDF format with the name completion_notice.pdf for the automation to process it properly.
After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Observability.
3. Select Logging.

The list of IBM Log Analysis instances is displayed.
4. Select the instance in the region where you want to view events. Then, click Open Dashboard.
5. In the web UI, click the Usage icon ![Usage icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/usage.png) > Usage Quotas.







 Enabling and disabling Usage Quotas 

To enable Usage Quotas make sure the selection at the top of the dialog is set to on. To disable the Usage Quota configuration, make sure the selection is set to off. Usage Quotes are disabled by default.





 Setting up your usage quotas 

When you first access the Usage Quotas dialog you will see the daily and monthly quotas set for your instance.

To change the daily and monthly quotas, do the following:



1. Click Edit Usage Quotas
2. Change the Daily Usage Quota and Monthly Usage Quota to your desired values. The quotas can be specified in MB, GB, or TB. These are hard quotas.
3. Select what you would like to occur when the quotas are reached.

Discard logs when the Daily Usage Quota is reached until midnight UTC
: If selected, when the daily quota is reached within a 24-hour period at UTC, logs will no longer be saved.

Discard logs when the Monthly Usage Quota is reached until the next billing cycle
: An alert-only quota will send an alert allowing logs to continue to be saved, and your data usage to grow, even though the defined threshold has been exceeded.





 Considerations when using usage quotas 

When you exclude logs using the Usage Quotas function, the excluded logs will not be archived or streamed.

When deciding to use Usage Quotas, consider the following:



* Usage Quotas configured actions are separate from any other [defined exclusion rules.](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-exclusion_rules)Usage Quotas rules are triggered dynamically based on your defined thresholds while other exclusion rules are always in effect.
* If the quota is set to a value lower than what has been consumed and sent to storage, all incoming logs after the rule value has been set will be discarded.
* If you change your daily or monthly usage quota, all exclusion rules will be automatically disabled. For example, if your set your monthly usage quota to 100 GB, and you have three daily exclusion rules configured to that quota, if you change your monthly usage quota to a different value the exclusion rules will be disabled. You can reenable them if desired. Exclusion rules are automatically disabled to help avoid having having logs being unintentionally discarded.







 Configuring usage quotas 

You can configure quotas and what is done when various thresholds are reached.



 Accessing usage quotas 

To configure Usage Quotas, access the Usage Quotas settings by doing the following:

The Usage Quotas option is in the left-pane of the LogDNA application, under Settings > Usage .



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Observability.
The Container Registry Quota Usage dashboard is available only if you enable metrics and you have both a storage and a traffic quota set. 



The predefined dashboards can't be changed. You can copy any predefined dashboard so that you can change it to suit your requirements. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboards).

When you start your dashboard, some metrics might display a Data Load Error warning icon. This warning is because more time is required to create the data. When data is available, the warning sign goes away, and the metric is populated. You might also need to change the resolution period.





 Platform metrics 



Table 8. Metrics available by plan names

 Metric Name Information 

 [Pull Traffic](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitoribm_containerregistry_pull_traffic) The account's pull traffic in the current month. 
 [Pull Traffic Quota](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitoribm_containerregistry_pull_traffic_quota) The account's pull traffic quota. 
 [Storage Quota](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitoribm_containerregistry_storage_quota) The account's storage quota. 
 [Storage](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitoribm_containerregistry_storage) The account's storage usage. 





 Pull Traffic 

The account's pull traffic in the current month.



Table 9. Pull Traffic metric metadata

 Metadata Description 

 Metric Name ibm_containerregistry_pull_traffic 
 Metric Type gauge 
 Value Type byte 







 Pull Traffic Quota 

The account's pull traffic quota.



Table 10. Pull Traffic Quota metric metadata

 Metadata Description 

 Metric Name ibm_containerregistry_pull_traffic_quota 
 Metric Type gauge 
 Value Type byte 







 Storage Quota
: (Optional) Check whether the use of public connections is prevented for image pushes or pulls in your account.





 Example 

Prevent image pulls or pushes over public network connections for your account.

ibmcloud cr private-only --enable







 ibmcloud cr quota 

Displays your current quotas for traffic and storage, and usage information against those quotas for the registry region that you're targeting.

ibmcloud cr quota



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).







 ibmcloud cr quota-set 

Modify the specified quota for the registry region that you're targeting.

ibmcloud cr quota-set [--traffic TRAFFIC] [--storage STORAGE]



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

--traffic TRAFFIC
: (Optional) Changes your traffic quota to the specified value in megabytes. The operation fails if you are not authorized to set traffic, or if you set a value that exceeds your current pricing plan.

--storage STORAGE
: (Optional) Changes your storage quota to the specified value in megabytes. The operation fails if you are not authorized to set storage quotas, or if you set a value that exceeds your current pricing plan.





 Example 

Set your quota limit for pull traffic to 7000 megabytes and storage to 600 megabytes.

ibmcloud cr quota-set --traffic 7000 --storage 600







 ibmcloud cr region 

Displays the targeted region and the registry.

ibmcloud cr region

For more information, see [Regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions).



 Prerequisites 

None







 ibmcloud cr region-set
[More icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/icons/actions-icon-vertical.svg), and select Usage quota. You can view how many hours you used Cloud Shell during the current weekly period and the day and time when it resets.

The time that you used of the 50-hour usage quota resets back to 0 at the same time each week. Even after you used all of your quota, you can still use IBM Cloud Shell for up to 5 minutes at a time to complete quick tasks, such as to run a few simple commands.

IBM Cloud Shell is intended for IBM Cloud administration and development purposes. Any usage outside of these guidelines might result in your access to IBM Cloud Shell or IBM Cloud being suspended. Because Cloud Shell is intended for interactive purposes only, long-running processes are stopped. For more information, see the [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).
* The IBM Cloud CLI (ibmcloud) is upgraded to version 1.2.1, and the CLI plug-ins are upgraded to the most recent versions









 12 August 2020 



* Increased the weekly usage quota from 30 hours to 50 hours so you have more time to use Cloud Shell each week. For more information about the usage quota, see [Tracking your usage](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-shell-uiusage-limit).
* Changed Cloud Shell to have separate workspaces for each account. Previously, workspaces in each region were set at the user level, which meant that your workspace was shared across all of your accounts. For more information about workspaces, see [Your Cloud Shell workspace](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-shell-uishell-workspace).
* Moved the cookie preferences from the in-page button to the Privacy option in the Cloud Shell menu.
* Updated the Cloud Shell server image to version 1.0.1, which includes the following changes:



* Added the Operator SDK (operator-sdk) for managing Kubernetes applications at version 0.19.0.
* Added the Mercurial source content management tool (hg) at version 4.4.1.
* Added the Bazaar version control system and CLI (bzr) at version 2.7.0.
* Updated the Python runtime from version 3.5 to 3.6.
* Updated the IBM Cloud Provider plug-in for Terraform to 1.8.1









 24 June 2020 

IBM Cloud Shell is now generally available (GA)! With this release, Cloud Shell includes the following updates:



* Increased service level availability to 99.99% and hardened disaster recovery plan to meet IBM Cloud requirements. For more information, see [Understanding high availability and disaster recovery for Cloud Shell](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-ha-dr).
* Added support for inputting and viewing double-byte characters on the command line in your sessions.
* [Private endpoints](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-securingsecurity-private-endpoints)
* [Search](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-add)
* [v2 Logs API](https://cloud.ibm.com/apidocs/assistant/assistant-v2listlogs)
* [Log webhook](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-webhook-log)
* [Autolearning](https://cloud.ibm.com/docs/assistant?topic=assistant-autolearn)
* [Intent conflict resolution](https://cloud.ibm.com/docs/assistant?topic=assistant-intentsintents-resolve-conflicts)



The following features are available only to users of Enterprise plans. ![Enterprise plan only](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/enterprise.png)



* [Activity tracker](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-auditing)



The plan type of the service instance you are currently using is displayed in the page header. You can upgrade from one plan type to another. For more information, see [Upgrading](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-managing-planadmin-managing-plan-upgrade).





 User-based plans explained 

Unlike API-based plans, which measure usage by the number of API calls made during a month, the Plus and Enterprise plans measure usage by the number of monthly active users.

A monthly active user (MAU) is any unique user who has at least one meaningful interaction with your assistant or custom application over the calendar billing month.
General gateway appliance considerations 

The following considerations help provide additional information for using your gateway appliances.



  Bandwidth allotment 

Bandwidth allotment is the allowed public bandwidth during a monthly billing cycle. For a gateway appliance, this is determined by the allotment assigned to each node or server. You can view this allotment by performing the following procedure:



1.  From your browser, open the [IBM Cloud catalog](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the top left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click on the gateway whose details you want to view.



The bandwidth allotment is in the Network details section, under Public bandwidth allotment. To view the current usage, click on the bandwidth value for the current billing cycle.

For standalone configurations, bandwidth allotment is defined for the individual server. For example, if the server has a 10 GB monthly allotment, then that is what is allowed for the gateway.

For High Availability (HA) configurations, the gateway has two servers, each with the same bandwidth allotment. The allotment for each server is available for use by the gateway but is not automatically pooled. HA gateways operate with a primary (active) and secondary (passive) nodes. The primary node manages all traffic, while the secondary node provides failover protection. The bandwidth of a server is used if that server is the primary node. For example, if a primary node server runs out of bandwidth during a cycle, the bandwidth of the secondary node is not automatically used. The unused secondary node server bandwidth is only used if the primary node has failed over to the secondary node.
Before you restart, be sure that you download any files that you want to keep to your local system.

To restart, click the Menu icon ![More icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/icons/actions-icon-vertical.svg), and select Restart.





 Tracking your usage 

You can use Cloud Shell for up to 50 hours within a week per region. Any time that you have at least one open session counts toward this usage quota, even if you aren't actively running commands. For example, if you're working in Cloud Shell for 15 minutes and then leave your session open for a 30-minute lunch break, those 45 minutes are counted as usage. If you have three sessions open at the same time over an hour period, your usage is one hour because concurrent sessions don't count as additional usage. To minimize your usage, be sure to close sessions after you're done using them.

If you use all of your quota, your Cloud Shell sessions are closed. Closing Cloud Shell removes any data in your workspace, including your files and command history.

When you reach your usage quota, you get a notification that Cloud Shell will close in 5 minutes. Use this time to complete any urgent tasks.

At any point, you can track your usage and check when your weekly quota resets. In the Cloud Shell menu bar, click the Menu icon ![More icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/icons/actions-icon-vertical.svg), and select Usage quota. You can view how many hours you used Cloud Shell during the current weekly period and the day and time when it resets.

The time that you used of the 50-hour usage quota resets back to 0 at the same time each week.