vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Available options are name, displayname, kind, provider, created, and updated.

--reverse (optional)
: Flag is only valid for services search. Use it to reverse the sorting order.

--fields FIELDS (optional)
: Flag is only valid for services search. Customize the table, for example, --fields name,kind,metadata.service.iam_compatible.





 Output 

The command returns the following output:

Name ID Category
2 Zone VPC f10d9ae9-ac94-4718-b24a-3994241ae2a4-global Networking
Apache Qml0bmFtaS1hcGFjaGU=-global Developer Tools
Apache Airflow Qml0bmFtaS1haXJmbG93-global Databases
Apache Airflow Qml0bmFtaS1haXJmbG93-global Developer Tools







 ibmcloud catalog filter get 

Run the following command to retrieve filter details for either the account or a particular catalog.

ibmcloud catalog filter get --catalog CATALOG [--output FORMAT]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--account-group ACCOUNT GROUP
: The account group name or ID. This field applies only to enterprise accounts.

--output FORMAT (optional)
: Specifies output format. Default is terminal compatible and the only supported alternative is JSON, for example, --output json.





 Output 

The command returns the following output:

Account: The IBM Cloud catalog is visible to all users in this account.

Filter:
Including IBM Cloud catalog

Type Include Tags
Pricing plan false Free
Provider false Third Party







 ibmcloud catalog filter create 

Run the following command to create a new filter. If a filter exists, this command overrides the current filter.
Click the ![question mark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/question_mark.png) to access install instructions.
3. Click NXLog.
4. Click Download Root CA Certificate to download a copy of the certificate.
5. Copy the certificate to <NXLOGDIR>certca.pem, where <NXLOGDIR> is directory nxlog is installed.











 Run NXLog 

Run the following in PowerShell from the directory where you installed NXLog.

.nxlog.exe

Run the following in PowerShell from the directory where you installed NXLog to stop the service.

.nxlog.exe --stop





 Step 4: Launch the logging Web UI 

To launch the IBM Log Analysis dashboard from the IBM Cloud UI, complete the following steps:



1. Log in to your IBM Cloud account.

Click [IBM Cloud dashboard](https://cloud.ibm.com/login) to launch the IBM Cloud dashboard.

After you log in with your user ID and password, the IBM Cloud Dashboard opens.
2. In the navigation menu, select Observability.
3. Click Logging.

The list of IBM Log Analysis instances that are available on IBM Cloud is displayed.
4. Select one instance. Then, click Open dashboard.

The logging Web UI opens and displays your cluster logs.







 Step 5: View your logs 

From the logging Web UI, you can view your logs as they pass through the system. You view logs by using log tailing.

With the Free service plan, you can only tail your latest logs.

Due to Windows limitations, when the Windows VPC instance is created, the hostname is truncated to the first 15 characters of the instance name. The Windows hostname is included as the Hostname in the IBM Log Analysis log lines.
Step 5: View your logs 

From the logging Web UI, you can view your logs as they pass through the system. You view logs by using log tailing.

With the Free service plan, you can only tail your latest logs.

Due to Windows limitations, when the Windows VPC instance is created, the hostname is truncated to the first 15 characters of the instance name. The Windows hostname is included as the Hostname in the IBM Log Analysis log lines.

For example, if you created a Windows VPC named my-cloud-windows-vpc-instance then the hostname created in Windows Server, and displayed in the logs, will be my-cloud-window.

You can filter the log lines displayed in IBM Log Analysis by entering queries in the Search... box.



Table 2. Example queries

 Search for Returns 

 host:<WINDOWS_HOSTNAME> (EventType:INFO OR Severity:INFO) All log lines with event type or severity of INFO 
 host:<WINDOWS_HOSTNAME> (EventType:warn OR Severity:WARNING) All log lines with an event type of warn or severity of WARNING 
 host:<WINDOWS_HOSTNAME> Severity:ERROR All log lines with a severity of ERROR 



Where <WINDOWS_HOSTNAME> is the hostname of your Windows VPC server instance.

For more information, see [Viewing logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs).





 Next steps 

The following additional features are available:



* [Filtering logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step5)
* [Searching logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step6)
* [Defining views](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step7)
Allowing trial experience 

IBM provides promotion credits to allow a trial experience. The promotion code is sized to allow free trial of IBM® watsonx.data for seven days, if you carefully follow the tutorial. In this trial, you can explore and familiarize yourself with watsonx.data.

In this tutorial you learn how to claim your free promo code, apply it, monitor the usage of the credit, get started, size your starter instance of watsonx.data and try it out.

After you fully use the promo credits, you are automatically billed at the advertised rate. So, watch the usage and consumption of the promotion code credits closely.



 Objective 



* Getting the promotion code
* Monitoring the promotion credit usage
* Getting started with watsonx.data
* Loading data
* Querying data



Zoom

![Workflow diagram](https://cloud.ibm.com/docs-content/v1/content/4c3c4670556d1cad9f530a5c8a9edd2e63919b83/watsonxdata/images/happypath_userjourney.svg)

Figure 1. User journey





 Before you begin 



* To use the promotion credits, you must have an IBM Cloud® account with a payment method added.







 Step 1: Exploring key features 

Explore and review the following information in the watsonx.data IBM Cloud® catalog page.



 Viewing promotion code 

To view the promotion code and to know about the free credits, follow the steps:



1. Go to the watsonx.dataIBM Cloud® catalog page.
2. The Summary section displays an information dialog box with the promotion code and the free credits information.







 Review price estimate and plan resource 

Your watsonx.data features an elastic scalable computation method with cost per hour that is computed in Resource Units per Hour (RU/Hr). The cost varies depending on the resources that you add. It is important to right size the resources so that you can maximize the promotion credits. Take the time to carefully review the section and select minimum resources to conserve your promotion credits.
Certificate administrators also need to maintain a backup of all client certificates outside of the Hyper Protect Crypto Services instance, for example, by using [IBM Cloud Secrets Manager](https://www.ibm.com/cloud/secrets-manager). It is also suggested to monitor the expiration of the certificates.







 Before you begin 

Before you can enable the second layer of authentication for GREP11 or PKCS #11 API connections, make sure that you complete the following prerequisites:



1. You are assigned the Certificate Manager IAM role to perform the corresponding actions. For more information about assigning IAM roles, see [Managing user access](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-access) and [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).
2. You have a client certificate prepared on your workstation that is used for the TLS authentication. It is suggested to use the [IBM Cloud Secrets Manager](https://www.ibm.com/cloud/secrets-manager) to manage SSL/TLS certificates for your applications and services. It is free and provides persistent storage for your certificates. With the IBM Cloud Certificate Manager service, you can [order free certificates](https://cloud.ibm.com/docs/certificate-manager?topic=certificate-manager-ordering-certificates), [import your certificates](https://cloud.ibm.com/docs/certificate-manager?topic=certificate-manager-managing-certificates-from-the-dashboardimporting-a-certificate), and [enable notifications for expiring certificates](https://cloud.ibm.com/docs/certificate-manager?topic=certificate-manager-configuring-notifications).
3. Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
4. Install the latest certificate manager CLI plug-in with the following command:

ibmcloud plugin install hpcs-cert-mgr
Unless otherwise noted in the [Release notes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-release-notes-saas-20), these upgrades are optional, but recommended. You cannot upgrade nodes that have been imported into the console.

The best practice is to apply upgrades to one node at a time. While the upgrade is being applied, the node is unavailable to process requests or transactions. Therefore, to avoid any disruption of service, whenever possible you should ensure another node of the same type is available to process requests. Upgrading a node takes about a minute to complete and when the update is complete, the node is ready to process requests.

For information about how to upgrade a node, check out [Upgrading to the latest version of Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-upgrade).





 Kubernetes cluster expiration 

If you are using a free IBM Cloud Kubernetes service cluster, it will expire after 30 days. When this happens, you can no longer access your console. All of the associated nodes and certificates are deleted as well. You can have only one free cluster at a time. Therefore, before you can create another blockchain service instance, you need to ensure that the expired cluster and its associated service instance have been deleted from IBM Cloud. To confirm if they have already been deleted or to manually delete these resources, follow these steps:



1. In your IBM Cloud dashboard, click the menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/icons/icon_hamburger.svg) and open the Resource List.
2. Scroll to the Services twistie and expand it to view your service instance.
3. If your instance is listed, click the action menu for the service instance, then Delete, to delete this service instance.
4.
For more information on supported operating systems, see the [Bare metal to bare metal migration supported operating systems](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-p-p-migration-bare-metal-overviewp-p-migration-bare-metal-supported-os).





 How does RackWare handle bare metal servers with NIC bonding? 

The RMM migration tool does support migration over the bonded interface for classic to classic migration as well as on-premises to VPC migration. User intervention is not needed for migration with bonded interface.





 Is RMM a free service? 

RackWare RMM is a Bring-Your-Own-License (BYOL) subscription-based service. Contact the RackWare sales team or see [Order a license](https://cloud.ibm.com/cloud-infrastructure?topic=cloud-infrastructure-p-p-migration-bare-metal-overviewp-p-migration-bare-metal-ordering-license) for bare metal to bare metal migration.





 Mounted file system or storage did not show up on target automatically? 

Make sure to have /etc/fstab/entry for automatic mounting of any file system at the target server.





 Is it necessary to add RMM SSH key to source and target server? 

Yes, RMM uses SSH to communicate to both the source and target servers.





 Where can I find IBM Cloud documentation about classic bare metal to classic bare metal migration? 

For more information, see [IBM Cloud classic bare metal to bare metal migration overview](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-p-p-migration-bare-metal-overview).





 Who do I reach out for support? 



1. Open any issues directly with RackWare support team. The support team is available 365x24x7.
2. Open a case by using the following options:

a. Email: [support@rackwareinc.com](mailto:support@rackwareinc.com)

b. Phone: +1 (844) 797-8776

c.
Private subnet 'xyz' must have at least 'n' free IP addresses. The selected private subnet does not have any free IP addresses. Check these [troubleshooting steps](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-load-balancer-provisioning-troubleshooting) for more information. 
 Specified private subnet VLAN is on router 'xyz'. However, no public subnet with 'n' free IPs was found with VLAN on the same router. This happens because you selected the Allocate from public subnet from this account option during provisioning. Select Allocate from IBM System Pool instead, or contact IBM Support. 
 Given new description must be a string. You might have entered an invalid description. Enter a valid load balancer description, no larger than 255 characters. 
 A billing item is required to process a cancellation for load balancer uuid=aaaa-bbbb-cccc-dddd. Billing information is missing or invalid for your account, and the load balancer cannot be cancelled. Contact IBM Support. 
 An internal error occurred. Data could not be retrieved. Metrics data cannot be retrieved Reload the page. If the issue still persists, then contact IBM Support. 
 Front-end port must be an integer between 1 and 65535 excluding the range 56500-56520. You might have entered a front-end port number between 56500-56520. Enter a unique port number between 1 to 65535, excluding the range of 56500 to 56520. 
 Back-end port must be an integer. You might have entered an invalid back-end port value. Enter a back-end port number between 1 and 65535. 
 Back-end port must be an integer between 1 and 65535 excluding the range 56500-56520. You might have entered a back-end port between 56500 and 56520. Enter a back-end port number between 1 and 65535, excluding the range of 56500 to 56520. 
 Backend protocol HTTP is not compatible with frontend protocol TCP.
See [About DNS Services](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-about-dns-services) for details.

When you specify this DNS server, you must also create a VPN route after the VPN server is provisioned, with destination 161.26.0.0/16 and the translate action.





 VPN server provisioning considerations 

Consider the following when provisioning a VPN server.



 Client IPv4 address pool 

When you create a VPN server, you are prompted for a client IPv4 address pool (CIDR range). The client is assigned an IP address for its session from this address pool. Keep in mind that the client IP pool property must not overlap with VPC address prefixes. The VPN service validates the client IP address if the client IP pool overlaps with an existing address prefix.

Review the following requirements:



* Each active VPN client is assigned an IP address from a configurable IP pool. You must select the IP CIDR range carefully to make sure it does not overlap with the VPC prefix and personal device local CIDR.
* Depending on the use case, the client IP pool cannot overlap with a customer's local device IP address. The client IP pool also cannot overlap with the destination network; for example, if the VPN server is used to access the IBM Cloud classic network, the client IP cannot overlap with the IBM Cloud classic network.
* You must ensure that the block size is at least /22 (1024 free IP addresses). It is recommended to use a CIDR block that contains twice the number of IP addresses that are required to enable the maximum number of concurrent connections.







 Subnets: high-availability versus stand-alone mode 

When you create a VPN server, you can specify either high-availability or stand-alone mode.



* If you select high-availability mode, you must deploy the VPN server across two subnets in different zones. Use this mode for production deployments. Best for multi-zone deployments and solutions where client VPN access is critical.
* If you select stand-alone mode, you deploy the VPN server in a single subnet and zone.
Lifecycle for CentOS operating systems

 Operating system End of support 

 Stream 9 (available only on bare metal servers) [End of RHEL 9 full support phase](https://access.redhat.com/support/policy/updates/errataFull_Support_Phase). 
 Stream 8 (available only on bare metal servers) 31 May 2024 
 CentOS 8.x 31 December 2021 
 CentOS 7.9 30 June 2024 
 CentOS 6 30 November 2020 







 Citrix XenServer 

The following table describes the end of support date for Citrix XenServer operating systems. This guest OS is a free operating system. For more information, see [Citrix product matrix](https://www.citrix.com/support/product-lifecycle/product-matrix.html).



Table 3. Lifecycle for Citrix XenServer operating systems

 Operating system End of support 

 8.2 LTSR (available only on bare metal servers) 30 June 2025 







 Debian 

The following table describes the end of support date for Debian operating systems. This guest OS is a free operating system. For more information, see [Debian community](https://www.debian.org/).



Table 4. Lifecycle for Debian operating systems

 Operating system End of support 

 Debian 11 01 July 2024 
 Debian 10 01 June 2024 
 Debian 9 30 June 2022 







 OSNEXUS (QuantaStor) 

The following table describes the end of support date for OSNEXUS QuantaStor operating systems. This guest OS is a free operating system. For more information, see [OSNEXUS product notifications](https://wiki.osnexus.com/index.php?title=Product_EOL_Notifications).



Table 5. Lifecycle for OSNEXUS QuantaStor operating systems

 Operating system End of support 

 5.x (available only on bare metal servers) 30 April 2025 







 Red Hat Enterprise Linux (RHEL) 

The following table describes the end of support date for RHEL operating systems. This guest OS is a paid operating system.
Virtuozzo: Hardware Requirements 



*  You need at least 2 GB of RAM.



*  4 GB to 8 GB or more is recommended.
*  Virtuozzo alone, with no Containers, can use 2 GB (or more) of RAM depending on what processes are running.



*  4 GB of free disk space is recommended.
*  Network
[From your IBM Cloud Object Storage resource list](https://cloud.ibm.com/resources), select your IBM Cloud Object Storage instance and select the bucket that you specified in your PVC.
2. Select Access Policies > Authorized IPs and verify that the Cloud Service Endpoint source IP addresses of your VPC are displayed.



You can't read or write to your bucket from the console. You can only access your bucket from within an app pod on your cluster.
11. [Create a deployment YAML that references the PVC you created](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_appscreate-cos-deployment-steps).
12. Create the app in your cluster.

oc create -f app.yaml
13. Verify that your app pod is Running.

oc get pods | grep <app_name>
14. Verify that your volume is mounted and that you can read and write to your COS bucket.



1. Log in to your app pod.

oc exec -it <pod_name> bash
2. Verify that your COS bucket is mounted from your app pod and that you can read and write to your COS bucket. Run the disk free df command to see available disks in your system. Your COS bucket displays the s3fs file system type and the mount path that you specified in your PVC.

df

In this example, the COS bucket is mounted at /cos-vpc.

Filesystem 1K-blocks Used Available Use% Mounted on
overlay 102048096 9071556 87786140 10% /
tmpfs 65536 0 65536 0% /dev
tmpfs 7565792 0 7565792 0% /sys/fs/cgroup
shm 65536 0 65536 0% /dev/shm
/dev/vda2 102048096 9071556 87786140 10% /etc/hosts
[From your IBM Cloud Object Storage resource list](https://cloud.ibm.com/resources), select your IBM Cloud Object Storage instance and select the bucket that you specified in your PVC.
2. Select Access Policies > Authorized IPs and verify that the Cloud Service Endpoint source IP addresses of your VPC are displayed.



You can't read or write to your bucket from the console. You can only access your bucket from within an app pod on your cluster.
11. [Create a deployment YAML that references the PVC you created](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_appscreate-cos-deployment-steps).
12. Create the app in your cluster.

kubectl create -f app.yaml
13. Verify that your app pod is Running.

kubectl get pods | grep <app_name>
14. Verify that your volume is mounted and that you can read and write to your COS bucket.



1. Log in to your app pod.

kubectl exec -it <pod_name> bash
2. Verify that your COS bucket is mounted from your app pod and that you can read and write to your COS bucket. Run the disk free df command to see available disks in your system. Your COS bucket displays the s3fs file system type and the mount path that you specified in your PVC.

df

In this example, the COS bucket is mounted at /cos-vpc.

Filesystem 1K-blocks Used Available Use% Mounted on
overlay 102048096 9071556 87786140 10% /
tmpfs 65536 0 65536 0% /dev
tmpfs 7565792 0 7565792 0% /sys/fs/cgroup
shm 65536 0 65536 0% /dev/shm
/dev/vda2 102048096 9071556 87786140 10% /etc/hosts
To get the CRN of an instance, run [ibmcloud ks ingress instance ls --cluster CLUSTER](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_ingress_instance_ls).

--private-vlan PRIVATE_VLAN
: This parameter is not available for free clusters. If this standard cluster is the first standard cluster that you create in this zone, don't include this option. A private VLAN is created for you when the cluster is created. If you created a standard cluster before in this zone or created a private VLAN in IBM Cloud infrastructure before, you must specify that private VLAN. Private VLAN routers always begin with bcr (back-end router) and public VLAN routers always begin with fcr (front-end router). When you create a cluster and specify the public and private VLANs, the number and letter combination after those prefixes must match.
: To find out whether you already have a private VLAN for a specific zone or to find the name of an existing private VLAN, run ibmcloud ks vlan ls --zone ZONE.

--public-vlan PUBLIC_VLAN
: This parameter is not available for free clusters. If this standard cluster is the first standard cluster that you create in this zone, don't use this option. A public VLAN is created for you when the cluster is created. If you created a standard cluster before in this zone or created a public VLAN in IBM Cloud infrastructure before, specify that public VLAN. If you want to connect your worker nodes to a private VLAN only, don't specify this option. Private VLAN routers always begin with bcr (back-end router) and public VLAN routers always begin with fcr (front-end router). When you create a cluster and specify the public and private VLANs, the number and letter combination after those prefixes must match.
: To find out whether you already have a public VLAN for a specific zone or to find the name of an existing public VLAN, run ibmcloud ks vlan ls --zone ZONE.