vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [CAP Theorem](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cap-theorem)
* [Combining IBM Cloudant with other IBM services](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-combine-ibm-services)



* How documents work



* [Overview](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-documents)
* [Creating a document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-create-document)
* [Reading a document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-read-a-document)
* [Updating a document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-update-docs)
* [Deleting a document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-delete-a-doc)
* ["Tombstone" documents](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-tombstone-docs)
* [Bulk operations](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-bulk-operations)
* [How design documents work](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-design-documents)
* [Design document management](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-design-document-management)
* [Grouping related documents together in IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-grouping-related-documents-together-in-ibm-cloudant)
* [How to use attachments](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-how-to-use-attachments)



* Monitoring your instance
* [Design document management](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-design-document-management)
* [Grouping related documents together in IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-grouping-related-documents-together-in-ibm-cloudant)
* [How to use attachments](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-how-to-use-attachments)



* Monitoring your instance



* [Monitoring an IBM Cloudant cluster](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-monitoring-an-ibm-cloudant-cluster)
* [Capacity](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-capacity)
* [Active tasks](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-active-tasks)
* [Managing tasks](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-managing-tasks)



* Querying the database



* [Working with IBM Cloudant Query](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-query)
* [IBM Cloudant Query Parameters](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloudant-query-parameters)
* [Working with indexes](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-working-with-indexes)
* [Creating selector expressions](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-selector-expressions)
* [Selector syntax](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-selector-syntax)
* [IBM Cloudant Operators](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-operators)
(https://cloud.ibm.com/docs/containers?topic=containers-learning-path-adminadmin_cluster)[Add storage Plan and add highly available persistent storage for your app data.](https://cloud.ibm.com/docs/containers?topic=containers-learning-path-adminadmin_plan)

 Learn more 

[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture/architectures/kubernetes-infrastructure-with-ibm-cloud)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/search?query=Kubernetes)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)
* Run the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) command:

ibmcloud cr image-list --no-trunc

If you run the ibmcloud cr image-list command without the --no-trunc option, you see the truncated format of the digest.







 How do I use digests to work with images? 

The [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) identifies an image by using the sha256 hash of the [image manifest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_manifest).

To find the digests for your images, run the [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) command. You can refer to an image by using a combination of the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.





 How do you use access control? 

You can create IBM Cloud Identity and Access Management (IAM) policies to control access to your namespaces in IBM Cloud Container Registry. For more information, see [Granting access to IBM Cloud Container Registry resources tutorial](https://cloud.ibm.com/docs/Registry?topic=Registry-iam_access) and [Managing IAM access for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iam).





 How can I share an image with many users? 

You can create an IBM Cloud account and invite all the users to it. They can then all have access to any

namespacethat is created in the account. You can create a subset of the users and set an IAM access policy to differentiate access at the namespace level.
[checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 TXT ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 XLS, XLSX ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 





* PDF files that are secured with a password or certificate are not supported. Vector objects, including SVG images and vectorized text, are not supported. Only images of the supported image file types that occur in the PDF are rendered.
* Only single-page image files are supported.
Tags You can assign a label to this resource so that you can easily filter resources in your resource list. 
 Source Select Cloud Object Storage as the source. A list displays from which you select a IBM Cloud Object Storage service instance where the image that you want to import is stored. <br>Do you need to create a custom image from a volume instead? Select the source for the custom image by choosing either Virtual server instance boot volume or Block storage boot volume. For more information, see [Creating an image from a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifv). 
 Location Select the specific geographic region where your image is stored. 
 Bucket Select the IBM Cloud Object Storage bucket where your image is stored. 
 Name Select the image file in the IBM Cloud Object Storage service instance that you want to import. If you are importing an encrypted image, the image must be encrypted with LUKS encryption by using QEMU and your own passphrase. For more information, see [Encrypting the image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-encrypted-custom-imagemanually-encrypt-image). 
 Operating System Select the operating system that is included in your image.<br><br>For custom images with Red Hat Enterprise Linux or Windows operating systems, you can bring your own license (BYOL) or to license through IBM Cloud.<br><br>For Red Hat Enterprise Linux or Windows [BYOL custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about), you must select the OS with -byol appended to the name. For example, if you have a Windows 2019 BYOL custom image, select Windows-2019-amd64-byol for the operating system. Failure to select the -byol version of the operating system when you import a BYOL custom image might result in a virtual server that is unable to start.<br><br>If you configured your Red Hat Enterprise Linux or Windows custom image to license through IBM Cloud, you must select the nonbyol operating system.
Create an image by using the [ibmcloud cr image-tag](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_tag) command.

In the region that you are logged in to, create an image in IBM Cloud Container Registry that refers to an existing image in the same region. This action is supported for source images that are created by using supported versions of Docker Engine, see [Support for Docker](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewdocker).

New images that are created by using this mechanism do not retain signatures. If you require the new image to be signed, do not use this mechanism.

Before you begin, complete the following tasks.



* [Install the CLI](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespacecli_namespace_registry_cli_install) to work with images in your namespace.
* Ensure that you have access to a private namespace in IBM Cloud Container Registry that contains a source image to which you want to refer another image.



To create an image from a source image, complete the following steps.



1. Log in to the CLI by running the [ibmcloud cr login](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_login) command.

ibmcloud cr login
2. Run the following command to add the new reference, where SOURCE_IMAGE is the name of your source image and TARGET_IMAGE is the name of your target image. The source and target images must be in the same region. SOURCE_IMAGE must be in the format repository:tag or repository@digest and TARGET_IMAGE must be in the format repository:tag, for example, us.icr.io/namespace/image:latest.

To find the names of your images, run ibmcloud cr image-list. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag.
ibmcloud is image-create IMAGE_NAME [--file IMAGE_FILE_LOCATION] [--os-name OPERATING_SYSTEM_NAME] [--deprecate-at YYYY-MM-DDThh:mm:ss+hh:mm] [--obsolete-at YYYY-MM-DDThh:mm:ss+hh:mm]

The following example creates a custom image with the name of my-ubuntu-16-amd64. The image source location is cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2. The operating system is ubuntu-16-amd64. The image is scheduled to be deprecated on 2023-03-01T06:11:28+05:30. The image is scheduled to be obsolete on 2023-12-31T06:11:28+05:30.

ibmcloud is image-create my-ubuntu-16-amd64 --file cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2 --os-name ubuntu-16-amd64 --deprecate-at 2023-03-01T06:11:28+05:30 --obsolete-at 2023-12-31T06:11:28+05:30

For more information, see [ibmcloud is image-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceimage-create)in the VPC CLI reference page.







 Importing a custom image by using the API 

Make sure that your compatible custom image is available in IBM Cloud Object Storage.
For more information, see the [High availability (HA), disaster recovery (DR), and backup](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backup) documentation.

Dedicated Hardware plan instances can be deployed in most [IBM data center locations](https://www.ibm.com/cloud/data-centers/). See the drop-down menu in the IBM Cloud catalog for an up-to-date list of available locations.

‡All IBM Cloudant instances that are deployed from the IBM Cloud Frankfurt region are deployed into EU-managed environments. Any IBM Cloudant account or API key that is generated outside an EU-managed environment can't be granted access to an EU-managed IBM Cloudant instance. For more information, see [Enabling the EU Supported setting](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedbill_eusupported) for your IBM Cloud account.





 Authentication methods 

IBM Cloudant is accessed by using an HTTPS API. Where the API endpoint requires it, the user is authenticated for every HTTPS request IBM Cloudant receives. During provisioning, the available authentication methods include Use both legacy credentials and IAM or Use only IAM. For more information, see the [IAM guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-managing-access-for-cloudant) or the legacy [Authentication API document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountauthentication).

After you provision an IBM Cloudant instance, the connection URL and IAM authorization details can be found when you generate new credentials in the Service Credentials tab of the IBM Cloud Dashboard. For more information, see [Locating your service credentials](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-locating-your-service-credentials). If you chose this option during provisioning, the IBM Cloudant legacy username and password is also included.

The IBM Cloudant team recommends you use IAM access controls for authentication whenever possible.
When your Linux custom image is created and available in IBM Cloud Object Storage, you can [import the custom image into VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-importing-custom-images-vpc) and [Onboard a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial&interface=ui). Make sure that you [Granted access to IBM Cloud Object Storage to import images](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq).

If you plan to use a private catalog to manage your custom images, you must first import that image into IBM Cloud VPC, and then onboard the virtual server image into a private catalog.

After the custom image is imported, you can then use the custom image to deploy a virtual server in the IBM Cloud® Virtual Private Cloud infrastructure.
* ibmcloud is image-deprecate my-image-from-volume-cli-do-not-delete







 Command options 



* IMAGE: ID or name of the image.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is image-obsolete 

Obsolete an image

ibmcloud is image-obsolete IMAGE [--output JSON] [-q, --quiet]



 Command example 



* ibmcloud is image-obsolete my-image-from-volume-cli-do-not-delete







 Command options 



* IMAGE: ID or name of the image.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is catalog-image-offerings 

List all catalog image offerings.

ibmcloud is catalog-image-offerings [--output JSON] [-q, --quiet]



 Command example 



* ibmcloud is catalog-image-offerings







 Command options 



* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is catalog-image-offering 

Get catalog image offering.

ibmcloud is catalog-image-offering CATALOG OFFERING [--output JSON] [-q, --quiet]



 Command example 



* ibmcloud is catalog-image-offering 2497ae83-40cb-46ba-ac7f-5303514a2669 54372a73-7a0a-4799-ac9c-8736620c67f1







 Command options 



* CATALOG: ID of the catalog.
Copy and paste just the url from the credentials to the CLOUDANT_URL field of the .env file and save the changes. The result will be something like:

CLOUDANT_URL=https://123456789 ... bluemix.cloudant.com
4. Run your app locally.

rails server

View your app at: http://localhost:3000. Any names you enter into the app will now get added to the database.

Your local app and the IBM Cloud app are sharing the database. View your IBM Cloud app at the URL listed in the output of the push command from above. Names you add from either app should appear in both when you refresh the browsers.

If you don't need your app live, stop it so you don't incur any unexpected charges.







 Next steps 



* [Samples](https://ibm-cloud.github.io)
* [Architecture Center](https://www.ibm.com/cloud/architecture/architectures)
If the API key is lost, you must create a new API key. For more information, see [Working with API keys](https://cloud.ibm.com/docs/account?topic=account-manapikeymanapikey). 
 Notes Add any notes that are related to the image that might be helpful to users. 
 COS service instance Select the IBM Cloud Object Storage service instance where the image that you want to import is stored. 
 Location Select the specific geographic region where your image is stored. You can import images into the following regions and associated data centers: US-South (DAL13), US-East (WDC07), EU-Great Britain (LON02), EU-Germany (FRA02), AP-Japan, and AU-Sydney. After the image is imported to one of the data centers that are listed, you can move it to another data center. 
 Bucket Select the IBM Cloud Object Storage bucket where your image is stored. Only buckets that exist in the regional location that you selected are valid. You receive an error message if you select a bucket that doesn't exist in the selected location. 
 Name Select the image file in the IBM Cloud Object Storage service instance that you want to import. Supported file types are VHD (Virtual Hard Disk), VMDK (Virtual Machine Disk), and ISO. If you are importing an encrypted image, the image must be in the VHD file format and encrypted with the vhd-util tool. 
 Operating System Select the operating system that is included in your image. 
 Boot Mode Select the boot mode for your image. If a default boot mode is set for the operating system that you specify, that boot mode is selected here automatically. 
 Your License If you plan to provide your own operating system license, select this checkbox. If you are importing an image with a Windows operating system, you can select this option if you plan to use the image to provision [dedicated host instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-dedicated-hosts-and-dedicated-instancesdedicated-hosts-and-dedicated-instances).
On the Objects page of your IBM Cloud® Object Storage bucket, click Upload. You can use the Aspera high-speed transfer plug-in to upload images that are larger than 200 MB. For more information about uploading to IBM Cloud Object Storage, see [Upload data](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload).





 Next steps 

When your Windows®custom image is created and available in IBM Cloud Object Storage, you can [import the custom image into VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-importing-custom-images-vpc) and [Onboarding a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial&interface=ui). Make sure that you have [Granted access to IBM Cloud Object Storage to import images](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq).

If you plan to use a private catalog to manage your custom images, you must first import that image into IBM Cloud VPC and then onboard the virtual server image into a private catalog.

After the custom image is imported, you can then use the custom image to deploy a virtual server in the IBM Cloud® Virtual Private Cloud infrastructure.
* --bucket: The Cloud Object Storage bucket to export the image to. The bucket must exist and an IAM service authorization must grant Image Service for VPC of VPC Infrastructure Services writer access to the bucket.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is image-export-job-update 

Update an image export job.

ibmcloud is image-export-job-update IMAGE JOB --name NAME [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is image-export-job-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 6451a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-image-export-job
* ibmcloud is image-export-job-update my-image my-export-job --name my-image-export-job







 Command options 



* IMAGE: ID or name of the image.
* JOB: ID or name of the image export job.
* --name: Name of the image export job.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is image-export-job-delete 

Delete one or more image export jobs.

ibmcloud is image-export-job-delete IMAGE (JOB1 JOB2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command examples
IBM Cloudant is a modern NoSQL database that is useful for many data-driven use cases: from key-value to complex document-oriented data storage and query. To manage the growing set of regulatory and management report rules, the mortgage company uses IBM Cloudant to store documents that are associated with raw regulatory data the come into the firm. Compute processes on Red Hat OpenShift on IBM Cloud are triggered to compile, process, and publish the data in various reporting formats. Intermediate results common across reports are stored as IBM Cloudant documents so template-driven processes can be used to produce the necessary reports.





 Results 



* Complex financial simulations are completed in 25% of the time than was previously possible with the existing on-premises systems.
* Time to deployment improved from the previous 6 - 9 months to 1 - 3 weeks on average. This improvement occurs because Red Hat OpenShift on IBM Cloud allows for a disciplined, controlled process for ramping up app containers and replacing them with newer versions. Reporting bugs can be fixed quickly, addressing issues, such as accuracy.
* Regulatory reporting costs were reduced with a consistent, scalable set of storage and compute services that Red Hat OpenShift on IBM Cloud and IBM Cloudant bring.
* Over time, the original apps that were initially moved to the cloud were restructured into cooperative microservices that run on Red Hat OpenShift on IBM Cloud. This action further sped up development and time to deploy and allowed more innovation due to the relative ease of experimentation. They also released innovative apps with newer versions of microservices to take advantage of market and business conditions (that is, so called situational apps and microservices).









 Payment tech company streamlines developer productivity, deploying AI-enabled tools to their partners 4 times faster 

A Development Exec has Developers that use on-premises application tools that slow down prototyping while they wait for hardware procurement.

Red Hat OpenShift on IBM Cloud provides spin-up of compute by using open-source standard technology. After the company moved to Red Hat OpenShift on IBM Cloud, Developers have access to DevOps friendly tools, such as portable and easily shared containers.

Then, Developers can experiment easily, pushing changes to Development and Test systems quickly with open toolchains.