vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* CLI
* API







 Managing endpoints (API V1) 

You can use the the IBM Cloud® Activity Tracker Event Routing CLI or IBM Cloud Activity Tracker Event Routing REST API to manage private and public endpoints in your account.

The V1 API is deprecated. This CLI and API can only be used while using the IBM Cloud Activity Tracker Event Routing V1 API. Once you have [migrated to the V2 API](https://cloud.ibm.com/docs/atracker?topic=atracker-migrate-resources) this CLI and API can no longer be used.

By default, private endpoints are enabled.



* You cannot disable private endpoints.
* The private endpoint format is as follows:

https://private.<region>.atracker.cloud.ibm.com/api/v1
* For more information about the list of ENDPOINTS that are available, see [Private endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api-private).



By default, public endpoints are enabled.



* You can disable public endpoints per region in your account.
* The public endpoint format is as follows:

https://<region>.atracker.cloud.ibm.com/api/v1



If public and private endpoints are enabled, you can disable a public endpoint by using private or public endpoints.

If public endpoints have been disabled, you can only enable public endpoints by using the private endpoint.

For more information about the list of ENDPOINTS that are available, see [Public endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api-public).



 API actions 

The following table lists the actions that you can run to manage endpoints:



Table 1. Endpoints actions by using the IBM Cloud Activity Tracker Event Routing REST API

 Action REST API Method API_URL 

 Get endpoints that are enabled in a region GET <ENDPOINT>/api/v1/endpoints
Managing a logging agent deployed in an OpenShift cluster 

The logging agent is responsible for collecting and forwarding logs to your IBM Log Analysis instance. After you provision an instance of IBM® Log Analysis, you must configure a logging agent for each log source that you want to monitor.

To configure your Kubernetes cluster to send logs to your IBM Log Analysis instance, you must install a logging-agent pod on each node of your cluster. The logging agent reads log files from the pod where it is installed, and forwards the log data to your logging instance.



 Deploy the logging agent by using kubectl commands 

Complete the following steps from the command line to configure your OpenShift cluster to forward logs to your logging instance by using the default YAML file:

You can use an existing YAML file if you are configuring a newer logging agent version. Change the image value in your existing YAML file to match the version you are configuring.



 Prereq 

To deploy the logging agent in a cluster, you must have a user ID that has the following IAM roles:



* Viewer platform role, and Manager service role to work with that cluster instance.
* Viewer permissions on the resource group where the cluster is available.



To configure the logging agent in the cluster, you need the following CLIs:



* The IBM Cloud CLI to log in to the IBM Cloud by using ibmcloud commands, and to manage the cluster by using ibmcloud ks commands. [Learn more](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_installcs_cli_install_steps).
* The Kubernetes CLI to manage the cluster by using kubectl commands. [Learn more](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_installkubectl).
* The Openshift CLI to login to the cluster from the command line and deploy the agent. [Learn more](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-cli).







 Step 1.
Managing GPUs 

The GPU-enabled family of profiles provides on demand, cost-effective access to NVIDIA GPUs. GPUs help to accelerate the processing time that is required for compute intensive workloads such as AI, machine learning, inferencing and more. To use the GPUs, make sure that you install the appropriate NVIDIA driver and associated toolkit for your workloads.



 Configuring a virtual server instance with a GPU 



1. Provision a [virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) by choosing a [GPU profile](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uigpu) in the Profile field. Stock and custom operating system images are supported.
2. Install the NVIDIA GPU driver for your Virtual Server Instance's image and GPU profile. A NVIDIA driver level of R440 or newer is recommended. To download the drivers, see NVIDIA's [Download drivers](https://www.nvidia.com/Download/index.aspx?lang=en-us) page.
3. Install associated toolkit for your workload. Visit NVIDIA's [CUDA toolkit downloads](https://developer.nvidia.com/cuda-downloads) page.



For detailed instructions to complete Steps 2 and 3, other GPU tools, and examples, see [How to Use V100-Based GPUs on IBM Cloud VPC](https://www.ibm.com/cloud/blog/how-to-use-v100-based-gpus-on-ibm-cloud-vpc).

For a Linux focused guide on installing the NVIDIA drivers, see the [NVIDIA Driver Installation Quickstart Guide](https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html).
The Access Management Tool is a self-service tool, located in the Saas Self-Service Portal, where users can manage access to their MAS-Dedicated environments.

Self-Service Portal URL:

[https://devops.maximo.com](https://devops.maximo.com)





 Access Management Tool Overview 



 User Roles 

The Access Management Tool supports two user roles - standard users and manager users. Manager users have elevated accesses to manage the tool for their customer.

![SSP-AM-Overview-User-Roles](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Overview-User-Roles.png)

Manager User

A manager user is a user in the Access Management Tool with a role assignment of MANAGER. Manager user responsibilities include:



* Adding/removing users to the tool.
* Granting users access to the customer they are managing.
* Reviewing access requests.
* Viewing, modifying, and removing user accesses.
* Standard user responsibilities.



Standard User

A standard user is a user in the Access Management Tool with a role assignment of STD_USER. Standard user responsibilities include:



* Submitting access requests.
* Viewing, modifying, and removing their accesses.
* Deactivating their user account.







 Views & Tabs 

List View

The List View page is the homepage of the Access Management Tool. This is where you can view the user accounts you have access to. Manager users can view user accounts that have access to the customer they are managing from this page. Standard users can view their user account from this page.

!
* CLI
* API







 Managing targets by using the V1 API 

You can manage targets in your account by using the IBM Cloud® Activity Tracker Event Routing CLI or the IBM Cloud Activity Tracker Event Routing REST API. A target is a resource where you can collect auditing events.

The V1 API is deprecated. See [managing IBM Cloud Activity Tracker Event Routing hosted event search offering targets by using the V2 API](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_at) and [managing COS targets by using the V2 API](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_cos) for information on using the V2 API. Also see [migrating resources](https://cloud.ibm.com/docs/atracker?topic=atracker-migrate-resources) for information on migrating from your V1 configuration.

The version of the API running in your account can be determined by running the [ibmcloud atracker init version command.](https://cloud.ibm.com/docs/atracker?topic=atracker-v2api)

You can define up to 16 targets in each region.

You must define a IBM Cloud Object Storage (COS) target for each region. While you can use the same COS bucket for collecting auditing events in your account across multiple regions, you should consider defining a bucket in each region to improve performance and reduce network latency.

The following table outlines valid target types:



Table 1. List of targets

 Target Type 

 IBM Cloud Object Storage (COS) cloud_object_storage 



When you define a target in IBM Cloud Object Storage (COS), consider the following information:



* You can create the bucket in any location. For more information, see [Managing IBM Cloud Object Storage (COS) buckets](https://cloud.ibm.com/docs/atracker?topic=atracker-cos).
* You configure 1 bucket for each target.
Managing global IPs (ibmcloud sl globalip) 

A global IP address is a specialized static secondary subnet. It is delivered to you as a /32 subnet (in other words, a single IP address) that can be routed to any other IP address on your account.

Use the following commands from the IBM Cloud® Command Line Interface to manage a global IP in the IBM Cloud classic infrastructure Global IP service.



  ibmcloud sl globalip assign 

Assign a global IP to a target router or device:

ibmcloud sl globalip assign IDENTIFIER TARGET [OPTIONS]

Examples:

ibmcloud sl globalip assign 12345678 9.111.123.456

This command assigns IP address with ID 12345678 to a target device whose IP address is 9.111.123.456.





  ibmcloud sl globalip cancel 

Cancel a global IP:

ibmcloud sl globalip cancel IDENTIFIER [OPTIONS]

Command options:

-f, --force
:   Force operation without confirmation.

Examples:

ibmcloud sl globalip cancel 12345678

This command cancels IP address with ID 12345678.





  ibmcloud sl globalip create 

Create a global IP:

ibmcloud sl globalip create [OPTIONS]

Command options:

--v6
:   Order an IPv6 IP address.

--test
:   Test order.

-f, --force
:   Force operation without confirmation.

Examples:

ibmcloud sl globalip create --v6

This command creates an IPv6 address.





  ibmcloud sl globalip list 

List all global IPs on your account:

ibmcloud sl globalip list [OPTIONS]

Command options:

--v4
:   Display IPv4 IPs only.

--v6
:   Display IPv6 IPs only.

--order
:   Filter by the ID of order that purchased this IP address.

Examples:

ibmcloud sl globalip list --v4

This command lists all IPv4 addresses on the current account.





  ibmcloud sl globalip unassign 

Unassign a global IP from a target router or device:

ibmcloud sl globalip unassign IDENTIFIER [OPTIONS]

Examples:

ibmcloud sl globalip unassign 12345678

This command unassigns IP address with ID 12345678 from the target device.
Access management in IBM Cloud 

Access management enables you to control which users see, create, use, and manage resources in your account. To grant access, you can assign roles that allow users levels of access for completing platform management tasks and accessing account resources.

The way that you manage access in IBM Cloud® depends on the type of resource that you want to assign access to. IBM Cloud Identity and Access Management (IAM) is the access management system that is used for consistently managing resources that are organized in a resource group across the IBM Cloud platform. Classic infrastructure resources are not managed by using Cloud IAM. These resource types have their own access management system.

If you have a combination of resource types, you manage each type separately:



* For [IAM resources](https://cloud.ibm.com/docs/account?topic=account-userroles), go to Manage > Access (IAM) in the IBM Cloud console, and then select Users, Access groups, Trusted profiles, or Service IDs to get started.
* For assigning access to your [classic infrastructure resources](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra), you set permissions within Manage > Access (IAM) on the Classic infrastructure tab for the user that you want to assign access. You can also choose to assign Classic infrastructure access by using Trusted profiles if your account is linked to a Softlayer account.



While each type of access is managed separately, all access policies are made up of a subject you want to assign access to, a target for the policy to scope what the subject has access to, and then finally an IAM role or classic infrastructure permission to determine the level of access the subject has on the target.

Zoom

![Access management policies by using IAM or classic infrastructure permissions.](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/access-management.svg)

Figure 1. Access management policies by using IAM or classic infrastructure permissions
Managing streaming to Event Streams by using the API 

IBM® Log Analysis provides an API that you can use to configure streaming for an IBM Log Analysis instance.



 Get details of the streaming configuration 

Use [this method](https://cloud.ibm.com/apidocs/log-analysisget-v1-config-stream) to get the details about an existing streaming configuration.

curl --request GET https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following:

{"status":"active","brokers":["kafka-0.mh-svc1-0000.eu-de.containers.appdomain.cloud:9093","kafka-1.mh-sv2.eu-de.containers.appdomain.cloud:9093","kafka-2.mh-sv3.eu-de.containers.appdomain.cloud:9093"],"topic":"la-london-topic","user":"token"}





 Delete the streaming configuration 

Use [this method](https://cloud.ibm.com/apidocs/log-analysisdelete-v1-config-stream) to delete an existing streaming configuration.

curl --request DELETE https://api.eu-gb.logging.cloud.ibm.com/v1/config/stream
-H "content-type: application/json"
-H "servicekey: <SERVICE_KEY>"

The response will be similar to the following if the configuration is successfully deleted:

{"deleted":true}

If an incorrect service key was specified, a response similar to the following will be returned:

{"error":"Service Key Validation Error: Invalid or deactivated servicekey","status":"error","code":"NotAuthorized"}





 Configure streaming
Publishing your content 

Publishing is a way to maintain a healthy lifecycle management process. You can create incremental versions of your content over time, making it easier to manage deployment of changes and roll back (revert) to prior versions if necessary.

When you are ready to create a snapshot of your content and settings, you can publish from the Publish page. Each time that you publish, you create a new version, such as V1 or V2.

Zoom

![Publish page](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/publish-page.png)

Publish page

When you publish your content, Watson Assistant creates a snapshot of the draft content, resulting in a version. This version contains all of the content from actions, including settings and variables. Versions do not contain integration configurations or environment settings. Integration configurations and environment settings must be configured manually in each environment.

The three most recent published versions appear in a list on the Publish page itself. If you have more than three versions, you can click View all to see a list of all published versions.

Zoom

![All versions](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/published-versions.png)

All versions

The number of versions that can be maintained depends on the type of plan you have. If you reach the plan limit of versions you can have, you need to delete a version before you can publish another one.



Service plan published versions

 Service plan Published versions 

 Enterprise 50 
 Premium (legacy) 50 
 Plus 10 
 Trial 10 
 Lite 2 





 How to publish 



1. If changes are available to publish, click Publish.
2. Enter a description of the version.
3. Choose to publish to the live environment, or to create a version without publishing.
Presto update process for watsonx.data 

IBM® watsonx.data is a managed service with regular release updates occurring as part of standard operations.

The upgrade process is designed to ensure that any outage is kept to a minimum. Your applications must be designed to handle temporary interruptions to the service by implementing the following:



*  error handling for failed commands
*  retry logic to recover from a temporary interruption



If a Presto coordinator node restarts on update, applications must re-establish connection with the Presto engine.

Before updates begin and after the new version becomes available, the latest version can be tested. A new Presto engine can be provisioned from the infrastructure manager within your watsonx.data instance, which uses the latest version thereby ensuring that all applications work seamlessly with the new version.

Applications can then be migrated to the new engine at your convenience, allowing better control of the update. For more information, see [Creating an engine](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-prov_engine).
For more information, see [Managing authentication](https://cloud.ibm.com/docs/appid?topic=appid-managing-idpidp-token-lifetime).



1. In terminal, run the following command to obtain an API key.

ibmcloud iam api-key-create NAME [-d DESCRIPTION] [-f, --file FILE]



Table 2. Understanding the creating an API key command options

 Option Description 

 NAME The name that you want to give your key. For example, myKey. 
 DESCRIPTION A description of the key or its use. For example, "This is my App ID API key". 
 FILE The location where you want to store your key. For example, key_file. 



2. Obtain an IAM token by using the API key that you got in the previous step.

curl -k -X POST "https://iam.cloud.ibm.com/identity/token" --header "Content-Type: application/x-www-form-urlencoded" --header "Accept: application/json" --data-urlencode "grant_type=urn:ibm:params:oauth:grant-type:apikey" --data-urlencode "apikey=<apiKey>"
3. Get the tenant ID for your instance of the service. You can find the value in either your service or application credentials.
4. Make a PUT request to the /config/tokens endpoint with your token configuration.

curl -X PUT "https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/config/tokens" -H 'Content-Type: application/json' -H "Authorization: Bearer <IAMToken>" -d '{
"access": {
"expires_in": 3600
},
"refresh": {
"enabled": true,
"expires_in": 2592001
},
"anonymousAccess": {
"enabled": false
Managing endpoints (API V2) 

You can use the the IBM Cloud® Activity Tracker Event Routing CLI or IBM Cloud Activity Tracker Event Routing REST API to manage private and public endpoints in your account.

You can view the type of endpoints that are available in the account to manage Activity Tracker Event Routing by using the [settings API](https://cloud.ibm.com/docs/atracker?topic=atracker-settings).



  Private endpoints 

By default, private endpoints are enabled.



*  You cannot disable private endpoints.
*  The private endpoint format is as follows:

https://private.<region>.atracker.cloud.ibm.com/api/v2
*  For more information about the list of ENDPOINTS that are available, see [Private endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api-private).







  Public endpoints 

By default, public endpoints are enabled.



*  You can disable public endpoints per region in your account.
*  The public endpoint format is as follows:

https://<region>.atracker.cloud.ibm.com/api/v2



For more information about the list of ENDPOINTS that are available, see [Public endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api-public).





  Disabling public endpoints 

If public and private endpoints are enabled, you can disable a public endpoint by using private or public endpoints.

If public endpoints have been disabled, you can only enable public endpoints by using the private endpoint.

See [Enforcing private endpoints to configure Activity Tracker resources](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-mng-endpoints).
Activity Tracker logdna [Managing Activity Tracker hosted event search targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_at&interface=cli) 
 IBM® Event Streams for IBM Cloud® event_streams [Managing IBM® Event Streams for IBM Cloud® targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_ies&interface=cli) 







 Routes 

A route defines the rules that indicate where auditing events that are generated in the account are routed.



* Routes are global under an account and are evaluated in all regions where Activity Tracker Event Routing is deployed.
* Routes may be managed from any regional IBM Cloud® Activity Tracker Event Routing API endpoint.
* You can define up to 4 routes for an account.
* By default, the account has 0 routes configured.
* You can configure up to 4 rules for each route. A routing rule indicates the locations and associated targets where auditing events are routed.
* You can configure up to 8 locations for each rule.
* You can configure up to 3 targets (target_ids) for each rule.
* Routes are processed independently. If you have multiple routes with rules that match the same event, that event will be sent to multiple targets.
* Rules are processed in order. The first matching rule (for example, location) an event matches will be used to process the event. Once an event has been processed it will not be processed by a subsequent rule within that route's definition. If you want to specify a default rule for all events that were not processed by other rules you would specify the rule ("locations" : [""]) as the final rule in your rules definition for the route.
* If an event doesn't match any rule and no default target is configured, the event will be dropped and not routed to any target.
* Any update to a rules configuration must include all location rules. An update will discard the existing rule set and replace it with the specified configuration.
Managing VMware licenses 



1.  Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog/).
2.  Go to Devices > Manage > VMware® licenses. Each VMware® add-on that is purchased displays the following information:



*  License key
*  CPUs
*  Order date





Ordering VMware® licensing



1.  Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog/).
2.  Go to Devices > Manage > VMware® licenses.
3.  Click Order VMware® licenses.
4.  Select the appropriate licenses.
5.  Click Continue.
6.  Review charges and the MSA and click Place order.