Service Updates for Liferay Cloud Version 4

The services update to 2020.45.1 includes updates to the Search and Webserver services.

 

liferay/dxp docker image tags

In an ever evolving effort to provide the best support, the docker tags on liferay/dxp docker repository have changed. The new addition is a `-dx.y.z` designation (e.g. -d1.0.2), which provides information about any changes to the underlying docker scripts that are utilized by the image. The new tags on Dockerhub for liferay/dxp are formatted as follows

liferay/dxp:{Liferay.DXP.Version}-{Patching-Level}-{Docker.Script.Version}-{Timestamp}
liferay/dxp:7.2.10-dxp-7-d1.0.0-202009071842

When selecting which liferay/dxp base image to utilize for your project, please consider the entire docker tag, and please be sure to check out the release notes for your patching level before applying to your environment: DXP Release Notes

 

Webserver Configuration

Four new environment variables have been added to the webserver service in order to facilitate more advanced configuration. These properties target the HAProxy instance that is used for sticky session enablement that resides behind nginx. Nginx and HAProxy work together to serve traffic in the Webserver service.

The pattern used for these environment variables is LCP_HAPROXY_{DIRECTIVE}_{PROPERTY}. For example, the configuration controlling the "hold valid" property inside of the "resolver" directive is LCP_HAPROXY_RESOLVER_HOLD_TIME.

The following is the list of properties and the default values:

• LCP_HAPROXY_RESOLVER_HOLD_TIME=10s
• LCP_HAPROXY_GLOBAL_MAXCONN=10000
• LCP_HAPROXY_DEFAULT_MAXCONN=10000
• LCP_HAPROXY_FRONTEND_MAXCONN=10000

Version Compatibility between 3 and 4

For details on service compatibility between version 3 and 4 please see release update 6/11/2020 Services Update 2020.24.1 or 5/28/2020 Services Update 2020. 22.1 

 

Feature Exclusion in Version 3 DXP Stack

Due to the deprecation process for the Version 3 DXP Stack, the 3.x service images will no longer receive feature updates. 

 

Version 4 DXP Stack 2020.45.1 

NOTE: LCD-9059 has been back ported into liferaycloud/nginx:1.16.1-3.2.2 to provide the downtime fix for projects still on 3.x service versions

Service Name	Previous Release	Current Release	Docker Images
Backup	4.0.9	4.0.9	liferaycloud/backup:4.0.9
CI	4.0.7	4.0.7	liferaycloud/jenkins:2.235.5-4.0.7
Database	4.0.6	4.0.6	liferaycloud/database:4.0.6
Liferay	4.0.7	4.0.7	liferaycloud/liferay-dxp:7.3-4.0.7 liferaycloud/liferay-dxp:7.2-4.0.7 liferaycloud/liferay-dxp:7.1-4.0.7 liferaycloud/liferay-dxp:7.0-4.0.7
Search	4.0.1	4.0.2	liferaycloud/elasticsearch:7.9.3-4.0.2 liferaycloud/elasticsearch:6.8.13-4.0.2 liferaycloud/elasticsearch:2.4.6-4.0.2
Webserver	4.0.3   3.2.1	4.0.4   3.2.2	liferaycloud/nginx:1.16.1-4.0.4   liferaycloud/nginx:1.16.1-3.2.2

 

Version 4 Update Instructions

Only Applicable to Version 4 Images

After upgrading your project using this guide, the Liferay Cloud image versions are no longer set inside of the gradle.properties file. They now need to be set inside of the <service>/LCP.json file. Note, however, that the liferay service uses two image properties. The DXP Cloud image is set in the liferay/LCP.json file, but the liferay/dxp image is set in the gradle.properties. This change was made in order to facilitate easier deployment using the Liferay Cloud CLI.

liferay/LCP.json file would set the liferaycloud/liferay-dxp image:

"image":"liferaycloud/liferay-dxp:7.3-4.0.7"

liferay/gradle.properties file would set the liferay/dxp image:

liferay.workspace.docker.image.liferay=liferay/dxp:7.3.10-ga1-d1.2.1-20201005160536

Once the LCP.json files are updated, commit the changes to your Git repository.

git add . && git commit -m "update dxp cloud stack to 2020.45.1"

After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.

Version 4 Change Log

Service Name	Service Version	Ticket Number	Description
Search	4.0.2	LCD-8993	update base ES images to 7.9.3 and 6.8.13
Webserver	4.0.4	LCD-9059	decrease the time valid IPs are held for the backend service resolving some short downtimes during deployment
		LCH-1965	expose configuration for maxconn in HAProxy