vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Existing applications and jobs continue to function normally. However, if you want to bind an additional service instance to an app or job, you must first delete any existing service bindings from that app or job. You can then re-create those service bindings with the improved service binding implementation. See [Integrating IBM Cloud services with service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-binding).







 February 2022 

Review the release notes for February 2022.



 24 February 2022 

Review the release notes for 24 February 2022.

CLI version 1.26.1 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 22 February 2022 

Review the release notes for 22 February 2022.

New region!
: Code Engine is supported in a new region: US East (us-east). See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).





 17 February 2022 

Review the release notes for 17 February 2022.

CLI version 1.26.0 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 10 February 2022 

Review the release notes for 10 February 2022.

CLI version 1.25.4 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 03 February 2022 

Review the release notes for 03 February 2022.

CLI version 1.25.3 released
Managing Liberty apps 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

App Management is a set of development and debugging utilities that can be enabled for your Liberty apps on IBM Cloud®.



 IBM Cloud console and CLI 



 Managing app through IBM Cloud console 

The IBM Cloud console provides the ability to start, stop and restart app from the Action tab on your app from the console.





 Managing the app by using the ibmcloud cf CLI 

You can also manage your app by using the command line. In the commands replace <myApp> with your app name.

To start the app:

ibmcloud cf start <myApp>

To stop an app:

ibmcloud cf stop <myApp>

To restart an app:

ibmcloud cf restart <myApp>







 App management by using an SSH shell session 

Apps can be managed and debugged after accessing the app by using the ssh command. This can be accomplished through IBM Cloud console and ibmcloud cf CLI.



 IBM Cloud console 

User can ssh into the app by using the IBM Cloud console. Navigate to the Runtime tab on your app and then click SSH to manage.





 Command Line CLI 

To use ssh to access your app from the command line use:

ibmcloud cf ssh <myApp>







 App Management utilities 



 Liberty utilities 



* [proxy](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementproxy)
* [noproxy](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementnoproxy)
* [hc](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementhc)
schematics 1.8.1 true
cloud-functions[wsk/functions/fn] 1.0.58 false
cloud-internet-services[cis] 1.14.2 true
code-engine[ce] 1.29.3 true
 ibmcloud dev --version
ibmcloud dev version 2.11.0
 java -version
openjdk version "17.0.2" 2022-01-18
IBM Semeru Runtime Open Edition 17.0.2.0 (build 17.0.2+8)
Eclipse OpenJ9 VM 17.0.2.0 (build openj9-0.30.0, JRE 17 Linux amd64-64-Bit Compressed References 20220128_115 (JIT enabled, AOT enabled)
OpenJ9 - 9dccbe076
OMR - dac962a28
JCL - 64cd399ca28 based on jdk-17.0.2+8)
 ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021
 mvn -version
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/IBM/maven
Java version: 17.0.2, vendor: IBM Corporation, runtime: /usr/local/jdk17
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.16.18-200.fc35.x86_64", arch: "amd64", family: "unix"
 gradle -version
Welcome to Gradle 7.4.2!
Here are the highlights of this release:
- Aggregated test and JaCoCo reports
- Marking additional test source directories as tests in IntelliJ
- Support for Adoptium JDKs in Java toolchains
For more details see https://docs.gradle.org/7.4.2/release-notes.html
IBM Cloud [provides buildpacks](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-available_buildpacks) supporting Java and Node.js among others. If you are using these languages and frameworks, you don't need to specify the buildpack when you deploy your app by using the command line interface. Because IBM Cloud is built on Cloud Foundry, the command defaults to these buildpacks.

If you use an external buildpack, when deploying your app you must specify the URL of the buildpack by using the -b option.



* To deploy Liberty server packages to IBM Cloud, use the following command from your source directory:

ibmcloud cf push

For more information about Liberty Buildpack, see [Liberty for Java](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-getting-started-liberty).
* To deploy Java Tomcat apps to IBM Cloud, use the following command:

ibmcloud cf push <appname> -b https://github.com/cloudfoundry/java-buildpack.git -p <app_path>
* To deploy WAR packages to IBM Cloud, use the following command:

ibmcloud cf push <appname> -p app.war

Or, you can specify a directory that contains your app files by using the following command:

ibmcloud cf push <appname> -p "./app"
* To deploy Node.js apps to IBM Cloud, use the following command:

ibmcloud cf push <appname> -p <app_path>

A package.json file must be in your Node.js app for the app to be recognized by the Node.js buildpack. The app.js file is the entry script for the app, and can be specified in the package.json file. The following example shows a simple package.json file:

{
"name": "MyUniqueNodejs01",
"version": "0.0.1",
"description": "A sample package.json file",
IBM Cloud Foundry buildpacks 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

IBM® Cloud Foundry buildpacks provide the runtime support for apps in the IBM Cloud Foundry environment. When you deploy an app to IBM Cloud® using IBM Cloud Foundry, IBM Cloud Foundry starts a buildpack that supports your app type. IBM Cloud provides Cloud Foundry buildpack support for Java EE, Node.js, ASP.Net, Swift, and other app types. You can use the buildpacks included with IBM Cloud to deploy apps and bind them to services.



*  Cloud Foundry

Cloud Foundry is an open source platform for app lifecycle automation. IBM Cloud Foundry is built on top of the open source Cloud Foundry platform as a service. Check out the [Cloud Foundry website](https://www.cloudfoundry.org/) to learn more about the Cloud Foundry platform.
*  Cloud Foundry App

A cloud foundry app or app, is any app intended to be instantiated by on one of the buildpacks provided by IBM Cloud Foundry.
*  Buildpack

A buildpack is a typically language specific package of software provided by IBM Cloud Foundry. When an app is deployed to the IBM Cloud a buildpack appropriate for the app is chosen. The buildpack provisions the runtime environment for the app. You can see the set of buildpacks provided by IBM Cloud Foundry by issuing the ibmcloud cf buildpacks command from the command line.
*  Runtime

A runtime is the set of software components which provide the execution environment for an app. The terms runtime and buildpack are sometimes used interchangeably. When a buildpack has completed deploying an app the runtime environment is established.
*  Starter

A starter is a simple app designed for a particular runtime. The starters provide templates or samples of the language and runtime specific app types. You can use a starter to begin development of more sophisticated apps.
*  Service

A service is an IBM Cloud provided facility which can be coupled with an app.
Using Terraform to configure Schematics 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud services to rapidly build complex, multitiered cloud environments following Infrastructure as Code (IaC) principles. Similarly, you can automate the provisioning, update, and deletion of your IBM Cloud Schematics Workspace and Actions instances using Terraform.

Looking for a managed Terraform on IBM Cloud solution? Try out [IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform language that you are familiar with, but you don't have to worry about setting up and maintaining the Terraform command-line and the IBM Cloud Provider plug-in. Schematics also provides predefined Terraform templates that you can install from the IBM Cloud catalog.

Before you begin, make sure that you have the [required access](https://cloud.ibm.com/docs/schematics?topic=schematics-access) to create and work with IBM Cloud Schematics Workspace.



 Example: Creating the Schematics Workspaces by using Terraform 

Complete the following steps to create the Schematics Workspaces by using Terraform:



1. Follow the [Terraform on IBM Cloud getting started tutorial](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform) to install the Terraform CLI and configure the IBM Cloud Provider Plug-in for Terraform. The plug-in abstracts the IBM Cloud APIs that are used to provision, update, or delete Schematics resources.
2. Create the Terraform configuration files named main.tf, terraform.tfvars, and versions.tf.

You can use the Terraform example Git URL https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-api-gateway. This example uses service instance to set up an API for an IBM Cloud service of your choice.
ibmcloud version 2.13.0+05fd406-2022-11-30T20:39:15+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.62 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.40.3 true
container-registry[cr] 1.0.5 true
container-service[kubernetes-service/ks] 1.0.480 false
cra 1.0.7 false
doi 0.4.1 false
schematics 1.12.5 true

 ibmcloud dev --version
ibmcloud dev version 2.16.0

 java -version
openjdk version "17.0.5" 2022-10-18
IBM Semeru Runtime Open Edition 17.0.5.0 (build 17.0.5+8)
Eclipse OpenJ9 VM 17.0.5.0 (build openj9-0.35.0, JRE 17 Linux amd64-64-Bit Compressed References 20221018_325 (JIT enabled, AOT enabled)
OpenJ9 - e04a7f6c1
OMR - 85a21674f
JCL - 32d2c409a33 based on jdk-17.0.5+8)

 ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021

 mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /opt/IBM/maven
Java version: 17.0.5, vendor: IBM Corporation, runtime: /usr/local/jdk17
Default locale: en_US, platform encoding: UTF-8
Provision a virtual server instance, install Teleport, and complete the Teleport configuration for unified access to your infrastructure.





 Before you begin 

Before you deploy and configure a bastion host into a virtual server instance running on the VPC reference architecture, make sure you have completed the following prerequisites:



* Acquire a Teleport Enterprise Edition license
* Configure a VPC like VPC 0 (Edge Network) in the architecture diagram



Zoom

![IBM Cloud for Financial Services reference architecture with bastion host](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/bastion-host/vpc-single-region-bastion.svg)

Figure 1. Single-region IBM Cloud for Financial Services reference architecture for VPC with bastion host





 Limitations 

The following limitations currently apply for the bastion host solution that is described:



* Windows is not supported.
* RDP is not supported.







 Step 1: Configure Object Storage 

Complete the following steps to configure Object Storage.



1. [Provision a IBM Cloud® Object Storage instance](https://cloud.ibm.com/objectstorage/create) with the Standard Plan.
2. Create a custom bucket for storing session recordings with the following configuration:



* Storage class set to Standard
* Resiliency set to Regional
* Location set to the region of your VPC
* [Retention](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable) set to 12 months



3. [Generate a new set of service credentials](https://cloud.ibm.com/docs/account?topic=account-service_credentials) with the [bucket permissions](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions) of Object Write access and the advanced option of Include HMAC Credentials enabled.
The [ibmcloud fn service bind](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_service_bind) command makes your IBM Cloud service credentials available to your Cloud Functions code at run time.

Example syntax

ibmcloud fn service bind SERVICE ACTION_NAME [--instance INSTANCE_NAME] [--keyname CREDENTIALS_NAME]

For example, to bind an IBM Watson Composer service to an action named hello, run the following command.

ibmcloud fn service bind composer hello --instance Composer-qp --keyname Credentials-1

Example output

Service credentials 'Credentials-1' from service 'Composer-qp' bound to action 'hello.
4. Verify that the credentials are successfully bound. The action that the service is bound to doesn't support any custom flags, but does support the debug and verbose flags.

ibmcloud fn action get hello parameters

Example output

ok: got action Hello World
{
"parameters": [
{
"key": "var1",
"value": "val1"
},
{
"key": "dog",
"value": "cat"
},
{
"key": "__bx_creds",
"value": {
"composer": {
"password": "Service password]",
"url": "Service url]",
"username": "Service username]",
"instance": "Composer-qp",
"credentials": "Credentials-1"
},
}
}
],
}

In this example, the credentials for the composer service, along with any other credentials for other service types belong to a parameter called __bx_creds. The action code can access the necessary information by getting the __bx_creds parameter.
Creating a custom Docker image for your action 

In a Dockerfile, you can specify a Cloud Functions base runtime image by using the FROM instruction. You can use the RUN instruction to specify dependencies and packages to install in your Docker image. For more information about creating a Dockerfile, see the [Dockerfile reference](https://docs.docker.com/engine/reference/builder/).

You can see a list of ibmfunctions Docker base images on [Docker Hub](https://hub.docker.com/u/ibmfunctions).

Cloud Functions limits app code to the maximum codeSize as described in the [Action Limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_actions).



1. Create a test directory on your Desktop and cd to it.

cd desktop; mkdir test; cd test
2. Create a Dockerfile in your test directory and open it in vim.

touch Dockerfile; vim Dockerfile
3. Press the i key to edit your Dockerfile.
4. Specify a Cloud Functions base image with the FROM argument in your Dockerfile.
5. Install any packages and dependencies by specifying them RUN argument followed by the installation commands for your dependencies.
6. Press ESC, then :wq and Enter to save and close your Dockerfile.

Example Dockerfile for installing Python dependencies

The following example uses ibmfunctions/action-python-v3.7 as a base image and installs the Python modules: matplotlib, pandas, and statsmodels.

FROM ibmfunctions/action-python-v3.7

RUN pip install 
--upgrade pip 
matplotlib 
pandas 
statsmodels
7. Build your custom Docker image.

docker build -t <dockerhub_username>/<repo_name>:<tag_name>
8.
Liberty features supported in IBM Cloud 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

The Liberty for Java runtime includes a subset of Liberty features. To use a feature that is not included in the runtime, see [Install Liberty features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-install-features). For a complete list of the features available in Liberty, along with Java EE versions and other information, see [Liberty features](https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/rwlp_feat.html).



 Cloud-specific features 

The following features are included and are specific to IBM Cloud:



* appstate-1.0
* appstate-2.0
* cloudAutowiring-1.0
* logAnalysis-1.0



A subset of the available features are enabled by default when deploying WAR or EAR files. See [Stand-alone apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingstand_alone_apps) for details.

The Liberty for Java runtime also makes some Liberty beta features available. These features are listed in [Using the beta features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_beta_features).





 Feature compatibility 

Some features that Liberty provides are not available in the Liberty for Java runtime because they are not applicable in the cloud environment.

Keep in mind that a server cannot load incompatible features, so be sure it is configured to enable only features that are compatible.
Setting up the IBM Cloud Schematics CLI 

Before you begin using the IBM Cloud® Schematics CLI to deploy IBM Spectrum LSF, review and complete the following prerequisites:



1. Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to the IBM Cloud CLI with your IBMid. If you have multiple accounts, you are prompted to select which account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. For more information, see [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id).
3. Install and set up the [IBM Cloud Schematics CLI plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin).
4. Make sure to generate your IBM Cloud API key. For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey).
5. Create the config.json file that represents the configuration parameters that you would like to use to build the Spectrum LSF cluster. To learn more about all the properties, see [Deployment values](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-deployment-values). You can view a sample configuration file [here](https://github.com/IBM-Cloud/hpc-cluster-lsf/blob/main/sample/configs/hpc_workspace_config.json).
For part numbers, see [Passport Advantage part numbers](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_2.0.0/about/part_numbers.html).
* You must have a supported version of OpenShift Container Platform that is installed by using IBM Cloud Kubernetes Service so that the managed OpenShift service is supported. For the list of supported versions, see [Supported OpenShift versions and platforms](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_2.0.0/install/supported_os.html).



* You must have permission as an administrator user on the cluster where you are installing the IBM Cloud Pak for Multicloud Management.
* You must have at least viewer access permission to the resource group that includes the cluster where you are installing IBM Cloud Pak for Multicloud Management. Ensure that this resource group exists in IBM Cloud and that the user ID that is used in the IBM Cloud Provider cloud connection has access to this resource group.









 Supported upgrade paths 

IBM Cloud Pak for Multicloud Management supports upgrading within the the main version. It does not support upgrading between main versions. For example, you cannot upgrade from Version 1.x to Version 2.x. The IBM Cloud Pak for Multicloud Management supported upgrade paths within the main version are:



* IBM Cloud Pak for Multicloud Management Version 1.2.0 to Version 1.3.0
* IBM Cloud Pak for Multicloud Management Version 1.3.0 to Version 1.3.1, 1.3.2
* IBM Cloud Pak for Multicloud Management Version 1.3.1 to Version 1.3.2







 Minimum hardware requirements 



 Worker Nodes CPU (Cores/Node) Memory (GB/Node) 

 Worker 4+ 16 32 







 Minimum storage requirements 

Mandatory: 240GB of persistent storage.





 Procedure 



 Step 1. Configure your installation environment 

From the Create tab on the Cloud Pak for Multicloud Management installation page in the IBM Catalog on IBM Cloud, specify where you want to install IBM Cloud Pak for Multicloud Management:

1.
ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
doi 0.3.3 false
schematics 1.7.2 false
cloud-functions[wsk/functions/fn] 1.0.58 false
cloud-internet-services 1.14.1 true
code-engine[ce] 1.26.0 true
container-registry 0.1.560 true
container-service[kubernetes-service] 1.0.372 false
cra 0.1.11 false

 ibmcloud dev --version
ibmcloud dev version 2.10.1

 java -version
openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
Eclipse OpenJ9 VM AdoptOpenJDK-11.0.11+9 (build openj9-0.26.0, JRE 11 Linux amd64-64-Bit Compressed References 20210421_975 (JIT enabled, AOT enabled)
OpenJ9 - b4cc246d9
OMR - 162e6f729
JCL - 7796c80419 based on jdk-11.0.11+9)

 ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021

 mvn -version
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/IBM/maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: /usr/local/openjdk-11
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.18-200.fc35.x86_64", arch: "amd64", family: "unix"

 gradle -version
Setting up the CLI 

Install, update, and delete the required CLIs and set up your environment to use IBM Cloud® Code Engine.



 Supported environments for Code Engine CLI 

The Code Engine CLI supports the following environments:



* Linux 64 bit
* Linux 64 bit ARM
* Linux 32 bit
* Mac OS X 64 bit
* Mac OS X M1/ARM
* Windows 64 bit
* Windows 32 bit







 Installing the IBM Cloud CLI 

Install the latest version of the IBM Cloud CLI.

Before you begin

You must create an [IBM Cloud account](https://cloud.ibm.com/).



1. Download and install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

This installation includes the following files:



* IBM Cloud Functions plug-in
* IBM Cloud Object Storage plug-in
* IBM Cloud Container Registry plug-in
* IBM Cloud Kubernetes Service plug-in



For more information, see [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
2. Log in to the IBM Cloud CLI.

ibmcloud login
3. If you have more than one account, you are prompted to select which account to use. Follow the prompts or use the target command to select your IBM Cloud account.

ibmcloud target -c <account_id>
4. You must also specify a region. You can use the target command to target or change regions.

ibmcloud target -r <region>
5. You must specify a resource group. To get a list of your resource groups, run the following command.

ibmcloud resource groups

Example output

Retrieving all resource groups under account <account_name> as email@ibm.com...
OK
Name ID Default Group State
default a8a12accd63b437bbd6d58fb8b462ca7 true ACTIVE