vania-janet/multiturn-rag-retrieval-data huggingface dataset:
With the Full Linux Subscription, you have access to stock images that are already prepared for Power Systems Virtual Server. For more information, see [Full Linux® subscription for Power Systems Virtual Server instances](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-set-full-Linux).

If you want to import a custom Linux image, you need to first upload the image to IBM Cloud® Object Storage in OVA format.



* [Deploying a custom image within a Power Systems Virtual Server workspace](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-image), which outlines the necessary steps for
* [Creating an IBM Cloud® Storage bucket](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-imagecloud-storage-bucket)
* [Generating secret and access keys](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-imageaccess-keys)



Before you begin, make sure that the OVA image is loaded in the storage bucket.



1. Log in to [Boot images in Power Systems Virtual Server](https://cloud.ibm.com/power/boot-images).
2. Select the workspace that you created.
3. Click Import image.
4. Enter Custom image name as image name in your catalog.
5. Select Storage type either as Tier 1 or Tier 3. A virtual server instance can use volumes from one storage type only, and the custom image need to be prepared for this storage type.
6. Select the Region for your deployment.
7. Enter the file name of the image as Image file name.
8. Enter the Bucket name of your Cloud Object Storage.
9. Enter Cloud Object Storage access key and Cloud Object Storage secret key.
10. Click Import image.







 Creating a Service ID and API key in IBM Cloud®
IBM Cloud File Storage for Classic plug-in and monitor 420 421 Updated universal base image (UBI) to resolve [CVE-2022-42898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42898). Updated Go to version 1.18.8 
 Key Management Service provider v2.5.11 v2.5.12 Updated Go dependencies. 
 Kubernetes v1.24.8 v1.24.9 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.9). 
 Load balancer and load balancer monitor for IBM Cloud Provider 2110 2325 Update Go to version 1.19.1 and update dependencies. 







 Change log for worker node fix pack 1.24.8_1546, released 05 December 2022 

The following table shows the changes that are in the worker node fix pack 1.24.8_1546. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.8_1545

 Component Previous Current Description 

 Containerd 1.6.8 1.6.10 See the [1.6.10 change log](https://github.com/containerd/containerd/releases/tag/v1.6.10) and the [1.6.9 change log](https://github.com/containerd/containerd/releases/tag/v1.6.9).
IBM Cloud File Storage for Classic plug-in 348 349 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 IBM Cloud Provider v1.14.5-160 v1.14.6-172 Updated to support the Kubernetes 1.14.6 release. 
 Key Management Service provider 207 212 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Kubernetes v1.14.5 v1.14.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.6).
IBM Cloud File Storage for Classic plug-in 348 349 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 IBM Cloud Provider v1.15.2-94 v1.15.3-112 Updated to support the Kubernetes 1.15.3 release. 
 Key Management Service provider 207 212 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Kubernetes v1.15.2 v1.15.3 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.15.3).
IBM Cloud File Storage for Classic plug-in and monitor 420 421 Updated universal base image (UBI) to resolve [CVE-2022-42898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42898). Updated Go to version 1.18.8 
 Key Management Service provider v2.5.11 v2.5.12 Updated Go dependencies. 
 Kubernetes v1.25.4 v1.25.5 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.5). 
 Load balancer and load balancer monitor for IBM Cloud Provider 2110 2325 Update Go to version 1.19.1 and update dependencies. 







 Change log for worker node fix pack 1.25.4_1524, released 05 December 2022 

The following table shows the changes that are in the worker node fix pack 1.25.4_1524. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.25.4_1523

 Component Previous Current Description 

 Containerd 1.6.8 1.6.10 See the [1.6.10 change log](https://github.com/containerd/containerd/releases/tag/v1.6.10) and the [1.6.9 change log](https://github.com/containerd/containerd/releases/tag/v1.6.9).
IBM Cloud File Storage for Classic plug-in 348 349 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 IBM Cloud Provider v1.13.9-209 v1.13.10-221 Updated to support the Kubernetes 1.13.10 release. 
 Key Management Service provider 207 212 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Kubernetes v1.13.9 v1.13.10 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.13.10).
To list available images in your IBM Cloud Container Registry account, run ibmcloud cr image-list.

name
: The name of the container that you want to deploy to your cluster.

runAsUser
: In the spec containers security context section, you can optionally set the run as user value.

mountPath
: In the spec containers volume mounts section, enter the absolute path of the directory to where the volume is mounted inside the container. If you want to share a volume between different apps, you can specify [volume sub paths](https://kubernetes.io/docs/concepts/storage/volumes/using-subpath) for each of your apps.

volumeMounts.name
: In the spec containers volume mounts section, enter the name of the volume to mount to your pod.

volumes.name
: In the volumes section, enter the name of the volume to mount to your pod. Typically this name is the same as volumeMounts/name.

claimName
: In the volumes persistent volume claim section, enter the name of the PVC that binds the PV that you want to use.



 Creating a deployment 

After you create PVC and deployment configuration files, create the deployment in your cluster.



1. Create the deployment.

kubectl apply -f <local_yaml_path>
2. Verify that the PV is successfully mounted.

kubectl describe deployment <deployment_name>

The mount point is in the Volume Mounts field and the volume is in the Volumes field.

Volume Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-tqp61 (ro)
/volumemount from myvol (rw)
...
Volumes:
myvol:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: mypvc
ReadOnly: false
3. Verify that you can write data to your IBM Cloud Object Storage service instance by logging in to the app pod and writing data. Log in to the pod that mounts your PV.
IBM Cloud File Storage for Classic plug-in 348 349 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Key Management Service provider 207 212 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Load balancer and load balancer monitor for IBM Cloud Provider 147 148 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 







 Change log for worker node fix pack 3.11.135_1521_openshift, released 19 August 2019
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/icons/icon_hamburger.svg) > Resource list > Storage > Cloud Object Storage name > Buckets. 
 Cloud Object Storage access key To identify your access key, select Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/icons/icon_hamburger.svg) > Resource list > Storage > Cloud Object Storage name > Service credentials > View credentials. Copy the access_key_id value and past it into this field. 
 Cloud Object Storage secret key To identify your secret key, select Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/icons/icon_hamburger.svg) > Resource list > Storage > Cloud Object Storage name > Service credentials > View credentials. Copy the secret_access_key value and paste it into this field. 





1. Return to Virtual server instances and provision a new Power Systems Virtual Server instance. Click the arrow in the appropriate boot image tile to see your custom boot image.

If you'd like to download your image at a later point, go to the Resource List in the Power Systems Virtual Server user interface. Once there, access your Cloud Object Storage workspace. In the bucket where your image is stored, select the image file that you want to download and select Download objects. See [Download an object](https://cloud.ibm.com/docs/cloud-object-storage-cli-plugin?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-download-object) for the Cloud Object Storage CLI command.
The example shows an authorization policy for the Image Service for VPC to access IBM Cloud Object Storage.

curl --location --request POST 'https://iam.cloud.ibm.com/v1/policies' --header 'Content-Type: application/json' --header 'Authorization: Bearer <iam token>' --data-raw '{
"type": "authorization",
"subjects": [
{
"attributes":
{
"name": "accountId",
"value": "$ACCOUNT_ID"
},
{
"name": "serviceName",
"value": "is"
},
{
"name": "resourceType",
"value": "image"
}
]
}
],
"roles": [
{
"role_id": "crn:v1:bluemix:public:iam::::serviceRole:Reader"
},
{
"role_id": "crn:v1:bluemix:public:iam::::serviceRole:Writer"
}
],
"resources": [
{
"attributes":
{
"name": "accountId",
"value": "$ACCOUNT_ID"
},
{
"name": "serviceName",
"value": "cloud-object-storage"
}
]
}
]
}'







 Next steps 

When you've completed these steps so that Image Service for VPC can access images in IBM Cloud Object Storage or export images to IBM Cloud Object Storage, continue with one of the following topics:



* [Creating a Linux custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-linux-custom-image)
* [Creating a Windows custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-windows-custom-image)
IBM Cloud File Storage for Classic plug-in 348 349 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Key Management Service provider 207 212 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 
 Load balancer and load balancer monitor for IBM Cloud Provider 147 148 Image updated for [CVE-2019-9512](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512), [CVE-2019-9514](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514), and [CVE-2019-14809](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14809). 







 Change log for worker node fix pack 1.12.10_1564, released 19 August 2019 

The following table shows the changes that are in the worker node fix pack 1.12.10_1564.
: This filter accepts only changes for documents whose ID is specified in the doc_ids parameter.

_selector
: Returns changes for documents that match the selector request body parameter. The [selector syntax](https://cloud.ibm.com/apidocs/cloudantpostfind) is the same as the syntax that is used for [_find](https://cloud.ibm.com/apidocs/cloudantpostexplain). If you want to use a selector filter, you must use the POST changes feed (as you can't supply a document body with a GET request). Use the _selector method of filtering instead of the _view filtering method because it's faster and easier to use.

For more information, see the [API documentation](https://cloud.ibm.com/apidocs/cloudantgetchanges-changes-request).

_view
: Enables use of an existing [map function](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-views-mapreducea-simple-view) as the filter.





 The since argument 

Use the since argument to get a list of changes that occurred after a specified sequence identifier. If the since identifier is 0 (the default), or omitted, the request returns all changes. If the since identifier is now, the request asks for changes that are made after the current time.

The distributed nature of IBM Cloudant can affect the results that you get in a response. For example, if you request a list of changes twice, by using the same since sequence identifier both times, the order of changes in the resulting list might not be the same.

You might also see some results that appear to be from before the since parameter. The reason is that you might be getting results from a different replica of a shard (a shard replica).

Shard replicas automatically and continuously replicate to each other and eventually have the same data. However, at any point in time, a shard replica might differ from another shard replica because the replication between them isn't yet complete.

When you request a list of changes, normally the same replicas are used to respond.
Step 8: Mirror the Operator index to IBM Cloud Container Registry 



1. Copy the following ImageSetConfiguration and save it as a file called imageset.yaml.

apiVersion: mirror.openshift.io/v1alpha2
kind: ImageSetConfiguration
storageConfig:
registry:
imageURL: us.icr.io/NAMESPACE/redhat-operator-index
skipTLS: false
mirror:
operators:
- catalog: registry.redhat.io/redhat/redhat-operator-index:v4.10
packages:
- name: local-storage-operator
- name: ocs-operator
- name: mcg-operator
- name: odf-operator
- name: odf-csi-addons-operator
2. Mirror the OpenShift Data Foundation images from registry.redhat.io to your IBM Cloud Container Registry namespace.

Before running oc-mirror make sure to set the umask of your bastion host to 0022.

oc-mirror --config=imageset.yaml docker://us.icr.io/NAMESPACE --dest-skip-tls







 Step 9: Create a secret to pull images from IBM Cloud Container Registry 



1. Find and record your unique Red Hat registry pull secret. For more information on how to find your Red Hat registry pull secret, see [Red Hat Container Registry Authentication](https://access.redhat.com/RegistryAuthentication).
2. Rename the pull-secret file secret to auth.json.
3. Encode your IAM API key in base64.

printf "iamapikey:IAM-API-KEY" | base64
4. Add the following section to your auth.json file.

{"auths": {"us.icr.io": {"auth": "BASE64-VALUE","email": "IBM-EMAIL"}}}
5. Create the secret in the openshift-marketplace namespace.
By default, boot volumes are encrypted by IBM-managed encryption, however, customer-managed encryption is an option. Boot volumes can not be detached, deleted or increased or reduced in size. Boot volumes are always deleted when the virtual server is deleted. Boot volumes contain the operating system files.
* Data volumes - Data volumes leverage block storage for VPC and provides hypervisor-mounted, high-performance data storage that is stored redundantly across multiple physical disks in an Availability Zone (AZ) to prevent data loss due to failure of any single component. Data volumes range from 10 GB to 2000 GB and maximum IOPS varies based on volume size and the IOPS tier profile selected. For example, the max IOPS for a 5 IOPS/GB volume of 2000 GB is 10,000 IOPS. You are able to select a volume profile that best meets your requirements as volume profiles are available as three predefined IOPS tiers or as a custom IOPS profile:



* 3 IOPS/GB - A general-purpose tier profile provides IOPS/GB performance suitable for a virtual server instance Balanced profile.
* 5 IOPS/GB - This profile provides IOPS/GB performance suitable for a virtual server instance Compute profile.
* 10 IOPS/GB - Typically used for a virtual server instance Memory profile.



For more information, see [IOPs tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers). The number of volumes that can be attached to a virtual server depends on how many vCPUs the virtual server contains. For more information, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). Data volumes can be detached and attached to virtual servers as required. Data volumes are encrypted by default with IBM-managed encryption. You can also encrypt data volumes using your own root keys. Refer to [Block storage capacity and performance](https://cloud.ibm.com/docs/vpc?topic=vpc-capacity-performance) advice on choosing the optimal block storage volume size and performance level.
Open the [Workload Protection UI](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-launch).
2. Hover over the Posture icon ![Posture icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/posture.png) and click Compliance.



The compliance posture for each of your [zones](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-zones) is displayed.



3. Click the zone or policy for the report. The Results page will open.
4. If desired, [filter the displayed results.](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-details-filter)
5. Click the desired requirement or control and click the sub-requirement or control for the report.
6. In the control details, click Download Report. The report will be downloaded to your local system.

The maximum file size for a report file is 10 MB.
These options allow you to choose between Standard and High speed as the default transport for uploads and downloads.

Typically, using the IBM Cloud Object Storage web-based console isn't the most common way to use Object Storage. The Standard transfer option limits objects size to 200 MB and the file name and key will be the same. Support for larger object sizes and improved performance (depending on network factors) is provided by Aspera high-speed transfer.

An Aspera server runs one SSH server on a configurable TCP port (22 by default, but often customers use port 33001). The firewall on the server side must allow this one TCP port to reach the Aspera server. No servers are listening on UDP ports. When a transfer is initiated by an Aspera client, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port over which the data will travel. By default, Aspera clients and servers are configured to use UDP port 33001. After the session initiation step, both the client and the server will send and receive UDP traffic on the negotiated port. To allow the UDP session to start, the firewall on the Aspera server side must allow port UDP 33001 to reach the Aspera server.WFor For more information, see [Firewall Considerations](https://www.ibm.com/support/pages/firewall-considerations).





 Transfer status 

Active: Once you initiate a transfer, the transfer status displays as active. While the transfer is active, you can pause, resume, or cancel an active transfer.

Completed: Upon completion of your transfer, information about this and all transfers in this session display on the completed tab. You can clear this information. You will only see information about transfers that are completed in the current session.

Preferences: You can set the default for uploads and downloads to High speed.

Downloads that use Aspera high-speed transfer incur egress charges. For more information, see the [pricing page](https://cloud.ibm.com/objectstorage/createpricing).

Advanced Preferences: You can set bandwidth for uploads and downloads.
],
"model_name": "natural_language_understanding"
}
]
}
],
"metadata": {},
"enriched_html": [
{
"tables":
{
"body_cells":
{}
],
"location": {
"begin": 99,
"end": 183
},
"row_headers": ],
"key_value_pairs": ],
"section_title": {},
"contexts": ]!,
"text": "Holiday Popular greeting Christmas Merry Christmas",
"table_headers": ],
"title": {},
"column_headers": ]
}
]
}
],
"html": [!
"<html><head>This is my html file</head><body><p>My file contains a table.</p><table><tbody><tr><th>Holiday</th><th>Popular greeting</th></tr><tr><td>Christmas</td><td>Merry Christmas</td></tr></tbody></table></body></html>"
]
},
"notices": []
}
Show more







 Analyze API limits 

The following table shows the file size and usage limits for the Analyze API.



Limits that are applied to the Analyze API usage

 Deployment type File size limit Concurrent collections limit Concurrent queries per collection limit 

 Cloud Pak for Data installed deployment Unlimited Unlimited Unlimited 
 Enterprise plan managed deployment 50 KB 5 5 



Use of the Analyze API from Discovery Cartridge for IBM Cloud Pak for Data affects license usage. For more information, see the [license information](https://www-40.ibm.com/software/sla/sladb.nsf/displaylis/F644E41EA1B29A96002587F10057A1C7?OpenDocument).





 Monitoring usage IBM Cloud Pak for Data