vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You set up the internal registry to back up images to a cloud storage provider. Stored images are not available across clusters. The internal registry is set up to back up images automatically to a bucket in your IBM Cloud Object Storage instance. Your cluster has image pull secrets automatically set up to pull images from default registries, including IBM Cloud Container Registry. You can also set up the internal registry to work with IBM Cloud Container Registry, which your cluster is also automatically set up to pull images from. For more information, see [Setting up an image registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registry). 
 Operators and OperatorHub OpenShift Container Platform sets up many operators to manage default components for the cluster. You can also use the OperatorHub to install other operators such as from 3rd-party providers. IBM sets up many of the same operators as OCP to manage default component for the cluster. However, because IBM manages the master and provides you with IBM Cloud APIs to manage your cloud infrastructure, some operators, such as the machine set operator and other components as noted in this table, are not set up or configurable. You can also use the OperatorHub to [install other operators](https://cloud.ibm.com/docs/openshift?topic=openshift-operators) such as from 3rd-party providers. Note that operators that you install or create are not supported by IBM, and might come with their own support terms and pricing. 
 Projects, builds, and apps OpenShift Container Platform provides tools such as projects, build configurations, and the internal registry that you can use to deploy your apps while following a cloud-native, continuous integration and continuous delivery (CI/CD) methodology. Red Hat OpenShift on IBM Cloud clusters come with all the same configurable project and build components as OCP clusters. You can also choose to integrate your cluster with IBM Cloud services like [Continuous Delivery](https://cloud.ibm.com/docs/openshift?topic=openshift-cicd). 
 Cluster health You can also set up logging, monitoring, and metering tools by installing and configuring various operators.
Client libraries 

Client libraries are the tools that you use to develop your own applications to work with IBM® Cloudant® for IBM Cloud® databases.

The following client libraries are formally supported by IBM Cloudant: Java™, Node.js, Python, and Go.

A supported library is one where you can contact IBM Cloudant if you come across a specific, reproducible problem in the current version of the library.



 Java 

The IBM Cloudant SDK for Java™ is the official IBM Cloudant library for Java™.

To install the IBM Cloudant SDK for the Java™ library, see [Installation](https://github.com/ibm/cloudant-java-sdkinstallation) about installing the library by adding it as a dependency to your Maven or Gradle builds. You can also see details and examples of how to use the library in the guide.



 Library for Java 



* [IBM Cloudant SDK for Java™](https://github.com/ibm/cloudant-java-sdk)









 Node.js 

The IBM Cloudant SDK for the Node.js library is the official IBM Cloudant library for Node.js.

Install the [IBM Cloudant SDK for Node.js](https://www.npmjs.com/package/@ibm-cloud/cloudant) library by running the following command:

npm install @ibm-cloud/cloudant



 Library for Node.js 



* [IBM Cloudant SDK for Node.js](https://github.com/ibm/cloudant-node-sdk)









 Python 

The IBM Cloudant SDK for Python library is the official IBM Cloudant library for Python.

Install the [IBM Cloudant SDK for Python](https://pypi.org/project/ibmcloudant/) library by running pip or easy_install as shown in the following examples:

pip install --upgrade "ibmcloudant>=0.0.27"

or

easy_install --upgrade "ibmcloudant>=0.0.27"
Onboarding a virtual server image with Terraform to a private catalog 

This tutorial walks you through how to onboard a virtual server image with Terraform to a private catalog. By completing this tutorial, you learn how to import the virtual server image from a GitHub repository, configure the deployment and other details, and validate that you can deploy the image to a target IBM Cloud® Virtual Private Cloud (VPC).

This tutorial is one of four in a series that demonstrates how to onboard and publish a [sample virtual server image with Terraform](https://github.com/IBM-Cloud/isv-vsi-product-deploy-sample/tree/v1.0) to IBM Cloud®. As you complete the tutorial, adapt each step to fit your product's needs.

This tutorial includes deploying the virtual server image to a target VPC. As a result, you will incur associated IBM Cloud infrastructure charges.



 Before you begin 



1. Create an instance of [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) and upload your image to a bucket.
2. Create your [VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
3. [Import your custom image to all regions](https://github.com/IBM-Cloud/isv-vsi-product-deploy-sample/tree/mainimport-your-custom-image-to-all-supported-regions) in which you want your software to be available.
4. Create your [Terraform template](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-config).
5.
* [Create a cluster and use this image to deploy a container](https://cloud.ibm.com/docs/containers?topic=containers-getting-startedgetting-started) to the cluster in IBM Cloud Kubernetes Service.







 Copying images between registries 

You can pull an image from a registry in one region and push it to a registry in another region so that you can share the image with users in both regions.

Zoom

![Copying images between registries.](https://cloud.ibm.com/docs-content/v1/content/cbb80bf851fb762a838129cba09d5674f8bfffda/Registry/images/copying_images_mul.svg)

Figure 3. Copying images between registries

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.
* [Set up your own namespace in IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespaceregistry_namespace_setup).
* [Make sure that you can run Docker commands without root permissions](https://docs.docker.com/engine/install/linux-postinstall/). If your Docker client is set up to require root permissions, you must run ibmcloud login, ibmcloud cr login, docker pull, and docker push commands with sudo.

If you change your permissions to run Docker commands without root privileges, you must run the ibmcloud login command again.



To copy an image between two registries, complete the following steps:



1. [Pull an image from a registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_pulling_reg).
2.
* You need an IAM role that includes the is.image.image.export and is.image.image.operate actions. For more information, see [Managing IAM access for VPC Infrastructure Services](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started).
* You need an IBM Cloud Object Storage service instance created. You must also create an authorization for the Image Service for VPC to access IBM Cloud Object Storage with the Writer service access role. For more information, see [Granting access to IBM Cloud Object Storage to import and export images](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq).
* You need IAM access to write to the bucket where you plan to export an image. For more information, see [Assigning access to an individual bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions).



If the image that is being exported is deleted while an export job is in progress, the image status is set to deleting. The export job is allowed to complete before deletion of the image completes. When the image deletion is complete, its export job history is not available. You can use [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-images) events for the export job to determine its final status.





 Exporting a custom image by using the UI 

To export a custom image to IBM Cloud Object Storage, complete the following steps.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.
2.
ibmcloud target -r us-south

If you had used the cloud-object-storage (cos) plugin before, you might need to [reconfigure the crn and set it to the current service](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-iam-authentication).
3. Upload the files named index.html, a-css-file.css, a-picture.png, and a-video.mp4 from the content directory of the web application code you downloaded previously. Upload the files to the root of the bucket.

ibmcloud cos upload --bucket $BUCKET_NAME --key index.html --file index.html
ibmcloud cos upload --bucket $BUCKET_NAME --key a-picture.png --file a-picture.png
ibmcloud cos upload --bucket $BUCKET_NAME --key a-css-file.css --file a-css-file.css
ibmcloud cos upload --bucket $BUCKET_NAME --key a-video.mp4 --file a-video.mp4
4. View your files from your dashboard.

Zoom

![Bucket Content](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution3/Buckets.png)

Bucket Content
5. Access the files through your browser or by using curl:

curl http://$BUCKET_NAME.$PUBLIC_ENDPOINT/index.html
echo open http://$BUCKET_NAME.$PUBLIC_ENDPOINT/index.html

It will look like:

<html>
<head>
<title>Files hosted in Cloud Object Storage and accessible through a Content Delivery Network</title>
...
</html>
* [Disaster recovery and backup for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backup)
* [Configuring IBM Cloudant for cross-region disaster recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-configuring-ibm-cloudant-for-cross-region-disaster-recovery)
* [IBM Cloudant backup and recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloudant-backup-and-recovery)



* Enhancing security for IBM Cloudant



* [Managing access for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-managing-access-for-cloudant)
* [Learning about IBM Cloudant architecture and workload isolation](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-compute-isolation)
* [Using service endpoints to privately connect to IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-service-endpoints)
* [Securing your connection](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-securing-your-connection-to-cloudant)
* [Managing security and compliance with IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-manage-security-compliance)
* [Securing your data in IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-securing-your-data-in-cloudant)
* [Auditing events](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-at_events)





* Reference



* [Understanding your responsibilities when you use IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cloudant-responsibilities)
* Observability
Identify the DEK that you want use to encrypt your image, and then [wrap it with your root key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-cli-referencekp-key-command). If you need to generate a DEK, you can use the [kp wrap](https://cloud.ibm.com/docs/key-protect?topic=key-protect-cli-referencekp-key-command) command with no plain text parameter (-p) to generate the key and wrap it. If you already have a DEK, you can [import](https://cloud.ibm.com/docs/key-protect?topic=key-protect-import-standard-keysimport-standard-keys) it and then wrap it by specifying the plain text parameter on the kp wrap command. Make sure to save the cipher text that is returned by the kp wrap command. You must specify the WDEK cipher text when you import your encrypted image to IBM Cloud console.



Key Protect doesn't save extra authentication data (AAD), so use WDEKs that don't require ADD for unwrapping them.
{: tip}
3. From IBM Cloud Identity and Access Management (IAM), [create an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthcreate-auth) between your Cloud Block Storage (source service) and your Key Management Service (target service). The authorization permits the IBM Cloud backplane services to use your WDEK for data encryption.
4. In IBM Cloud Console, create an instance of IBM Cloud Object Storage and create a bucket to store the data. For more information, see the [Getting started tutorial for IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage-cloud-object-storage)



1. Create the IBM Cloud Object Storage instance in the region where your key management service is provisioned.
2.
* An instance of IBM Cloud Object Storage
* Content in fixed form, like text (HTML would be perfect), and image files



Check that you have the access as appropriate to either the instance of IBM Cloud Object Storage you will be using or the proper [permissions](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions) for the buckets you will be using for this tutorial.

For use of the [IBM Cloud CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cli) with this tutorial, you will need to [configure the Object Storage plug-in](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-config) to specify the service instance you want to use and the default region where you want your new bucket to be created.





 Create a bucket configured for public access 

Creating a bucket for a static website will require public access. There are a number of options for configuring public access. Specifically, using the ObjectReader [IAM role](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam) will prevent the listing of the contents of the bucket while still allowing for the static content to be viewed on the internet. If you want to allow the viewing of the listing of the contents, use the ContentReader [IAM role](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam) for your bucket.



 Create a bucket 

After configuring the CLI plug-in, replace the placeholder content as shown in the example command to create a bucket:

ibmcloud cos bucket-create --bucket <bucketname>

Once you login to the Console and after you create an instance of IBM Cloud Object Storage, you can create a bucket.
For the queries described previously, you need two indexes:



1. A global index-mapping device ID to infrastructure ID
2. A partitioned index-mapping device ID to reading





 Creating a global view index 

A view index is the most efficient way to do the simple device ID to infrastructure ID mapping. To define it, upload a design document with options.partitioned set to false as this index is global. While in a real map function you'd want to be more defensive around field existence, this document would look something like this:

{
"options": {
"partitioned": false
},
"views": {
"by-device": {
"map": "function(doc) { emit(doc.deviceID, doc.infrastructureID) }"
}
}
}

Assuming the previous document in ./view.json, this document is uploaded to the database by using the following command:

curl -X PUT "$SERVICE_URL/readings/_design/infrastructure-mapping" -H 'Content-Type: application/json' --data @view.json

For more language examples that show creating a global view, see the [Storing the view definition](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-views-mapreducestoring-the-view-definition) guide, or [the Create or modify a design document section in API Docs](https://cloud.ibm.com/apidocs/cloudantputdesigndocument).





 Creating a partitioned IBM Cloudant Query index 

To return the readings for a specific device from a partition, you can use an IBM Cloudant Query index. For this document, use POST to _index with an index definition that includes the partitioned field set to true.

For Query index definitions, the partitioned field isn't nested inside an options object.

For these queries, you need two partitioned indexes:



1. By timestamp
2. By device ID and timestamp





 Uploading partitioned index by timestamp
Authorized users default to any user on your account; however, images also can be shared between multiple accounts by updating the sharing options in the IBM Cloud console.





 Can I capture and deploy virtual servers with my self-managed hypervisor? 

Only servers that are provisioned by IBM Cloud can be captured and deployed. Individual virtual servers that you manually created on personal devices cannot be captured, provisioned, or deployed.





 Can I share my private ISO template with other customers? 

The only ISO templates that are made public to all customers are templates that are generated by IBM Cloud. Private ISO templates are account-specific and cannot be shared between customers through the IBM Cloud console.





 Does my ISO template need to be in the same data center as my virtual server to complete a boot from image? 

Yes, ISO templates must be in the same data center as a virtual server to boot from the image. If the ISO template isn't in the same data center, the ISO template must be copied to the appropriate data center. If this situation occurs, a warning appears about the transaction. When an ISO template is copied to a different data center, a small fee is charged to the account as they are for copying other types of image templates.





 What is the difference between physical data and volume size? 

Volume is the disk space that is available for storing files, while physical data consists of the actual files that are stored on the disk.





 What is the image import export feature? 

The image import export feature converts VHDs and ISOs that are stored on an Object Storage account to convert into image templates, and vice versa. When you import an image, a specific file (either VHD or ISO) is sourced from a specified [Object Storage] Account's Container and is converted into an image template. The image template can then be used to start or load a device. When you export an image, the image template is converted into a file (or several files if the template has multiple disks). The image template is then stored in a specified location on an Object Storage Account's Container.





 How do I create an image template for my entire server and not just my primary drive?
const service = CloudantV1.newInstance({});

service.getDocument({
db: 'products',
docId: 'small-appliances:1000042'
}).then(response => {
console.log(response.result);
});

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.

The response contains the document that you requested, or a description of the error if the document can't be retrieved.

See an example response of retrieving a document:

{
"_id": "exampleid",
"brand": "Foo",
"colours": [
"red",
"green",
"black",
"blue"
],
"description": "Slim Colourful Design Electronic Cooking Appliance for ...",
"image": "assets/img/0gmsnghhew.jpg",
"keywords": [
"Foo",
"Scales",
"Weight",
"Digital",
"Kitchen"
],
"name": "Digital Kitchen Scales",
"price": 14.99,
"productid": "1000042",
"taxonomy": [
"Home",
"Kitchen",
"Small Appliances"
],
"type": "product"
}
Show more



 Query parameters 

You can add some query parameters to the URL, for example /mydatabase/doc?attachments=true&conflicts=true.

All parameters are optional.



Table 1.
Image templates 

With IBM Cloud® Virtual Servers image templates, you can capture a device's image to quickly replicate its configuration with minimal changes in the order process.

Image templates provide an imaging option for all Virtual Servers, regardless of operating system. Image templates are used to capture an image of an existing virtual server and create a new one based on the captured image. Image templates are not compatible with bare metal servers.

Image templates are not intended for backing up your data.



  How image templates work 

The two main actions for any image template are create and deploy. When you request to create an image, the automated system of IBM Cloud® takes your server offline. While the server is offline, a compressed backup of your data is created, the configuration information is recorded, and the image template is stored on the IBM Cloud SAN. During the deployment stage of the image template, the automated system constructs a new server that is based on the data that is gathered from the selected image. The deployment process makes adjustments for volume, restores the copied data, and then makes final configuration changes (for example, network configurations) for the new host.

For more information about image templates, see [Getting started with image templates](https://cloud.ibm.com/docs/image-templates?topic=image-templates-getting-started-with-image-templates).
Limits 

Limits that pertain to the usage of IBM® Cloudant® for IBM Cloud® databases are shown in the following tables.



  Databases 



Table 1. Limits for databases

 Description     Limit                                                                             

 Database size   Consult the IBM Cloudant team if your database is likely to exceed 5 TB in size.  
 Partition size  10 GB                                                                             







  Indexes 



Table 2. Limits for indexes

 Description                  Limit     

 Number of global indexes     Unlimited 
 Number of partition indexes  10        







  Request payload 



Table 3. Limits for request payload

 Description         Limit 

 Total request size  10 MB 
 Document size       1 MB  
 Attachment size     10 MB 







  Request timeouts 



Table 4. Limits for request timeouts

 Description     Limit      

 Default         60 seconds 
 _partition/*    5 seconds  







  Query 



Table 5. Limits for query results

 Description                    Limit     

 Default                        Unlimited 
 _partition/* default           2000      
 _search                        200       
 _find by using text index      200