vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<xsd:annotation>
<xsd:documentation>The related item must not be used as a grouping item and must not be aggregated. This value is used for the item that represents the property of a level of a dimension.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="taxonomyFamilyType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="cNone"/>
<xsd:enumeration value="cDate"/>
<xsd:enumeration value="cYear"/>
<xsd:enumeration value="cQuarter"/>
<xsd:enumeration value="cSeason"/>
<xsd:enumeration value="cMonth"/>
<xsd:enumeration value="cWeek"/>
<xsd:enumeration value="cDay"/>
<xsd:enumeration value="cHour"/>
<xsd:enumeration value="cMinute"/>
<xsd:enumeration value="cSecond"/>
<xsd:enumeration value="cContinent"/>
<xsd:enumeration value="cSubContinent"/>
<xsd:enumeration value="cCountry"/>
<xsd:enumeration value="cRegion"/>
<xsd:enumeration value="cStateProvince"/>
<xsd:enumeration value="cCounty"/>
<xsd:enumeration value="cCity"/>
<xsd:enumeration value="cPostalCode"/>
<xsd:enumeration value="cStreetAddress"/>
--skipNUMBER_OF_ACTIONS, -s NUMBER_OF_ACTIONS
: Exclude a specified number of the most recently created actions from the result.





 Example 

ibmcloud fn action list







 ibmcloud fn action update 

Update an action or the app within an action.

When you update parameters for a package or action, you must specify all previously created parameters. Otherwise, the previously created parameters are removed. For packages, any services that were bound to the package are also removed, so after you update other parameters you must [bind services](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-services) to your package again.

ibmcloud fn action update ACTION_NAME APP_FILE [--annotation ANNOTATION_KEY ANNOTATION_VALUE] [--annotation-file FILE] [--copy] [--docker DOCKER_HUB_USERNAME/IMAGE_NAME] [--kind LANGUAGE] [--logsize LIMIT] [--main ENTRY_METHOD_NAME] [--memory MEMORY_LIMIT] [--native] [--param KEY VALUE] [--param-file FILE] [--sequence ACTION_NAME, ACTION_NAME] [--timeout LIMIT] [--web yes|true|raw|no|false] [--web-secure SECRET]



 Command options 

--annotationANNOTATION_KEYANNOTATION_VALUE, -aANNOTATION_KEYANNOTATION_VALUE
: Annotations are specified in a KEYVALUE format. To include more than one annotation, specify this option for each annotation. This flag is optional.

--annotation-fileFILE, -AFILE
: A JSON file that contains annotation in a KEYVALUE format. This flag is optional.

ACTION_NAME
: The name of the action. To include the action in a package, enter the name in the format PACKAGE_NAME/ACTION_NAME. This value is required.

APP_FILE
: The path to the app file or package to run as an action.
Two-level certificate authority hierarchy





 Three levels: Root CA and two subordinate CAs 

Use this option if your workload requires an additional layer between the root CA and lower-level CA operations. In this scenario, the middle subordinate CA is used only to sign subordinate CAs that issue leaf certificates to your apps.

Zoom

![The diagram shows a three-level hierarchy of certificates that begins with a root certificate authority in the first level.](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/certificate-hierarchy-3.svg)

Figure 3. Three-level certificate authority hierarchy







 Setting the depth of your CA hierarchy 

When you're creating a certificate authority in Secrets Manager, you can set the Maximum path length parameter to determine how many CA certificates can exist in its authority chain. This value enforces how many CA certificates can exist in the certification path of your CA.

Generally, you can configure a root CA that doesn't limit the number of subordinate CAs that it can create in its certification path. However, defining a maximum path length on subordinate CAs is an important security step to avoid misconfigured CAs. Depending on the placement of a subordinate CA in your hierarchy, make sure to specify a maximum path length so that its signing authority power is limited to only the intended depth.

Zoom

![The diagram shows a four-level hierarchy of certificates that begins with a root certificate authority in the first level.](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/max-path-length.svg)

Figure 3. Three-level certificate authority hierarchy

The maximum path length that you define does not include leaf certificates. In the previous example, the subordinate CA in level 4 can issue leaf certificates but is unable to have more CA certificates in its path.





 Choosing a validity period for your certificates
For more information, see [Regions and endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpointsendpoints).
* Regional: With this option, your data is replicated across multiple zones within one region. If you have workloads that are located in the same region, you see lower latency and better performance than in a cross-regional setup. The regional endpoint is automatically set by the ibm Helm plug-in that you installed earlier based on the location that your cluster is in. For example, if your cluster is in US South, then your storage classes were configured to use US South as the regional endpoint for your buckets. For more information, see [Regions and endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpointsendpoints).



4. Review the detailed IBM Cloud Object Storage bucket configuration for a storage class.

oc describe storageclass <storageclass_name>

Example output

Name: ibmc-s3fs-standard-cross-region
IsDefaultClass: No
Annotations: <none>
Provisioner: ibm.io/ibmc-s3fs
Parameters: ibm.io/chunk-size-mb=16,ibm.io/curl-debug=false,ibm.io/debug-level=warn,ibm.io/iam-endpoint=https://iam.bluemix.net,ibm.io/kernel-cache=true,ibm.io/multireq-max=20,ibm.io/object-store-endpoint=https://s3-api.dal-us-geo.objectstorage.service.networklayer.com,ibm.io/object-store-storage-class=us-standard,ibm.io/parallel-count=2,ibm.io/s3fs-fuse-retry-count=5,ibm.io/stat-cache-size=100000,ibm.io/tls-cipher-suite=AESGCM
AllowVolumeExpansion: <unset>
For example, if the aggregate rule for Q1_a is set to total, and the rule for q1_b is set to average, then if this query item is based on the expression (QI_a / QI_b)* 100, the aggregate is computed as: ( total(QI_a) / average( QI_b ) ) 100.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="count">
<xsd:annotation>
<xsd:documentation>Compute the number of the values of the group.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="countDistinct">
<xsd:annotation>
<xsd:documentation>Compute the number of distinct values in the group.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="countNonZero">
<xsd:annotation>
<xsd:documentation>Compute the number of the values of the group, excluding zero and NULL values.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="maximum">
<xsd:annotation>
<xsd:documentation>Compute the maximum value of the values of the group.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="median">
<xsd:annotation>
<xsd:documentation>Compute the median value of the values of the group.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="minimum">
<xsd:annotation>
To set the maximum number of requests that can be served through one keepalive connection, use the following Kubernetes ibm-k8s-controller-config configmap [field](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/keep-alive-requests).

keep-alive-requests: 100

The default value for keep-alive-requests in Kubernetes Ingress is 100, which is much less than the default value of 4096 in IBM Cloud Kubernetes Service Ingress. If you migrated your Ingress setup from IBM Cloud Kubernetes Service Ingress to Kubernetes Ingress, you might need to change keep-alive-requests to pass existing performance tests.





 Setting a maximum keepalive request timeout 

To set the maximum time that a keepalive connection stays open between the client and the ALB proxy server, use the following Kubernetes ibm-k8s-controller-config configmap [field](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/keep-alive).

keep-alive: 60





 Modifying how the ALB matches the request URI 

To modify the way the ALB matches the request URI against the app path, use the following Kubernetes Ingress resource [annotation](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/use-regex).

nginx.ingress.kubernetes.io/use-regex: "true"

For more info, see [this blog](https://kubernetes.github.io/ingress-nginx/user-guide/ingress-path-matching/ingress-path-matching).





 Adding custom location block configurations
The following terms have changed in the [experimental](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks-faqsexperimental) release:



Table 1. Terminology changes for IBM Cloud version

 Term in IBM Marketplace Term in IBM Cloud Notes 

 project workspace This term was changed because IBM Cloud also uses the term project 
 import and export upload and download The terms import and export are now referred to as upload and download when used in terms of documents and entity types. The term export is still used when referring to exporting a model to applications such as Watson Explorer. 



Experimental Cloud release documentation
: For the IBM Cloud [experimental](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks-faqsexperimental) release, some of the documentation task steps do not match the new interface. The documentation matches the interface in IBM Marketplace. The following table summarizes the navigation changes for the [experimental](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks-faqsexperimental) release:



Table 2. Navigation changes for IBM Cloud version

 Feature IBM Marketplace location IBM Cloud location 

 Annotator Component tab Main navigation No longer exists 
 Confusion Matrix table (from the Statistics tab) Annotator Component > Details Model Management > Performance > Detailed Statistics link 
 Dictionaries tab Main navigation Assets & Tools > Pre-annotators 
 Dictionary Mapping page Annotator Component Assets & Tools > Pre-annotators 
 Entity Types tab Type System Assets & Tools > Entity Types 
 Ground Truth Editor Human Annotation Document Annotation tab 
 Ground Truth Editor Settings tab Human Annotation Settings > Document Annotation Settings 
 Models, running and exporting Annotator Component Model Management > Versions 
 Rules tab Main navigation Document Annotation > Rules 
 Statistics tab Annotator Component > Details Model Management > Performance 
 Summary table (from the Statistics tab) Annotator Component > Details Model Management > Performance > Detailed Statistics link
: Enter the <statefulset_name> of your PVC name.

spec.replicas
: Enter the number of replicas that you want to create for your stateful set. The number of replicas must equal the number of PVCs that you created earlier.

If your PVCs are in different zones, don't include a region or zone label in your stateful set.
3. Verify that the PVCs are used in your stateful set replica pods by listing the pods in your cluster. Identify the pods that belong to your stateful set.

oc get pods
4. Verify that your existing PVC is mounted to your stateful set replica. Review the ClaimName in the Volumes section of your CLI output.

oc describe pod <pod_name>

Example output

Name: nginx-0
Namespace: default
Node: 10.xxx.xx.xxx/10.xxx.xx.xxx
Start Time: Fri, 05 Oct 2022 13:24:59 -0400
...
Volumes:
myvol:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: myvol-nginx-0
...









 Changing the size and IOPS of your existing storage device 

If you want to increase storage capacity or performance, you can modify your existing volume.

For questions about billing and to find the steps for how to use the IBM Cloud console to modify your storage, see [Expanding Block Storage capacity](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacityexpandingcapacity) and [Adjusting IOPS](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-adjustingIOPS). Updates that you make from the console are not reflected in the persistent volume (PV). To add this information to the PV, run oc patch pv <pv_name> and manually update the size and IOPS in the Labels and Annotation section of your PV.



1.
n3392fd peerc-statedb-pvc Bound pvc-e945df85-5a32-4d37-991d-b2be334bc09b 100Gi RWO ibmc-file-bronze 48d
n3392fd peerorg1ca-pvc Bound pvc-152be78e-202d-43a4-bcf7-81a6a9013c2d 20Gi RWO ibmc-file-bronze 49d
Show more

To get the details on a particular volume, issue:

kubectl describe pv <VOLUME>

If you are using the CLI to manage snapshots, you'll need the volumeId value. If you are using the cluster UI, you'll need the Username value. For an example volume named pvc-494ba122-3501-4413-b719-cbb4b3a8f91b, you would issue this command:

kubectl describe pv pvc-494ba122-3501-4413-b719-cbb4b3a8f91b

Which produces a list of details similar to this example:

Name: pvc-494ba122-3501-4413-b719-cbb4b3a8f91b
Labels: CapacityGb=100
Datacenter=dal10
Iops=2
StorageType=ENDURANCE
Username=IBM02SEV2046428_106
billingType=hourly
failure-domain.beta.kubernetes.io/region=us-south
failure-domain.beta.kubernetes.io/zone=dal10
path=IBM02SEV2046428_106data01
server=fsf-dal1002h-fz.adn.networklayer.com
volumeId=155617812
Annotations: ibmFileProvisionerIdentity: 44cc1a5f-b755-11ea-bfae-3692beefed97
failure-domain.beta.kubernetes.io/zone=dal10
path=IBM02SEV2046428_106data01
server=fsf-dal1002h-fz.adn.networklayer.com
volumeId=155617812
Annotations: ibmFileProvisionerIdentity: 44cc1a5f-b755-11ea-bfae-3692beefed97
pv.kubernetes.io/provisioned-by: ibm.io/ibmc-file
Finalizers: [kubernetes.io/pv-protection]
StorageClass: ibmc-file-bronze
Status: Bound
Claim: n3392fd/peera-statedb-pvc
Reclaim Policy: Delete
Access Modes: RWO
VolumeMode: Filesystem
Capacity: 100Gi
Node Affinity: <none>
Message:
Source:
Type: NFS (an NFS mount that lasts the lifetime of a pod)
Server: fsf-dal1002h-fz.adn.networklayer.com
Path: /IBM02SEV2046428_106/data01
ReadOnly: false
Events: <none>
Show more

You can then order snapshots for that volume, which can be done by using either the CLI or the cluster UI. For information on how to take the snapshot, see [Ordering Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-ordering-snapshots).

In this case, "ordering" refers to the "order to take snapshots" and not "ordering nodes".

For our example, we use the CLI and order a single snapshot by using 5 GB of space by issuing:

ibmcloud sl file snapshot-order 155617812 -s 5

You might need more or less than 5 GB of space, depending on the size of the pod and the resources that have been used on it.
runAsNonRoot: false
runAsUser: 0
privileged: false
resources:
limits:
cpu: 50m
memory: 50Mi
requests:
cpu: 5m
memory: 10Mi
volumeMounts:
- mountPath: /csi
name: plugin-dir
serviceAccountName: ibm-vpc-block-node-sa
tolerations:
- operator: Exists
volumes:
- hostPath:
path: /var/lib/kubelet/plugins_registry/
type: Directory
name: registration-dir
- hostPath:
path: /var/lib/kubelet
type: Directory
name: kubelet-data-dir
- hostPath:
path: /var/lib/kubelet/plugins/vpc.block.csi.ibm.io/
type: DirectoryOrCreate
name: plugin-dir
- hostPath:
path: /dev
type: Directory
name: device-dir
- hostPath:
path: /etc/udev
type: Directory
name: etcudevpath
- hostPath:
path: /run/udev
type: Directory
name: runudevpath
- hostPath:
path: /lib/udev
type: Directory
name: libudevpath
- hostPath:
path: /sys
type: Directory
name: syspath
- name: customer-auth
secret:
secretName: storage-secret-store
- configMap:
name: cluster-info
name: cluster-info
- apiVersion: apps/v1
kind: StatefulSet
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: ibm-vpc-block-csi-controller
namespace: kube-system
kubectl patch storageclass <storageclass> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

Replace <storageclass> with the name of your storage class.

After you deploy blockchain nodes to your cluster, you should not change the default storage class. This will result in losing the storage for the CAs, peers, and ordering nodes that are already deployed. Therefore, you need to decide on your storage before you deploy any blockchain nodes.

If you need to increase storage capacity of your cluster, see this information on how to modify your existing volume:



* [IBM File Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacity)
* [Portworx](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/create-pvcs/resize-pvc/)
* [Block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacityexpandingcapacity)









 Using Multizone (MZR) clusters with IBM Blockchain Platform 

In regions where it is offered, [multizone support](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions_multizone) is pre-selected by default when you create a standard Kubernetes cluster on IBM Cloud. Although not required, this capability provides for high availability of your nodes in case any one zone, or data center, goes down. If your cluster includes multizone support, you need to bring your own storage solution. You can choose from several [persistent storage options](https://cloud.ibm.com/docs/containers?topic=containers-storage_planningpersistent_storage_overview).

If you are setting up an IBM Blockchain Platform network in an MZR cluster and want your components to eventually fail over between data centers, you should select Portworx as your storage type.
For more information, see [Delete Pods](https://kubernetes.io/docs/tasks/run-application/force-delete-stateful-set-pod/delete-pods).

VolumeClaimTemplates.name
: In the spec volume claim templates metadata section, enter a name for your volume. Use the same name that you defined in the spec.containers.volumeMount.name section. The name that you enter here is used to create the name for your PVC in the format: <volume_name>-<statefulset_name>-<replica_number>.

ibm.io/auto-create-bucket
: In the spec volume claim templates metadata section, set an annotation to configure how buckets are created. Choose between the following options:



* true: Choose this option to automatically create a bucket for each stateful set replica. Note that the service credentials must have Writer permissions to automatically create the bucket.
* false: Choose this option if you want to share an existing bucket across your stateful set replicas. Make sure to define the name of the bucket in the spec.volumeClaimTemplates.metadata.annotions.ibm.io/bucket section of your stateful set YAML.



ibm.io/auto-delete-bucket
: In the spec volume claim templates metadata section, set an annotation to configure how buckets are deleted. Choose between the following options:



* true: Your data, the bucket, and the PV is automatically removed when you delete the PVC. Your IBM Cloud Object Storage service instance remains and is not deleted. If you choose to set this option to true, then you must set ibm.io/auto-create-bucket: true and ibm.io/bucket: ""so that your bucket is automatically created with a name with the format tmp-s3fs-xxxx.
* false: When you delete the PVC, the PV is deleted automatically, but your data and the bucket in your IBM Cloud Object Storage service instance remain. To access your data, you must create a new PVC with the name of your existing bucket.



ibm.io/bucket
You can [set up periodic snapshots for your block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-snapshotssnapshots), which is a read-only image that captures the state of the instance at a point in time.

To store the snapshot, you must request snapshot space on your block storage. Snapshots are stored on the existing storage instance within the same zone. You can restore data from a snapshot if a user accidentally removes important data from the volume. \n \n **To create a snapshot for your volume, complete the following steps.



1. [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
2. Log in to the ibmcloud sl CLI.

ibmcloud sl init
3. List existing PVs in your cluster.

kubectl get pv
4. Get the details for the PV for which you want to create snapshot space and note the volume ID, the size, and the IOPS. The size and IOPS are shown in the Labels section of your CLI output.

kubectl describe pv <pv_name>
5. To find the volume ID, review the ibm.io/network-storage-id annotation of your CLI output.
6. Create the snapshot size for your existing volume with the parameters that you retrieved in the previous step.

ibmcloud sl block snapshot-order <volume_ID> --size <size> --tier <iops>
7. Wait for the snapshot size to create. The snapshot size is successfully provisioned when the Snapshot Size (GB) in your CLI output changes from 0 to the size that you ordered.

ibmcloud sl block volume-detail <volume_ID>
8. Create the snapshot for your volume and note the ID of the snapshot that is created for you.
: In the spec volume claim templates spec section, enter the same storage class that you entered in the spec.volumeClaimTemplates.metadata.annotations.volume.beta.kubernetes.io/storage-class section of your stateful set YAML.

storage
: In the spec volume claim templates spec resource requests section, enter a fictitious size for your IBM Cloud Object Storage bucket in gigabytes. The size is required by Kubernetes, but not respected in IBM Cloud Object Storage. You can enter any size that you want. The actual space that you use in IBM Cloud Object Storage might be different and is billed based on the [pricing table](https://cloud.ibm.com/objectstorage/create).
Start Time: Fri, 05 Oct 2022 13:24:59 -0400
...
Volumes:
myvol:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: myvol-nginx-0
...









 Changing the size and IOPS of your existing storage device 

If you want to increase storage capacity or performance, you can modify your existing volume.

For questions about billing and to find the steps for how to use the IBM Cloud console to modify your storage, see [Expanding Block Storage capacity](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacityexpandingcapacity) and [Adjusting IOPS](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-adjustingIOPS). Updates that you make from the console are not reflected in the persistent volume (PV). To add this information to the PV, run kubectl patch pv <pv_name> and manually update the size and IOPS in the Labels and Annotation section of your PV.



1. List the PVCs in your cluster and note the name of the associated PV from the VOLUME column.

kubectl get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
myvol Bound pvc-01ac123a-123b-12c3-abcd-0a1234cb12d3 20Gi RWO ibmc-block-bronze 147d
2. If you want to change the IOPS and the size for your block storage, edit the IOPS in the metadata.labels.IOPS section of your PV first. You can increase or decrease the IOPS value. Make sure that you enter an IOPS that is supported for the storage type that you have. For example, if you have endurance block storage with 4 IOPS, you can change the IOPS to either 2 or 10.