vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you have an issue that has a Public Cloud Security Exception (PCE), you can change its due date to be the same as the expiration date of the PCE so that evidence collection continues up to the PCE expiration date.







 Slack alerts for pending and overdue issues for CC pipeline 

The Continuous Compliance (CC) pipeline can set due dates for the incident issues. The pipeline can also notify users about issues that have approaching due dates and overdue due dates by using Slack, if Slack integration is enabled.

For more information, see [Set up a Continuous Integration (CI) toolchain](https://cloud.ibm.com/docs/devsecops?topic=devsecops-tutorial-ci-toolchaintutorial-ci-toolchain-slack). For more information about due dates, see [Incident issues with due date](/docs/devsecops?topic=devsecops-incident-issuesdevsecops-devsecops-issues-due-date.

The issues that are notified are classified as follows:



* Issues having pending due dates within a specific timeframe: issues that are open, have due dates, and are due within a timeframe.
* Issues having past due dates: issues that are open, have due dates, and the date is passed.



The timeframe durations are overdue, due in 1 day, due in 2 days, due in 5 days, and due in 10 days.

An example of this capability is as follows:

Overdue issues:
- <issue url1>
- <issue url2>
- <issue url3>

Issues due in 1 day:
- <issue url4>

Issues due in 2 days:
- <issue url5>

Issues due in 5 days:
- <issue url6>
- <issue url7>

Issues due in 10 days
- <issue url8>
- <issue url9>
- <issue url10>
- <issue url11>
- <issue url12>
Show more
4. Sort, filter, or search in your spreadsheet to view the cases for a specific user.







 Can I create a support case if my account was deactivated? 

If your account is deactivated, you have 30 days to log in to the console and [create a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui). If you can't access your account, you can create a support case by completing the [Create an Account, Login or Billing Request](https://watson.service-now.com/x_ibmwc_open_case_app.do!/create) form.





 Do watchlists apply account-wide or to a specific case? 

Watchlists are specific to each case. You must manually add a user to each individual case. You can't configure an account to have a list of users that are added to the watchlist for all cases.
If the volume group is in an error state, you can use the volume-group action API to reset the volume group status for availability.
* When you delete a volume from a site, the replicated volume that is managed on its corresponding remote site moves to error state in an interval of 24 hours.
* When the volume is resized from a site, the replicated-enabled volume on its corresponding remote site is also resized after an interval of 24 hours.
* When you perform any operation on a volume that is deleted, it fails.







 Best practices for Global replication service 



* You must set the bootable flag explicitly on onboarded volumes, if required.
* Start the onboarding of auxiliary volumes only when the master volumes and volume-group are in consistent copying state.
* When you add or remove a master or auxiliary volume from a volume-group from one site, you must perform the same operation from other site to keep the data is in sync.
* You must delete the volumes from primary and secondary site. Volumes are charged when you delete auxiliary volume but fail to delete the master volume.
* You must use primary site for all the volume operations and perform operations on auxiliary volume on secondary site only during failover.
* Lock user accounts for 30 minutes after more than three unsuccessful logon attempts. When the lockout period ends, the user can reset their password. Internal privileged accounts must remain locked until they are released by an administrator.
* Set sessions to time out after 15 minutes of inactivity.



3. [Generate a service credential](https://cloud.ibm.com/docs/account?topic=account-service_credentials) with the role of Reader.
4. From your App ID service dashboard, click Manage Authentication > Authentication Settings and add the [web direct URLs](https://cloud.ibm.com/docs/appid?topic=appid-managing-idpadd-redirect-uri) of https://<virtual server instance FQDN>:3080/v1/webapi/oidc/callback.







 Step 3: Provision virtual server instances for Teleport Enterprise 



1. [Provision a virtual server instance](https://cloud.ibm.com/vpc-ext/compute/vs) within each zone of the VPC cluster.



* Profile: cx2-4x8 with 4 vCPUs, 8 GB RAM, 8 Gbps.
* Linux-based operating system (CentOS, Debian, RHEL, Ubuntu).



2. If your identity provider is hosted publicly and not accessible directly from the Teleport virtual server instance in the VPC, you must [provision a public gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpcexternal-connectivity).
3. Register each virtual server instance that you plan to run Teleport into a Domain Name Server.
4. Generate an SSL certificate for each of the provisioned virtual server instances or use a wildcard certificate.







 Step 4: Configure a security group for your virtual server instances 

[Configure the Security group](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups) for your virtual server instances.

Security group inbound rules
Checking vSRX readiness 

A readiness check verifies the ability of your IBM Cloud® Juniper vSRX to perform certain gateway actions. They include:



* OS reloads
* License upgrades
* Version upgrades



After you run the readiness check, errors alert you to any necessary actions that you should take before beginning one of these actions, or inform you that you're ready to proceed.

To run a readiness check, perform the following procedure:



1. From your browser, open [https://cloud.ibm.com](https://cloud.ibm.com) and log into your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click Classic Infrastructure.
3. Choose Network > Gateway Appliances.
4. Click the name of the vSRX you want to run a readiness check on.
5. Find the Readiness Check module on the vSRX details page.
6. Click the Run check button.
7. Select one of the three actions you would like to check for readiness, then select Run check.
8. The details page for your vSRX displays again, as do the test results in the readiness check module.

Ensure the status for any action you want to perform is Ready before beginning that action.



The following section provides details on the various readiness status conditions your check might return.



 Readiness status 

There are seven unique status conditions for the readiness check that you might encounter.



 Unchecked 

A readiness check has not yet been run for this action.





 Expired 

The readiness check has not run recently enough to reflect accurate results. Run a new check to see the current status. Readiness checks expire 5 hours after they complete.





 Ready 

Your vSRX is ready to perform the given action.





 Not Ready 

Your vSRX is not ready to perform the action in question. This could occur because of several reasons. Either a readiness check error occurred, or the readiness check did not complete fast enough, and timed out.
If you are provisioning many resources simultaneously, which takes time in number of hours, it is suggested to split the resources into different workspaces. Schematics limits the execution time of a job to 24 hours. After 24 hours the jobs are terminated and the job is marked as STOPPED and workspace shows ACTIVE, or INACTIVE.

In the point of transition of the state file of 24 hours, an interrupt signal is sent to the command execution. A graceful period of 10 minutes is given for the command to finish. If not, a kill signal is sent and the job is stopped. A refresh is done after stopping the state file and other data is collected at the end. This is helpful, in cases where a Terraform command is stuck forever and user doesn't intervene.

In a job, multiple commands such as terraform init, terraform apply, and terraform refresh are executed. If the job times out in a command, all further commands gets only 10 minutes to finish. At the end of 10 minutes, each command is killed.

Example If a job is stuck forever on a Terraform apply, when the command is stopped, and if you run a refresh. If refresh is also stuck, after 15 minutes, a kill is executed. The Terraform local exec and remote exec already have a time limit of 30 minutes.
See the topic on [Reallocating resources](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-components) for the steps to scale down the CPU. If the root CA is needed later, for example to enroll another intermediate CA, you can always repeat the steps to scale back up the CPU. The minimum CPU required for a CA to be operational is 0.1 CPU.

By default, certificates generated by IBM Blockchain Platform CAs expire after one year and peer and ordering node TLS certificates expire after 15 years. Exactly thirty days before peer and ordering node certificates are due to expire, the platform automatically attempts to contact the CA and renew the certificates. If the CA is not online, the automatic renewal fails and enrollment to generate a new certificate needs to be performed manually. If automatic renewal of these certificates is important for your business, careful consideration should be given to scaling down a root CA or intermediate CA. See the topic on [Certificate expiration and renewal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmt) to learn more about the process.
To ensure that updates to a file share are valid, you can obtain an ETag hash string value and specify it in the If-Match header in the PATCH /shares/{share_id} call. That confirms that no change happened to the share object between the last observed state and the state at the time of the PATCH call.

To modify existing user tags that are added to a file share, you first make a GET /shares/{share_id} call and copy the hash value from ETag property in the response header. Then, you send the ETag value by using the If-Match header in a PATCH /shares/{share_id} request. Specifying an Etag value ensures any updates to or deletions of a file share fail if the If-Match value does not match the file share's current Etag. Follow these steps:



1. Make a GET /shares/{share_id} call and copy the hash string from ETag property in the response header. Use need the hash string value for when you specify If-Match in the PATCH /shares/{share_id} request to modify user tags for the share in step 2.

curl -sSL -D GET "https://us-south.cloud.ibm.com/v1/shares/{share_id}?version=2023-07-11&generation=2&maturity=beta&maturity=beta" -H "Authorization: Bearer $TOKEN" -o /dev/null

The response header looks similar to the following example:

HTTP/2 200
date: Mon, 09 January 2023 17:48:03 GMT
content-type: application/json; charset=utf-8
content-length: 1049
cf-ray: 69903d250c4966ef-DFW
cache-control: max-age=0, no-cache, no-store, must-revalidate
expires: -1
strict-transport-security: max-age=31536000; includeSubDomains
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="[uri...]"
resource-controller.instance.retrieve View a Continuous Delivery service instance in a resource group. Administrator, Editor, Operator, Viewer 
 continuous-delivery.instance.add-auth-users Add entries to the Authorized Users list on the Manage tab within the Continuous Delivery service instance. Administrator, Writer, Manager 
 continuous-delivery.instance.remove-auth-users Remove entries from the Authorized Users list on the Manage tab within the Continuous Delivery service instance. Administrator, Writer, Manager 
 continuous-delivery.instance.config-auth-users Reserved for future use. Administrator, Manager
Since other workloads exist on the ESXi servers, for example, vCenter Server, VMware NSX® Controller, or VMware NSX Edge, by using these resources, the third requirement is not met. The reason is because 33.6 GHz of CPU and 24 GB RAM for the two FortiGate VMs are needed.

In this case, the FortiGate Virtual Appliance installation might fail, unless at least one ESXi server is added to the environment. Also, the vSphere HA failover reservations must be updated to ensure that enough resources are available for two FortiGate VMs.

If more resources are needed to run the FortiGate Virtual Appliance service, you can add more ESXi servers before you install the service.





 Considerations when you delete FortiGate Virtual Appliance 

Review the following considerations before you delete the service:



* Before you delete the FortiGate Virtual Appliance service, ensure that the configuration of the existing FortiGate Virtual Appliances is deleted correctly. Specifically, network traffic must be routed around FortiGate Virtual Appliances instead of through FortiGate Virtual Appliances. Otherwise, the existing data traffic within your environment might be impacted.
* If you installed the FortiGate Virtual Appliance service before VMware Solutions v4.0, and you then delete that service, you must manually remove the DNS entries. For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering FortiGate Virtual Appliance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-fortinetvm_ordering)
* [Managing FortiGate Virtual Appliance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingfortinetvm)
ibmcloud hpcs-cert-mgr cert delete --crn HPCS_CRN --admin-priv-key ADMIN_PRIV_KEY --cert-id CERT_ID [--private]

Replace the variables in the example request according to the following table.



Table 2. Describes the variables needed to delete CA certificates

 Variable Description 

 HPCS_CRN Required. The Cloud Resource Name (CRN) of your Hyper Protect Crypto Services instance. You can use the ibmcloud resource service-instances --long command to retrieve the CRN. 
 ADMIN_PRIV_KEY Required. The file path of your current private key that is stored on your local workstation. The private key is used to sign this command action towards your instance certificate manager server. 
 CERT_ID Required. The string ID of the CA certificate that you want to delete. You can first use the ibmcloud hpcs-cert-mgr cert list --crn HPCS_CRN command to list all the certificates including their IDs. 



The parameter --private is optional. If you use this option, the certificate manager server URL points to the private endpoint and you need to use the private network to connect your service instance.

If multiple certificate administrators are set up for your service instance, make sure to delete all the CA certificates under these administrators.

If you delete a CA certificate from the certificate manager server, all applications using the client certificates that are issued by this CA certificate do not have access to the GREP11 instance through mutual TLS connection.

After you delete all CA certificates from the certificate manager server, the mutual TLS authentication for the GREP11 instance is disabled. Applications then do not need mutual TLS connection to connect to the GREP11 instance.
2. (Optional) Check and confirm whether all the CA certificates are deleted with the following command:

ibmcloud hpcs-cert-mgr cert list --crn HPCS_CRN [--private]

If no certificate is returned, it means all the certificates of your service instance are deleted.
3.
The Cloud Resource Name (CRN) under ID contains your Tenant ID and Cloud Instance ID. The following example shows a typical CRN:

crn:v1:staging:public:power-iaas:us-east:a/abcdefghijklmnopqrstuvwxyzabcdef:121d5ee5-b87d-4a0e-86b8-aaff422135478::
5. Target your service by entering the following command, ibmcloud pi service-target <crn>.



ibmcloud pi service-target crn:v1:staging:public:power-iaas:us-east:a/abcdefghijklmnopqrstuvwxyzabcdef:121d5ee5-b87d-4a0e-86b8-aaff422135478::

Power Systems Virtual Server CLI requires a valid IAM token authorization before each use. Use the ibmcloud login command to renew authorization if your token expires.

--------------------





 Release notes 

Use these release notes to learn about the latest changes to the Power Systems™ Virtual Server.



 December 2022 



* You can now get new error messages for undefined response codes for new service endpoint response codes.







 September 2022 



* You can now use shared processor pool using CLI. The following are new commands for shared processor pools:



* [View details of a shared processor pool](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referenceibmcloud-pi-shared-processor-pool)
* [Create a shared processor pool](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referenceibmcloud-pi-shared-processor-pool-create)
Security group The security group must be detached from all network interfaces. The default security group for a VPC cannot be deleted. 
 Floating IP The floating IP must be detached from any network interface. 
 Public gateway The public gateway must be detached from all subnets. 
 Load balancer 
 VPN gateway Because IKE and IPsec policies can be shared between gateways, these policies are not deleted when a VPN Gateway is deleted. These policies must be removed manually. 





 VPC resources cannot be deleted in a transient state 

VPC resources cannot be deleted when they are in a transient state, such as pending. All resources must be in a "final" state, such as available or failed, before they can be deleted. You must wait for the resource to get to available or failed before you try to delete the resource. [Contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support) if a resource does not show an available or failed status within 30 minutes.

After you request to delete a resource, the resource enters a transient state of deleting. Wait for the resource to disappear from the list before you try to delete the parent or attached resource. In some situations, the delete operation might fail, and the resource enters a failed status within a few minutes. Contact support if a resource doesn't disappear or show a failed status within 30 minutes after you made a delete request. After the resource is in failed status, you can attempt to delete it again. [Contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support) if you are unable to delete a resource in failed status.





 Follow this order when you delete a VPC 

A VPC contains subnets and public gateways. A public gateway can be attached to one or more subnets in the VPC. A subnet also can contain virtual server instances, and one virtual server instance can have multiple network interfaces in different subnets within the VPC.
However, by default, vSphere HA reserves 50% of CPU and RAM for failover on vCenter Server instances that were initially deployed with two ESXi servers. For this example, the following configuration is available:

50% of 2 * 16 cores * 2.1 GHz = 33.6 GHz available

Other workloads are also present on the ESXi servers, for example, VMware vCenter Server, VMware NSX® Controller™, and VMware NSX Edge™. Because these resources are used, the third requirement cannot be satisfied because 33.6 GHz of CPU and 32 GB RAM are needed for the two BIG-IP VMs.

In this case, the F5 BIG-IP installation might fail, unless at least one ESXi server is added to the environment and vSphere HA failover reservations are updated to ensure that enough resources are available for two BIG-IP VE VMs. If more resources are needed to run the F5 BIG-IP service, you can add more ESXi servers before you install F5 BIG-IP.





 Considerations when you delete F5 BIG-IP 

Review the following considerations before you delete the service:



* Before you delete the F5 BIG-IP service, ensure that the existing BIG-IP VE configuration is removed correctly. Specifically, network traffic must be routed around BIG-IP VE instead of through BIG-IP VE. Otherwise, the existing data traffic from your environment might be impacted.
* If you installed the F5 BIG-IP service before VMware Solutions v4.0 and then deleted that service, you must manually remove the DNS entries. For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering F5 BIG-IP](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-f5_ordering)
Update a target PUT <ENDPOINT>/api/v2/targets/<TARGET_ID> 
 Delete a target DELETE <ENDPOINT>/api/v2/targets/<TARGET_ID> 
 Read a target GET <ENDPOINT>/api/v2/targets/<TARGET_ID> 
 List all targets GET <ENDPOINT>/api/v2/targets 
 Validate a target POST <ENDPOINT>/api/v2/targets/{id}/validate 



For more information, see [IBM Cloud Activity Tracker Event Routing V2 API](https://cloud.ibm.com/apidocs/atracker).





 HTTP response codes 

When you use the IBM Cloud Activity Tracker Event Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 7. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Activity Tracker Event Routing processing. 







 Next 

Choose 1 of the following options to con figure a target in your account:



* [Managing IBM Cloud Object Storage (COS) targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_cos).
* [Managing IBM Cloud Activity Tracker Event Routing AT hosted event search targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_at).
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 5. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 204 OK The route was successfully deleted. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests reach the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Metrics Routing processing.