vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Make sure to use a bucket in a [regional location](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints).



1. In IBM Cloud Object Storage, go to your bucket and select Upload > Files to [upload](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload) the image.
2. Use the [Aspera](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-aspera) high-speed transfer plug-in for the fastest upload speeds of your image.



You can use COS SDK with Aspera to initiate high-speed transfer within your custom applications when you use Java, Python, or NodeJS. For more information, see [Using Libraries and SDKs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-asperaaspera-sdk).





 Importing an Image from IBM Cloud Object Storage 

Complete the following steps to import an image from IBM Cloud Object Storage.



1. Go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
* Make sure 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).
} Moved to the [Collections API](https://cloud.ibm.com/apidocs/discovery-datalistcollections). 
 "conversions.pdf": { ... } Not available. If you used special parameters to extract text from images in PDFs, enable optical character recognition (OCR) from the product user interface for the collection that contains the PDFs instead. 
 "conversions.segment": { ... } Not available programmatically. You can split a document at each occurrence of an SDU-generated field such as subtitle from the product user interface. <br>The segment_metadata object with parent_id, id, and total_segments information is not available in v2. You can use the metadata.parent_document_id field to find the common parent for many document segments. 
 "conversions.word": { ... } Not available 
 "enrichments": { ... } [/v2/projects/{project_id}/enrichments](https://cloud.ibm.com/apidocs/discovery-datalistenrichments), [/v2/projects/{project_id}/collections/{collection_id}](https://cloud.ibm.com/apidocs/discovery-datagetcollection) <br>Use the enrichments API to explore existing enrichments. Use the collections API to see and change the enrichments that are enabled on a field in a collection. <br>Some enrichments are applied to the service by default based on the type of project that you create. For more details, see [Default project settings](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-project-defaults). <br>The version of the Entities enrichment that is available in v2 doesn't include the disambiguation field, which in v1 contains the disambiguation information for the entity and includes the entity subtype information.
1. Get the registration script to attach hosts to your IBM Cloud Satellite location. Note that the token in the script is an API key, which should be treated and protected as sensitive information. Make a note of the location of the attach script. Also note that for RHCOS hosts, the attach script is a RHCOS ignition file.

ibmcloud sat host attach --location <location_name_or_ID>
2. [Download the Red Hat CoreOS image](https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/) that you want to use. Use IBM Cloud Object Storage to store your custom image. If you don't already have an instance, [create one](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_service) and create at least one bucket.
3. [Upload the RHCOS image](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload) that you downloaded earlier to a bucket in your Object Storage instance. You can use the Minio command-line client to copy your image from a directory on your local machine to your bucket. First, [create a set of HMAC service credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-credentials) and make a note of the access_key_id and secret_access_key. Then, install the [Minio client](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-minio) and configure it to use your credentials.
4. [Grant access to Object Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq&interface=cli).
5.
Images embedded in PDF, Word, PowerPoint, and Excel documents will not be processed - only the non-image portion of these documents will be processed for text recognition. To work around this issue, import or train an SDU model and reprocess the collection. This will allow text to be extracted from the images. * After you create a Search Skill in Watson Assistant and are directed to the Watson Discovery tooling, the screen is blank. This happens because the URL is missing the Discovery instance ID. To work around this issue:
<-- <ol> -->

1. From the IBM Cloud Pak for Data web client menu, choose My Instances. For example: https://mycluster.com/zen//myInstances.
2. Select the Discovery instance you are using and click Launch Tool.
3. Once the tooling is loaded, the URL should have the following structure: https://mycluster.com/discovery/core/instances/00000000-0000-0000-0001-597165341876/projects
4. Copy the entire path, excluding /projects. For example: https://mycluster.com/discovery/core/instances/00000000-0000-0000-0001-597165341876
5. Go back to the browser tab that is displaying the blank Discovery screen. That URL structure will look like this: https://mycluster.com/discovery/core/collections/new?redirect_uri=...
6. Replace https://mycluster.com/discovery/core with the URL you copied previously, so the new URL should look like this: https://mycluster.com/discovery/core/instances/00000000-0000-0000-0001-597165341876/collections/new?redirect_uri=...
7. Press enter to open updated URL. You should now be on the Watson Discovery Manage collections page.

<-- </ol> -->
[Analyzers extract information about people, companies, organizations, cities, geographic features, and other information from the content.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/analyzers.png)

Figure 1. Analyzers

As well as entities, the API can also place the article in a hierarchy of categories. In this case, Watson suggests the following categories:



* Travel, tourist destinations France
* Sports, soccer
* Sports, football



You can pre-process your raw data by calling the Watson API for each document and storing a list of entities, concepts, and categories in your IBM Cloud document. This pre-processing provides automatic metadata about your free-text information. It can also provide an easier means to search and navigate your app.
You can use the [ibm-backup-restore image](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesibmcloud-backup-restore) to configure the service to make one-time or scheduled backups for data in your clusters. For more information about the service, see the [Object Storage documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage). Yes Yes 
 IBM Cloud Classic File Storage for Classic [IBM Cloud Classic File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedgetting-started) is persistent, fast, and flexible network-attached, NFS-based file storage that you can add to your apps by using Kubernetes persistent volumes. You can choose between predefined storage tiers with GB sizes and IOPS that meet the requirements of your workloads. For more information about how to provision file storage in your cluster, see [Setting up IBM Cloud File Storage for Classic](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_storage). Yes 
 Portworx [Portworx](https://portworx.com/products/portworx-enterprise//) is a highly available software-defined storage solution that you can use to manage persistent storage for your containerized databases and other stateful apps, or to share data between pods across multiple zones. You can install Portworx with a Helm chart and provision storage for your apps by using Kubernetes persistent volumes. For more information about how to set up Portworx in your cluster, see [Setting up software-defined storage (SDS) with Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_about). Yes Yes 







 Database services 



Table 7. Database services

 Service Description Classic VPC
IBM Cloud File Storage for Classic plug-in and monitor Master 357 358 Image updated for [CVE-2019-5188](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5188). 
 OpenVPN server Master N/A N/A OpenVPN server is now restarted during [cluster master refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh). 
 Ubuntu 18.04 packages Worker N/A N/A Updated worker node images with package updates for [CVE-2019-19956](https://nvd.nist.gov/vuln/detail/CVE-2019-19956), [CVE-2020-7595](https://nvd.nist.gov/vuln/detail/CVE-2020-7595), [CVE-2019-18634](https://nvd.nist.gov/vuln/detail/CVE-2019-18634), [CVE-2019-3843](https://nvd.nist.gov/vuln/detail/CVE-2019-3843), [CVE-2019-3844](https://nvd.nist.gov/vuln/detail/CVE-2019-3844), [CVE-2019-20386](https://nvd.nist.gov/vuln/detail/CVE-2019-20386), and [CVE-2020-1712](https://nvd.nist.gov/vuln/detail/CVE-2020-1712).
Configuring CDN with IBM Cloud Object Storage 

You can use IBM Cloud® Content Delivery Network (CDN) to quickly and securely deliver the website assets (images, videos, documents) hosted and served on the IBM Cloud Object Storage to users around the world.



 Before you begin 

Before you begin using CDN with IBM Cloud Object Storage (ICOS), you'll first need to store objects with [public access](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-public-access) in IBM Cloud Object Storage.





 Create a CDN instance with ICOS 



1. Follow the [guidelines to create a CDN instance](https://cloud.ibm.com/docs/CDN?topic=CDN-order-a-cdn) with Object Storage type of origin to configure your S3 Endpoint and Bucket name with public access objects stored in the ICOS.
2. Follow the [guidelines to get your CDN instance into RUNNING status](https://cloud.ibm.com/docs/CDN?topic=CDN-next-steps-after-ordering).
3. Access your ICOS objects with CDN URL: http://<hostname>/<path>/index.html.



For more information, see [Accelerate delivery of static files using a CDN](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-static-files-cdn).





 FAQs for CDN with ICOS 



 Can I use ICOS private endpoints for CDN? 

No. The CDN edge servers can only access the ICOS public endpoints, so objects in the ICOS buckets should provide public access.





 Will traffic sent from ICOS to CDN be charged? 

Yes. The CDN and ICOS don't have a way of measuring each other's traffic, so both traffic from ICOS and CDN are charged.





 How does the CDN edge server retrieve content from the ICOS objects?
IBM Cloud File Storage for Classic plug-in and monitor Master 357 358 Image updated for [CVE-2019-5188](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5188). 
 OpenVPN server Master N/A N/A OpenVPN server is now restarted during [cluster master refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh). 
 Ubuntu 18.04 packages Worker N/A N/A Updated worker node images with package updates for [CVE-2019-19956](https://nvd.nist.gov/vuln/detail/CVE-2019-19956), [CVE-2020-7595](https://nvd.nist.gov/vuln/detail/CVE-2020-7595), [CVE-2019-18634](https://nvd.nist.gov/vuln/detail/CVE-2019-18634), [CVE-2019-3843](https://nvd.nist.gov/vuln/detail/CVE-2019-3843), [CVE-2019-3844](https://nvd.nist.gov/vuln/detail/CVE-2019-3844)[CVE-2019-20386](https://nvd.nist.gov/vuln/detail/CVE-2019-20386), and [CVE-2020-1712](https://nvd.nist.gov/vuln/detail/CVE-2020-1712).
IBM Cloud File Storage for Classic plug-in 347 348 Image updated for [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 Kubernetes DNS 1.14.13 1.15.4 See the [Kubernetes DNS release notes](https://github.com/kubernetes/dns/releases/tag/1.15.4). Image update resolves [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 Kubernetes DNS autoscaler 1.2.0 1.3.0 See the [Kubernetes DNS autoscaler release notes](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler/releases/tag/1.3.0). Image update resolves [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 Load balancer and load balancer monitor for IBM Cloud Provider 146 147 Image updated for [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 OpenVPN client 2.4.6-r3-IKS-13 2.4.6-r3-IKS-116 Image updated for [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697).
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 IBM Cloud Kubernetes Service 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 IBM Cloud Kubernetes Service 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 IBM Cloud Kubernetes Service and IBM Cloudant bring.
* Over time, the original apps that were initially moved to the cloud were restructured into cooperative microservices that run on IBM Cloud Kubernetes Service. 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 traditional tools that slow down prototyping while they wait for hardware procurement.

IBM Cloud Kubernetes Service provides spin-up of compute by using open-source standard technology. After the company moved to IBM Cloud Kubernetes Service, 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. Their traditional development tools get a new face when they add on AI cloud services to apps with a click.



 Context 

Streamlining developer productivity and deploying AI tools to partners 4 times faster**
cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin,
cloudbaseinit.plugins.common.localscripts.LocalScriptsPlugin
8. Modify the Unattend.xml file in C:Program FilesCloudbase SolutionsCloudbase-InitconfUnattend.xml to set PersistAllDeviceInstalls to false.
9. Disconnect all mounted drives. For more information, see [Sysprep (Generalize) a Windows installation](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation?view=windows-10).
10. Run Sysprep by using the following command:

C:WindowsSystem32SysprepSysprep.exe /oobe /generalize /shutdown "/unattend:C:Program FilesCloudbase SolutionsCloudbase-InitconfUnattend.xml"

If you are customizing a virtual server to migrate from the Classic infrastructure, return to [Migrating a virtual server from the classic infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-migrate-vsi-to-vpcmigrate-customize-image-vpc) and continue completing migration steps.







 Uploading the custom image 

Upload your image to IBM Cloud Object Storage. 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).







 Importing and validating custom images into VPC for Citrix-DaaS 

You can create your own custom image on premises and then import it to IBM Cloud® Virtual Private Cloud infrastructure from IBM Cloud® Object Storage.
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.
3. Create your [HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).
4. [Open a support case](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-help-and-support) so that the Power Systems Virtual Server product management team can convert your image into a stock image. Include your HMAC credentials and bucket details in the support case.
Each folder has its own simple Dockerfile file that is used by the script to create a container image, which is then uploaded to the IBM Container Registry.
2. It creates a bunch of kubernetes secrets with all the credentials that are going to be needed to access the different IBM services (IBM Cloudant, Redis and Event Streams).
3. It deploys the application code (and the secretes) to the Red Hat OpenShift on IBM Cloud cluster using the instructions contained in the deployment.yml script.







 The deployment.yml script 

This script tells Openshift what to deploy to the machines in the Openshift cluster. In our case this is:



1. Data producers (trucktrackerproducer).
2. Data consumers (trucktrackerredisconsumer and trucktrackercloudantconsumer)
3. Web application (trucktrackerweb)



In all cases, they pull an image from the container registry and get fed some environment variables with the credentials they require to access external services.





 The Truck Tracker system 

The Truck Tracker system is a set of simple Node.js scripts that use four main packages:



1. [@ibm-cloud/cloudant](https://github.com/IBM/cloudant-node-sdk) to connect to IBM Cloudant and read/write data.
2. [Redis](https://www.npmjs.com/package/redis) to connect to the Redis instance and read/write data.
3. [kafkajs](https://www.npmjs.com/package/kafkajs) to connect to the Event Streams instance.
4. [Express](https://expressjs.com/) to enable a simple web server that allows interaction with the data.



There are five main files:



1. server.js: This runs the web server and communicates with Redis. It is getting regular calls from the front end to the /data route. It connects to Redis, downloads an object with the ID and position of every truck and returns that to the front end.
For more information, see [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_change_storage_configuration). When you resize the volume in your IBM Cloud infrastructure account, the attached PVC description is not updated. Instead, you can log in to the openshift-image-registry pod that uses the registry-backing PVC to verify that the volume is resized.







 Storing images in the worker node empty directory 

You might store the internal registry images locally in the emptyDir of the worker node, such as a bare metal worker node, to increase performance if you build containers from large images regularly.

Keep in mind that this data is not persistent, and if the pod or worker node is restarted, the stored data is deleted and unrecoverable.



1. [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
2. [Update the image registry operator configmap](https://docs.openshift.com/container-platform/4.11/registry/configuring_registry_storage/configuring-registry-storage-baremetal.htmlinstallation-registry-storage-non-production_configuring-registry-storage-baremetal) to set the storage to use the emptyDir of the worker node.

oc patch configs.imageregistry.operator.openshift.io/cluster --type merge --patch '{"spec":{"storage":{"emptyDir":{}}}}'
3. If the [image registry operator management state](https://docs.openshift.com/container-platform/4.11/registry/configuring-registry-operator.htmlregistry-operator-configuration-resource-overview_configuring-registry-operator) is set to Unmanaged, such as in Satellite clusters, update the management state to Managed. Now, the operator updates the internal registry pod.
<h2>Upload Image to IBM Cloud Object Storage</h2>
<div class="row">
<div class="col-md-12">
<div class="container" style="margin-top: 20px;">
<div class="row">

<div class="col-lg-8 col-md-8 well">

<p class="wellText">Upload your JPG image file here</p>

<form method="post" enctype="multipart/form-data" action="/">
<p><input class="wellText" type="file" size="100px" name="img-file" /></p>
<br/>
<p><input class="btn btn-danger" type="submit" value="Upload" /></p>
</form>

<br/>
<span class="notice"><%=status%></span>
</div>
</div>
</div>
</div>
</div>
</div>
</body>

</html>
Show more

Let's take a moment to return to app.js. The example sets up Express routes to handle extra requests that are made to our app. The code for these routing methods are in two files under the ./src/routes directory in your project:



* imageUploadRoutes.js: This file handles what happens when the user selects an image and clicks Upload.
* galleryRoutes.js: This file handles requests when the user clicks the Gallery tab to request the imageGallery view.



//...
var imageUploadRoutes = require('./src/routes/imageUploadRoutes')(title);
var galleryRouter = require('./src/routes/galleryRoutes')(title);