vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To view a list of VPN server routes for a VPN server by using the CLI, enter the following command:

ibmcloud is vpn-server-routes VPN_SERVER_ID [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]

Where:



* VPN_SERVER_ID: is the ID of the VPN server.
* --resource-group-id: is the ID of the resource group. This option is mutually exclusive with --resource-group-name.
* --resource-group-name: is the name of the resource group. This option is mutually exclusive with --resource-group-id.
* --all-resource-groups: queries all resource groups.
* --output: specifies output format, only JSON is supported. One of: JSON.
* -q, --quiet: suppresses verbose output.







 Deleting a route by using the CLI 

To delete a VPN server route by using the CLI, enter the following command:

ibmcloud is vpn-server-route-delete VPN_SERVER_ID (ROUTE_ID1 ROUTE_ID2 ...) [--output JSON] [-f, --force] [-q, --quiet]

Where:



* VPN_SERVER_ID: is the ID of the VPN server.
* ROUTE_ID1: is the ID of the VPN route.
* ROUTE_ID2: is the ID of the VPN route.
* --output: specifies output format, only JSON is supported. One of: JSON.
* --force, -f: forces the operation without confirmation.
* -q, --quiet: suppresses verbose output.







 Creating a route by using the API 

To create a VPN route on the VPN server by using the API, follow these steps:



1.
Prior to completing the steps in [Install and configure the PHP application on the application servers](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-highly-available-and-scalable-web-applicationhighly-available-and-scalable-web-application-php_application), first create the directory /mnt/www/ on both app servers. This directory was original created in the now removed file storage section.

mkdir /mnt/www



At the end of this step the load balancer should be in a healthy state and the Wordpress site accessible on the internet. The virtual servers making up the web application are protected from external access via the internet by the VRA firewall and the only access is via the load balancer. For a production environment DDoS protection and Web Application Firewall (WAF) should also be consider as provided by [IBM Cloud Internet Services](https://cloud.ibm.com/catalog/services/internet-services).





 Step 4: Remove resources 

Steps to take to remove the resources created in this tutorial.

The VRA is on a monthly paid plan. Cancellation does not result in a refund. It is suggested to only cancel if this VRA will not be required again in the next month.



1. Cancel any virtual servers or bare-metal servers
2. Cancel the VRA
3. [Cancel any additional VLANs](https://cloud.ibm.com/docs/vlans?topic=vlans-cancel-vlan)
4. Delete the Load Balancer
5. Delete the File Storage services







 Expand the tutorial 



1. In this tutorial only two virtual servers are initially provisioned as the app tier, more servers could be added automatically to handle additional load. [Auto Scale](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-auto-scale) provides you with the ability to automate the manual scaling process associated with adding or removing virtual servers to support your business applications.
2.
* Port: 443
* Back-end pool: POOL in the same region
* Choose the current region as your SSL region
* Choose the SSL certificate order name you just created for lb.example.com



4. Click Save to configure an HTTPS listener



Repeat the above steps in the load balancer of region 2.

In a browser open https://lb.example.com to verify success





 Failover test 

By now, you should have seen that most of the time you are accessing the servers in region 1 as it's assigned higher weight compared to the servers in region 2. Let's introduce a health check failure in the region 1 origin pool,



1. Navigate to the list of virtual server instances.
2. Click three dots(...) next to the server(s) running in zone 1 of region 1 and click Stop.
3. Repeat the same for server(s) running in zone 2 of region 1.
4. Return to GLB under CIS service and wait until the health status changes to Critical.
5. Now, when you refresh your domain url, you should always be hitting the servers in region 2.

Don't forget to start the servers in zone 1 and zone 2 of region 1.









 Step 7: Remove resources 



* Remove the global load balancer, origin pools and health checks under the CIS service
* Remove the certificates in the Secrets Manager service.
* Remove the load balancers, VSIs, subnets and VPCs.
* Under [Resource list](https://cloud.ibm.com/resources), delete the services used in this tutorial.







 Related content 



* [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [Using Load Balancers in IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb)
1. In the [IBM Cloud dashboard ![External link icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/launch-glyph.svg)](https://cloud.ibm.com), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Bare metal servers
2. Click the name of the bare metal server that you want to delete.
3. Click Actions..., then click Delete.



The delete action permanently removes a server and its connected vNIC, boot volume, and data from your account.







 Managing your bare metal server by using the CLI 



 Viewing your bare metal servers 

Use the following command to list all bare metal servers:

ibmcloud is bare-metal-servers [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups]

Use the following command to retrieve a bare metal server:

ibmcloud is bare-metal-server $bare_metal_server_id





 Rebooting a bare metal server 

Use the following CLI command to reboot your bare metal server.

ibmcloud is bare-metal-server-restart $bare_metal_server_id [-f, --force] [-q, --quiet]

The [-f, --force] flag forces the operation without confirmation.





 Stopping and starting a bare metal server 

Use the following CLI command to stop and start your bare metal server.

To stop the bare metal server:

ibmcloud is bare-metal-server-stop $bare_metal_server_id [--type soft | hard] [-f, --force] [-q, --quiet]

To start the bare metal server:
iamPolicyManagementService.listPolicies(params)
.then(res => {
console.log('listPolicies() result:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

The format of the response is represented in JSON.

{
"policies":
{
"id": examplePolicyId1,
"type": "access",
"subjects": ...],
"roles": ...],
"resources": ...],
...
"last_modified_at": "2021-04-09T14:36:30.505Z",
"last_modified_by_id": "IBMid-310000JVN5",
"last_permit_at": null,
"last_permit_frequency": 0,
"state": "deleted" <-- deleted policy
},
{
"id": examplePolicyId2,
"type": "access",
"subjects": ...],
"roles": ...],
"resources": ...] !!!,
...
"last_modified_at": "2019-05-09T15:28:07.045Z",
"last_modified_by_id": "IAM",
"last_permit_at": "2021-04-20T19:45:44.058Z",
"last_permit_frequency": 137,
"state": "deleted" <-- deleted policy
},
...
2. With the previously retrieved policy ID, you can restore the policy:
<-- <ul> -->

* Curl
* Java
* Python
* Go
* Node
* Run the application on multiple Virtual Servers for VPC and add a [load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb) to distribute inbound microservice traffic.







 Remove resources 



1. Navigate to [Schematics Workspaces](https://cloud.ibm.com/schematics/workspaces), click on your workspace
2. Click Actions... > Destroy resources
3. Click Actions... > Delete workspace







 Related content 



* [IBM Cloud CLI plugin for VPC Reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference)
* [VPC using the REST APIs](https://cloud.ibm.com/apidocs/vpc/latest)
* Solution tutorial: [Securely access remote instances with a bastion host](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-secure-management-bastion-server)
By now, you should have seen that most of the time you are accessing the servers in region 1 as it's assigned higher weight compared to the servers in region 2. Let's introduce a health check failure in the region 1 origin pool,



1. Navigate to the list of virtual server instances.
2. Click three dots(...) next to the server(s) running in zone 1 of region 1 and click Stop.
3. Repeat the same for server(s) running in zone 2 of region 1.
4. Return to GLB under CIS service and wait until the health status changes to Critical.
5. Now, when you refresh your domain url, you should always be hitting the servers in region 2.

Don't forget to start the servers in zone 1 and zone 2 of region 1.









 Step 7: Remove resources 



* Remove the global load balancer, origin pools and health checks under the CIS service
* Remove the certificates in the Secrets Manager service.
* Remove the load balancers, VSIs, subnets and VPCs.
* Under [Resource list](https://cloud.ibm.com/resources), delete the services used in this tutorial.







 Related content 



* [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [Using Load Balancers in IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb)
* [Getting started with IBM Cloud Internet Services](https://cloud.ibm.com/docs/cis?topic=cis-getting-started)
* [Getting started with Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-getting-started)
Delete all VPN gateways in the subnet, if any 

To list all VPN gateways in your account, run the following command:

curl -X GET "$rias_endpoint/v1/vpn_gateways?version=$version&generation=2" -H "Authorization:$iam_token"

Run the following command for each VPN gateway in the subnet that you want to delete, where $vpnid is the ID of the VPN gateway.

curl -X DELETE "$rias_endpoint/v1/vpn_gateways/$vpnid?version=$version&generation=2" 
-H "Authorization:$iam_token"

The status of the VPN gateway changes to deleting immediately, but it is still returned when you do a list query. The deletion of a VPN gateway can take up to 30 minutes. You can request other subnet resources to be deleted in parallel while you wait for the VPN gateway to be deleted. However, the subnet can't be deleted until the VPN gateway and all other resources in the subnet no longer appear in the list queries.





 Delete all load balancers in the subnet, if any 

To list all load balancers in your account, run the following command:

curl -X GET "$rias_endpoint/v1/load_balancers?version=$version&generation=2" 
-H "Authorization:$iam_token"

Run the following command for each load balancer in the subnet that you want to delete, where $lbid is the ID of the load balancer.

curl -X DELETE "$rias_endpoint/v1/load_balancers/$lbid?version=$version&generation=2" 
-H "Authorization:$iam_token"

The status of the load balancer changes to deleting immediately, but it is still returned when you do a list query. The deletion of a load balancer can take up to 30 minutes. You can request other subnet resources to be deleted in parallel while you wait for the load balancer to be deleted.
Why is the namespace where my storage operator was deployed stuck in Terminating status? 

 What’s happening 

When you remove a storage configuration from a cluster, the resources such as operator pods and storage classes are removed, but the namespace is stuck in Terminating status.

 Why it’s happening 

There are [finalizers](https://kubernetes.io/blog/2021/05/14/using-finalizers-to-control-deletion/) that are preventing the remaining resources in the namespace and the namespace itself from being deleted.

 How to fix it 

Take the following steps to remove the resources and the namespace.

Do not delete or patch the resource finalizers in the kube-system namespace.



1. Get the namespace that is stuck in Terminating status. Make a note of the resources that are listed in the message: 'Some resources are remaining: section.

oc get ns <namespace> -o yaml

Example output for a NetApp Trident namespace

status:
conditions:
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: All resources successfully discovered
reason: ResourcesDiscovered
status: "False"
type: NamespaceDeletionDiscoveryFailure
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: All legacy kube types successfully parsed
reason: ParsedGroupVersions
status: "False"
type: NamespaceDeletionGroupVersionParsingFailure
- lastTransitionTime: "2021-05-18T17:40:31Z"
message: All content successfully deleted, may be waiting on finalization
reason: ContentDeleted
status: "False"
type: NamespaceDeletionContentFailure
- lastTransitionTime: "2021-05-18T17:40:31Z"
The following table lists the actions that are related to client-to-site VPN servers and the generation of events.



Table 12. Actions that generate events for client-to-site VPN servers

 Resource Action Description 

 vpn is.vpn-server.vpn-server.create VPN server was created 
 vpn is.vpn-server.vpn-server.delete VPN server was deleted 
 vpn is.vpn-server.vpn-server.update VPN server was updated 
 vpn is.vpn-server.vpn-server.read VPN server was retrieved 
 vpn is.vpn-server.vpn-server.list VPN servers were listed 
 vpn is.vpn-server.vpn-server-configuration.read VPN server configuration was downloaded 
 vpn is.vpn-server.vpn-server-client.delete VPN client was disconnected and deleted from a VPN server 
 vpn is.vpn-server.vpn-server-client.read VPN client was retrieved from a VPN server 
 vpn is.vpn-server.vpn-server-client.list VPN server clients were listed 
 vpn is.vpn-server.vpn-server-client.disconnect VPN client was disconnected from a VPN server, and deleted according to the VPN server's auto-deletion policy 
 vpn is.vpn-server.vpn-server-route.create VPN server route was created 
 vpn is.vpn-server.vpn-server-route.delete VPN server route was deleted 
 vpn is.vpn-server.vpn-server-route.update VPN server route was updated 
 vpn is.vpn-server.vpn-server-route.read VPN server route was retrieved 
 vpn is.vpn-server.vpn-server-route.list VPN server routes were listed 









 Compute resources 

The following tables list the actions that are related to compute resources and the generation of events.



 Instance events 



Table 13. Actions that generate events for Instance

 Resource Action Description
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI
Don’t delete the bastion server or update its OS image after creation (Apply plan) because the bastion server is used to access other servers. If the Bastion server is removed, you lose access to your infrastructure. Get a snapshot of the bastion server for backup and recovery.





 Before you begin 



* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
* [Create or retrieve your SSH key name](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). The SSH key is used to SSH to the bastion server.
* Collect the information that you need to specify for the script parameters in the user inputs file:



 Component type Parameter values needed 

 User-specific information <br><br> * API key<br> * SSH key or keys<br> * Resource Group<br> * IP address or addresses<br> * Your local machine OS<br> * Prefix to add to resource names<br><br><br> 
 OS type for each server <br><br> * Bastion Server<br> * App Server<br> * Web Server<br> * Db Server<br><br><br> 
 Region Region where resources are deployed 
 Image ID to use for region VSIs <br><br> * Bastion Server<br> * App Server<br> * Web Server<br> * Db Server <br> Images are region-specific. To find the image IDs for your region, open the IBM Cloud shell and enter ibmcloud target -r < region_name > to set your region, then ibmcloud is images to see a list of images for that region.<br><br><br> 
 Load Balancer <br><br> * Domain Name<br> * Region Code<br><br><br>
Recovering a deleted database instance 

When a service instance is deleted, it is put in a suspend state for 7 days after which its removed. The deleted instance can be recovered within 7 days of deletion by following these steps.

The user must be logged into their IBMCloud account to be able to recover an instance.



 Listing instances available for recovery 

The following command list the deleted instances that are available for reclamation:

ibmcloud resource reclamations

Example:

>$ ibmcloud resource reclamations
List all resource reclamations
OK
ID Resource Instance ID Entity CRN State Target Time
835bdb40-b33b-43b4-a1f6-e234433334 d670d057-34c2-4430-8071-bafb0dfddse108 crn:v1:bluemix:public:dashdb-for-transactions:us-south:a/a8a1951114b2d2esddf59d2d01:d670d057-34c2-4430-8071-ba23443108:: SCHEDULED 2021-10-27T14:08:22Z





 Recovering the deleted the instance 

The following command will recover the deleted service instance:

ibmcloud resource reclamation-restore <ID>

Example:

>$ ibmcloud resource reclamation-restore "835bdb40-b33b-43b4-a1f6-e234433334"
Submitting request to restore resource reclamation 835bdb40-b33b-43b4-a1f6-e234433334 under account
OK
Request to restore reclamation 835bdb40-b33b-43b4-a1f6-e234433334 was submitted

Issuing a ibmcloud resource reclamations will now show the service instnace in a RESTORING state

Example:

>$ ibmcloud resource reclamations
List all resource reclamations
OK
ID Resource Instance ID Entity CRN State Target Time
For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan
2. Run terraform apply to create the resources that are defined in the plan.

terraform apply





For more information about the fields that are used to create dynamic rules, see [IAM condition properties](https://cloud.ibm.com/docs/account?topic=account-iam-condition-properties).





 Viewing dynamic members of access groups 

You can view the users that are added to an access group by using dynamic rules. To view dynamic members of access groups, go to Manage > Access (IAM) > Access groups in the IBM Cloud console. Select an access group and click Users. Dynamically added users are indicated by the type Dynamic.

The following users will not appear in the table:



* Dynamically added users who are not logged in yet
* Dynamically added users whose session expired



Dynamic users that are logged out but whose sessions are still valid continue to appear in the table until their sessions expire.

You can't remove a dynamic user manually. To remove a dynamic user, adjust your dynamic rules.



 Viewing a user's dynamic membership 

You can also view a list of access groups that a user is added to based on dynamic rules by completing the following steps:



1. Go to Manage > Access (IAM) > Users in the IBM Cloud console.
2. Click on a user.
3. Click Access.
4. The access groups that a user is a dynamic member of is indicated by the type Dynamic.
removeGroup [cluster-group rm](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-rm) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 







 Resources service access roles 



Actions that you can take with service access roles.

 Action API CLI None Reader Writer Deployer Manager 

 View Kubernetes resources that are managed by Satellite Config. resources calls [resource ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-resource-ls) <br>[resource get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-resource-get) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 



* You cannot scope access policies to a particular Satellite Config resource. Instead, scope the policy to the IBM Cloud Satellite service so that users can list Satellite Config resources.
Before you can remove a configuration, all associated subscriptions must be removed. To list the subscriptions that are associated with your configuration, run ibmcloud sat config get --config <configuration_name_or_ID>. If you remove a configuration, all versions of Kubernetes resources that you added to the configuration as versions are permanently removed. Make sure that you back up these resource definitions if you plan to use them later.

ibmcloud sat config rm --config CONFIG [-f] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Configuration resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name of your configuration that you want to remove. To list available configurations, run ibmcloud sat config ls.

-f
: Optional. Force the command to run with no user prompts.

--q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat config rm --config myapp_prod







 ibmcloud sat config version create 

Add a Kubernetes resource definition as a version to your Satellite configuration. You can later use the [ibmcloud sat subscription create](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-config-subscription-create) command to specify the clusters where you want to deploy the version.

ibmcloud sat config version create --name NAME --read-config FILEPATH --config CONFIG --file-format TYPE [--description DESCRIPTION] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Configuration resource in Satellite.