vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Adding Bare Metal Server bandwidth](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-adding-bare-metal-server-bandwidth) and [Adding virtual server instance bandwidth](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-adding-virtual-server-insance-bandwidth).

When the bandwidth usage on a device reaches 85% of its total allocation, the account owner receives notifications.

IBM charges for some firewall bandwidth metering. For example, the Hardware Firewall (shared) product is not metered for bandwidth. The Fortigate Security Appliance 10G does receive an included bandwidth allocation, and is charged for egress bandwidth overages after that allocation has been exceeded. Additionally, these products can reduce total bandwidth usage by limiting the traffic that servers must respond to. Because monthly server bandwidth is recorded at the server switch port, traffic that is blocked by the hardware firewall is not counted against your monthly allocations, eliminating the need to pay for unwanted traffic. For more information, see [About Hardware Firewall](https://cloud.ibm.com/docs/hardware-firewall-shared?topic=hardware-firewall-shared-about-hardware-firewall-shared-).

For Citrix Netscaler VPX appliances, you can purchase larger allocations of bandwidth at a reduced cost compared to the overage rate. For more information, see [Ordering a Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-getting-startedordering-a-citrix-netscaler-vpx).





 About bandwidth pools 

Bandwidth pooling optimizes your bandwidth usage by "pooling" all of the bandwidth of individual servers together into a bandwidth pool.

The bandwidth usage of devices in a bandwidth pool is summed up as a whole, and overages are calculated only if the total bandwidth of all servers exceeds the total allocated bandwidth for all servers.
* To remove untagged images collectively from your namespace, use the [ibmcloud cr image-prune-untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_image_prune_untagged) command, see [Clean up your namespaces by deleting untagged images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_images_untagged).
* To use retention policies, see [Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).



3. Review your storage quota usage.

ibmcloud cr quota
4. To reduce your pull traffic usage, you must wait until the next billing period.

To continue pulling images from your namespaces, choose between the following options.



* Wait until the next billing cycle starts.
* If you have a free plan, [upgrade to the standard service plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plan_upgrade).
* If you already have a standard plan, [set new quota limits for the pull traffic](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_set).
Check that the image that is used by your job run exists and is referred to correctly.



* From the console, from your job page, check that the image that is specified for Image reference is correct and confirm that this image exists in the container registry.
* With the CLI, use the ibmcloud ce jobrun get command to display details of your job run, which includes the name of the image. Confirm that you are using an image that exists.



3. Check for an ImagePullBackOff error by running the [ibmcloud ce jobrun events --jobrun JOBRUN_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-events) command; for example,

ibmcloud ce jobrun events --jobrun myjobrun



* If the error in the events is similar to the following message, this error indicates that the registry quota is exceeded. Consider upgrading your plan. For information about IBM Cloud Container Registry service plans and quota limits, see [About IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview).

403 Forbidden - Server message: denied: You have exceeded your pull traffic quota for the current month. Review your pull traffic quota and pricing plan.
* If the error in the events is similar to the following message, this error indicates that access to the registry does not exist or might require authorization. Check that your credentials have appropriate [access to the registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_access).

Failed to pull image "<image_name>": rpc error: code = Unknown desc = failed to pull and unpack image "<image_name:image_tag>": failed to resolve reference <image_name:image_tag>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed.



4. View details of the submitted job run.



* From the console, view details of your submitted job run by clicking the name of your job run in the Job runs tab on your job page.
Controlling data usage 

In IBM Cloud® Activity Tracker, you can control the data that is collected and available for analysis through an auditing instance. You can define exclusion rules in the UI that apply to data collected in that instance. You can define an alert that is triggered when the data usage threshold that you define for that auditing instance is reached.



 Controlling data by using exclusion rules 

You can configure exclusion rules through the UI to stop events from counting against your data usage quota and from being stored for long term storage.

Events that are excluded do not count towards your data usage quota. Also, events that match the exclusion rule are not archived.

When you exclude events through an exclusion rule, you can choose to Preserve these lines for live-tail and alerting. When you check this option, log lines that match the exclusion rule are shown through the live tail and you can set up an alert for that data. These lines show as (not retained).

[Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-exclusion_rules).





 Configuring the usage alert 

In IBM Cloud® Activity Tracker, you can define an alert to notify when the data usage in the instance reaches the data usage threshold that you set for the instance.

[Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_alert).





 Configuring an ingestion alert 

In IBM Cloud® Activity Tracker, you can define an alert to notify when the data collected reaches a threshold within a period of time that you can customize.

[Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-control_usage_instance).





 Analyzing event data trends 

In IBM Cloud® Activity Tracker, you can query your auditing instance by using the Usage API and identify trends over a period of time.

You can analyze event data trends to assess the growth or decline of auditing data over time for services running in your account. You can monitor data trends to identify patterns and make predictions of how services are used in the account.
The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=apibackup-plan-ui). 



3. Optionally, [estimate the costs](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=apibackup-cost-estimator-ui) for your backups.
4. Click Create backup policy. The order summary side panel shows the backup policy and all plans that were created for it.







 Creating a backup plan in the UI 

You can schedule backups in your plan on a daily, weekly, or monthly basis by using predefined settings, or by way of a cron-spec expression. The following steps continue from [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=apibackup-policy-create-ui) and describe the backup plan side panel.



1. From the Plan side panel, enter a name for the plan (for example, daily-dallas-vol1). The plan name must be unique within the policy.
2. Specify the Frequency. Select one of the following options from the list.



* Daily



* For a Daily plan, enter the starting time (UTC) in hours and minutes, Coordinated Universal Time. For example, 12 noon is 12:00. Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly
The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=uibackup-plan-ui). 



3. Optionally, [estimate the costs](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=uibackup-cost-estimator-ui) for your backups.
4. Click Create backup policy. The order summary side panel shows the backup policy and all plans that were created for it.







 Creating a backup plan in the UI 

You can schedule backups in your plan on a daily, weekly, or monthly basis by using predefined settings, or by way of a cron-spec expression. The following steps continue from [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=uibackup-policy-create-ui) and describe the backup plan side panel.



1. From the Plan side panel, enter a name for the plan (for example, daily-dallas-vol1). The plan name must be unique within the policy.
2. Specify the Frequency. Select one of the following options from the list.



* Daily



* For a Daily plan, enter the starting time (UTC) in hours and minutes, Coordinated Universal Time. For example, 12 noon is 12:00. Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly
The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=clibackup-plan-ui). 



3. Optionally, [estimate the costs](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=clibackup-cost-estimator-ui) for your backups.
4. Click Create backup policy. The order summary side panel shows the backup policy and all plans that were created for it.







 Creating a backup plan in the UI 

You can schedule backups in your plan on a daily, weekly, or monthly basis by using predefined settings, or by way of a cron-spec expression. The following steps continue from [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=clibackup-policy-create-ui) and describe the backup plan side panel.



1. From the Plan side panel, enter a name for the plan (for example, daily-dallas-vol1). The plan name must be unique within the policy.
2. Specify the Frequency. Select one of the following options from the list.



* Daily



* For a Daily plan, enter the starting time (UTC) in hours and minutes, Coordinated Universal Time. For example, 12 noon is 12:00. Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly
The page refreshes with a summary of the plan details. You can create up to four backup plans. All apply to the volumes with tags that match the backup policy. <br>For more information about options, see [Specify a backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=terraformbackup-plan-ui). 



3. Optionally, [estimate the costs](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=terraformbackup-cost-estimator-ui) for your backups.
4. Click Create backup policy. The order summary side panel shows the backup policy and all plans that were created for it.







 Creating a backup plan in the UI 

You can schedule backups in your plan on a daily, weekly, or monthly basis by using predefined settings, or by way of a cron-spec expression. The following steps continue from [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=terraformbackup-policy-create-ui) and describe the backup plan side panel.



1. From the Plan side panel, enter a name for the plan (for example, daily-dallas-vol1). The plan name must be unique within the policy.
2. Specify the Frequency. Select one of the following options from the list.



* Daily



* For a Daily plan, enter the starting time (UTC) in hours and minutes, Coordinated Universal Time. For example, 12 noon is 12:00. Local time conversion is automatically provided on the screen, for example, 12 PM Central Daylight Time.



* Weekly



* For a Weekly plan, select the days of the week that you want backups to run. For example, you can select Monday, Wednesday, and Friday. Specify the starting time in the same manner as a Daily plan.



* Monthly
imagePullPolicy: Always





 Port for the app's service 

Select a container port to open the app's services on. To see which port needs to be opened, refer to your app specs or Dockerfile. The port is accessible from the private network, but not from a public network connection. To expose the app publicly, you must create a NodePort, load balancer, or Ingress service. You use this same port number when you [create a Service object](https://cloud.ibm.com/docs/containers?topic=containers-appapp-service).

Port 25 is blocked for all services in IBM Cloud.

ports:
- containerPort: 9080





 Resource requests and limits 

Cluster administrators make sure that teams that share a cluster don't take up more than their fair share of compute resources (memory and CPU) by creating a [ResourceQuota object](https://kubernetes.io/docs/concepts/policy/resource-quotas/) for each Kubernetes namespace in the cluster. If the cluster admin sets a compute resource quota, then each container within the deployment template must specify resource requests and limits for memory and CPU, otherwise the pod creation fails.



1. Check whether a resource quota is set for a namespace.

kubectl get quota --namespace=<namespace>
2. See what the quota limits are.

kubectl describe quota <quota_name> --namespace=<namespace>



Even if no resource quota is set, you can include resource requests and limits in your deployment to improve the management of worker node resources.

If a container exceeds its limit, the container might be restarted or fail. If a container exceeds a request, its pod might be evicted if the worker node runs out of that resource that is exceeded. For more information about troubleshooting, see [Pods repeatedly fail to restart or are unexpectedly removed](https://cloud.ibm.com/docs/containers?topic=containers-ts-app-pod-fail).

Request
: The minimum amount of the resource that the scheduler reserves for the container to use.
imagePullPolicy: Always





 Port for the app's service 

Select a container port to open the app's services on. To see which port needs to be opened, refer to your app specs or Dockerfile. The port is accessible from the private network, but not from a public network connection. To expose the app publicly, you must create a NodePort, load balancer, or Ingress service. You use this same port number when you [create a Service object](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsapp-service).

Port 25 is blocked for all services in IBM Cloud.

ports:
- containerPort: 9080





 Resource requests and limits 

Cluster administrators make sure that teams that share a cluster don't take up more than their fair share of compute resources (memory and CPU) by creating a [ResourceQuota object](https://kubernetes.io/docs/concepts/policy/resource-quotas/) for each Red Hat OpenShift project in the cluster. If the cluster admin sets a compute resource quota, then each container within the deployment template must specify resource requests and limits for memory and CPU, otherwise the pod creation fails.



1. Check whether a resource quota is set for a namespace.

oc get quota --namespace=<namespace>
2. See what the quota limits are.

oc describe quota <quota_name> --namespace=<namespace>



Even if no resource quota is set, you can include resource requests and limits in your deployment to improve the management of worker node resources.

If a container exceeds its limit, the container might be restarted or fail. If a container exceeds a request, its pod might be evicted if the worker node runs out of that resource that is exceeded. For more information about troubleshooting, see [Pods repeatedly fail to restart or are unexpectedly removed](https://cloud.ibm.com/docs/containers?topic=containers-ts-app-pod-fail).

Request
: The minimum amount of the resource that the scheduler reserves for the container to use.
When a user selects your service and its pricing plan from the IBM Cloud catalog and creates an instance, the data for the service including the pricing plan and metrics, is sent to your service broker. The broker is integrated with the backend system that manages the provisioning of service instances and the metrics for a selected pricing plan. If a customer deletes an instance of the product, a request is sent to the service broker, and it manages the deprovisioning of the instance.

Zoom

![A diagram that shows third-party providers what role a service broker performs when a user selects their product from the catalog.](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/sell/images/Broker_role.svg)

Figure 1. Understanding the role of a service broker when a user selects a product from the IBM Cloud catalog.

The broker architecture provides significant benefits for both development and operations teams:



* Developers can connect their applications and containers to the backing services they need. The operation is the same, regardless of the backing service.
* Operators no longer have to manually create and delegate access to services. Instead, they configure a marketplace of services and service plans. From there, developers can self-serve, reducing the administrative costs many enterprises face today.



Each service broker that's built to the Open Service Broker API specification has the same intuitive set of lifecycle commands. These commands provide useful benefits for the service broker:

Fetching the catalog of backing services that a service broker offers
: The catalog describes all of the services that can be created through a service broker, and each service is made up of plans. Plans typically represent the costs and benefits for a given variant of the service. Many services use plans related to the size the product, for example small, medium, and large.

Provisioning new service instances
: A service instance is a created instance of a service and plan as described in the service broker’s catalog.

Connecting and disconnecting applications and containers from those service instances
These interconnections or changes (e.g., upgrading or replacing applications and operating systems) may adversely affect previously implemented security controls. This control provides additional types of security testing/evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as static analysis, dynamic analysis, binary analysis, or a hybrid of the three approaches. Developers can employ these analysis approaches in a variety of tools (e.g., web-based application scanners, static analysis tools, binary analyzers) and in source code reviews. Security assessment plans provide the specific activities that developers plan to carry out including the types of analyses, testing, evaluation, and reviews of software and firmware components, the degree of rigor to be applied, and the types of artifacts produced during those processes. The depth of security testing/evaluation refers to the rigor and level of detail associated with the assessment process (e.g., black box, gray box, or white box testing). The coverage of security testing/evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security assessment plans, flaw remediation processes, and the evidence that the plans/processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the information system. Contracts may specify documentation protection requirements.
IBM ResellOne End of Service 

Effective 1 November 2021, IBM Cloud will no longer support our ResellOne Domain Resale service, which we offer in partnership with Tucows Inc.

On 1 November 2021, depending on how many domains that you are managing, Tucows and IBM Cloud will automatically migrate your domains and reseller accounts over to Tucows’ retail domain platform, [Hover](https://hover.com/) or the [OpenSRS](https://manage.opensrs.com/) reseller platform.

For more information and actions that you must take, see [Migrating from IBM ResellOne to Tucows](https://cloud.ibm.com/docs/dns?topic=dns-resellone-migration).

Contact [IBM Cloud Support](https://cloud.ibm.com/docs/dns?topic=dns-gettinghelp-with-dns) with any questions about migration options, or reach out to your Customer Success Manager or Technical Account Manager if you have these services.