vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs for IBM Cloud Internet Services 

Have a question about IBM Cloud® Internet Services? Review these frequently asked questions, which provide answers to provisioning concerns, application access, and other common inquiries.



 What do I get with a Free Trial Plan? 

The Free Trial plan, by design, allows only one zone per account. It is recommended that only one instance be created per account and the zone name be verified. It is critical that the zone name be verified before it is added. If a zone is deleted, another zone or the same zone cannot be added during the Free Trial Plan.





 How many Free Trial instances can I have? 

You can have, at most, one Free Trial instance per account, for the lifetime of the account. If you already have a free trial instance, if you delete a free trial instance, or if the free trial expires, you are not allowed to create another free trial instance. You can, however, create instances of other paid plan types (for example, Standard), independent of any free trials you might have created.





 Can I downgrade from Standard to the Free Trial? 

No. Downgrading from Standard to a Free Trial plan is not allowed.





 My Free Trial has expired. What are my options? 

To avoid any data loss you must upgrade from Free Trial to Standard prior to the expiration date. After that, we only support upgrading the Plan or Deleting the CIS instance. If the instance is not deleted or upgraded after 45 days (from the initiation of the instance) the configuration domain, global load balancers, pools, and health checks are deleted automatically.





 What happened to Enterprise Package plans? 

Starting on 21 June 2023, you can no longer configure the Enterprise package plan. The functionality of this plan was split across various tiers and are now available in Enterprise Essential, Enterprise Advanced, and Enterprise Premier plans. See [Transition to Enterprise](https://cloud.ibm.com/docs/cis?topic=cis-transitioning-next-plan).





 How do I delete my CIS instance? 

To delete a CIS instance, you must first delete all global load balancers, pools, and health checks. Then delete the associated domain (zone).
Yes, this feature is known as NetScaler Gateway™ and is included in all editions. For more information regarding this feature please visit the [Citrix website")](https://www.citrix.com/products/netscaler-adc/)



Cloud Internet Services (CIS)



* What do I get with a Free Trial Plan?

The Free Trial plan, by design, allows only one zone per account. It is recommended that only one instance be created per account and the zone name be verified. It is critical that the zone name be verified before it is added. If a zone is deleted, another zone or the same zone cannot be added during the Free Trial Plan.
* How many Free Trial instances can I have?

You can have, at most, one Free Trial instance per account, for the lifetime of the account. If you already have a free trial instance, if you delete a free trial instance, or if the free trial expires, you are not allowed to create another free trial instance. You can, however, create instances of other paid plan types (for example, Standard), independent of any free trials you might have created.
* Can I downgrade from Standard to the Free Trial?

No. Downgrading from Standard to a Free Trial plan is not allowed.
* My Free Trial has expired. What are my options?

To avoid any data loss you must upgrade from Free Trial to Standard prior to the expiration date. After that, we only support upgrading the Plan or Deleting the CIS instance. If the instance is not deleted or upgraded after 45 days (from the initiation of the instance) the configuration domain, global load balancers, pools, and health checks are deleted automatically.
* What happened to Enterprise Package plans?

Starting on 21 June 2023, you can no longer configure the Enterprise package plan. The functionality of this plan was split across various tiers and are now available in Enterprise Essential, Enterprise Advanced, and Enterprise Premier plans. See [Transition to Enterprise](https://cloud.ibm.com/docs/cis?topic=cis-transitioning-next-plan).
* How do I delete my CIS instance?
Power Systems Virtual Server supports multiple levels of RHEL and SLES. You can either use IBM provided stock Linux images with IBM Full Linux Subscription or bring your own custom Linux image with vendor-provided subscription.

See the [various versions of OSs](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqsos-versions) that Power Systems Virtual Server supports.





 How does third-party licensing work? 

Clients are responsible for third-party licensing.





 What are the hardware specifications? 

For more information, see [Hardware specifications](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-serverhardware-specifications).





 Do Power Systems Virtual Servers run in a multi-tenant environment? 

Yes, Power Systems Virtual Server run in a multi-tenant environment.





 Are there bare-metal options? 

There are no bare-metal options. The Power Systems Virtual Server offering focuses on virtual instances.





 Can you tell me more about the snapshotting, cloning, and restoring capabilities? 

Power Systems Virtual Server provides the capability to capture full, point-in-time copies of entire logical volumes or data sets. Using IBM's FlashCopy feature, the [Power Systems Virtual Server API](https://cloud.ibm.com/apidocs/power-cloudintroduction) lets you create delta snapshots, volume clones, and restore your disks. To learn more, see [Snapshotting, cloning, and restoring](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-volume-snapshot-clone).





 What are the key differences between a snapshot and clone? 

The key differences are as follows:



 Context Snapshot Clone 

 Definion A snapshot is a thin-provisioned group of volumes that cannot be attached to a host or accessed/manipulated. A clone is created from a snapshot and results in independent volumes which surface in the GUI and can be attached to hosts. 
 Primary function Revert or restore the source disks to a desired state Create a complete volume clone
Trusted profiles with an administrator role for a resource can also grant access to that resource. Conditions can be specified so that only federated users that require the highest privileges can apply this trusted profile. All other federated users can be filtered out based on their SAML attributes.
* A policy that grants compute resources Reader and Writer roles on a resource group. When compute resources authenticate and fulfill the conditions that are specified in the trusted profile, such as location or resource type the trusted profile is automatically applied. This way, any existing or future resources that meet these conditions can have the profile that is automatically applied when authenticated.
* You can also establish trust with specific compute resources, like a single Kubernetes cluster. For example, you might have an application that is running on Kubernetes Service where the application needs to read and write from IBM Cloudant and read and write to a Cloud Object Storage Dedicated IBM Managed bucket. Both the IBM Cloudant and Cloud Object Storage Dedicated IBM Managed instances would be in the same resource group and the trusted profile would be assigned Reader or Writer roles.



Using trusted profiles is a best practice for applications running on IBM Cloud compute resources to gain access to IAM-enabled resources.







 Compare access groups and trusted profiles 

Access groups are best used for granting access for a user's day-to-day work, while trusted profiles are suited for granting federated users the level of access they need to complete a specialized and specific set of tasks within a limited time period. These are usually critical tasks that you would want to avoid doing unintentionally in daily work. With trusted profiles, federated users don't need to onboard to IBM Cloud, they are granted access to IBM Cloud resources in an account by way of the trust relationship. If a federated user leaves your company, you can simply delete their corporate identity in your directory, which then also removes access to IBM Cloud. Time-based access with trusted profiles allows frequent authentication checks for reduced security risks.

Use the following table to understand the differences between using access groups and trusted profiles to make the best decision for your use case.



Table 1. Compare access groups and trusted profiles

 Access group Trusted profile 

 IAM access control Yes Yes 
 Inviting users to the IBM Cloud account required Yes No
: The Text to Speech service is now available in the IBM Cloud Seoul location (kr-seo). As with other locations, the IBM Cloud location uses token-based IAM authentication. All new service instances that you create in this location use IAM authentication.





 1 October 2019 

New US HIPAA support for Premium plans in Washington, DC, location
: US HIPAA support is available for Premium plans that are hosted in the Washington, DC, location and are created on or after 1 April 2019. For more information, see [US Health Insurance Portability and Accountability Act (HIPAA)](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-information-securityhipaa).





 22 August 2019 

Defect fix: Multiple small improvements
: Defect fix: The service was updated for small defect fixes and improvements.





 30 July 2019 

New Japanese neural voice: ja-JP_EmiV3Voice
: The service now offers a neural voice in Japanese: ja-JP_EmiV3Voice. Both standard and neural versions of all available voices in all supported languages are now available. For more information, see [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices).





 24 June 2019 

New support for standard and neural voices
: The service now offers two versions of most of its available voices:



* Standard voices that use concatenative synthesis to assemble segments of recorded speech to generate audio. Standard voices do not include a version string in their name (for example, en-US_AllisonVoice).
* Neural voices that use Deep Neural Networks (DNNs) to predict the acoustic (spectral) features of the speech. Neural voices include a version string (V3) in their name (for example, en-US_AllisonV3Voice).



Neural versions are available for all standard voices except for the ja-JP_EmiVoice voice, which is pending and will be available soon.
For more information about phrase sentiment, see [Detecting phrases that express sentiment](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-phrase-sentiment). You cannot detect the sentiment of entities or keywords in v2.
* What is a nested field?

When you ingest a file or crawl an external data source, the data that you add to Discovery is processed and added to the collection as a document. Fields from the original file are converted to document fields and are added to the collection's index. Some content is added to root-level index fields and some information is stored in nested fields. Where data gets stored differs by file type. Most of the fields from structured data sources are stored as root-level fields. For files with unstructured data, much of the body of the file is stored in the text field in the index. Other information, such as the file name, is stored in nested fields with names like extracted_metadata.filename. You can determine whether a field is a nested field by its name. If the field name includes a period, it is a nested field. For more information about how different file types are handled, see [How your data source is processed](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-index-overview).
* Which type of query should I use in my custom app?

When you submit a query, you can choose to submit a natural language query or use the Discovery Query Language to customize the search to target specific fields in the index, for example. For more information about the different types of queries and how to decide which one to use, see [Choosing the right query type](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-conceptsquery-choose).



Knowledge Studio



* How do I set data collection options?

For Lite and Standard plans, by default, Knowledge Studio uses client data to improve the service. This data is used only in aggregate. Client data is not shared or made public.
Migrating to Discovery v2 

A redesign of the product, Discovery v2, was introduced in November 2019. Discovery v2 offers significant advantages over Discovery v1.

Learn about how to migrate a v1 Discovery service instance to Discovery v2, including how to move data and update your applications.

The major structural differences between Discovery v1 and v2 include:



* There is no concept of an environment in v2. The deployment details such as size and index capacity are managed for you when you choose the appropriate service plan for your needs. For managed deployments, you can choose a Plus, Enterprise, or Premium plan, for example. For installed deployments, the sizing is managed by the deployment type that you specify when you install the service in Cloud Pak for Data.
* There is no single configuration object in v2. Control of the enrichments that are applied to documents is managed in the collections and project objects in v2. Other v1 configuration capabilities, such as the ability to customize the conversion step of ingestion, are not available in v2.
* Greater programmatic support is available for custom enrichments in v2. New enrichment API methods are available that you can use to create enrichments. v2 also introduces document classifier API methods that you can use to train document classifier models programmatically. You can apply these custom enrichments to a collection by using the API.
* The capabilities of a natural language query search are expanded in v2 to enable the return of the top passages per document and of succinct answers from passages. Other advanced search capabilities are introduced, including table retrieval. In v2, the deduplication parameter is not available and the continuous relevancy training and query logging functions are not available.
* For more information about feature differences, see [the feature comparison table](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-version-chooseversion-choose-comparison).
* For more information about detailed API differences, see [API version comparison](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2-api).
For more information about working with the Delivery Pipeline private worker tool integration, see [Working with tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations) and [Configuring Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-privateworker).

You cannot use Terraform or APIs to manage Delivery Pipeline private workers. Instead, use the console or the CLI to install, register, configure, and update private workers. For more information about these tasks, see [Installing Delivery Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers).
* Why does the Toolchains page show that the Continuous Delivery service Lite plan is exceeded?

Continuous Delivery offers two plans: Lite and Professional. If you have the Continuous Delivery Lite plan, you can use toolchains for free, up to the limits of the plan. The error message indicates that you exceeded one or more limits of the Lite plan. For example, you might exceed the plan if you have too many authorized users who are associated with the Continuous Delivery service instance, or if you ran the maximum number of Delivery Pipeline jobs. For more information about the terms of your plan, see [Plan limitations and usage](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage).
* I created a toolchain, why does the Toolchains page show that a Continuous Delivery service is required?

The terms of the plan for the Continuous Delivery service instance that is in the same resource group as the toolchain manages the use of some of the tool integrations (Delivery Pipeline and Git Repos and Issue Tracking) that are contained in the service. The error message indicates that the resource group doesn't contain the required instance of the Continuous Delivery service.
npm install -g @cloudant/couchbackup

For more information, see [couchbackup](https://github.com/cloudant/couchbackup).







 Unsupported tools 

Unsupported tools are not maintained or supported by IBM Cloudant.



 cURL 

A tool that you use from the command line to transfer data.

For more information, see [curl](https://curl.haxx.se/).





 jq 

A tool that you use from the command line to parse JSON. IBM Cloudant uses the JSON data format.

Download the package to install [jq](https://stedolan.github.io/jq/).

For more information, see [jq](https://stedolan.github.io/jq/).





 couchdiff 

A tool that you use from the command line to show the differences between an IBM Cloudant and a CouchDB database.

To install couchdiff, run the following command by using npm:

npm install -g couchdiff

For more information, see [couchdiff](https://www.npmjs.com/package/couchdiff).





 couchimport 

A tool that you use from the command line, or programmatically, to import data into CouchDB efficiently.

To install couchimport, run the following command by using npm:

npm install -g couchimport

For more information, see [couchimport](https://www.npmjs.com/package/couchimport).





 couchmigrate 

A tool that you use from the command line to migrate CouchDB design documents.

To install couchmigrate, run the following command by using npm:

npm install -g couchmigrate

For more information, see [couchmigrate](https://www.npmjs.com/package/couchmigrate).





 couchreplicate 

A tool that you use from the command line to coordinate Apache CouchDB or IBM Cloudant replications.
You can also deploy virtual machines by using the native management tools. By default, systems are deployed in VLANs for segmentation and networking components (such as gateways, routers, and firewalls) and are used to create almost any topology.
* Can I deploy VMware components directly from the IBM Cloud® catalog?

Yes, you have two options:



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





Virtual Servers for Classic



* What is a standard image template?

A standard image template is the IBM® Virtual Servers imaging option for IBM Cloud. You use standard image templates to capture an image of an existing virtual server instance regardless of its operating system and create a new virtual server that is based on the image.
* What is an ISO template?

The ISO template is a type of template that is reserved for ISOs that can be used to start a virtual server instance. ISO templates are available in two versions: public and private. Public ISO templates are preconfigured templates that are provided by IBM Cloud and can be used by any customer. Private ISO templates are created by importing an image of an ISO stored on an Object Storage account. In order for an ISO to be imported to the Image Templates screen, the ISO must be bootable.

IBM Cloud supported operating systems can be used only to load an ISO template onto an instance. For more information, see [Supported Operating Systems](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-software&locale=ensupported-operating-systems-for-ibm-cloud-virtual-servers).
* What is the difference between a public image and a private image?
From the navigation, select Resources and verify that your resources show the updated configuration.







 Managing drift between your cloud environment and your Terraform configuration 

Use Terraform-native capabilities to determine the differences between the infrastructure and platform services that you provisioned in IBM Cloud and the resources that you specified in your Terraform configuration files.

Managing deviations between the real-world state of your cloud environment and your infrastructure code, also referred to as drift, is a key challenge when implementing infrastructure as code. Deviations can happen for many reasons, such as:



* You added, updated, or removed resources in your Terraform configuration file without running your infrastructure code.
* You manually added, updated, or removed IBM Cloud without Terraform.
* You used other automation tools, such as scripts to manipulate the state of your IBM Cloud resources.



Where does Schematics store the state of my cloud resources?
After you successfully provisioned IBM Cloud resources by running a Schematics apply action, the state of resources is stored in a Terraform state file (terraform.tfstate). Schematics uses this state file as the single source of truth to determine what resources exist in your account. The state file maps the resources that you specified in your Terraform configuration file to the IBM Cloud resource that you provisioned.

How can I compare the required state of my cloud resources against the actual state of my resources?
To create a deviation report and view the changes between the infrastructure and platform services that you specified in your Terraform configuration files and the resources that exist in your IBM Cloud account, you can use Terraform execution plans. A Terraform execution plan summarizes what actions Schematics needs to take to provision the cloud environment that is described in your Terraform configuration files. These actions can include adding, modifying, or removing IBM Cloud resources.

What deviations cannot be detected?
A Terraform execution plan is based on the Terraform state file that was created when you ran your first Schematics apply action. Resources that you provisioned in other Schematics Workspaces, by using automation tools such as Ansible or Chef, or that you added without Schematics are not considered and not included in the Terraform execution plan.

To view deviations between the resources in your IBM Cloud account and your Terraform configuration:



1.