vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing an instance template 

When you have an instance template created, you can view it to display its configuration details, duplicate it, delete it, or use it to create a virtual server instance.

To manage your instance template from the Instance templates for VPC page, complete the following steps.



1.  In the [IBM Cloud console](https://cloud.ibm.com/vpc-ext), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Auto scale > Instance templates.
2.  On the Instance templates for VPC page, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for the instance template that you want to manage and select from the options, Duplicate, Create virtual server, or Delete.
3.  To view the details of an instance template, click the name of the instance template to access the Instance template details page.





  Duplicating an instance template 

Duplicating an instance template makes a copy of the current settings and presents you with the New instance template page, with fields pre-populated. You can make any necessary changes and then create a new instance template based on the instance template that you duplicated.





  Creating a virtual server 

You can provision a virtual server instance directly from an instance template. This instance is not associated with any instance group for auto scaling. When you create a virtual server instance from an instance template, the instance is created with the configuration that is specified in the instance template.





  Deleting an instance template 

If you no longer need the instance template, you can delete the instance template to permanently remove it from your account.

An instance template that is specified in an instance group cannot be deleted.
* UI
* CLI
* API







 Managing virtual server instances 

Manage your IBM Cloud® Virtual Servers for Virtual Private Cloud instances by performing tasks such as start, stop, restart, and delete virtual server instances.



 Managing virtual server instances using the UI 

You can view and manage your IBM Cloud® Virtual Servers for Virtual Private Cloud instances from the Virtual server instances page in IBM Cloud console.

To manage your instances, complete the following steps.



1. In [IBM Cloud console](https://console.cloud.ibm.com), navigate to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. On the Virtual server instances page, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for the instance that you want to manage. You can select from the following actions:





Table 1. Actions available for virtual server instances

 Action Description 

 Rename Change the name of the instance. 
 Stop Stop the instance. 
 Start Start an instance that is stopped. This action is not available if the instance status is Running. 
 Reboot Immediately powers off a running instance and then powers it back on again. 
 Resize Vertically scale virtual server instances to any supported profile size. For more information, see [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance). 
 Delete To delete an instance, the instance must have a powered off status. If the instance has a floating IP address, it must be unassociated or released before the instance is deleted.
CIS CLI change log 

In this change log, you can learn about the latest changes, improvements, and updates for the IBM Cloud Internet Services CLI.



  Version 1.14.11 

Version 1.14.11 of the CLI was released on 16 March 2023.
:   Add URL normalization for domain setting.
:   Add certificate authority options.
:   Add universal CA options.
:   Add binary M1 and s390x support.
:   Fix origin certificate list issue.
:   Upgrade go dependency package versions.
:   Unhide standard plan for 45 days.





  Version 1.14.9 

Version 1.14.9 of the CLI was released on 27 October 2022.
:   Add authenticated origin pull list.
:   Enhance certificates order.
:   Add probe_zone option for glb monitor.





  Version 1.14.8 

Version 1.14.8 of the CLI was released on 26 Augest 2022.
:   Add new alert policies.
:   Enable Domain cname stetup.
:   Extend rate limit threshold range.





  Version 1.14.5 

Version 1.14.5 of the CLI was released on 09 Augest 2022.
:   Fix edge functions trigger.
:   Fix cross account resource access.
:   Add ppc64le binary release.
:   Page rule action remove always online.





  Version 1.14.4 

Version 1.14.4 of the CLI was released on 23 March 2022.
:   Add customer cert type.
:   Add domain security level setting.
:   Deprecate edge trigger disable option.
:   Support onion routing.





  Version 1.14.3 

Version 1.14.3 of the CLI was released on 8 March 2022.
:   Add session affinity attributes.





  Version 1.14.2 

Version 1.14.2 of the CLI was released on 1 March 2022.
:   Added Log Analysis instance support to the CLI for creating and configuring Logpush jobs.
:   Allow short aliases name cis for plugin install/upgrade/delete.
The service instance must be in the same IBM Cloud account as your cluster, but can be in a different resource group or region than your cluster. To create a service instance, follow the steps in [Provision an instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provision). This value is required.

--logdna-ingestion-key INGESTION_KEY
: The Log Analysis ingestion key that you want to use for your configuration. This value is optional. If you don't specify this option, the latest ingestion key is automatically retrieved.

--private-endpoint
: When you add this option to your command, the private cloud service endpoint is used to connect to IBM Log Analysis. To use the private cloud service endpoint, your cluster must be enabled for using private cloud service endpoints. For more information, see worker communication to other services and networks in [clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_basicsworker-services-onprem).

Example command

ibmcloud ob logging config create --cluster mycluster --instance mylogna





 ibmcloud ob logging config delete 

Virtual Private Cloud

Classic infrastructure

Delete a Log Analysis configuration from your cluster.

To remove logging configurations that you manually set up without using the Red Hat OpenShift on IBM Cloud observability plug-in, you must first make this configuration available to the plug-in by using the ibmcloud ob logging agent discover[command](https://cloud.ibm.com/docs/openshift?topic=openshift-observability_clilogging_agent_discover).

When you delete the logging configuration, the components that are deleted depend on how you created the logging configuration. For logging configurations that were created with the ibmcloud ob logging config create command, the daemon set for the Log Analysis agent, the ConfigMap, and secret are removed from your cluster, and pod logs are no longer sent to your IBM Log Analysis service instance.
The following steps show you how to delete a request by using HTTP.



1. Send a DELETE request with the document's most recent _rev in the query string by using HTTP.
2. Run the following command: DELETE /$DATABASE/$DOCUMENT_ID?rev=$REV HTTP/1.1.



The following code examples show you how to delete a document by using the command line.



* Curl
* Java
* Python
* Go
* Node



 make sure $JSON contains the correct _rev value!

curl -H "Authorization: Bearer $API_BEARER_TOKEN" -X DELETE "$SERVICE_URL/events/0007241142412418284?rev=2-9a0d1cd9f40472509e9aac6461837367"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.DeleteDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;

Cloudant service = Cloudant.newInstance();

DeleteDocumentOptions documentOptions =
new DeleteDocumentOptions.Builder()
.db("events")
.docId("0007241142412418284")
.rev("2-9a0d1cd9f40472509e9aac6461837367")
.build();

DocumentResult response =
service.deleteDocument(documentOptions).execute()
.getResult();

System.out.println(response);

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.delete_document(
db='events',
doc_id='0007241142412418284',
Kubernetes cluster instance Resource Editor us-south This policy is required to delete and configure the secret and the logging agent in the Kubernetes cluster. 



For more information about the IBM Cloud® Kubernetes Service IAM roles, see [User access permissions](https://cloud.ibm.com/docs/containers?topic=containers-access_referenceaccess_reference).

Install the IBM Cloud CLI and the Kubernetes CLI plug-in. For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).





 Step 1: Reset the ingestion key 

To renew the ingestion key for an IBM Log Analysis instance by using the IBM Log Analysis Web UI, complete the following steps:



1. [Launch the IBM Log Analysis web UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step2).
2. Click the Settings icon ![Settings icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/admin.png).
3. Select Organization.
4. Select API keys.

You can see the ingestion keys that have been created.
5. Select Generate Ingestion Key.

A new key is added to the list.
6. Delete the old ingestion key. Click the X next to the ingestion key to be deleted.







 Step 2: Remove any configuration in the cluster that uses the old ingestion key 

Complete the following steps:



1. Open a terminal. Then, log in to the IBM Cloud. Run the following command and follow the prompts:

ibmcloud login -a cloud.ibm.com
Removing a permitted network using the API 

To remove a permitted network from your linked zone using the API, follow these steps:



1. Set up your API environment with the correct variables.
2. Store the following values in variables to be used in the API command:



* INSTANCE_ID, which is the unique identifier of a service instance.
* LINKED_DNSZONE_ID which is the unique identifier of a linked zone.
* PERMITTED_NETWORK_ID which is the unique identifier of a permitted network
* IAM_TOKEN, which is the IAM authorization token.



3. When all variables are initiated, remove the permitted network:

curl -X DELETE https://api.dns-svcs.cloud.ibm.com/v1/instances/$INSTANCE_ID/linked_dnszones/$LINKED_DNSZONE_ID/permitted_networks/$PERMITTED_NETWORK_ID -H "Authorization: $IAM_TOKEN"
The service instance must be in the same IBM Cloud account as your cluster, but can be in a different resource group or region than your cluster. To create a service instance, follow the steps in [Provision an instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provision). This value is required.

--logdna-ingestion-key INGESTION_KEY
: The Log Analysis ingestion key that you want to use for your configuration. This value is optional. If you don't specify this option, the latest ingestion key is automatically retrieved.

--private-endpoint
: When you add this option to your command, the private cloud service endpoint is used to connect to IBM Log Analysis. To use the private cloud service endpoint, your cluster must be enabled for using private cloud service endpoints. For more information, see worker communication to other services and networks for [classic](https://cloud.ibm.com/docs/containers?topic=containers-plan_vpc_basicsvpc-worker-services-onprem) and [VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsworker-services-onprem).

Example command

ibmcloud ob logging config create --cluster mycluster --instance mylogna





 ibmcloud ob logging config delete 

Virtual Private Cloud

Classic infrastructure

Delete a Log Analysis configuration from your cluster.

To remove logging configurations that you manually set up without using the IBM Cloud Kubernetes Service observability plug-in, you must first make this configuration available to the plug-in by using the ibmcloud ob logging agent discover[command](https://cloud.ibm.com/docs/containers?topic=containers-observability_clilogging_agent_discover).

When you delete the logging configuration, the components that are deleted depend on how you created the logging configuration.
curl -X DELETE 'https://iam.cloud.ibm.com/v1/policies/$POLICY_ID' -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json'

DeletePolicyOptions options = new DeletePolicyOptions.Builder()
.policyId(examplePolicyId)
.build();

service.deletePolicy(options).execute();

response = iam_policy_management_service.delete_policy(
policy_id=example_policy_id
).get_result()

print(json.dumps(response, indent=2))

options := iamPolicyManagementService.NewDeletePolicyOptions(
examplePolicyID,
)

response, err := iamPolicyManagementService.DeletePolicy(options)
if err != nil {
panic(err)
}

const params = {
policyId: examplePolicyId,
};

iamPolicyManagementService.deletePolicy(params)
.then(res => {
console.log(JSON.stringify(res, null, 2));
})
.catch(err => {
console.warn(err)
});

A policy cannot be deleted if the subject ID contains a locked service ID.





 Reviewing assigned access in the console 

If you need to review your assigned access in an account that you've been added to, complete the following steps:



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users or Service IDs, depending on which identity you want to review.
2. Select your name or the service ID.
3. Review the assigned access in the Access tab.



If you need more access, you must contact the account owner to update your access or contact the administrator for the service or service instance to update the access policy.





 Reviewing assigned access by using the CLI
You can follow these steps to delete the Schematics Blueprints by using IBM Cloud console.



1. From the [Blueprints dashboard](https://cloud.ibm.com/schematics/blueprints). Click the name of the blueprint that you want to delete.
2. Select the Actions drop down list.
3. Select Delete blueprint option.
4. Type your <blueprint name> in Delete blueprint text box.
5. Click Delete blueprint button.





 Verifying blueprint config deletion 



1. From the [IBM Cloud Blueprints dashboard](https://cloud.ibm.com/schematics/blueprints), see that the deleted blueprint is not displayed.









 Deleting a blueprint config using the API 

Follow the [steps](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-apics_api) to retrieve your IAM access token and authenticate with IBM Cloud Schematics by using the API. For more information, see [Delete a blueprint config](https://cloud.ibm.com/apidocs/schematics/schematicsdelete-blueprint) by using API.

You need to run blueprint destroy command and then run blueprint delete command. For more information, see [Deleting a blueprint](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-blueprint) configuration.

Record the blueprint ID that needs to be deleted. To list the blueprint ID, run [get all the blueprint instances](https://cloud.ibm.com/apidocs/schematics/schematicslist-blueprint) command.

Example

POST /v2/jobs/ HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
Authorization: Bearer <auth_token>
refresh_token: <refresh_token>
{
Run the px_cleanup.sh script to remove the DaemonSet from your cluster.

sh ./px_cleanup.sh







 Removing Portworx from your cluster 

If you don't want to use Portworx in your cluster, you can uninstall the Helm chart and delete your Portworx instance.

The following steps walk you through deleting the Portworx Helm chart from your cluster and deleting your Portworx instance. If you want to clean up your Portworx installation by removing your volumes from your apps, removing individual worker nodes from Portworx, or if you want to completely remove Portworx and all your volumes and data, see [Cleaning up your Portworx cluster](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_removing).

The following commands result in data loss.



1. Follow the steps to [uninstall Portworx](https://docs.portworx.com/portworx-install-with-kubernetes/operate-and-maintain-on-kubernetes/uninstall/uninstall/delete-wipe-px-cluster-configuration). Note that for private clusters, you must specify the px-node-wiper image from the private icr.io registry.

curl -fSsL https://install.portworx.com/px-wipe | bash -s -- --talismanimage icr.io/ext/portworx/talisman --talismantag 1.1.0 --wiperimage icr.io/ext/portworx/px-node-wiper --wipertag 2.5.0
2. Find the installation name of your Portworx Helm chart.

helm ls -A | grep portworx

Example output

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
<release_name> <namespace> 1 2020-01-27 09:18:33.046018 -0500 EST deployed portworx-1.0.0 default
Debugging IBM Cloud Object Storage failures 

Review the options to debug Object Storage and find the root causes of any failures.



 Checking whether the pod that mounts your storage instance is successfully deployed 

Follow the steps to review any error messages related to pod deployment.



1. List the pods in your cluster. A pod is successfully deployed if the pod shows a status of Running.

kubectl get pods
2. Get the details of your pod and review any error messages that are displayed in the Events section of your CLI output.

kubectl describe pod <pod_name>
3. Retrieve the logs for your pod and review any error messages.

kubectl logs <pod_name>
4. [Review the Object Storage troubleshooting documentation for steps to resolve common errors](https://cloud.ibm.com/docs/containers?topic=containers-cs_sitemapsitemap_object_storage).







 Restarting your app pod 

Some issues can be resolved by restarting and redeploying your pods. Follow the steps to redeploy a specific pod.



1. If your pod is part of a deployment, delete the pod and let the deployment rebuild it. If your pod is not part of a deployment, delete the pod and reapply your pod configuration file.



1. Delete the pod.

kubectl delete pod <pod_name>

Example output

pod "nginx" deleted
2. Reapply the configuration file to redeploy the pod.

kubectl apply -f <app.yaml>

Example output

pod/nginx created



2. If restarting your pod does not resolve the issue, [reload your worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload).
3. Verify that you use the latest IBM Cloud and IBM Cloud Kubernetes Service plug-in version.

ibmcloud update

ibmcloud plugin repo-plugins
: Delete the application and wait for the application to be deleted. If you specify the --wait option, the application delete waits for a maximum time in seconds, as set by the --wait-timeout option, for the application to become deleted. If the application is not deleted within the specified --wait-timeout period, the application delete fails. This value is optional. The default value is false.

--wait-timeout, --wto
: The length of time in seconds to wait for the application to be deleted. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

ibmcloud ce application delete --name myapp -f





 Example output 

Deleted application 'myapp'







 ibmcloud ce application events 

Display the events of application instances.

ibmcloud ce application events (--instance APP_INSTANCE | --application APP_NAME) [--output OUTPUT] [--quiet]



 Command Options 

--application, --app, -a, --name, -n
: Display the events of all the instances of the specified application. This value is required if --instance is not specified.

--instance, -i
: The name of a specific application instance. Use the app get command to find the instance name. This value is required if --application is not specified.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

The following example displays the system event information for all the instances of a specified application.

ibmcloud ce application events --application myapp



 Example output
Click Create.







 Updating or deleting a shared processor pool 

To update or delete an SPP, navigate to Compute > Shared processor pools. Then select the SPP that you want to edit and click on the edit icon. You will get a notification after the SPP is deleted successfully.

You can update or delete the following details of an existing SPP:



* Name of the SPP - Follow the same naming conventions that you used while creating an SPP. For more information, see [Creating a shared processor pool](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-shared-processor-poolcreate-spp).
* Number of cores - You can update the number of reserved cores based on resource availability and allocation.
* Delete an existing SPP - You can delete any existing SPP. Before deleting, ensure that no virtual server instances exist in the SPP. If virtual server instances are present, it must be deleted or moved with a support ticket.









 Managing a virtual server instance of a shared processor pool 

When you deploy a virtual server instance, you can choose an SPP instead of a host. As you cannot move a virtual server instance into or out of an SPP, you can deploy a virtual server instance directly into an SPP as a best practice. You can also deploy a virtual server instance into a server placement group; the selected SPP host must be compatible with the affinity policy of the placement group that you selected.

When you deploy multiple virtual server instances simultaneously, a new server placement group is created automatically.

During any planned maintenance activity or when you want to perform a remote restart operation, ensure that the virtual server instances are linked to an SPP based on your requirements.



 Deploying a virtual server instance into a shared processor pool 

To add virtual server instances to an exsiting SPP, complete the following steps:



1. Go to Virtual server instances in the Power Systems Virtual Server user interface under Compute.
2. Click Create instance.
3. Complete the input fields under the General tile based on your requirement.
4. Select the checkbox Add to a Shared processor pool.
5. Select an existing shared processor pool.
6.
If you want to cancel all replications and start with a new, clean _replicator database, delete then re-create the replicator database.

See the following HTTP to remove and re-create the _replicator database:

DELETE /_replicator HTTP/1.1
HOST: $SERVICE_URL
Authorization: ...

PUT /_replicator HTTP/1.1
HOST: $SERVICE_URL
Authorization: ...



 Delete the replicator database 

See the following example to remove the _replicator database:



* Curl
* Java
* Node
* Python
* Go



curl -X DELETE "$SERVICE_URL/_replicator"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.DeleteDatabaseOptions;
import com.ibm.cloud.cloudant.v1.model.Ok;

Cloudant service = Cloudant.newInstance();

DeleteDatabaseOptions deleteDatabaseOptions = new DeleteDatabaseOptions.Builder()
.db("_replicator")
.build();

Ok response = service.deleteDatabase(deleteDatabaseOptions).execute()
.getResult();

System.out.println(response);

const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

service.deleteDatabase({db: '_replicator'}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.delete_database(db='_replicator').get_result()

print(response)

deleteDatabaseOptions := service.NewDeleteDatabaseOptions(
"_replicator",
)