vania-janet/multiturn-rag-retrieval-data huggingface dataset:
19.4R3-S2 19.4R3-S2.2 2.0 March 25, 2021 [More information](https://kb.juniper.net/InfoCenter/index?page=content&id=TSB17993) 
 19.4R2-S3 19.4R2-S3.1 2.0 December 8, 2020 [More information](https://kb.juniper.net/InfoCenter/index?page=content&id=TSB17918) 
 19.4 19.4R2-S1 2.0 September 21, 2020 [More information](https://kb.juniper.net/InfoCenter/index?page=content&id=TSB17827&actp=METADATA) 
 18.4 18.4R1-S1 2.0 April 8, 2019 [More information](https://kb.juniper.net/InfoCenter/index?page=content&id=TSB17520&actp=METADATA) 
 15.1 15.1X49 2.0 October 25, 2018 [More information](https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/15.1x49-d120/junos-release-notes-15.1X49-D120.pdf) 



It's critical that you review the [Junos OS dates and milestones](https://support.juniper.net/support/eol/software/junos/) to determine whether or not Juniper still supports your Junos version. If your installed version is approaching its end of support from Juniper, then you should [Upgrade your vSRX](https://cloud.ibm.com/docs/vsrx?topic=vsrx-upgrading-the-vsrx) immediately to maintain full support.

All versions prior to 19.4R3-S2 are prone to clustering issues and crashing. As a result, it is critical that you upgrade to the latest available version, especially if you are currently using 19.4R2-S3 or below.
If you are using Terraform, check your Terraform configuration to make sure that the [ibm_cd_toolchain_tool_keyprotect](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain_tool_keyprotect), [ibm_cd_toolchain_tool_secretsmanager](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain_tool_secretsmanager), or [ibm_cd_toolchain_tool_appconfig](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain_tool_appconfig) tool integration resource depends on the Key Protect, Secrets Manager, or App Configuration [ibm_resource_instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance) resource that the tool integration represents. You can specify this dependency within the tool integration resource by referring to attributes of the service instance resource, or by specifying a depends_on meta-argument that refers to the service instance resource. You can refer directly to the service instance resource, or indirectly through other intermediate resources. By declaring dependencies between resources correctly, you can coerce Terraform into creating, updating, and deleting resources in the correct sequence.

For an example of how dependencies work between Terraform resources, see [Specifying secret references with Terraform](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_data_security&interface=terraformcd_secrets_references_terraform).

If you are using the API, check the configuration parameters of the Key Protect, Secrets Manager, or App Configuration tool integration that you are trying to create or update. Verify that the name or ID of the service instance that you are trying to integrate is correctly specified within the configuration of the tool integration.
Generate log entries by sending requests that are not allowed by the policy that you created in step 1. For example, try to ping the pod that is protected by the network policy from a pod or an IP address that is not permitted.
5. Check for log entries that are written to the /var/log/syslog path. The DST (destination) or SRC (source) IP addresses in the log entry might be different than expected due to proxies, Network Address Translation (NAT), and other networking processes. The log entry looks similar to the following.

Sep 5 14:34:40 <worker_hostname> kernel: [158271.044316] calico-packet: IN=eth1 OUT= MAC=08:00:27:d5:4e:57:0a:00:27:00:00:00:08:00 SRC=192.XXX.XX.X DST=192.XXX.XX.XX LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=52866 DF PROTO=TCP SPT=42962 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0
6. Optional: Forward the logs from /var/log/syslog to [IBM® Log Analysis](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging) or to [an external syslog server](https://cloud.ibm.com/docs/containers?topic=containers-healthconfiguring).
See [system event information for apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-appsts-app-gettingevent) and [system event information for job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-jobts-job-gettingevent).

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





 2 March 2021 

Review the release notes for 2 March 2021.

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

New responsibilities for Code Engine topic.
: See [Understanding your responsibilities when using Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-responsibilities-ce).







 February 2021 

Review the release notes for February 2021.



 26 February 2021 

Review the release notes for 26 February 2021.

Commands and arguments
: Added information for defining commands and arguments for your apps and jobs. See [Defining commands and arguments for your Code Engine workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cmd-args).

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

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

Added notices file.
: See [Code Engine notices](https://cloud.ibm.com/docs/codeengine?topic=codeengine-notices).
Ingress change logs
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for versions 0.47.0_1434_iks and 0.45.0_1435_iks. Version 0.35.0 is now unsupported.

Worker node versions
: Worker node fix pack update change log documentation is available for version [1.21.3_1526](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1211213_1526), [1.20.9_1548](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1201209_1548), [1.19.13_1555](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911913_1555), and [1.18.20_1560](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1560).







 July 2021 



 27 July 2021 

New! IAM trusted profile support
: Link your cluster to a trusted profile in IAM so that the pods in your cluster can authenticate with IAM to use other IBM Cloud services.

Master versions
pacemaker: active/disabled
pcsd: active/enabled

Run the following command to check the defined constraints.

Sample output:

 pcs constraint --full
Location Constraints:
Resource: group_dev_non_prod
Disabled on:
Node: cl-prd-1 (score:-INFINITY) (resource-discovery=never) (id:loc-dev-avoid-cl-prd-1)
Ordering Constraints:
start SAPHanaTopology_PRD_00-clone then start SAPHana_PRD_00-clone (kind:Mandatory) (non-symmetrical) (id:order-SAPHanaTopology_PRD_00-clone-SAPHana_PRD_00-clone-mandatory)
stop group_dev_non_prod then promote SAPHana_PRD_00-clone (kind:Mandatory) (id:order-group_dev_non_prod-SAPHana_PRD_00-clone-mandatory)
Colocation Constraints:
vip_PRD_00 with SAPHana_PRD_00-clone (score:2000) (rsc-role:Started) (with-rsc-role:Master) (id:colocation-vip_PRD_00-SAPHana_PRD_00-clone-2000)
group_dev_non_prod with SAPHana_PRD_00-clone (score:-INFINITY) (rsc-role:Started) (with-rsc-role:Master) (id:colocation-group_dev_non_prod-SAPHana_PRD_00-clone-INFINITY)
Ticket Constraints:





 Enabling the automated registration of the secondary instance 

You need to set the parameter AUTOMATED_REGISTER according to your operational requirements. If you want to keep the ability to revert to the state of the previous primary SAP HANA instance, then AUTOMATED_REGISTER=false avoids an automatic registration of the previous primary as a new secondary.

If you experience an issue with the data after a takeover that was triggered by the cluster, you can manually revert if AUTOMATED_REGISTER is set to false.

If AUTOMATED_REGISTER is set to true, the previous primary SAP HANA instance automatically registers as secondary, and cannot be activated on its previous history.
":{"operates":{"qubits":[12,13]},"purpose":"cross-resonance","type":"control"},"u26":{"operates":{"qubits":[12,15]},"purpose":"cross-resonance","type":"control"},"u27":{"operates":{"qubits":[13,12]},"purpose":"cross-resonance","type":"control"},"u28":{"operates":{"qubits":[13,14]},"purpose":"cross-resonance","type":"control"},"u29":{"operates":{"qubits":[14,11]},"purpose":"cross-resonance","type":"control"},"u3":{"operates":{"qubits":[1,4]},"purpose":"cross-resonance","type":"control"},"u30":{"operates":{"qubits":[14,13]},"purpose":"cross-resonance","type":"control"},"u31":{"operates":{"qubits":[14,16]},"purpose":"cross-resonance","type":"control"},"u32":{"operates":{"qubits":[15,12]},"purpose":"cross-resonance","type":"control"},"u33":{"operates":{"qubits":[15,18]},"purpose":"cross-resonance","type":"control"},"u34":{"operates":{"qubits":[16,14]},"purpose":"cross-resonance
:[21,18]},"purpose":"cross-resonance","type":"control"},"u45":{"operates":{"qubits":[21,23]},"purpose":"cross-resonance","type":"control"},"u46":{"operates":{"qubits":[22,19]},"purpose":"cross-resonance","type":"control"},"u47":{"operates":{"qubits":[22,25]},"purpose":"cross-resonance","type":"control"},"u48":{"operates":{"qubits":[23,21]},"purpose":"cross-resonance","type":"control"},"u49":{"operates":{"qubits":[23,24]},"purpose":"cross-resonance","type":"control"},"u5":{"operates":{"qubits":[2,3]},"purpose":"cross-resonance","type":"control"},"u50":{"operates":{"qubits":[24,23]},"purpose":"cross-resonance","type":"control"},"u51":{"operates":{"qubits":[24,25]},"purpose":"cross-resonance","type":"control"},"u52":{"operates":{"qubits":[25,22]},"purpose":"cross-resonance","type":"control"},"u53":{"operates":{"qubits":[25,24]},"purpose":"cross-resonance","type"
For more information, see:<br><br><br><br> * [IBM Cloud IAM access groups](https://cloud.ibm.com/docs/containers?topic=containers-usersrbac)<br> * [Configuring pod priority](https://cloud.ibm.com/docs/containers?topic=containers-pod_prioritypod_priority)<br><br><br> 
 Kubernetes Heapster v1.5.2 v.1.5.4 Increased resource limits for the heapster-nanny container. See the [Kubernetes Heapster release notes](https://github.com/kubernetes-retired/heapster/releases/tag/v1.5.4). 
 Logging configuration N/A N/A The container log directory is now /var/log/pods/ instead of the previous /var/lib/docker/containers/.
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.dynamic_scan",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
}
]
},
{
"asset_type": "generic",
"evidences":
{
"evidence_type_id": "com.ibm.pipeline_run_data",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.pipeline_logs",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
}
]
},
{
"asset_type": "",
"evidences":
{
"evidence_type_id": "com.ibm.code-branch-protection",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.peer_review",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.unit_tests",
"rules": {
"required": ],
"optional":
{
"tool": ""
What are the possible network addresses that Cloud Foundry apps can be running on? 

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).

When you deploy Cloud Foundry apps, there are a known list of possible network addresses that the app will be deployed on depending on the region.

Network addresses are subject to change from time to time.

In the Dallas (us-south) region, the following network addresses are in use:

169.46.101.192/27
169.46.101.64/27
169.46.101.96/27
169.46.104.128/27
169.46.105.64/27
169.46.106.224/27
169.46.115.96/27
169.46.120.96/27
169.47.196.0/27
169.47.201.32/27
169.47.205.32/27
169.48.166.64/26
169.61.155.160/27
169.61.175.128/26
169.61.179.128/25
169.61.185.0/24
169.62.171.0/24
169.62.205.128/25
169.62.231.0/24
150.240.65.245/32
150.239.168.150/32
169.48.95.93/32
Show more

In the Washington DC (us-east) region, the following network addresses are in use:

169.60.80.160/27
169.60.82.128/26
169.60.84.128/25
169.61.82.224/27
169.61.87.128/25
169.61.87.64/26
169.63.78.192/26
169.63.80.128/25
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63",
"id": "199d78ec-b971-4a5c-a904-8f37ae710c63",
"iops": 14400,
"lifecycle_state": "stable",
"mount_targets": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63/mount_targets/d5fd8173-f519-4ff7-8f63-0ead23ecf1f4",
"id": "d5fd8173-f519-4ff7-8f63-0ead23ecf1f4",
"name": "my-share-mount-target",
"resource_type": "share_mount_target",
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/c2d941de-27f5-432c-b4d0-37a8491c3216",
"id": "c2d941de-27f5-432c-b4d0-37a8491c3216",
"name": "my-vpc",
"resource_type": "vpc"
}
}
],
"name": "my-share",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/dp2",
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.peer_review",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.unit_tests",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.static_scan",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.detect_secrets",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.code_vulnerability_scan",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.code_cis_check",
"rules": {
"required": ],
"optional":
{
"tool": ""
}
],
"ignore": ]
}
},
{
"evidence_type_id": "com.ibm.code_bom_check",
ge-0/0/3 {
gigether-options {
redundant-parent reth1;
}
}
ge-0/0/4 {
gigether-options {
redundant-parent reth1;
}
}
ge-0/0/5 {
gigether-options {
redundant-parent reth2;
}
}
ge-0/0/6 {
gigether-options {
redundant-parent reth2;
}
}
ge-0/0/7 {
gigether-options {
redundant-parent reth3;
}
}
ge-0/0/8 {
gigether-options {
redundant-parent reth3;
}
}
ge-7/0/1 {
gigether-options {
redundant-parent reth0;
}
}
ge-7/0/2 {
gigether-options {
redundant-parent reth0;
}
}
ge-7/0/3 {
gigether-options {
redundant-parent reth1;
}
}
ge-7/0/4 {
gigether-options {
redundant-parent reth1;
}
}
ge-7/0/5 {
gigether-options {
redundant-parent reth2;
}
}
ge-7/0/6 {
gigether-options {
redundant-parent reth2;
}
}
ge-7/0/7 {
gigether-options {
redundant-parent reth3;
}
}
ge-7/0/8 {
gigether-options {
redundant-parent reth3;
}
}
fab0 {
fabric-options {
member-interfaces {
ge-0/0/0;
ge-0/0/9;
}
}
}
"href": "$vpc_api_endpoint/v1/shares/r134-56f91d4a-2801-470a-b368-176bde64e954",
"id": "r134-56f91d4a-2801-470a-b368-176bde64e954",
"initial_owner": {
"gid": 0,
"uid": 0
},
"iops": 100,
"lifecycle_state": "pending",
"name": "myshare-3",
"profile": {
"href": "$vpc_api_endpoint/v1/share/profiles/dp2",
"name": "dp2",
"resource_type": "share_profile"
},
"replication_role": "none",
"replication_status": "none",
"replication_status_reasons": [],
"resource_group": {
"crn": "crn:[...]",
"href": "$vpc_api_endpoint/v2/resource_groups/678523bcbe2b4eada913d32640909956",
"id": "678523bcbe2b4eada913d32640909956",
"name": "Default"
},
"resource_type": "share",
"size": 20,
"mount_targets": [
{
"href": "$vpc_api_endpoint/v1/shares/r134-56f91d4a-2801-470a-b368-176bde64e954/mount_targets/r134-b8573e2c-60ee-4ecc-9eae-c52f890a8195",
"plugins": [
{
"type": "calico",
...
},
{
"type": "tuning",
...
},
{
"type": "bandwidth",
...
}
]
}
typha_service_name: calico-typha
...
Show more

Changing any other settings for the Calico plug-in in this ConfigMap is not supported.
3. Apply the change to your cluster by restarting all calico-node pods.

kubectl rollout restart daemonset -n kube-system calico-node
"keyId": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:bucket:my-cos-kms-bucket",
"createdBy": "crn-crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8::",
"creationDate": "2020-06-15T16:07:37Z",
"lastUpdated": "2020-06-15T16:07:37Z",
"keyVersion": {
"id": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f",
"creationDate": "2020-06-15T16:05:53Z"
}
}
] ! ! ! !
: See [Viewing logs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logs).

Tips for troubleshooting applications.
: See [Troubleshooting tips for apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-apps).





 12 November 2020 

Review the release notes for 12 November 2020.

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





 11 November 2020 

Review the release notes for 11 November 2020.

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

SDK documentation published
: See [SDK documentation](https://cloud.ibm.com/apidocs/codeengine).







 October 2020 

Review the release notes for October 2020.



 30 October 2020 

Review the release notes for 30 October 2020.

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

Lithops
: You can run a Code Engine job by using Lithops framework. See [Running jobs with Lithops framework](https://cloud.ibm.com/docs/codeengine?topic=codeengine-lithops).





 23 October 2020 

Review the release notes for 23 October 2020.

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

Project selected for current context
: When you create a project, it is automatically selected as the current context.
packages="libtool automake autoconf cmake make openssl libssl-dev git wget build-essential golang patch perl diffutils"
for REQUIRED_PKG in $packages
do
PKG_STATUS=$(dpkg-query -W --showformat='${Version},${Status}n' $REQUIRED_PKG|grep "install ok installed")
if [ "" = "$PKG_STATUS" ]
then
echo "$REQUIRED_PKG is NOT installed"
sudo apt-get -y install $REQUIRED_PKG
else
PKG_VER=$(echo $PKG_STATUS| cut -d',' -f 1)
if [ "cmake" == $REQUIRED_PKG ] && ! [ $PKG_VER = $CMAKE_VER_REQUIRED ]]
then
echo "$REQUIRED_PKG Version is: $PKG_VER. OQSSA requires cmake 3.5 and above."
fi
fi
done
echo "Prerequisites verification completed"
Show more



* RHEL (Centos/Fedora) dependencies: libtool automake autoconf cmake (3.5 or above) make openssl ncurses-devel gcc-c++ glibc-locale-source glibc-langpack-enopenssl-devel git wget golang (1.14 or above) patch perl diffutils 'Developement Tools''



If you are using a RHEL distribution, copy the following code snippet to a file and execute it to verify that all necessary packages have been installed:

echo "Starting prerequisites verification"
CMAKE_VER_REQUIRED="3."
Two applications are provided as part of the Management Utilities: the [Smart Card Utility Program](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptssmart-card-utility-concept) and the [Trusted Key Entry (TKE) application](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptstke-client-concept). With the Smart Card Utility Program, you can initialize the smart cards to use. The TKE application uses the smart cards to load master keys in service instances.

To install the applications on Red Hat Enterprise Linux 8.0, Red Hat Enterprise Linux 9.0, or Ubuntu 22.04.1 LTS, complete the following steps:



1. Download the latest installation file, cloudtke.bin, from [GitHub](https://github.com/IBM-Cloud/hpcs-management-utilities/releases) to your workstation.
2. (Optional) For maximum security, verify the integrity and authenticity of the Management Utilities installation file cloudtke.bin before you install or update the applications.

Hyper Protect Crypto Services Management Utilities enable [signed code verification](https://en.wikipedia.org/wiki/Code_signing) to ensure that the signature matches the original code. If the downloaded installation file is altered or corrupted, a different signature is produced and the verification fails. To make sure that the applications are not tampered with or corrupted during the download process, complete the following steps by using the [OpenSSL command-line tool](https://wiki.openssl.org/index.php/Binaries):



1. Download the latest version of following files from [GitHub](https://github.com/IBM-Cloud/hpcs-management-utilities/releases) to the same directory where you store the cloudtke.bin file:



* cloudtke.sig: The signed cryptographic hash of cloudtke.bin (SHA-256).
* digicert_cert.pem: An intermediate code signing certificate to prove the Management Utilities signing certificate.
packages="libtool automake autoconf cmake make openssl libssl-dev git wget build-essential golang patch perl diffutils"
for REQUIRED_PKG in $packages
do
PKG_STATUS=$(dpkg-query -W --showformat='${Version},${Status}n' $REQUIRED_PKG|grep "install ok installed")
if [ "" = "$PKG_STATUS" ]
then
echo "$REQUIRED_PKG is NOT installed"
sudo apt-get -y install $REQUIRED_PKG
else
PKG_VER=$(echo $PKG_STATUS| cut -d',' -f 1)
if [ "cmake" == $REQUIRED_PKG ] && ! [ $PKG_VER = $CMAKE_VER_REQUIRED ]]
then
echo "$REQUIRED_PKG Version is: $PKG_VER. OQSSA requires cmake 3.5 and above."
fi
fi
done
echo "Prerequisites verification completed"
Show more



* RHEL (Centos/Fedora) dependencies: libtool automake autoconf cmake (3.5 or above) make openssl ncurses-devel gcc-c++ glibc-locale-source glibc-langpack-enopenssl-devel git wget golang (1.14 or above) patch perl diffutils 'Developement Tools'



If you are using a RHEL distribution, copy the following code snippet to a file and execute it to verify that all necessary packages have been installed:

echo "Starting prerequisites verification"
CMAKE_VER_REQUIRED="3."
* [Service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqservice-binding-cfce)
* [Updating an app or job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqupdate-app-job)
* [Runtime support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqruntime)



* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faqmigrate-cf-ce-next-faq)







 Configuring application scaling 

[Configuring application scaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-scale)



* [How scaling works](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-how-scale)



* [Scaling boundaries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-scale-boundaries)
* [Autoscaling settings for concurrency and timing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-scale-timeconcurrency)
* [Example scenario for autoscaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-scale-example)



* [Optimize latency and throughput](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-optimize-latency)



* [Determining concurrency of your application container](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-determine-concurrency)