vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The file share must be in a stable or failed state (that is, when provisioning fails).

If the file share is configured for replication, you must take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete a mount target of a file share from the CLI 

Run the share-mount-target-delete command and specify the file share ID and mount target ID. To delete a mount target, the file share must be in a stable state.

ibmcloud is share-mount-target-delete <SHARE_ID> <MOUNT_TARGET_ID>





 Delete a file share from the CLI 

Run the share_delete command and specify the file share ID.

Before you can delete a file share, make sure that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-mount-target-cli). The file share must be in a stable or failed state (that is, when provisioning fails).

Also, if the file share has a replica file share, you must first remove the replication relationship. For more information, see [Remove the replication relationship in the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-cli).

ibmcloud is share-delete <SHARE_ID>









 Manage file shares and mount points with the API 

By using the API, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-file-share-api).
Do not reuse the same name for multiple locations, even after the other location is deleted. If you use the same name 5 times or more within 7 days, you might reach the Let's Encrypt [Duplicate Certificate rate limit](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_rate_limit).



 Manually creating locations from the console 

Use the Satellite console to create your location.

Before you begin:



* Make sure that you have the [correct permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iamiam-roles-usecases) to create locations. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).
* Satellite uses Object Storage to store data about your location and backups for your location's clusters. You can choose to have a bucket created automatically when you create your location or specify an existing bucket. If you want to use an existing bucket, it must have cross-regional resiliency. Do not delete your Object Storage instance or this bucket. If the service instance or bucket is deleted, your Satellite location control plane data cannot be backed up.





1. From the [Satellite console](https://cloud.ibm.com/satellite/locations), click Create location.
2. Click Advanced configuration.
3. In the Infrastructure type section, select On-premises or Public cloud. If your infrastructure is in a Public cloud, you can select your Cloud provider. Or, you can select Other cloud for a general setup.
4. In the Workflow section, select Manual.
5. If you selected a cloud provider, enter your credentials.
6. In the Satellite location section, review the following details. To change any of the default values, click Edit.



1. For Name: The Satellite location name must start with a letter, can contain letters, numbers, periods (.), and hyphen (-), and must be 35 characters or fewer.
For more information about the arguments and attributes, see [ibm_is_share_replica_operations](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/ibm_is_share_replica_operations).







 Deleting a replica file share 

The process for deleting a replica file share is similar to deleting a source file share. For example, you need to [delete mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-mount-target-api) for the share before you delete the share. Because the replica file share is in active replication from the source share, the replica file share must be split from the source before the deletion. You can do split the shares in two ways:



* Perform a manual split, which removes the replication relationship and creates two independent, read/write file shares. Then, you can delete the mount target and the replica file share as a normal file share.
* Delete the replica file share directly after you deleted the mount targets. A split process is automatically initiated in the background. After the split operation is finished, the replica file share is deleted.



You can use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-file-share-ui), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=clidelete-file-share-cli), [API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-file-share-api), or [Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=terraformdelete-file-share-terraform) to delete a file share.





 Activity tracker events for replication 

Activity tracker events are triggered when you establish and use file share replication.
Adding a rule would exceed the limit of rules per security group. The quotas per resource are specified in [Quotas and limits for VPC](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotassecurity-groups-quotas). Evaluate your strategy and consider creating another security group.





 security_group_sgs_per_interface_exceeded 

Message: Exceeded limit of security groups per interface.

Attaching this interface to another security group would exceed the limit of security groups per interface. The quotas per resource are specified in [Quotas and limits for VPC](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotassecurity-groups-quotas). Evaluate your strategy and consider adding rules to an existing security group.





 security_group_type_code_invalid_protocol 

Message: An 'icmp' type/code was given, but the requested protocol was not 'icmp'. Set the protocol to 'icmp' or specify a port range.

Only rules with an 'icmp' protocol have a type and code. Rules with 'tcp' or 'udp' protocols have a port range. For further information on security group rule configurations, refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).





 security_group_vpc_default 

Message: Cannot delete the default security group for a VPC.

The default security group cannot be deleted. For information on the default security group, refer to [Updating the default security group](https://cloud.ibm.com/docs/vpc-on-classic-network?topic=vpc-on-classic-network-updating-the-default-security-group).





 service_manager_service_failure 

Message: None

For further instructions to fix this problem, refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).
1. Create a configuration file to define your persistent volume claim (PVC). If you add your [IBM Cloud Object Storage credentials to the default storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_install), do not list your secret in the PVC.

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: <name> Enter the name of the PVC.
namespace: <namespace> Enter the namespace where you want to create the PVC. The PVC must be created in the same namespace where you created the Kubernetes secret for your service credentials and where you want to run your pod.
annotations:
ibm.io/auto-create-bucket: "<true_or_false>"
ibm.io/auto-delete-bucket: "<true_or_false>"
ibm.io/bucket: "<bucket_name>"
ibm.io/object-path: "<bucket_subdirectory>"
ibm.io/quota-limit: "true/false" Disable or enable a quota limit for your PVC. To use this annotation you must specify the -set quotaLimit=true option during installation.
ibm.io/endpoint: "https://<s3fs_service_endpoint>"
ibm.io/tls-cipher-suite: "default"
ibm.io/secret-name: "<secret_name>" The name of your Kubernetes secret that you created.
ibm.io/secret-namespace: "<secret-namespace>" By default, the COS plug-in searches for your secret in the same namespace where you create the PVC. If you created your secret in a namespace other than the namespace where you want to create your PVC, enter the namespace where you created your secret.
ibm.io/add-mount-param: "<option-1>,<option-2>" s3fs mount options
3. Keep the default Resource group.
4. The Region in which you created your subnets is already selected.
5. Optional: Tags. Enter tags to help you organize and find your resources. You can add more tags later. For more information, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag).
6. Paste the Public key, that you created according to [the guidelines mentioned in Securing Access](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-vs-gen2-netweaver-rhelquickstudy-vs-gen2-netweaver-rhel-secure-access).
7. Click Add SSH key.
8. Optional:User data, leave blank.







 Attaching a block storage volume 

To have file system space available beyond what is required by the operating system, you need to attach a block storage volume to your virtual server instance. This storage volume is used by the application that you're installing. In this example, the application is the Relational Database Management System (RDBMS) required for an SAP NetWeaver stack.



1. Click New volume.
2. Enter sap-app-vol1 for Name.
3. Select Custom for Profile.
4. Enter 500 for Size.
5. Enter 10000 for IOPS. Throughput defaults to 156.25 MiBps.
6. Keep the Encryption and Auto Delete defaults.



Zoom

![Figure 5. Attaching a block storage volume](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap//images/quickstudy-intel-vs-gen2-image10.png)

Figure 5. Attaching a block storage volume



1. Click Attach.
2. Keep the Network interfaces default.
3.
Optional If you don't want to reinstall ODF, you can [Remove the ODF add-on from your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-manage-deploymentocs-rm-cleanup-resources).







 Cleaning up your ODF deployment 

After you remove ODF from your apps, and remove your ODF storage cluster, you can clean up the remaining Kubernetes resources that were deployed with ODF.



 Cleaning up ODF 



1. Copy one of the following clean up scripts based on your ODF deployment.



* VPC or Satellite with dynamically provisioned disks Clean up the remaining Kubernetes resources from your cluster. Save the following script in a file called cleanup.sh to your local machine.

!/bin/bash
ocscluster_name=oc get ocscluster | awk 'NR==2 {print $1}'
oc delete ocscluster --all --wait=false
kubectl patch ocscluster/$ocscluster_name -p '{"metadata":{"finalizers":[]}}' --type=merge
oc delete ns openshift-storage --wait=false
sleep 20
kubectl -n openshift-storage patch persistentvolumeclaim/db-noobaa-db-0 -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephblockpool.ceph.rook.io/ocs-storagecluster-cephblockpool -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephcluster.ceph.rook.io/ocs-storagecluster-cephcluster -p '{"metadata":{"finalizers":[]}}' --type=merge
Deleting webhooks from a cluster 

Some troubleshooting and debugging steps might require you to temporarily remove certain webhooks from your cluster. Follow these steps to remove webhooks, then reapply them after you have resolved your issue.



1.  List the mutating webhooks in your cluster.

kubectl get mutatingwebhookconfigurations
2.  For each mutating webhook, copy the component YAML file and delete the webhook.



1.  Run the command to copy the YAML file. Save the YAML file so you can reapply it later.

kubectl get mutatingwebhookconfigurations <WEBHOOK-NAME> -o yaml > <WEBHOOK-NAME>.yml
2.  Delete the mutating webhook.

kubectl delete mutatingwebhookconfigurations <WEBHOOK-NAME>



3.  List the validating webhooks in your cluster.

kubectl get validatingwebhookconfigurations
4.  Identify any validating webhooks that are not included in the following list.



*  alertmanagerconfigs.openshift.io
*  managed-storage-validation-webhooks
*  multus.openshift.io
*  performance-addon-operator
*  prometheusrules.openshift.io
*  snapshot.storage.k8s.io



Any validating webhook that is included in this list should not be deleted in the following steps.
5.  For each validating webhook that is not included in the previous list, copy the component YAML file and delete the webhook.



1.  Run the command to copy the YAML file. Save the YAML file so you can reapply it later.

kubectl get validatingwebhookconfigurations <WEBHOOK-NAME> -o yaml > <WEBHOOK-NAME>.yml
2.  Delete the validating webhook.

kubectl delete validatingwebhookconfigurations <WEBHOOK-NAME>



6.  When you are done troubleshooting your worker node issue, reapply the webhook YAML files.

kubectl apply -f <webhook-yaml-file>
You can manage the list of authorized users only by using the console. For information about authorized user management, see [Authorized users](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage&interface=uiauthorized_users).
* Can I manage Continuous Delivery service instances by using an API?

You can use HTTP APIs or selected programming language SDKs to provision, update, and de-provision instances of the Continuous Delivery service. For more information about using Continuous Delivery with the API, see [Creating a Continuous Delivery service instance with the API](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-create_cd_service&interface=apicreate_cd_service_api) and [Deleting a Continuous Delivery service instance with the API](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-delete_cd_service&interface=apideleting_rg_api).

You cannot use APIs to manage the list of authorized users of a Continuous Delivery service instance. You can manage the list of authorized users only by using the console. For information about authorized user management, see [Authorized users](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage&interface=uiauthorized_users).
* Can I use the console, APIs, or CLI to modify resources that are managed by Terraform?

When you use Terraform to manage resources such as Continuous Delivery service instances, toolchains, and Tekton pipelines, avoid changing the resources by using the console, APIs, or CLI, or by any other method outside of Terraform's control.

If you circumvent Terraform by directly changing resources, you might cause [resource drift](https://developer.hashicorp.com/terraform/tutorials/state/resource-drift), a situation in which the states of your actual resources on IBM Cloud deviate from the definition of the resources in Terraform.
* UI
* CLI
* API







 Updating orgs and spaces 

As an IBM Cloud® account owner or Cloud Foundry organization manager, you can perform management tasks at the org level and the space level. These tasks include renaming an org or space, assigning or updating Cloud Foundry users' roles, managing domains, and viewing org quota details.

IBM Cloud Foundry Public is deprecated with an end-of-support date of 1 June 2023. For more information, see [Deprecation of IBM Cloud Foundry](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).



 Updating orgs and spaces in the console 

Go to Manage > Account in the IBM Cloud console, and select Cloud Foundry orgs.

You can view the resources of only one org at a time. If you are a member of multiple orgs, you can switch orgs from the user account preferences link in the console menu bar.



* To rename an org, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) for the org you want to rename, and select Rename.

Any changes that you make apply to all users in the org.
* To delete a space, select the org in which the space is assigned. Then, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg), and select Delete. When you delete a space, all included resources and users are also deleted.

You can delete spaces but not orgs.
* To repurpose an org, delete all spaces within the org and then rename it.
Create a configuration file to define your persistent volume claim (PVC). If you add your [IBM Cloud Object Storage credentials to the default storage classes](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install), do not list your secret in the PVC.

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: <name> Enter the name of the PVC.
namespace: <namespace> Enter the namespace where you want to create the PVC. The PVC must be created in the same namespace where you created the Kubernetes secret for your service credentials and where you want to run your pod.
annotations:
ibm.io/auto-create-bucket: "<true_or_false>"
ibm.io/auto-delete-bucket: "<true_or_false>"
ibm.io/bucket: "<bucket_name>"
ibm.io/object-path: "<bucket_subdirectory>"
ibm.io/quota-limit: "true/false" Disable or enable a quota limit for your PVC. To use this annotation you must specify the -set quotaLimit=true option during installation.
ibm.io/endpoint: "https://<s3fs_service_endpoint>"
ibm.io/tls-cipher-suite: "default"
ibm.io/secret-name: "<secret_name>" The name of your Kubernetes secret that you created.
ibm.io/secret-namespace: "<secret-namespace>" By default, the COS plug-in searches for your secret in the same namespace where you create the PVC. If you created your secret in a namespace other than the namespace where you want to create your PVC, enter the namespace where you created your secret.
ibm.io/add-mount-param: "<option-1>,<option-2>" s3fs mount options
A user of DevOps Insights is added to your Continuous Delivery authorized users. For more information, see [Authorized users](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usageauthorized_users).





 Can I manage DevOps Insights by using Terraform or APIs? 

You can use Terraform or APIs to add DevOps Insights to a toolchain or to remove it from a toolchain. For more information about working with the DevOps Insights tool integration, see [Working with tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations) and [Adding DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-dra).

You cannot use Terraform or APIs to manage DevOps Insights policies, rules, tags, or data. Instead, use the following methods to manage DevOps Insights policies, rules, tags, or data.



* Manage DevOps Insights policies and rules by using either the console or the ibmcloud CLI doi plug-in. Although you cannot delete policies by using the ibmcloud CLI doi plug-in, you can use the console to delete policies.
* Manage DevOps Insights tags only by using the console.
* Manage DevOps Insights data sets only by using the console. For more information about managing DevOps Insights data sets, see [Managing data sets](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-adding-data-sets).
* Publish test data to DevOps Insights by using the ibmcloud CLI doi plug-in. For more information about publishing test data, see [Publishing test data to DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-publishing-test-data).
* Explore build, environment, quality, deployment frequency, build frequency, and quality trend data only by using the console.
You can check the profile of the instance by launching [Cloud Shell](https://cloud.ibm.com/shell), changing the region to the one where you provisioned your VPC with ibmcloud target -r us-south command and then running ibmcloud is instances command or from [Virtual server instances for VPC](https://cloud.ibm.com/vpc-ext/compute/vs) UI by clicking on the dedicated instance name.







 Expand block storage volume capacity 



1. To expand the capacity of the attached block storage volume, navigate to the Settings tab of your Schematics workspace, update step5_resize_dedicated_instance_volume variable to true and Save the setting.
2. Apply the plan to increase the block storage volume capacity from 100 GB to 250 GB.
3. You can check the size of the Data volume from [Virtual server instances for VPC](https://cloud.ibm.com/vpc-ext/compute/vs) UI by clicking on the dedicated instance name.









 Step 6: What's next? 

Extend the scenario by configuring SSL termination, sticky sessions, and end-to-end encryption. For more information, refer to this [blog post](https://www.ibm.com/cloud/blog/deploy-and-auto-scale-isolated-workloads-across-multiple-zones).





 Step 7: Remove resources 

To remove the Schematics workspace and its resources, follow these steps:



1. Navigate to [Schematics](https://cloud.ibm.com/schematics/workspaces) workspaces and select your workspace.
2. Click on the Actions... drop down and click Destroy resources to clean up all the resources that were provisioned via Schematics.
3. Click on the Actions... drop down and click Delete workspace to delete the workspace.



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period.
You assign access to the specific access management tags for the file service. For more information about access groups, see [Setting up access groups](https://cloud.ibm.com/docs/account?topic=account-groups&interface=ui).
2. [Assign an access policy to a group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-assign-policy).
3. [Add users to the access group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-add-users-access-group).



When you look at the specific resources for the VPC infrastructure and specify File Storage for VPC as the resource type, you can see the access management tags for the file service.







 Manage file shares and mount targets from the CLI 

By using the CLI, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-file-share-cli).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-mount-target-cli).
* [Delete mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-mount-target-cli).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-file-share-cli).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-update-profile-cli)



As of 30 May 2023, you can use --mount-targets instead of --targets option.
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/bfb4a7c7-00d8-400b-98ba-5a67e5851970",
"id": "bfb4a7c7-00d8-400b-98ba-5a67e5851970",
"name": "Default"
},
"resource_type": "share",
"size": 100,
"mount_targets": [],
"zone": {
"href": "$vpc_api_endpoint/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}

The file share is deleted in background. Confirm the deletion by trying to view the mount target information. If you get _404 Not Found_ error, the mount target is successfully deleted.

A DELETE /shares/$share_id call can optionally include an If-Match header that specifies an ETag hash string. Make a GET /shares/{share_id} call and copy the ETag hash string from the response header. For more information, see [User tags for file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboufs-about-user-tags).









 Manage file shares and mount targets with Terraform 

With Terraform, you can:



* [Change file share attributes such as name, size, profile, tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifile-storage-share-update-terraform),