Service Updates for Liferay Cloud

The service updates for 2021.13.1 includes the Webserver service.

liferay/dxp docker image tags

The liferay/dxp docker images provide information about the liferay version, patching level, and docker script associated with the image. The tags on Dockerhub for liferay/dxp are formatted as follows

liferay/dxp:{Liferay.DXP.Version}-{Patching-Level}-d{Docker.Script.Version}-{Timestamp}
liferay/dxp:7.2.10-dxp-11-d1.5.4-20210310143709

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

Due to the way that docker images are cached within the platform, please always utilize the tags with the full timestamp at the end. These are snapshots and will always yield the exact image that is published. Docker tags without the timestamp are considered rolling tags and should not be used.

Webserver Max Scale

Up to this point, the maximum scale for any given service has been capped at 10 instances. This was a platform restriction that was based on most use cases for the portal. Recently, however, there was a need to dynamically scale to more than 10 liferay instances. To address this need, and allow autoscaling to much larger cluster sizes, we have introduced a property to set the maximum number of instances that a service should have.

Note: A project's plan should align with the maximum number of services running in a Liferay Cloud environment. Increasing the autoscale limit does not increase the project quota.

Setting the following environment variable will tell the webserver to route traffic to any available backend (liferay) services up to the maximum number specified in the environment variable.

LCP_HAPROXY_SERVER_TEMPLATE_BACKEND_NUM=10 (default of 10)

In addition, an LCP.json change is required to take advantage of more than 10 liferay instances. This is done by modifying the LCP.json property `autoscale.maxInstances`. For more information please see Setting the Maximum Number of Instances.

Default Nginx.conf and Environment Variables

In an effort to increase usability, the startup log for webserver version 4.1.0 has been enhanced to print out the default Nginx.conf to the log. This behavior is similar to the CI service, which prints out the built-in Jenkinsfile, so that there is always an easy reference on which to base customizations.

The startup logging now also shows the different environment variables that are read/set so that customization is easier without needing to modify the nginx.conf file.

 

DXP Stack 2021.10.1 

Service Name	Previous Release	Current Release	Docker Images
Backup	4.2.2	4.2.2	liferaycloud/backup:4.2.2
CI	4.1.0	4.2.0	liferaycloud/jenkins:2.249.3-4.2.0
Database	4.2.1	4.2.1	liferaycloud/database:4.2.1
Liferay	4.2.1	4.2.1	liferaycloud/liferay-dxp:7.3-4.2.1 liferaycloud/liferay-dxp:7.2-4.2.1 liferaycloud/liferay-dxp:7.1-4.2.1 liferaycloud/liferay-dxp:7.0-4.2.1
Search	4.1.1	4.1.1	liferaycloud/elasticsearch:7.9.3-4.1.1 liferaycloud/elasticsearch:6.8.13-4.1.1 liferaycloud/elasticsearch:2.4.6-4.1.1
Webserver	4.0.6	4.1.0	liferaycloud/nginx:1.16.1-4.1.0

 

Update Instructions

The Liferay 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.2.1"

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

liferay.workspace.docker.image.liferay=liferay/dxp:7.3.10-ga1-d1.5.2-20210301040217

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

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

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

Change Log

Service Name	Service Version	Ticket Number	Description
Webserver	4.1.0	LCD-10524	setting LCP_HAPROXY_SERVER_TEMPLATE_BACKEND_NUM will configure the total number of available backend servers that can receive traffic