vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can specify the user name in the provider block or retrieve the value from the IAAS_CLASSIC_USERNAME environment variable. 
 iaas_classic_endpoint_url Optional The API endpoint that you want to use to access IBM Cloud classic infrastructure. If this value is not specified, https://api.softlayer.com/rest/v3 is used by default. You can specify the URL in the provider block or retrieve the value from the IAAS_CLASSIC_ENDPOINT_URL. 
 iaas_classic_timeout Optional The number of seconds to wait until the classic infrastructure API is considered unavailable. The default values is 60. You can specify this information in the provider block or retrieve it from the IAAS_CLASSIC_TIMEOUT environment variable. 
 ibmcloud_api_key Required The IBM Cloud API key to authenticate with the IBM Cloud platform. For more information, about how to create an API key, see [Creating an API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). You can specify the API key in the provider block or retrieve the value from the IC_API_KEY or IBMCLOUD_API_KEY environment variables. If both environment variables are defined, IC_API_KEY takes precedence. 
 ibmcloud_timeout Optional The number of seconds that you want to wait until the IBM Cloud API is considered unavailable. The default value is 60. You can specify the timeout in the provider block or retrieve the value from the IC_TIMEOUT or IBMCLOUD_TIMEOUT environment variables. If both variables are specified, IC_TIMEOUT takes precedence. 
 function_namespace Required for Functions The IBM Cloud® Functions namespace that you want to use. The namespace is composed from your Cloud Foundry organization and space in the format <org>_<space>. You can specify the namespace in your provider block or retrieve the value from the FUNCTION_NAMESPACE environment variable. 
 generation Required for VPC infrastructure (Deprecated) The generation of Virtual Private Cloud infrastructure that you want to use. If this value is not specified, 2 is used by default.
- name: myNodejsapp
memory: 256M
disk_quota: 512M
path: /dev/myNodejsApp
buildpack: nodejs_buildpack
host: nodejs001
domain: mybluemix.net
command: node app.js
timeout: 80
services:
- mongo_8917
env:
env_type: production







 Environment variables 

Environment variables contain the environment information of a deployed app on IBM Cloud. Besides environment variables set by Diego and buildpacks, you can also set app-specific environment variables for apps on IBM Cloud.

You can view the following environment variables of a running IBM Cloud app by using the ibmcloud app env command or from the IBM Cloud user interface:



* User-defined variables that are specific to an app. For more information, see [Adding user-defined environment variables](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deployingappsud_env).
* The VCAP_SERVICES variable, which contains connection information to access a service instance. If your app is bound to multiple services, the VCAP_SERVICES variable includes the connection information for each service instance. For example:



{
"VCAP_SERVICES": {
"AppScan Dynamic Analyzer": [
{
"credentials": {
"bindingid": "0ab3162a-867e-4137-a2e7-39346a89472e",
"password": "xxxxxxxxxxxxxx"
},
"label": "AppScan Dynamic Analyzer",
"name": "AppScan Dynamic Analyzer-9q",
"plan": "standard",
"tags":
"Security",
"security",
"ibm_created"
]
}
],
"mysql-5.5": [
{
"credentials": {
"host": "23.246.200.38",
After you complete your changes, use the CLI to deploy the app to IBM Cloud again.

For example, run the following command in the root directory of the app:

ibmcloud cf push <varname><yourappname></varname>







 Access the VCAP_SERVICES environment 

To access the VCAP_SERVICES environment from a Node-RED flow, you must add the environment variable to the Function node's global context.



1. Edit your bluemix-settings.js and add an entry to the functionGlobalContext property to parse VCAP_SERVICES.
2. Redeploy your Node-RED app.

functionGlobalContext: { VCAP_SERVICES: JSON.parse(process.env.VCAP_SERVICES)}



After you redeploy Node-RED, you can access VCAP_SERVICES in a Function node as the context.global.VCAP_SERVICES variable.
The need to create a private connection between a remote network environment and servers on the private network of the IBM Cloud is a common requirement. Most typically this connectivity supports hybrid workloads, data transfers, private workloads or administration of systems on the IBM Cloud. A site-to-site Virtual Private Network (VPN) tunnel is the usual approach to securing connectivity between networks.

IBM Cloud provides a number of options for site-to-site data center connectivity, either using a VPN over the public internet or via a private dedicated network connection.

See [IBM Cloud® Direct Link ](https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-linkconfigure-ibm-cloud-direct-link) for more details on dedicated secure network links to the IBM Cloud. A VPN over the public internet provides a lower cost option, though without bandwidth guarantees.

There are two suitable VPN options for connectivity over the public internet to servers provisioned on the IBM Cloud:



* [IPSEC VPN](https://cloud.ibm.com/catalog/infrastructure/ipsec-vpn)
* [Virtual Router Appliance VPN](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-about-the-vravirtual-private-network-vpn-gateway)



This tutorial presents setup of a site-to-site IPSec VPN using a Virtual Router Appliance (VRA) to connect a subnet in a client data center to a secured subnet on the IBM Cloud private network.

This example builds on the [Isolate workloads with a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-secure-network-enclosuresecure-network-enclosure) tutorial. It uses a site-to-site IPSec VPN, GRE tunnel and static routing.
If both environment variables are defined, IC_API_KEY takes precedence. 
 ibmcloud_timeout Optional The number of seconds that you want to wait until the IBM Cloud API is considered unavailable. The default value is 60. You can specify the timeout in the provider block or retrieve the value from the IC_TIMEOUT or IBMCLOUD_TIMEOUT environment variables. If both variables are specified, IC_TIMEOUT takes precedence. 
 region Optional The IBM Cloud region where you want to create your resources. If this value is not specified, us-south is used by default. You can specify the region in the provider block or retrieve the value from the IBMCLOUD_REGION or IC_REGION environment variables. If both environment variables are specified, IC_REGION takes precedence. 
 resource_group Optional The ID of the resource group that you want to use for your IBM Cloud resources. To retrieve the ID, run ibmcloud resource groups. You can specify the resource group in the provider block or retrieve the value from the IC_RESOURCE_GROUP or IBMCLOUD_RESOURCE_GROUP environment variables. If both environment variables are defined, IC_RESOURCE_GROUP takes precedence. 



For more information on how to use environment variables, see [Using environment variables](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referenceenv-vars).

You can [add multiple provider configurations within the same Terraform on the IBM Cloud configuration file](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referencemultiple-providers) to create your IBM Cloud resources with different provider parameters. For example, you can multiple providers so that you can use different input parameters, such as different regions, zones, infrastructure generations, or accounts to create the IBM Cloud resources in your Terraform on IBM Cloud configuration file. For more information, see [Multiple Provider Instances](https://www.terraform.io/docs/language/providers/configuration.html).



 Option 1. Creating a static provider.tf file
domain: ng.mybluemix.net 
 host The host name of the app in IBM Cloud. This value must be unique in the IBM Cloud environment. host:host_name 
 name The app name in IBM Cloud. This value must be unique in the IBM Cloud environment. name: appname 
 path The location of your app. This value can be a relative path or absolute path. path:path_to_app 
 command The custom start command for your app, or the command to run script files. command:custom_commandcommand:bash ./run.sh 
 memory The amount of memory to allocate for the app. The default value is 1GB. memory: 512MB 
 instances The number of instances to create for your app. instances: 2 
 timeout The maximum amount of time in seconds that is used to start the app. The default value is 60 seconds. timeout: 80 
 no-route A Boolean value to prevent a route from being assigned to the app if the app is running in the background. The default value is false. no-route: true 
 random-route A Boolean value to assign a random route to the app. The default value is false. random-route: true 
 services The services to bind to the app. services: - mysql_maptest 
 env The custom environment variables for the app. env: DEV_ENV: production 







 A sample manifest.yml file 

The following example shows a manifest file for a Node.js app that uses the built-in community Node.js buildpack in IBM Cloud.

---
- name: myNodejsapp
memory: 256M
disk_quota: 512M
path: /dev/myNodejsApp
buildpack: nodejs_buildpack
host: nodejs001
domain: mybluemix.net
command: node app.js
timeout: 80
services:
- mongo_8917
env:
env_type: production







 Environment variables
It is also a challenge to meet data processing needs that will emerge with increased use of wireless technology and local 5G in medical equipment.

Satellite enables:
: Cloud platform services that were previously only available on cloud can be deployed and made available for use within the hospital environment.







 Communications use cases for Satellite 

This use case is applicable to the communications industry.



 Multi-access edge computing (MEC) platform support service 

Configure edge cloud distributed nationwide and use a single control point to remotely run and manage the platform for containerized applications and data.

Pain points:
: With the widespread adoption of 5G, increased edge cloud needs can be expected in the near future, where data must be processed close to users and devices.

Satellite enables:
: Edge cloud can be deployed to where it is needed to deliver platforms for running innovative new services using AI. Managed services can remotely support the edge cloud platform.







 Utilities use cases for Satellite 

This use case is applicable to the utilities industry.



 Expanding the use of smart meters with Satellite 

Deploy customer applications and IBM Cloud analytics services as managed services on the edge server that manages smart meters to not only manage electricity supply and demand but also deliver services tailored to specific regions and households.

Pain points:
: With the deregulation of the electricity industry, power companies must focus on providing added value and not simply supplying power. Power companies want to effectively use data collected from smart meters and use the data as a basis for delivering a diverse range of services.

Satellite enables:
: The various data collected from smart meters can be used in real time by applications. Use of management-free IBM Cloud services enables easier data processing. Applications distributed across multiple sites can be centrally managed.
Accessing the environment 

After a successful deployment, IBM Cloud Schematics provides an output log that lists all IP addresses of the created VPC and PowerVS instances. These IP addresses include: - An access host IP address that is the entry point to the whole landscape. - NFS, DNS, NTP server IP addresses. - PowerVS instance IP addresses for SAP HANA (management IP, backup IP, SAP system IP) - PowerVS instance IP addresses for SAP NetWeaver (management IP, backup IP, SAP system IP)

SAP solution provisioning as deployable architectures creates a secure and isolated environment. Network communication with the public internet and other landscapes that sit outside of the configured environment is prohibited. Opening the management network channel, for example, for the access with administrator laptop, is the step that must be done manually. In general, there a couple of options for such configuration:



1.  Open the VPN connection to the management VPC where access to the host is located.
2.  Add an additional IP address to the network access control list of the management VPC where the access host is located. For more information, see the steps in [Access to the environment](https://cloud.ibm.com/docs/powervs-vpc?topic=powervs-vpc-powervs-automation-solution-access).



After the configuration, you can connect to the landscape by using following SSH command:

ssh -A -o ServerAliveInterval=60 -o ServerAliveCountMax=600 -o ProxyCommand="ssh -W %h:%p root@<access_host_floating_ip>" root@<powervs_instance_ip>
Connection strings are displayed in the Endpoints panel of your deployment's Overview, and can also be retrieved from the [cloud databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-connections), and the [API](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026).

The information that you need to make a connection with mysql is in the "cli" section of your connection strings. The table contains a breakdown for reference.



Table 1. mysql/cli connection information

 Field Name Index Description 

 Bin The recommended binary to create a connection; in this case, it is mysql. 
 Composed A formatted command to establish a connection to your deployment. The command combines the Bin executable file, Environment variable settings, and uses Arguments as command-line parameters. 
 Environment A list of key/values you set as environment variables. 
 Arguments 0... The information that is passed as arguments to the command shown in the Bin field. 
 Certificate Base64 A self-signed certificate that is used to confirm that an application is connecting to the appropriate server. It is base64 encoded. 
 Certificate Name The allocated name for the self-signed certificate. 
 Type The type of package that uses this connection information; in this case cli. 





* 0... indicates that there might be one or more of these entries in an array.







 Connecting 

The ibmcloud cdb deployment-connections command handles everything that is involved in creating a command-line client connection. For example, to connect to a deployment named "example-mysql", use the following command.

ibmcloud cdb deployment-connections example-mysql --start

Or

ibmcloud cdb cxn example-mysql -s

The command prompts for the admin password and then runs the mysql command-line client to connect to the database.
The OS supported and deployed by IBM Cloud for running SAP HANA with HA/DR are:



* Red Hat Enterprise Linux (RHEL)
* SUSE Enterprise Linux Server (SLES)



The IBM Cloud environment does not support any preconfigured high availability (HA) scenarios. It does, however, let you implement HA solutions for SAP HANA through Red Hat Enterprise Linux HA extensions, in a similar manner to existing deployments using Traditional On-Premises data centers.

SAP HANA System Replication (HSR) is configured with an automated fail-over from one server to a replica, using various replication modes designed by SAP to fit:



* Different SAP Business Applications
* Different business risk acceptance of unplanned downtime
* Different infrastructure resiliency cost profiles



Refer to SAP documentation on SAP HANA System Replication (HSR) and OS vendor documentation on SAP HANA HA/DR; or consult SAP for recommendations on your landscape design for further clarity.

For more information on system replication, and network throughput and latency, see



* [How To Perform System Replication for SAP HANA - Version 5.4 January 2018](https://www.sap.com/documents/2017/07/606a676e-c97c-0010-82c7-eda71af511fa.html)
* [Network Configuration for SAP HANA System Replication](https://www.sap.com/documents/2016/06/18079a1c-767c-0010-82c7-eda71af511fa.html)
* [SAP Help - SAP HANA System Replication - SAP HANA Administration Guide for SAP HANA Platform](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/latest/en-US/676844172c2442f0bf6c8b080db05ae7.html)
* [SAP Help - SAP HANA System Replicatio Guide](https://help.sap.com/viewer/4e9b18c116aa42fc84c7dbfd02111aba/latest/en-US)
* Developer - Appropriate for all pre-production environments, and supports the same features and capacity as the Enterprise edition and is free.



For a full reference of SQL Server editions, refer to [Editions and supported features of SQL Server 2019 (15.x)](https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15).





 About Microsoft licensing 

IBM Cloud virtual servers can include Microsoft Windows operating system licenses. For more information, see [Stock images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-imagesstock-images). Microsoft Windows operating system Bring Your Own License (BYOL) cannot be used to provision public instances and can be used only to provision virtual server instances on dedicated hosts. For more information, see [BYOL for Windows operating systems](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-aboutbyol-vpc-windows).

For information on Microsoft SQL Server licenses, refer to [SQL Server 2019 licensing guide](https://download.microsoft.com/download/e/2/9/e29a9331-965d-4faa-bd2e-7c1db7cd8348/SQL_Server_2019_Licensing_guide.pdf).
* IBM Cloud File Storage for VPC add-on version 1.1
* Worker node fix packs 1.24.15_1574, 1.25.11_1550, 1.26.6_1542, and 1.27.3_1530.





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



* [27 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2723)



* Master fix packs 1.24.15_1573, 1.25.11_1549, 1.26.6_1541, and 1.27.3_1529.



* [26 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2623)



* CLI version 1.0.528.



* [23 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2323)



* Free cluster tier deprecation



* [22 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2223)



* Cluster autoscaler add-on version 1.0.9_44.
* Istio add-on version 1.17.3.



* [21 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2123)



* Block Storage for VPC add-on versions 5.0.16_127 and 5.1.11_126.



* [20 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jun2023)



* Worker node fix pack updates
ibmcloud plugin install vpc-infrastructure
ibmcloud plugin install code-engine

To see all the available plugins, run ibmcloud plugin repo-plugins and to install a plugin ibmcloud plugin install <PLUGIN_NAME>







 GitHub account 



1. Sign up for a free account at [https://github.com/](https://github.com/).
2. Create a new public repository at [https://github.com/new](https://github.com/new) to get familiar with GitHub.







 IBM Cloud GitLab 

IBM Cloud provides you with hosted Git repositories built on GitLab Community Edition and accessible with the same credentials used to log in IBM Cloud. It is recommended to configure your SSH public key to simplify the command line interactions with the Git repositories.



1. [Use these instructions](https://us-south.git.cloud.ibm.com/help/user/ssh.mdgenerate-an-ssh-key-pair) to generate a new SSH key pair if you don't have one.
2. [Add your SSH public key](https://us-south.git.cloud.ibm.com/help/user/ssh.mdadd-an-ssh-key-to-your-gitlab-account) to your Git settings in the region where you plan to host your Git repositories, such as [Dallas (us-south.git.cloud.ibm.com)](https://us-south.git.cloud.ibm.com/-/profile/keys), [London (eu-gb.git.cloud.ibm.com)](https://eu-gb.git.cloud.ibm.com/-/profile/keys) or [Frankfurt (eu-de.git.cloud.ibm.com)](https://eu-de.git.cloud.ibm.com/-/profile/keys).



To verify the configuration:



1.
The IBM Cloud® file service provides a [mount helper utility](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eitfs-mount-helper-utility) to automate the complex tasks of configuring and maintaining the connection. For more information, see [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit).





 16 June 2023 

VPC routing table authorizations
: You can use the new VPC routing table authorizations to allow users to administer VPC routing tables but not allow them to administer the broader VPC. Routing table operations were updated to check for these new authorizations, instead of the broader VPC authorizations. The VPC Administrator, Editor, Operator, and Viewer IAM access roles were updated so that users with those roles function as before. However, custom roles that require access to routing tables must be updated. For more information, see [IAM actions for VPC routing tables](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-actions-vpc-routing-tables).





 08 June 2023 

New stock images for bare metal servers
: The following stock images are now available for bare metal servers:



* CentOS 7.x is now supported as an image when you provision a bare metal server.
* CentOS Stream 9.x is now supported as an image when you provision a bare metal server. For more information, see [Bare metal server images](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-image).







 01 June 2023 

UI Enhancement to the List view
: You can now export table data with the current table column format. The supported export formats are CSV and Microsoft Excel.







 May 2023 



 30 May 2023 

File Storage for VPC file share activity tracker event name changes (beta)
About site-to-site VPN gateways 

You can use the IBM Cloud VPN for VPC service to securely connect your Virtual Private Cloud (VPC) to another private network. Use a static, route-based VPN, or a policy-based VPN to set up an IPsec site-to-site tunnel between your VPC and your on-prem private network or another VPC.

Route-based VPN is now available in addition to policy-based VPN. To get started, select Route-based as the mode when you create a VPN gateway and [create routes](https://cloud.ibm.com/docs/vpc?topic=vpc-create-vpc-route) by using the VPN connection type.



 VPN for VPC features 

The IBM Cloud VPN for VPC service includes the following features:

MD-5 and SHA-1 authentication algorithms, 2 and 5 DH groups, and the 3-DES encryption algorithm were deprecated on 20 September 2022 and are no longer supported in the UI. If you currently use these ciphers, you must [upgrade weak cipher suites on a VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers&interface=ui) before end of support is announced for use with the CLI and API.



* Authentication - IBM Cloud VPN for VPC supports a pre-shared key for Phase 1 peer authentication. Supported authentication algorithms for both phases include SHA-256, SHA-384, and SHA-512.
* Dead peer detection - Configurable mechanism to detect availability of an IPsec peer.
* Diffie-Hellman (DH) - Key exchange protocol used in Phase 1 to generate a shared secret key between VPN peers. Optionally, users can enable Perfect Forward Secrecy (PFS) and a DH group for Phase 2 IPsec negotiation. IBM Cloud VPN for VPC supports DH groups 14-24 and 31.
* Encryption - IBM Cloud VPN for VPC supports AES-128, AES-192, and AES-256 for data encryption during both IKE Phase 1 and Phase 2.