vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To buy an RHEL subscription, see [Red Hat Enterprise Linux Server](https://www.redhat.com/en/store/red-hat-enterprise-linux-ibm-power-little-endian).
2. To register your system, see [Quick Registration for RHEL](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/quick_registration_for_rhel/index).







 Capturing and importing an RHEL image 

To use RHEL within Power Systems Virtual Server, you can use the [IBM Power Virtualization Center (PowerVC)](https://www.ibm.com/support/knowledgecenter/en/SSXK2N_1.4.4/com.ibm.powervc.standard.help.doc/powervc_images_hmc.html) to capture your Linux image, then [import it](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-image) as an Open Virtualization Appliance (OVA) file. You must also bring your own license (BYOL). If you cannot use PowerVC to capture an image, see the [Power Systems OVA image capture](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-linux-deploymentvios-capture) instructions.





 Linux networking 

To connect a Linux virtual machine (VM) to the public internet, you must add a public network when you provision a Power Systems Virtual Server. You must set up a Linux-based Network Address Translation (NAT) gateway on a public-facing Linux VM if you have Linux VMs that do not need an internet-facing external IP address. For more information on NAT router, [Linux NAT Router Explained](https://www.slashroot.in/linux-nat-network-address-translation-router-explained).

When you are configuring a Source NAT (SNAT) gateway between your public and private networks, ensure that the TCP checksum offload option is disabled.
The subscription defines which Satellite configuration to deploy the Kubernetes resources to your clusters.



1. Select the configuration that you created to see the configuration details.
2. Click Create subscription.
3. Enter a name for your subscription and select the version name and the cluster group that you created earlier.
4. Click Create to create the subscription.



3. Select your subscription to see the subscription details and the rollout status of your Kubernetes resource deployment. If errors occur during the deployment, such as YAML files with formatting errors or unsupported API version values, you can view the error message in the Message column of your subscription details.







 (TO UPDATE WITH NEW COMMANDS:) Updating your Satellite Config with the CLI 

Use the CLI plug-in for Satellite commands to upload a new version file and change your subscription to use it.



1. Create a Version by uploading a Kubernetes resource file to your configuration. Make sure to specify the Kubernetes namespace where you want your resource to be deployed. If you do not specify a namespace, the resource is deployed to the razeedeploy namespace by default. Review the command options by running ibmcloud sat config version create.

To view the resources after they are created in the cluster through the Satellite Config dashboard, add the razee/watch-resource=lite label to the metadata.labels section of your YAML file or [choose another option to view your deployed resources](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resources), such as adding a ConfigMap to your cluster.

ibmcloud sat config version create --name <version_name> --config <config_name_or_ID> --file-format yaml --read-config <file_path>



Understanding this command's components

 Component Description 

 --name <version_name> Enter a name for your configuration version. 
 --config <config_name_or_ID> Enter the name or ID of the Satellite configuration that you created earlier.
Now that your Kafka event subscription, which references the kafka-receiver-job application, is created, use the kafka-sender-app to send message events to the receiver application.



1. Obtain the public URL of the destination app, kafka-sender-app by using the [ibmcloud ce app get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-get) command to find the URL of your app.

ibmcloud ce app get -n kafka-sender-app --output url

Example output

https://kafka-sender-app.abcdabcdabc.us-south.codeengine.appdomain.cloud
2. Run the Kafka event-producer app, kafka-sender-app to send events to the destination Code Engine job. Call the kafka-sender-app application with curl and specify values for the topic and the number of messages. Use the output of the ibmcloud ce app get command to find the public URL of your event-producing app. Be sure to wrap the value to curl in quotation marks to ensure that it is treated as a single string. For example,

curl "<public_URL_of_Kafka_sender_app>?topic=<your_topic_name>&num=<number_of_messages_to_produce>"

For example,

curl "https://kafka-sender-app.abcdabcdabc.us-south.codeengine.appdomain.cloud?topic=kafka-topic1&num=1"
3. View events in logs. When your Kafka event subscription is created with a broker, topics and an access secret that are valid, and you have a Kafka app that produces messages on that topic (such as kafka-sender-app), then you can see events in logs for your destination Code Engine job that receives Kafka messages, such as kafka-receiver-job.
--wait-timeout, --wto
: The length of time in seconds to wait for the cron event subscription to be deleted. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 15.





 Example 

ibmcloud ce subscription cron delete --name mycronevent -f





 Example output 

Deleting cron source 'mycronevent'...
OK







 ibmcloud ce subscription cron get 

Display details of a cron event subscription.

ibmcloud ce subscription cron get --name CRON_SOURCE_NAME [--output OUTPUT] [--quiet]



 Command Options 

--name, -n
: The name of the cron event subscription. This value is required.

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

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





 Example 

ibmcloud ce subscription cron get --name mycronevent





 Example output 

Getting cron source 'mycronevent'...
OK

Name: mycronevent
ID: abcdefgh-abcd-abcd-abcd-fb6be2347a14
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 18s
Created: 2021-03-14T13:33:53-05:00

Destination: App:kapp
Schedule: /2 * * * 
Time Zone: UTC
Ready: true

Events:
Type Reason Age Source Messages
ibmcloud ce secret create --name kafka-subscription-secret --from-literal password=abcdeH9tu3qE5Sn8VbJfcDEWtjR_l0iPisB3abcdefgh --from-literal username=token









 Creating a Code Engine app to send events 

Create a Code Engine app for connecting to your Event Streams instance and producing (sending) Kafka messages to a receiver of Kafka messages (Kafka consumer).



 Creating a Code Engine app to send events from the console 

To create the kafka-sender-app application from the console, complete the following steps.



1. [Create a Code Engine application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console) that is called kafka-sender-app with the following information.



1. Reference the icr.io/codeengine/kafka-sender container image for this app. This image is built from sender.go, which is available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/kafka). This sample sender app requires values for password and BROKERS.
2. In the Environment variables (optional) section, add the following environment variables.



1. Add a literal environment variable, BROKERS. For the value of this key, specify one or more of the broker hosts that are listed in the details of the service credentials in the Event Streams service instance.
2. Add another environment variable to [reference the full secret](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-ref-ui), kafka-subscription-secret. This secret contains the credentials for password.



3. (optional) In the Runtime settings section, specify 1 for the minimum number of instances so that the app always has an instance that is running and does not scale to zero. Configuring the app to always have a running instance is useful when you view logs.
Full Linux® subscription for Power Systems Virtual Servers 

The full Linux® subscription feature enables Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) support through IBM.

The full Linux subscription also provides, via activation keys, access to OS interim fixes and updates for Power servers hosted on an IBM satellite server within the IBM Cloud environment. Extra charges apply when setting up a Full Linux subscription account.

To register for the full Linux subscription, you must select one of the stock operating system (OS) images provided by IBM. IBM provides RHEL and SLES stock OS images for SAP and non-SAP applications. The following OS versions support a full Linux subscription:

SUSE:



* SLES 15 SP2 for SAP HANA (SLES15-SP2-SAP)
* SLES 15 SP2 for SAP NetWeaver (SLES15-SP2-SAP-NETWEAVER)
* SLES 15 SP3 for SAP HANA (SLES15-SP3-SAP)
* SLES 15 SP3 for SAP NetWeaver (SLES15-SP3-SAP-NETWEAVER)
* SLES 15 SP3 general purpose (SLES15-SP3)
* SLES 15 SP4 general purpose (SLES15-SP4)
* SLES 15 SP4 for SAP HANA (SLES15-SP4-SAP)
* SLES 15 SP4 for SAP NetWeaver (SLES15-SP4-SAP-NETWEAVER)



Red Hat:



* RHEL8.4 for SAP HANA (RHEL8-SP4-SAP)
* RHEL8.4 for SAP NetWeaver (RHEL8-SP4-SAP-NETWEAVER)
* RHEL 8.4 general purpose (RHEL8-SP4)
* RHEL 8.6 general purpose (RHEL8-SP6)
* RHEL8.6 for SAP HANA (RHEL8-SP6-SAP )
* RHEL8.4 for SAP NetWeaver (RHEL8-SP6-SAP-NETWEAVER)



The full Linux subscription feature OS filename starts with the Red Hat or Suse distribution name, RHEL... or SLES....
: Create the Kafka event subscription and wait for the subscription to be ready. If you specify the --wait option, the subscription create waits for a maximum time in seconds, as set by the --wait-timeout option, for the subscription to become ready. If the subscription is not ready within the specified --wait-timeout period, the Kafka event subscription create fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the Kafka event subscription to be ready. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 120.





 Example 

The following example creates a Kafka event subscription that is called mykafkaevent that forwards a Kafka event to a receiving app that is called kafka-receiver-app. Specify a --broker option for each broker for your topic. The --destination option specifies the Code Engine resource that receives the events. The kafka-subscription-secret provides credentials to access the message broker.
From the Event subscriptions page, click Create to create your subscription.
4. From the Create an event subscription page, select the Event Streams / Kafka tile to specify the event type.
5. For General, provide a name for the Event Streams / Kafka subscription. Click Next to proceed.
6. For Message broker details,



1. Specify the Kafka message broker hosts for the message queues from which messages are received as events through this subscription. To obtain information about the broker hosts, topics, and access credentials, view the service credential details for your service instance in the Event Streams console. For example, specify "broker-0-abcdabcdabcdabcd.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093", "broker-1-abcdabcdabcdabcd.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093" for the message broker hosts for the myeventstream-key service instance. You can find the brokers for the service instance in the Event Streams in the Kafka_brokers_sasl field.
2. Click Configure to configure access to the message broker. To authenticate from Code Engine to your Kafka or Event Streams instance, you need to provide a message broker access secret.



* You can create a new secret, choose an existing secret, or if credentials are not required to access the message brokers, then choose None.
* To create a secret, click Create. Provide a name for the secret, and values for username and password. The values for username and password must match the values in the service credentials for the Kafka or Event Streams instance. For example, the value for username is the value of user that is listed in the details of the service credentials in the Event Streams service instance. The value for password is the value of apikey that is listed in the details of the service credentials in the Event Streams service instance.
* For this example, use the existing kafka-subscription-secret secret that was previously created.



3.
ibmcloud event-notifications subscription delete 



* Action: Delete existing Subscription.

ibmcloud event-notifications subscription delete --id ID [--instance-id INSTANCE-ID] [--force]
* Parameters to provide:

--id ID (string)
: Unique identifier for subscription. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}/.

[--instance-id INSTANCE-ID] (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

[--force] (Boolean)
: Activate to force resource deletion (to bypass the confirmation prompt).







 ibmcloud event-notifications subscription update 



* Action: Update existing Subscription.

ibmcloud event-notifications subscription update --id ID [--name NAME] [--description DESCRIPTION] [--attributes ATTRIBUTES] [--instance-id INSTANCE-ID]
* Parameters to provide:

--id ID (string)
: Unique identifier for subscription. Required.

The maximum length is 36 characters. The minimum length is 36 characters.
This key is required for the sender sample, and to enable communications between the Code Engine Kafka event subscription and the Kafka message broker.







 Creating a secret with credentials required by the Kafka samples with the CLI 

To create the kafka-subscription-secret secret with the CLI, add a literal environment variable for password, and username. For more information, see [create a secret with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli).



* Specify the username key with the value of user that is listed in the details of the service credentials in the Event Streams service instance. For the Event Streams service instance, this value is token. This key is required for authentication between the Code Engine Kafka event subscription and the Kafka message broker.
* Specify the password key with the value of apikey that is listed in the details of the service credentials in the Event Streams service instance. This key is required for the sender sample, and to enable communications between the Code Engine Kafka event subscription and the Kafka message broker.

ibmcloud ce secret create --name kafka-subscription-secret --from-literal password=<value_of_apikey> --from-literal username=<value_of_user>

For example,

ibmcloud ce secret create --name kafka-subscription-secret --from-literal password=abcdeH9tu3qE5Sn8VbJfcDEWtjR_l0iPisB3abcdefgh --from-literal username=token









 Creating a Code Engine app to send events 

Create a Code Engine app for connecting to your Event Streams instance and producing (sending) Kafka messages to a receiver of Kafka messages (Kafka consumer).



 Creating a Code Engine app to send events from the console 

To create the kafka-sender-app application from the console, complete the following steps.



1.
To buy a SUSE subscription, see [How to Buy](https://www.suse.com/support/?id=SUSE_Linux_Enterprise_Server_for_SAP_Applicationshow-to-buy).
2. To register your system, see [Registering an Installed System](https://documentation.suse.com/sles/12-SP4/single-html/SLES-deployment/sec-y2-sw-register).







 Capturing and importing a SLES image 

To use SLES within the Power Systems Virtual Server, you can use the [IBM Power Virtualization Center (PowerVC)](https://www.ibm.com/support/knowledgecenter/en/SSXK2N_1.4.4/com.ibm.powervc.standard.help.doc/powervc_images_hmc.html) to capture your Linux image, then [import it](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-image) as an Open Virtualization Appliance (OVA) file. You must also bring your own license (BYOL). If you cannot use PowerVC to capture an image, see the [Power Systems OVA image capture](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-linux-deploymentvios-capture) instructions.





 Linux networking 

To connect a Linux virtual machine (VM) to the public internet, you must add a public network when you provision a Power Systems Virtual Server. You must set up a Linux-based NAT gateway on a public-facing Linux VM if you have Linux VMs that do not need an internet-facing external IP address. For more information, see [19.6 Basic Router Setup](https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-network.htmlsec-network-router) and [Linux NAT(Network Address Translation) Router Explained](https://www.slashroot.in/linux-nat-network-address-translation-router-explained).
8. For Summary, review the settings for your Kafka event subscription and make changes, if needed. When ready, click Create to create the Kafka subscription.







 Sending events to the receiving job from the console 

Now that your Kafka event subscription, which references the kafka-receiver-job job, is created, use the kafka-sender-app to send message events to the receiver job.



1. Start logging for the receiver job to [view job logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblogs-ui) to see events.
2. (optional) Start logging for the sender application to [view application logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-applogs-ui) to see information about events that are sent.
3. After logging is started, call the kafka-sender-app application with curl and specify the public URL of the kafka-sender-app, the name of your topic, and the number of messages to send. You can obtain the public URL of this application from the Domain mapping tab for your application. For example,

curl "<public_URL_of_Kafka_sender_app>?topic=<your_topic_name>&num=<number_of_messages_to_produce>"



Be sure to wrap the value to curl in quotation marks to ensure that it is treated as a single string.

When your Kafka subscription is created with a broker, topics and an access secret that are valid, and you have a Kafka job that produces messages on that topic (such as kafka-sender-app), then you can see events in logs for your Code Engine job that receives Kafka messages, such as kafka-receiver-job. When you use the Kafka receiver job (icr.io/codeengine/codeengine), search for CE_DATA in the logs for the receiver job to see the messages that are received.
For more information about the information that is included with the event, see [HTTP headers and body information for events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-header-body-cron).



 Subscribing to Periodic timer (cron) events for an application from the console 

You can create and update Periodic timer (cron) event subscriptions for an application from the console.

Before you begin



* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console). For example, create an application that is called myapp that uses the icr.io/codeengine/cron image. This image is built from cron.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cron).



Complete the following steps to create and update a Periodic timer (cron) event subscription for an application from the console.



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions.
3. From the Event subscriptions page, click Create to create your subscription.
4. From the Create event subscription page, complete the following steps.



1. For Event type, select the Periodic timer tile. Click Next.
2. For General, provide a name for the Periodic timer subscription, for example, myptimer. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
3.
To view the logs for the application that you created in the previous example,

ibmcloud ce application logs --application myapp

Example output

Getting logs for all instances of application 'myapp'...
OK

myapp-a2mvv-1-deployment-d97dcd6cf-zc9lg/user-container:
Listening on port 8080
2021-04-13 19:43:45 - Received:

Body: {"bucket":"mybucket","endpoint":"","key":"Notes.rtf","notification":{"bucket_name":"mybucket","content_type":"text/rtf","event_type":"Object:Write","format":"2.0","object_etag":"2944035e54ee1bdc423848c8eaf05e86","object_length":"4642","object_name":"NOtes.rtf","request_id":"6abc7123-382d-4115-98e8-7568b2cc03f8","request_time":"2021-04-13T19:43:36.610Z"},"operation":"Object:Write"}

Note that log information for apps lasts for only one hour. For more information about logging, see [Viewing logs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logs).

Looking for more code examples? Check out the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine).







 Subscribing to IBM Cloud Object Storage events for a job 

You can work with IBM Cloud Object Storage subscriptions from the console or with the CLI so events are sent to a Code Engine job.

When you create an event subscription for a job, a job run is created for each event that is triggered, and this job run has the environment variables that are related to the job.
Header: X-Forwarded-For=[172.30.118.174, 172.30.95.204, 172.30.163.42]
Header: X-Forwarded-Proto=[http]
Header: X-Request-Id=[ce502e5e-dd89-401e-a4cd-b72a6822f689]

Body: {"mydata":"hello world"}

For more information about headers and body, see [HTTP headers and body information for cron events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-header-body-cron).

For more information about viewing logs with the CLI, see [Viewing logs with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-logs-cli).

Note that subscriptions can affect how an application scales. For more information, see [Configuring application scaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scale).





 Step 5: Update your subscription 

Now that you know that your cron subscription is successful, you can update the cron event to run on a different schedule with the [ibmcloud ce sub cron update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-update) command. For example, update the subscription to run every day at midnight.

ibmcloud ce sub cron update -n cron-sub -d cron-app --data '{"mydata":"hello world again"}' -s '0 0 * * '

Run the ibmcloud ce sub cron get -n cron-sub command to find information about your subscription.

Example output

In this output, you can see that the schedule and data are updated.

Getting cron event subscription 'cron-sub'...
OK

Name: cron-sub