vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Affinity: Use this option to select an existing VM instance (VM) or an existing volume as the affinity object. The new volume is created in the same storage pool where the affinity object resides. If you are using VM instance as an affinity object, the storage pool that is selected is based on the PMV instance's root (boot) volume.
* Anti-affinity: Use this option to specify one or more existing VM instances or one or more volumes as the anti-affinity objects. The new volume is created in a different storage pool than the storage pool where one or more anti-affinity objects reside.



For more information about affinity and anti-affinity policy, see [What does it mean to set an affinity or anti-affinity rule?](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqsaffinity).

In the API for create volume feature two new properties antiAffinityVMInstances and antiAffinityVolumes have been added. These properties are used only to specify anti-affinity objects. You can specify only one object type for affinity or anti-affinity objects, either VM Instances or Volumes. For more information about storage volumes APIs, see [Create a new data volume](https://cloud.ibm.com/apidocs/power-cloudpcloud-cloudinstances-volumes-post) and [Create multiple data volumes from a single definition](https://cloud.ibm.com/apidocs/power-cloudpcloud-v2-volumes-post).
7. Click Create and Attach.







 Resizing a storage volume 

You can resize a storage volume after its initial creation. To delete a volume, its status must indicate one of the following states: available, error, error_restoring, error_extending, or error_managing. Additionally, the storage volume cannot be deleted if it is migrating, attached, belongs to a group, has snapshots, or is disassociated from its snapshots after a transfer. Resizing is not immediately available after you deploy a VM.
You need to order new Block Storage for Classic in the correct data center, and then cancel the Block Storage for Classic device that you ordered in the wrong location. When the volume is canceled, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. Billing for the volume stops immediately. When the reclaim period expires, the data is destroyed and the volume is removed from the console, too.
* How can we tell which Block Storage for Classic volumes are encrypted?

When you look at your list of Block Storage for Classic in the [IBM Cloud® console](https://cloud.ibm.com/login), you can see a lock icon next to the volume name for the LUNs that are encrypted.
* How do we know when we're provisioning Block Storage for Classic in an upgraded data center?

When you order Block Storage for Classic, all upgraded data centers are denoted with an asterisk () in the order form, and an indication that you're about to provision storage with encryption. When the storage is provisioned, you can see an icon in the storage list that shows that storage as encrypted. You can find a full list of upgraded data centers and available features [here](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-selectDC).
* If we own nonencrypted Block Storage for Classic in a data center that was recently upgraded, can we encrypt that Block Storage for Classic?

Block Storage for Classic that is provisioned before the data center upgrade can't be encrypted. New Block Storage for Classic that is provisioned in upgraded data centers is automatically encrypted. Data on nonencrypted storage in an upgraded data center can be encrypted by creating a LUN, then copying the data to the new encrypted LUN with host-based migration. For more information, see [Upgrading existing Block Storage for Classic to enhanced Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-migratestoragemigratestorage).
Select the location for your namespace, and click Create.



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





 Create a signing key 

Create an image signing key with the proper encoding to sign your application Docker images.

This key is required for the CI pipeline. The default secret name entry is signing_key. For more information, see [Generating a GPG key](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-image-signing).





 Create an IBM Cloud API key 

Create an [API key](https://cloud.ibm.com/iam/apikeys).

Save the API key value by either copying, downloading it, or adding it to your vault. The default secret name entry is ibmcloud_api_key.





 Create an IBM Cloud® Object Storage instance (optional) 

Create an IBM Cloud Object Storage instance and bucket.

For more information, see [Configuring IBM Cloud Object Storage for storing evidence](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-cos-config), and [What is IBM Cloud Object Storage?](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage)

The default IBM Cloud Object Storage API key is cos_api_key.
Configuring IBM Cloud Object Storage for storing evidence 

Complete these steps to create an IBM Cloud Object Storage instance and IBM Cloud Object Storage bucket to store evidence that is used by the IBM Cloud DevSecOps pipelines.



 Create a Cloud Object Storage instance 

Create an [IBM Cloud Object Storage instance](https://cloud.ibm.com/catalog/services/cloud-object-storage).





 Create a Cloud Object Storage bucket 

In Cloud Object Storage, files are grouped in buckets. You might think of buckets like directories, except that no subdirectories are in buckets.



1. In Cloud Object Storage, click Buckets.
2. Click Create bucket.
3. Choose the Customize your bucket option.
4. Give the bucket a unique, memorable name to help you remember what the bucket is for. Over time, you might create many buckets.
5. Set Resiliency to Regional. Regional resiliency has the best performance with the lowest cost. However, if the ability to survive a regional outage is essential, set the resiliency to "Cross Region."
6. For best performance, set Location to the same location as your toolchain location.
7. Usually, the default for Storage class is suitable for use, so you don't need to use ADVANCED CONFIGURATION.







 Create a service credential 



1. In Cloud Object Storage, click Service Credential.
2. Click New Credential.
3. Provide the details:



* Name: Name of the credential.
* Role: Role for the credential. The Object writer and Reader role is suggested for handling evidence.









 Provide bucket access to the service credential 



1. In Cloud Object Storage, click Buckets.
2. Select the bucket that was created in the previous step.
3. Click Access policies, and select the Service IDs option
4. Select the service credential that was created in the previous step, and select the Object writer and Reader role.
5. Click Create Access Policy.
Aspera High-Speed Transfer, Immutable Object Storage, creating Key Protect buckets, or Bucket Firewalls cannot be used by the CLI.





 Abort a multipart upload 



* Action: Abort a multipart upload instance by ending the upload to the bucket in the user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos multipart-upload-abort --bucket BUCKET_NAME --key KEY --upload-id ID [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* The KEY of the object.



* Flag: --key KEY



* Upload ID identifying the multipart upload.



* Flag: --upload-id ID



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Configure a static website 



* Action: Configures a bucket to host a static website.
* Usage:ibmcloud cos bucket-website-put --bucket BUCKET_NAME [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket. =======
* Flag: --bucket BUCKET_NAME
* The website configuration in the form of a JSON structure. The file:// prefix is used to load the JSON structure from the specified file, such as --website-configuration file://<filename.json>.
* Flag: --website-configuration STRUCTURE The following parameters are available for configuring static website behavior. None are required. For more details, [see the documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-static-website-options).

{
"ErrorDocument": {
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::backup-policy:r138-0521986d-963c-4c18-992d-d6a7a99d115f
Status stable
Last job completed at 2023-02-22T20:12:44.000Z
Plans ID Name Resource type
r138-2129a79a-5629-4069-bf79-7bb0af3b0bd3 my-policy-plan-a backup_policy_plan
r138-6f4f08ba-e0bb-470f-bbfb-f3a22aebbfa9 my-policy-plan-c backup_policy_plan

Backup tags dev:env,bck:test
Backup resource type volume
Resource group defaults
Created at 2023-02-21T22:42:10+00:00

For more information about available command options, see [ibmcloud is backup-policy-update](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policy-update).





 Updating a backup plan from the CLI 

Run the ibmcloud is backup-policy-plan-update command to update a backup plan. Identify the policy and plan by ID or name in the command line. You can update the plan name, cron-spec backup schedule, attach user tags, update backup retention period, add, or remove fast restore zones.

The following code snippet shows the command syntax.
* UI
* CLI
* API







 Using the Logpush service 

IBM Cloud® Internet Services Enterprise-level plans have access to detailed logs of HTTP and Range requests, and firewall events for their domains. These logs are helpful for debugging and analytics, especially when combined with other data sources, such as ingress or application server logs at the origin.

The data from Logpush is the same as that from [Logpull](https://cloud.ibm.com/docs/cis?topic=cis-logpulllogpull). However, unlike Logpull, which allows you to download request logs, Logpush provides the option to push the request logs to a IBM Cloud Log Analysis instance, or a IBM Cloud® Object Storage (Object Storage) bucket. You must [enable log retention](https://cloud.ibm.com/docs/cis?topic=cis-logpulllog-retention) before using Logpush.

Range and firewall event logs are not included in HTTP(s) logs and require separate jobs. These jobs can be pushed to the same Object Storage bucket, but must have a different path.

Logpush uses HTTPS endpoints for IBM Cloud Object Storage, so the log data is encrypted while in motion.



 Before you begin 

Before you create a Logpush job, you must have an [Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started) instance (for CLI and API use only) or an [Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) instance with a bucket that has write access granted to IBM Cloud® account cislogp@us.ibm.com. This enables CIS to write request logs into the Object Storage bucket.





 Setting up Logpush using the console 

You can use either Log Analysis instances or Cloud Object Storage buckets as destinations for logpush jobs.



 Creating Logpush with Log Analysis 

To configure a logpush job using Log Analysis, follow these steps.



1. Select the service.
The following built-in data source collections are not available in v2:

Watson Discovery News
: This pre-enriched data source is not offered in v2. For more information about an alternative way to get news data, see [Using a news service with v2](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2migrate-to-v2-news).

COVID-19 kit
: This pre-built collection was designed to help you fuel a dynamic chatbot that is built with IBM Watson® Assistant and Discovery to answer your customers' questions about COVID-19. In v2, you can build a similar solution. Create a Conversational Search project type with collections that crawl trusted websites for answers to COVID-19 questions.







 Ingesting data 

To ingest v1 data into a Discovery v2 instance, complete the following steps:



1. Create a v2 service instance.
2. Create a project.
3. Add a collection to the project.



* Uploaded data:

From the API, you create a collection and add documents to it with two separate methods. Use the [Create a collection](https://cloud.ibm.com/apidocs/discovery-datacreatecollection) method to create the collection. Next, add the same source documents that you added to your v1 collection to the v2 collection. Use the [Add document](https://cloud.ibm.com/apidocs/discovery-dataadddocument) or [Update document](https://cloud.ibm.com/apidocs/discovery-dataupdatedocument) methods. To assign the same v1 document ID to the document as you add it to the v2 collection, append the document ID to the endpoint. For more information, see [Retaining document IDs](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2migrate-to-v2-keep-docid).
Enabling MFA security questions for a user 

As an Administrator on the IAM Identity Service or All IAM Account Management services, you can enable the multifactor authentication (MFA) option that prompts a user for security questions and answers at login. This type of legacy account-based MFA is required only for the account where the setting is enabled and is available only for accounts with classic infrastructure.

For more information about your MFA options, see [Types of multifactor authentication](https://cloud.ibm.com/docs/account?topic=account-types).



 Before you begin 

If you have any of the following types of access, you can update this setting for other users in your account:



* Administrator role on the IAM Identity Service or All IAM Account Management services
* You are an ancestor in the classic infrastructure hierarchy for the user and you have the Manage users classic infrastructure permission assigned



You can manage this setting for yourself if you have the User-managed login setting turned on in your User detials.

To turn on security questions for a user, they must first set up [security questions](https://cloud.ibm.com/docs/account?topic=account-questionssecurity-questions-setup) and answers.





 Setting up security questions 

Users can set up answers to three security questions for extra authentication at login. You must set up your security questions and answers before you or administrator can enable this MFA requirement for you.

To set up your security questions, complete the following steps:



1. From the console, go to Go to Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Profile and settings, and select Login settings.
2. In the Security questions seciton, click Set up.
3. Select the questions that you want to have and answer them. You must answer all three security questions.
4. Click Save when you're finished.



To update your security questions, click Edit.
For the parameters to set a region or endpoint, refer to the documentation for [Cloud Object Storage CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cli) or [AWS CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-aws-cli).





 How do I copy or move files to another bucket in a different location? 

Refer to [Move data between buckets](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-region-copy) for an example of how to use the rclone command line utility for copying data. If you use other 'sync' or 'clone' tools, be aware that you might need to implement a script to move files to a bucket in a different location because multiple endpoints are not allowed in a command.





 Other support options 



* If you have technical questions about Object Storage, post your question on [Stack Overflow](https://stackoverflow.com/search?q=object-storage+ibm) and tag your question with ibm and object-storage.
* For questions about the service and getting started instructions, use the [IBM Developer dW Answers forum](https://developer.ibm.com/answers/topics/objectstorage/). Include the objectstorage tag.







 Next Steps 

For more information about asking questions, see [Contacting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatarasking-a-question).

See [Getting help](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar) for more details about using the forums.

For more information about opening an IBM support ticket, see how to [create a request](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).
Getting started with Watson Discovery 

In this tutorial, we introduce IBM Watson® Discovery and walk you through the Discovery sample project. Exploring the sample project is a great way to tour and try out some of the product's features.



 Step 1: Open Watson Discovery 

IBM Cloud

These instructions apply to all managed deployments, including IBM Cloud Pak for Data as a Service instances.



1. Click the Discovery instance that you created to go to the service dashboard.
2. On the Manage page, click Launch Watson Discovery.

If you're prompted to log in, provide your IBM Cloud credentials.



IBM Cloud Pak for Data

These instructions apply to Discovery deployments:



1. From the IBM Cloud Pak for Data web client main menu, expand Services, and then click Instances.
2. Find your instance, and then click it to open its summary page.

You can create a maximum of 10 instances per deployment. After you reach the maximum number, the New instance button is not displayed in IBM Cloud Pak for Data.
3. Click Launch tool.







 Step 2: Open the sample project 

A new browser tab or window opens and the My Projects page is displayed.

Zoom

![Shows the main My Projects page with a single Sample Project tile.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-home-page.png)

Figure 1. My projects page of the Sample project

To get familiar with the product, you can watch an under 3-minute overview video by clicking the Watch a video link from the product home page.

In this tutorial, you explore the sample project.

The sample project is a built-in project that is provided as a resource for you to initially explore the product. The sample project is a Document Retrieval project type. Document Retrieval projects are used to search and find the most relevant answers from your data.



1. Click Sample Project.

The Improve and customize page is displayed.
iam_api_key: bmZrUHR1VS1fNVpMOExsTmIxeTdQcXFTSENMc2pTUjRsNTQyTzZkZ2ZQMkk= Prefixed field type using the iam name in Secrets Manager followed by the api_key default name.





 Updating secret fields 

Run the ingress secret update command to update a secret field's values. Note that this does not update the CRN. For more information and command options, see the [CLI reference](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_update).

ibmcloud ks ingress secret update --cluster example-cluster --name example-secret --namespace default





 Removing a secret field 

You can remove a secret field from a non-TLS secret. For more information and command options, see the [CLI reference](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_field_add).

ibmcloud ks ingress secret field rm -c example-cluster --name example-secret --namespace default --field-name example-Field

You can verify that the field is removed by checking the data block of the secret's details.

kubectl get secret -n default example-secret -o yaml









 Secrets FAQ 

Review the answers to commonly asked questions about managing secrets in your cluster.

Are my secrets automatically updated if I do not create and register a [Secrets Manager](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgr) instance?
: If you do not register a Secrets Manager instance to your cluster, your default Ingress secrets continue to update automatically every 90 days and are applied to your cluster. However, any secrets you created that reference the default Ingress secret are not automatically updated.
: Example scenario: You have a default Ingress certificate in the default namespace.
iam_api_key: bmZrUHR1VS1fNVpMOExsTmIxeTdQcXFTSENMc2pTUjRsNTQyTzZkZ2ZQMkk= Prefixed field type using the iam name in Secrets Manager followed by the api_key default name.





 Updating secret fields 

Run the ingress secret update command to update a secret field's values. Note that this does not update the CRN. For more information and command options, see the [CLI reference](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_secret_update).

ibmcloud oc ingress secret update --cluster example-cluster --name example-secret --namespace default





 Removing a secret field 

You can remove a secret field from a non-TLS secret. For more information and command options, see the [CLI reference](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_secret_field_add).

ibmcloud oc ingress secret field rm -c example-cluster --name example-secret --namespace default --field-name example-Field

You can verify that the field is removed by checking the data block of the secret's details.

kubectl get secret -n default example-secret -o yaml









 Secrets FAQ 

Review the answers to commonly asked questions about managing secrets in your cluster.

Are my secrets automatically updated if I do not create and register a [Secrets Manager](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgr) instance?
: If you do not register a Secrets Manager instance to your cluster, your default Ingress secrets continue to update automatically every 90 days and are applied to your cluster. However, any secrets you created that reference the default Ingress secret are not automatically updated.
: Example scenario: You have a default Ingress certificate in the default namespace.
To get familiar with the product, you can watch an under 3-minute overview video by clicking the Watch a video link from the product home page.

In this tutorial, you explore the sample project.

The sample project is a built-in project that is provided as a resource for you to initially explore the product. The sample project is a Document Retrieval project type. Document Retrieval projects are used to search and find the most relevant answers from your data.



1. Click Sample Project.

The Improve and customize page is displayed.

If you just installed Discovery, the Sample Project needs time to finish processing documents. Wait for processing to finish before you start experimenting. You can check the status of data processing from the Activity page, which is described in the next step.

Zoom

![Shows the Improve and customize page for the Sample Project.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-sample-project-improve.png)

Figure 2. Sample project Improve and customize page







 Step 3: Learn about the sample collection 

Learn about ways you can manage and enhance a collection by exploring the sample collection that is available with the sample project. The sample collection consists of a set of uploaded IBM Support PDF documents.



1. Click the Manage collections icon on the navigation panel.

Any collections in your project are displayed here. This project has only one collection.

Zoom

![Shows the collections page with the Sample Collection only.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-manage-collection.png)

Figure 3. Collections page in the Sample project
2. Click Sample Collection.

The Activity page is displayed. This page shows the status of the collection.