vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Replace SECRET_TOKEN_AS_IDENTIFIER with your chosen secret value. It is used to identify the event giver to the app.

ibmcloud ce subscription cron create --name ghstats-daily --destination ghstats-app --path /collectStats --schedule '0 6 * * ' --data '{"token":"SECRET_TOKEN_AS_IDENTIFIER"}' --content-type application/json
2. To make the secret token know to the app, [update the app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update). Replace SECRET_TOKEN_AS_IDENTIFIER with the value you picked at the previous step.

ibmcloud ce app update --name ghstats-app --registry-secret usicr --env EVENT_TOKEN=SECRET_TOKEN_AS_IDENTIFIER

This creates a new app revision. You can check that the events were received and processed by the app when navigating in the app to Administration, then System log.

The command above creates a schedule for 6 am UTC daily. To directly check that the eventing works, choose a time few minutes after your current time, converted to UTC.







 Step 7: Conclusions 

In this tutorial, you deployed a serverless app in IBM Cloud Code Engine. The app source is taken from a GitHub repository. You instructed Code Engine to build the container image and store it in the IBM Cloud® Container Registry. Next, it was pulled from there and deployed as container. The app is bound to IBM Cloud services.

The app and the associated eventing allow to automatically retrieve traffic data for GitHub repositories. Information about those repositories, including the tenant-specific access token, is stored in a SQL database (Db2® Warehouse on Cloud). That database is used by the Python app to manage users, repositories and to present the traffic statistics. Users can see the traffic statistics in searchable tables or visualized in a simple line chart (see image below).
Outputs:

ibm1_private_ip = "10.1.0.4"
ibm1_public_ip = "52.116.140.202"
test_info = "curl 52.116.140.202:3000/info"
test_remote = "curl 52.116.140.202:3000/remote"

Try the two curl commands (test_info, test_remote) that were suggested above. Copy the statements from your output.

curl 52.116.140.202:3000/info

The first one results in something like what was captured below:

{
"req_url": "/info",
"os_hostname": "widget0-application1-vsi",
"ipArrays": [

"10.1.0.4"
]
]
}

Then try the second command (from your output):

curl 52.116.140.202:3000/remote

Wait, that second curl command did not work! Fix it in the next step. Remember these curl commands, you will use them again shortly.







 Step 6: Create Transit Gateway 

IBM Cloud Transit Gateway is a network service used to interconnect IBM Cloud VPC resources providing dynamic scalability, high availability and peace of mind that data isn’t traversing the public internet. Earlier the CIDR blocks for each of the VPCs were chosen without overlap to allow Transit Gateway to route packets by IP address.



1. Change directory and become a member of the network group (use the existing API key):

cd ../network
source local.env
2. Optionally investigate the terraform files. Open the main.tf file and you will notice the Transit Gateway resources (ibm_tg). Each has a count = var.transit_gateway ? 1 : 0. This is a Terraform construct that creates an array of resources of length 1 or 0 based on the value of transit_gateway. An array of length 0 will result in no resource. For example:

resource "ibm_tg_gateway" "tgw"{
vsphere-csi-driver change log 

Review the version history for the vsphere-csi-driver Satellite storage template.



  Version 2.5.1 



  Revision 6, released 20 February 2023 



*  Adds the vmware-system-csi namespace resource explicitly.
Calico configuration N/A N/A Calico configuration now sets container network sysctl tuning for net.ipv4.tcp_keepalive_intvl to 15, net.ipv4.tcp_keepalive_probes to 6 and net.ipv4.tcp_keepalive_time to 40. 
 Cluster health image v1.3.16 v1.3.17 Updated Go to version 1.19.7 and updated dependencies. 
 GPU device plug-in and installer 79a2232 a873e90 Updated Go to version 1.19.6. 
 IBM Calico extension 1308-amd64 1366-amd64 Updated to resolve [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916). 
 IBM Cloud Block Storage driver and plug-in v2.3.7 v2.4.0 Removed ExpandInUsePersistentVolumes feature gate. 
 IBM Cloud Controller Manager v1.24.10-10 v1.24.12-1 Updated to support the Kubernetes 1.24.12 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 427 429 Updated universal base image (UBI) to resolve CVEs. Updated Go to version 1.19.6 and updated dependencies. 
 Key Management Service provider v2.6.3 v2.6.4 Updated Go to version 1.19.7 and updated dependencies. 
 Kubernetes v1.24.10 v1.24.12 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.12). 
 Load balancer and load balancer monitor for IBM Cloud Provider 2383 2420 Updated the image to resolve CVEs. 







 Change log for worker node fix pack 1.24.12_1560, released 27 March 2023 

The following table shows the changes that are in the worker node fix pack 1.24.12_1560.
SID: 3
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE

Timeouts:

Recovery Timeout: 5
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15

CHAP:

username: IBM02SU1575811-I117305979
password: 
username_in: <empty>
password_in: 

Negotiated iSCSI params:

HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 262144
MaxXmitDataSegmentLength: 65536
FirstBurstLength: 65536
MaxBurstLength: 65536
ImmediateData: Yes
InitialR2T: No
MaxOutstandingR2T: 1

Attached SCSI devices:

Host Number: 3 State: running
scsi3 Channel 00 Id 0 Lun: 1 match the "Lun: 1" here to the LUN ID.
Attached scsi disk sdd State: running
Show more







 Viewing the LUN ID in Windows® 



1. In PowerShell, issue the command iscsicli SessionList| findstr /c:"Device Number" /c:"Location" /c:"Target Portal". The output shows the IP address and the LUN ID. In the example, the IP address is 10.201.174.123 and the LUN ID is LUN 0.

C:UsersAdminisitrator>iscsicli SessionList| findstr /c:"Device Number" /c:"Location" /c:"Target Portal"
Target Portal : 10.201.174.124/3260
Device Number : 3
Location : Bus Number 0, Target Id O, LUN 0
Target Portal : 10.201.174.123/3260
Device Number : 4
Location: : Bus Number 0, Target ID 1, LUN 0
2.
* [14 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june1419)



* kubectl troubleshooting
* Tutorials landing page
* Using existing subnets to create a cluster



* [12 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june1219)



* Aggregating cluster roles



* [7 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0719)



* Access to the Kubernetes master through the private cloud service endpoint
* IBM Cloud® Direct Link
* Ingress ALB change log



* [6 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0619)



* Fluentd change log
* Ingress ALB change log



* [5 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0519)



* CLI reference



* [4 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0419)



* Version change logs



* [3 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0319)



* Bringing your own Ingress controller
* IBM Cloud Object Storage
* Ingress ALB change log
* Kustomize
* Razee





* [May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may19)
Average time spent acquiring locks in microseconds total_average 

Average time spent acquiring locks in microseconds



Table 2: Average time spent acquiring locks in microseconds metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_locks_time_acquiring_microseconds_total_average 
 Metric Type gauge 
 Value Type second 
 Segment By Service instance 







 Average time spent acquiring locks in microseconds W_average 

Average time spent acquiring locks in microseconds



Table 3: Average time spent acquiring locks in microseconds metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_locks_time_acquiring_microseconds_W_average 
 Metric Type gauge 
 Value Type second 
 Segment By Service instance 







 Connections 

The number of connections to the database.



Table 4. Connections metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_connections 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Disk read latency mean 

Disk read latency mean



Table 5: Disk read latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_disk_read_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Disk write latency mean 

Disk write latency mean



Table 6: Disk write latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_disk_write_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 IO utilization in percent 5 minute average 

How much disk I/O has been used over 5 minutes as a percentage of total disk I/O available.



Table 7. IO utilization in percent 5 minute average metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mongodb_disk_io_utilization_percent_average_5m 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 IO utilization in percent 15 minute average 

How much disk I/O has been used over 15 minutes as a percentage of total disk I/O available.
1.0.516 16 May 2023 <br><br>1. Updates sat storage template command outputs to include storage template provider details. /n 2. Updates the help text in various languages.<br><br><br> 
 1.0.498 1 Mar 2023 Adds the --host-link-agent-endpoint option to the host attach command. 
 1.0.487 24 Jan 2023 Adds host-link-agent-endpoint option to host attach script. 
 1.0.480 14 Dec 2022 Updates ibmcloud sat config create and ibmcloud sat subscription create commands to support new options for GitOps. 
 1.0.454 3 Oct 2022 Adds the --operating-system option for the cluster create commands. 
 1.0.452 21 Sept 2022 Updates the help text in various languages. 
 1.0.446 12 Sept 2022 Adds --pod-network-interface-selection option to location create flow. 
 1.0.433 5 Aug 2022 Updates the help text in various languages. 
 1.0.426 6 Jul 2022 <br><br>1. Adds the ibmcloud sat key commands, allowing you to view and manage your Satellite Config keys. /n 2. Adds the ibmcloud sat subscription identity set command, which updates a Satellite subscription to use your identity to manage resources.<br><br><br> 
 1.0.422 20 Jun 2022 <br><br>1. Makes the template-version option optional for the ibmcloud sat storage config create command. /n 2. Updates the output of the ibmcloud sat storage template ls and ibmcloud sat storage template get commands to specify if a version is deprecated or the current default template version.<br><br><br> 
 1.0.420 15 Jun 2022 <br><br>1. Adds the new ibmcloud sat storage config param set command. /n 2. Updates the ibmcloud sat storage template get command output to indicate whether a storage config is mutable.<br><br><br>
Message: The configuration can't be saved because it is read-only.





 BXNUI2013E 

Message: A class wasn't created from the "{0}" configuration because of an error.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2014E 

Message: The class name is not in the "{0}" configuration.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2015E 

Message: The attempt to log in failed because the cloud controller URL is formatted incorrectly.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2016E 

Message: The resource metadata could not be loaded.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2017E 

Message: The resource metadata could not be saved.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2018E 

Message: The metadata for the "{1}" starter didn't have the required "{0}" property.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2019E 

Message: The template metadata specified an unknown source control management type of "{0}".

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2020E 

Message: The "{0}" resource doesn't exist.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2021E 

Message: The "{0}" starter directory doesn't exist.
Check whether Event Notifications are configured for each of the supported Services SI-2(a) and SI-5(a) The rule was removed. 
 Check whether App ID email verification is enabled for Cloud Directory users IA-5(a) The rule was added. 







 Version 1.2.0 

The following rules were updated in the IBM Cloud for Financial Services library and profile as of 20 April 2023.



Table. Summary of the changes for version 1.2.0 of the IBM Cloud for Financial Services profile

 Rule Associated controls Update 

 Check whether DevSecOps Toolchain scans source code and their dependencies to identify vulnerabilities CM-10(1)(0), CM-3(2)(0), CM-4(0), CM-4(1)(0), CM-7(1)(a), RA-5(1)(0), RA-5(2)(0), RA-5(3)(0), RA-5(a), RA-5(b), RA-5(c), RA-5(d), SA-10(e), SA-15(a), SA-3(a), SA-3(d), SA-8(0), SI-2(2)(0), SI-2(a), SI-2(b), SI-2(c), and SI-2(d) Rule was added 
 Check whether DevSecOps Toolchain passes unit tests to validate all code changes CM-3(2)(0), SA-15(a), SA-8(0), SI-2(2)(0), SI-2(a), SI-2(b), and SI-2(d) Rule was added
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 798M 660K 798M 1% /run
/dev/vda2 99G 1.6G 93G 2% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/vda1 240M 73M 155M 33% /boot
fsf-dal2433a-dz.adn.networklayer.com:/nxg_s_voll_246a9cb9-4679-4dc5-9522-4a7ed2575136 190G 384K 190G 1% /mnt/test
tmpfs 798M 0 798M 0% /run/user/0
5. Go to the mount point to create a test file and list all files to verify that the share is mounted as read/write.

touch /mnt/test/test.txt
ls -al /mnt/test

$ touch /mnt/test/test.txt
ls -al /mnt/test
total 12
drwxr-xr-x 2 nobody nobody 4096 Apr 8 15:52 .
dr-xr-xr-x. 22 root root 4096 Apr 8 14:30 ..
-rw-r--r-- 1 nobody nobody 0 Apr 8 15:52 test.txt

The files are created by root and have an ownership of nobody:nobody. To display the ownership correctly, update idmapd.conf with the correct domain settings. For more information, see [How to implement no_root_squash for NFS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-mount-centosfs-CentOS-norootsquash).
6. Mount the remote file share on start.
kube-dal12-crb2f60e9735254ac8b20b9c1e38b649a5-w33 169.xx.210.102 10.xxx.xx.xxx b3c.4x16.encrypted normal Ready dal12 1.26
3. List the VLAN subnets for each unique network ID.

ibmcloud sl subnet list | grep -e <networkID1> -e <networkID2>

Example output

ID identifier type network_space datacenter vlan_id IPs hardware virtual_servers
1234567 169.xx.210.xxx ADDITIONAL_PRIMARY PUBLIC dal12 1122334 16 0 5
7654321 169.xx.178.xxx ADDITIONAL_PRIMARY PUBLIC dal10 4332211 16 0 6
4. Retrieve the subnet address. In the output, find the number of IPs. Then, raise 2 to the power of n equal to the number of IPs. For example, if the number of IPs is 16, then 2 is raised to the power of 4 (n) to equal 16. Now get the subnet CIDR by subtracting the value of n from 32 bits. For example, when n equals 4, then the CIDR is 28 (from the equation 32 - 4 = 28). Combine the identifier mask with the CIDR value to get the full subnet address. In the previous output, the subnet addresses are:



* 169.xx.210.xxx/28
* 169.xx.178.xxx/28





* Individual worker node IP addresses: If you have a small number of worker nodes that run only one app and don't need to scale, or if you want to add only one worker node, list all the worker nodes in your cluster and note the Public IP addresses. If your worker nodes are connected to a private network only and you want to connect to IBM Cloud services by using the private cloud service endpoint, note the Private IP addresses instead. Only these worker nodes are added. If you delete the worker nodes or add worker nodes to the cluster, you must update your allowlist accordingly.
The following entries to /etc/fstab mount the file systems after their mount points (/hana/data, /hana/log and /hana/shared) have been created:

/dev/mapper/hana_log_vg-hana_log_lv /hana/log xfs defaults,swalloc,nobarrier,inode64
/dev/mapper/hana_vg-hana_shared_lv /hana/shared xfs defaults,inode64 0 0
/dev/mapper/hana_vg-hana_data_lv /hana/data xfs defaults,largeio,swalloc,inode64 0 0









 Sample storage configurations on IBM Power Infrastructure 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

The following sections demonstrate storage configurations in various different SAP workload scenarios, when you are using IBM Power Infrastructure.

When you create new storage volumes, keep the following points in mind:



* Different storage tiers differ



* For SAP HANA, only Tier 1 storage is supported.
* For SAP NetWeaver, the Tier 1 and Tier 3 storage cannot be mixed.



* After you provision the storage with Affinity, you cannot change it. Carefully plan your storage layer and make sure that your configuration is correct. Affinity prevents issues with new volume discovery on existing virtual servers.
* When you finish provisioning new volumes, you can toggle bootable and sharing switches.
* Make volumes that belong to different OS file systems unique sizes. Otherwise, it is difficult to identify the storage volumes within the operating system.





 Sample storage configuration for SAP NetWeaver that use the IBM Power Virtual Server 

Table 1 is a sample storage configuration for a IBM Power Systems Virtual Server for SAP NetWeaver on Linux.

The storage can't be combined within one IBM Power Systems Virtual Server; it must be either Tier 1 or Tier 3. When you provision the Linux server, you automatically get the standard LVM configuration for the root volume group. These file systems are included in table 1. Disk sizes depend on whether the installation is Greenfield, or whether the server is a copy of an on-premises AIX server that you decided to use as a sizing reference.
* The [CDI 1.2](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingstand_alone_apps) implicit bean archive scanning feature is disabled by default when deploying WAR or EAR files.
* To reduce the droplet size, the [App Management utilities](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management)devconsole and shell, require a restage operation instead of a restart.
* The IBM JRE's shared class cache is disabled as it was not being reused in the IBM Cloud environment.









 15 October 2015 

Updated Node.js buildpack v2.6-20151006-1309
: This release of the Node.js buildpack features the integration of [StrongLoop Process Manager](https://strong-pm.io) to the App Management feature. For more information, see the blog post [StrongLoop DevOps for Node.js Apps on IBM Cloud](https://www.ibm.com/blogs/cloud-archive/2015/10/strongloop-devops-on-bluemix/).





 18 September 2015 

Updated Liberty buildpack v2.0-20150914-1535
: The buildpack introduces two major changes:



* The default configuration for WAR and EAR files enables Java EE 7 Web Profile features instead of Java EE 6 Web Profile features.
* The default Java version is version 8 instead of version 7.
* Refer to the [Upcoming Liberty for Java buildpack changes](https://www.ibm.com/blogs/cloud-archive/2015/09/upcoming-liberty-for-java-buildpack-changes/) blog post for details about these changes and how they may affect your app.
* The buildpack also introduces app_state configuration option to disable the appstate feature via the JBP_CONFIG_LIBERTY environment variable. The appstate feature integrates with the Cloud Foundry health check process to ensure the Liberty app is fully initialized before the app can receive HTTP requests.
Install the Helm chart to your cluster with the updated config.yaml file.

If you have multiple VPN deployments in a single cluster, you can avoid naming conflicts and differentiate between your deployments by choosing more descriptive release names than vpn. To avoid the truncation of the release name, limit the release name to 35 characters or less.

helm install vpn iks-charts/strongswan -f config.yaml
4. Check the chart deployment status. When the chart is ready, the STATUS field near in the output has a value of DEPLOYED.

helm status vpn
5. After the chart is deployed, verify that the updated settings in the config.yaml file were used.

helm get values vpn



Only strongSwan Helm chart versions that were released in the last 6 months are supported. Ensure that you consistently [upgrade your strongSwan Helm chart](https://cloud.ibm.com/docs/containers?topic=containers-vpnvpn_upgrade) for the latest features and security fixes.







 Testing and verifying strongSwan VPN connectivity 

After you deploy your Helm chart, test the VPN connectivity.



1. If the VPN on the on-premises gateway is not active, start the VPN.
2. Set the STRONGSWAN_POD environment variable.

export STRONGSWAN_POD=$(kubectl get pod -l app=strongswan,release=vpn -o jsonpath='{ .items[0].metadata.name }')
3. Check the status of the VPN. A status of ESTABLISHED means that the VPN connection was successful.

kubectl exec $STRONGSWAN_POD -- sudo ipsec status

Example output

Security Associations (1 up, 0 connecting):
k8s-conn[1]: ESTABLISHED 17 minutes ago, 172.30.xxx.xxx[ibm-cloud]...192.xxx.xxx.xxx[on-premises]
* IBM Cloud Object Storage plug-in



* [13 January 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan1321)



* Istio add-on



* [06 January 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan0622)



* Block Storage for VPC add-on.
* Kubernetes Service 1.20 end of support date change



* [4 January 2022](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan422)



* Worker node fix pack update





* [December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec21)



* Review the release notes for December 2021.
* [20 December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec2021)



* Deprecated and unsupported Kubernetes versions



* [14 December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec1421)



* Istio add-on



* [7 December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec721)



* Istio add-on
* Master fix pack update



* [6 December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec621)



* Worker node fix pack update



* [2 December 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec221)



* Kubernetes Service default version update.