vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"boot_volume_attachment": {
"volume": {
"capacity": 250",
"encryption_key": {
"crn": "crn:[...]"
},
"name": "my-boot-volume",
"profile": {
"name": "general-purpose"
}
}
},
"image": {
"id": "9aaf3bcb-dcd7-4de7-bb60-24e39ff9d366"
},
.
.
.
}'
Show more

For more information, see [Create an instance](https://cloud.ibm.com/apidocs/vpccreate-instance) in the VPC API reference.





 Increasing capacity of an existing boot volume with the API 

With the API, locate the boot volume that you want to expand by making a GET volumes call. Then, make a PATCH volumes call with the ID of the boot volume and specify a new value for capacity.

For example, this call increases capacity of a boot volume to 250 GB.

curl -X PATCH "$vpc_api_endpoint/v1/volumes/$volume_id/?version=2022-02-12&generation=2" -H "Authorization: $iam_token" -d '{
"capacity": 250,
}'







 Next steps 

Create more volumes or manage your existing block storage volumes.



* [Creating block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage).
* [Managing block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage).



Optionally, [increase the capacity of your data volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes) that are attached to a virtual server instance.
[Review the Object Storage troubleshooting documentation for steps to resolve common errors](https://cloud.ibm.com/docs/containers?topic=containers-cs_sitemapsitemap_object_storage).







 Checking whether your PVC is successfully provisioned 

Follow the steps to check the status of your PVC and review any error messages.



1. Check the status of your PVC. A PVC is successfully provisioned if the PVC shows a status of Bound.

kubectl get pvc



* If the PVC shows a status of Bound, the PVC is successfully provisioned.

Example output

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
silver-pvc Bound pvc-4b881a6b-ada8-4a44-b568-fe909107d756 24Gi RWX ibmc-file-silver 7m29s
* If the status of the PVC shows Pending, describe the PVC and review the Events section of the output for any warnings or error messages. Note that PVCs that reference storage classes with the volume binding mode set to WaitForFirstConsumer remain Pending until an app pod is deployed that uses the PVC.

kubectl describe pvc <pvc_name>

Example output

Name: local-pvc
Namespace: default
StorageClass: sat-local-file-gold
Status: Pending
Volume:
Labels: <none>
Annotations: <none>
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ProvisioningFailed 60s (x42 over 11m) persistentvolume-controller storageclass.storage.k8s.io "sat-local-file-gold" not found



2.
"boot_volume_attachment": {
"volume": {
"id": "r006-feec3e99-995e-4e8f-896b-48b42c7d05a7"
}
},
"keys": [
{
"id": "363f6d70-0000-0001-0000-00000013b96c"
}
],
"name": "my-instance",
"placement_target": {
"id": "0787-8c2a09be-ee18-4af2-8ef4-6a6060732221"
},
"primary_network_interface": {
"name": "my-network-interface",
"subnet": {
"id": "bea6a632-5e13-42a4-b4b8-31dc877abfe4"
}
},
"profile": {
"name": "bx2-2x8"
},
"volume_attachments": [
{
"volume": {
"capacity": 1000,
"encryption_key": {
"crn": "crn:...]"
},
"name": "my-data-volume",
"profile": {
"name": "5iops-tier"
}
}
}
],
"vpc": {
"id": "f0aae929-7047-46d1-92e1-9102b07a7f6f"
},
"zone": {
"name": "us-south-1"
}
}'
Show more

For more information, see [Create an instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance).
IBM Cloud File Storage for Classic plug-in 338 342 The file storage plug-in is updated as follows:<br><br><br><br> * Supports dynamic provisioning with [volume topology-aware scheduling](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile-topology).<br> * Ignores persistent volume claim (PVC) delete errors if the storage is already deleted.<br> * Adds a failure message annotation to failed PVCs.<br> * Optimizes the storage provisioner controller's leader election and resync period settings, and increases the provisioning timeout from 30 minutes to 1 hour.<br> * Checks user permissions before starting the provisioning.<br><br><br> 
 Key Management Service provider 111 122 Added retry logic to avoid temporary failures when Kubernetes secrets are managed by IBM Key Protect for IBM Cloud. 
 Kubernetes v1.11.6 v1.11.7 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.11.7). 
 Kubernetes configuration N/A N/A The Kubernetes API server audit policy configuration is updated to include logging metadata for cluster-admin requests and logging the request body of workload create, update, and patch requests. 
 OpenVPN client 2.4.6-r3-IKS-8 2.4.6-r3-IKS-13 Updated image for [CVE-2018-0734](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0734) and [CVE-2018-5407](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5407). Additionally, the pod configuration is now obtained from a secret instead of from a configmap.
of Active Transactions 0
Replicant Count 0







 Viewing the LUN ID in VMWare® 



1. Run the esxcli storage vmfs extent list command. The output includes the volume name iscsi-datastore and its unique Network Addressing Authority (naa) identifier. That number is guaranteed to be unique to that LUN.

Volume Name VMFS UUID Extent Device Name Partition
Number
--------------- ----------------------------------- ------ ------------------------------------ ----
datastore1 5f69774e-f1031e44-7bdb-ac1f6bc4b812 0 naa.600062b2049d040026fc1e4b2f305682 3
iscsi-datastore 621f425f-0dc2da8a-927b-ac1f6bc4b812 0 naa.600a098038305674695d51694b427849 1
2. Next, enter the esxcfg-mpath -b command. The output contains the same naa number, the LUN ID, and the PortalTag.

naa.600a098038305674695d51694b427849 : NETAPP iSCSI Disk (naa.600a098038305674695d51694b427849)
vmhba64:C0:T1:L0 LUN:0 state:active iscsi Adapter: iqn.2020-10.com.ibm:sl02su1160157-h1907004
The following stateful set dynamically provisions Block Storage for VPC volumes by creating PVCs that use ibmc-vpc-block-5iops-tier storage class.



1. Save the following YAML configuration as a file on your local machine called statefulset.yaml.

apiVersion: v1
kind: Service
metadata:
name: nginx
labels:
app: nginx
spec:
ports:
- port: 80
name: web
clusterIP: None
selector:
app: nginx
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: web
spec:
serviceName: "nginx"
replicas: 2
podManagementPolicy: "Parallel"
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
securityContext:
privileged: false
image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: www
mountPath: /usr/share/nginx/html
tolerations:
- operator: Exists
volumeClaimTemplates:
- metadata:
annotations:
volume.beta.kubernetes.io/storage-class: ibmc-vpc-block-5iops-tier
name: www
spec:
accessModes:
- ReadWriteOnce access mode
resources:
requests:
storage: 25Gi 
Show more
2. Create the stateful set in your cluster.

kubectl create -f statefulset.yaml
3. Verify that the stateful set pods are running.

kubectl get pods

Example output

NAME READY STATUS RESTARTS AGE
web-0 1/1 Running 0 2m52s
app: nginx-v01 must match spec.template.metadata.labels and spec.selector.matchLabels in stateful set YAML
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: web-v01
namespace: default
spec:
selector:
matchLabels:
app: nginx-v01 must match spec.template.metadata.labels in stateful set YAML and metadata.labels in service YAML
serviceName: "nginx-v01"
replicas: 3
template:
metadata:
labels:
app: nginx-v01 must match spec.selector.matchLabels in stateful set YAML and metadata.labels in service YAML
spec:
terminationGracePeriodSeconds: 10
containers:
- name: nginx
image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: mypvc
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: mypvc
annotations:
ibm.io/auto-create-bucket: "false"
ibm.io/auto-delete-bucket: "false"
ibm.io/bucket: mybucket
ibm.io/secret-name: mysecret
volume.beta.kubernetes.io/storage-class: ibmc-s3fs-standard-perf-cross-region
volume.beta.kubernetes.io/storage-provisioner: ibm.io/ibmc-s3fs
spec:
accessModes: [ "ReadOnlyMany" ]
storageClassName: "ibmc-s3fs-standard-perf-cross-region"
resources:
requests:
storage: 1Gi
Show more



name
: Enter a name for your stateful set.
[Review the File Storage for Classic troubleshooting documentation for steps to resolve common errors](https://cloud.ibm.com/docs/openshift?topic=openshift-sitemapsitemap_file_storage).







 Checking whether your PVC is successfully provisioned. 

Follow the steps to check the status of your PVC and review any error messages.



1. Check the status of your PVC. A PVC is successfully provisioned if the PVC shows a status of Bound.

oc get pvc



* If the PVC shows a status of Bound, the PVC is successfully provisioned.

Example output

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
silver-pvc Bound pvc-4b881a6b-ada8-4a44-b568-fe909107d756 24Gi RWX ibmc-file-silver 7m29s
* If the status of the PVC shows Pending, describe the PVC and review the Events section of the output for any warnings or error messages. Note that PVCs that reference storage classes with the volume binding mode set to WaitForFirstConsumer remain Pending until an app pod is deployed that uses the PVC.

oc describe pvc <pvc_name>

Example output

Name: local-pvc
Namespace: default
StorageClass: sat-local-file-gold
Status: Pending
Volume:
Labels: <none>
Annotations: <none>
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ProvisioningFailed 60s (x42 over 11m) persistentvolume-controller storageclass.storage.k8s.io "sat-local-file-gold" not found



2.
Release notes 

The following new features and changes to IBM Watson® Knowledge Studio are available.



 May 2022 

Advanced Rules Editor (Beta) will be ending on 30 June 2022.
: The Advanced Rules Editor (ARE) (Beta) feature will end on 30 June 2022. Existing rules created in ARE workspaces can be edited and exported until that time. Any rules models that are exported can continue to be run in IBM Watson® Discovery or IBM Datacap after that date.

After 30 June 2022, Rules models can be created using the Knowledge Studio [Rules annotator](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-rule-annotator). You may also use Discovery; the creation of rules is provided by teaching Discovery to [recognize patterns in your data](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-domainpatterns).





 March 2020 

Enhanced pre-annotation workflow
: Run multiple pre-annotators at once and configure the order of pre-annotators to resolve annotation conflicts between them. Existing pre-annotator results are preserved unless you remove them with the Wipe option.
: Human annotations are preserved when running pre-annotators, even when using the Wipe option.





 December 2019 



 New features and changes 

New advanced rules tokenizer
: Advanced rules has introduced a new tokenizer which is not compatible with the previous one. The following extractor categories are affected:



* Parts of Speech extractor names are renamed automatically



* Cardinal is renamed to Numeral
* Preposition is renamed to Adposition



* Machine Data Analytics Splitter extractors have been removed and will disappear from the canvas. There is no substitute for these extractors that is provided by the new tokenizer.



* Generic Splitters:



* Date Time Splitter
* Day First Splitter
* Month First Splitter
* Year First Splitter



* Syslog Splitter:



* Date Time Splitter







: Cross-sentence relations (Experimental)
"name": "my-volume-attachment-1",
"volume": {
"crn": "crn:...]",
"id": "2cc091f5-4d46-48f3-99b7-3527ae3f4392",
"name": "my-data-volume"
}
}
],
"vpc": {
"crn": "crn:[...]",
"id": "f0aae929-7047-46d1-92e1-9102b07a7f6f",
"name": "my-vpc",
"resource_type": "vpc"
},
"zone": {
"name": "us-south-1"
}
}
Show more





 Extra instance metadata endpoints 

Table 1 shows more endpoints for API GET calls that you can make to get specific metadata for an instance. (The well-known URL is omitted in the list.)



Table 1. Instance metadata endpoints

 API endpoint Description 

 /metadata/v1/instance/network_interfaces List metadata for all network interfaces for an instance. 
 /metadata/v1/instance/network_interfaces/{id} Retrieve metadata for a network interface by ID. 
 /metadata/v1/instance/volume_attachments List metadata for all volume attachments for an instance. 
 /metadata/v1/instance/volume_attachment/{id} Retrieve metadata for a volume attachment by ID. 



For more information about these APIs, including required parameters and examples, see the [Metadata service API reference guide](https://cloud.ibm.com/apidocs/vpc-metadata).







 Retrieve metadata about SSH keys 

Make a GET "http://169.254.169.254/metadata/v1/keys" call to retrieve information about all SSH keys configured for the instance. The output is parsed by jq.
"id": "r006-feec3e99-995e-4e8f-896b-48b42c7d05a7"
}
},
"keys": [
{
"id": "363f6d70-0000-0001-0000-00000013b96c"
}
],
"name": "my-instance",
"placement_target": {
"id": "0787-8c2a09be-ee18-4af2-8ef4-6a6060732221"
},
"primary_network_interface": {
"name": "my-network-interface",
"subnet": {
"id": "bea6a632-5e13-42a4-b4b8-31dc877abfe4"
}
},
"profile": {
"name": "bx2-2x8"
},
"volume_attachments": [
{
"volume": {
"capacity": 1000,
"encryption_key": {
"crn": "crn:...]"
},
"name": "my-data-volume",
"profile": {
"name": "5iops-tier"
}
}
}
],
"vpc": {
"id": "f0aae929-7047-46d1-92e1-9102b07a7f6f"
},
"zone": {
"name": "us-south-1"
}
}'

For more information, see [Create an instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance).





 Restore a boot volume from a snapshot and use it to provision a new instance
The provider-managed encryption-at-rest feature is available for Block Storage for Classic in all IBM Cloud® [data centers](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-selectDC).

When you order Block Storage for Classic, select a data center noted with an asterisk (). You can see a lock icon to the right of the LUN/Volume Name field that indicates that the volume is encrypted.

Zoom

![Figure 1. Example of the lock icon that indicates that the LUN is encrypted.](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/encryptedstorage.svg)

FFigure 1. Example of the lock icon that indicates that the LUN is encrypted.

Nonencrypted storage that was provisioned before the data center was upgraded isn't automatically encrypted. If you own nonencrypted storage in an upgraded data center and you want encrypted storage, then you need to create a new volume and migrate your data. For more information, see [Block Storage for Classic Migration in Upgraded Data Centers](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-migratestorage).





 Deleting Block Storage for Classic instances 

If you no longer need a specific LUN, you can cancel it at any time. IBM Cloud® Block Storage for Classic presents Block volumes to customers on physical storage that is wiped before any reuse. For more information, see the [FAQs](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqsdeleted).

Customers with special requirements for compliance such as NIST 800-88 Guidelines for Media Sanitization can perform the data sanitization procedure before they delete their storage.

To delete a storage LUN, it's necessary to revoke access from any hosts first.
* UI
* CLI
* Terraform







 Connecting to iSCSI LUNs on Linux 

These instructions are mainly for mounting Block Storage for Classic on RHEL6 and CentOS6. Notes for other OS were added, but the topic does not cover all Linux® distributions. If you're using another Linux® operating system, refer to the Documentation of your specific distribution, and ensure that the multipath supports ALUA for path priority.

If multiple hosts mount the same Block Storage for Classic volume without being cooperatively managed, your data is at risk for corruption. Volume corruption can occur if changes are made to the volume by multiple hosts at the same time. You need a cluster-aware, shared-disk file system to prevent data loss such as Microsoft® Cluster Shared Volumes (CSV), Red Hat Global File System (GFS2), VMware® VMFS, and others. For more information, see your host's OS Documentation.

It's best to run storage traffic on a VLAN, which bypasses the firewall. Running storage traffic through software firewalls increases latency and adversely affects storage performance. For more information about routing storage traffic to its own VLAN interface, see the [FAQs](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqshowtoisolatedstorage).

Before you start, make sure the host that is accessing the IBM Cloud® Block Storage for Classic volume is authorized correctly.



 Authorizing the host in the UI 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/login). From the menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/icon_hamburger.svg), select Classic Infrastructure!
However, after the separation process is complete, the data can be manually refreshed by using another snapshot of the original parent volume.



For more information about duplicates, see [Creating and managing duplicate volumes](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-duplicatevolume).



Table 1. Comparison of features between different types of volume copies.
This table has row and column headers. The row headers identify the capability. The column headers identify the type of volume copy.

 Feature Replica Dependent duplicate Independent duplicate 

 Created from a snapshot ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Location of copied volume Remote Availability Zone Same Availability Zone Same Availability Zone 
 Supports failover ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Different Size and IOPS ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Auto-synced with parent volume ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 On-demand refresh from parent volume ![Checkmark icon.]
r014-158e904d-0d48-4090-b6c1-57617c1fcc20 csi-boot-vol-txmz-54wzen5m available 100 3000 general-purpose attached boot us-east-1 Default
r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac demo-volume-update available 100 3000 general-purpose attached data us-east-1 defaults
r014-eef16365-17e3-4627-bc8b-c7c3dd1d6a81 kj-test-ro-boot-1629867631000 available 100 3000 general-purpose attached boot us-east-1 defaults

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







 Viewing Block Storage for VPC volumes with the API 

View Block Storage for VPC volumes programmatically by making calls to the [VPC REST APIs](https://cloud.ibm.com/apidocs/vpc). You can list all volumes and view details for a specific volume.

Before you begin, make sure that you [set up your API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storageblock-storage-api-prereqs).



 Viewing all Block Storage for VPC volumes with the API 

Make a GET /volumes call to list summary information about all volumes. See the following example.

curl -X GET "$vpc_api_endpoint/v1/volumes?version=2022-12-09&generation=2" -H "Authorization: $iam_token"

A successful response looks like the following example. This example shows three data volumes. The first in the list is attached to an instance.

{
"first": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes?limit=50"
Unusable A volume is unusable because the customer root key (CRK) was [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managingbyok-delete-root-keys) or [disabled](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managingbyok-disable-root-keys). Inapplicable 







 Block storage volume health states 

Volume health states correspond with volume statuses. Table 2 describes the health states and health reasons.



Table 2. Block storage health states and reasons

 Health State Reason 

 OK A volume is performing at the expected I/O performance and capacity is sufficient. No network connection issues are present. Or the volume was restored from a snapshot (hydration is completed). 
 Degraded A volume is experiencing degraded performance for any of the following reasons:<br><br><br><br> * Volume data is being restored (hydrated) and the volume shows as degraded until hydration is completed.<br> * Volume initialization from a snapshot failed, and the volume hydration failed.<br> * Volume hydration is not started.<br> * Volume hydration is paused.<br> * Snapshot is in an unusable state.<br><br><br> 
 Inapplicable The volume is being created. The volume creation failed. The volume is pending, pending deletion, or unusable. No health reason is reported. 
 Faulted The volume is unreachable, inoperative, or entirely incapacitated. 



For more information about the health states and reason codes in the API, see the [API reference](https://cloud.ibm.com/apidocs/vpc/latestcreate-volume) for creating, listing, and updating volumes.





 Volume performance when you restore from a snapshot 

Boot and data volume performance is initially degraded when you restore them from a snapshot. During the restoration, your data is copied from IBM Cloud® Object Storage to Block Storage for VPC.
"source": "",
"revisions_checked": 12,
"continuous": true,
"doc_id": null,
"doc_write_failures": 0,
"docs_read": 12,
"target": "",
"type": "replication",
"updated_on": 1371118477,
"user": "username",
"checkpointed_source_seq": "61764-dskfjalsfjsalkfjssadjfhasdfkjhsdkfhsdkf",
"changes_pending": 1196,
"pid": "<0.9955.4120>",
"node": "dbcore@db7.meritage.cloudant.net",
"docs_written": 12,
"missing_revisions_found": 12,
"replication_id": "asfksdlfkjsadkfjsdalkfjas+continuous+create_target"
}
Show more





 Troubleshooting stuck tasks 



 Is a task stuck? 

For a one-off, non-continuous replication, where the source database isn't updated significantly during the replication, the changes_pending value shows how many documents remain to be processed. Therefore, the changes_pending value is good indicator of when the replication is likely to be finished.

For a continuous replication, you're more interested in how the number of documents processed changes over time, and whether the changes_pending value increases. If changes_pending increases, but revisions_checked stays constant for a while, the replication is probably stalled. If changes_pending increases, and revisions_checked also increases, these increases might indicate that the replication can't keep up with the volume of data added to, or updated in, the database.





 What to do about a stuck task? 

To resolve a stalled replication, you might have to [cancel the replication process](https://cloud.ibm.com/apidocs/cloudantdeletereplicationdocument) and start it again.