Service Updates for Liferay Cloud Version 3 and 4
The services update to 2020.33.1 includes updates to the liferay and database services.
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
Remove Proxy between Liferay and Database Resource
The Liferay service needs a database to function properly. In Liferay Cloud we provide a database resource through the platform that is accessible/configurable through the Database service.
Prior to this release, the Database service would proxy the connection between the Liferay service and the underlying database resource. In essence, the Database service functioned as both a proxy for the jdbc connection as well as a configuration service for the provided database. In order to provide better resilience and recovery in case of a downtime, the Database service is no longer acting as a proxy for the jdbc connection.
LCP_DATABASE_SERVICE=database--route
In liferay service version 4.0.4 and database version 4.0.3, You will now see that the `database--route` hostname is used instead of `database` for the jdbc url. This removes the Database service as the proxy; preferring an internal network route directly to the database resource. The internal route is initially created by the Database service, but once it is created, it stays even if the Database service goes down.
There are three important notes with this change:
- There is now a compatibility dependency (when using the default configuration) between database version 4.0.3 and liferay version 4.0.4. If you rely on the default configuration for both of those services, you should be using database 4.0.3+ and liferay 4.0.4+
- If only the Database service 4.0.3+ is used with a lower Liferay version, then you will need to make sure that Liferay is using an updated jdbc url (typically set through the LCP_DATABASE_SERVICE environment variable.
- if only Liferay 4.0.4+ is used with a lower Database version, then you will NOT have a `database--route` endpoint available and you will have to configure the LCP_DATABASE_SERVICE environment variable to use 'database' instead of the newer 'database--route'
Version 4 DXP Stack 2020.33.1
Service Name | Previous Release | Current Release | Docker Images |
Backup |
4.0.3 |
4.0.3 |
liferaycloud/backup:4.0.3 |
CI |
4.0.4 |
4.0.4 |
liferaycloud/jenkins:2.235.1-4.0.4 |
Database |
4.0.2 |
4.0.3 |
liferaycloud/database:4.0.3 |
Liferay |
4.0.3 |
4.0.4 |
liferaycloud/liferay-dxp:7.2-4.0.4 liferaycloud/liferay-dxp:7.1-4.0.4 liferaycloud/liferay-dxp:7.0-4.0.4 |
Search |
4.0.0 |
4.0.0 |
liferaycloud/elasticsearch:6.8.6-4.0.0 liferaycloud/elasticsearch:2.4.6-4.0.0 |
Webserver |
4.0.1 |
4.0.1 |
liferaycloud/nginx:1.16.1-4.0.1 |
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 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.2-4.0.4"
liferay/gradle.properties file would set the liferay/dxp image:
liferay.workspace.docker.image.liferay=liferay/dxp:7.2.10-dxp-6-202006221121
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.33.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 |
Database |
4.0.3 |
LCP-5063 |
Remove Proxy between Liferay and Database communication |
Liferay |
4.0.4 |
LCP-5063 |
Remove Proxy between Liferay and Database communication |
Version 3 DXP Stack 2020.33.1
Service Name | Previous Release | Current Release | Docker Images |
Backup |
3.2.15 |
3.2.15 |
liferaycloud/backup:3.2.15 |
CI |
3.2.8 |
3.2.8 |
liferaycloud/jenkins:2.235.1-3.2.8 |
Database |
3.2.11 |
3.2.12 |
liferaycloud/database:3.2.12 |
Liferay |
3.0.27 |
3.0.28 |
liferaycloud/liferay-dxp:7.2.10-sp1-fp7-3.0.28 liferaycloud/liferay-dxp:7.1.10-ga1-fp18-3.0.28 liferaycloud/liferay-dxp:7.0.10-ga1-fp93-3.0.28 |
Search |
3.0.8 |
3.0.8 |
liferaycloud/elasticsearch:6.8.6-3.0.8 liferaycloud/elasticsearch:2.4.6-3.0.8 |
Webserver |
3.2.1 |
3.2.1 |
liferaycloud/nginx:1.16.1-3.2.1 |
Version 3 Update Instructions
To apply these updates, update the gradle.properties file the project root folder with the new docker image tags. Here is an example of applying update 2020.33.1 for a 7.2 Liferay project:
liferay.workspace.lcp.backup.image=liferaycloud/backup:3.2.15
liferay.workspace.lcp.database.image=liferaycloud/database:3.2.12
liferay.workspace.lcp.search.image=liferaycloud/elasticsearch:6.8.6-3.0.8
liferay.workspace.lcp.liferay.image=liferaycloud/liferay-dxp:7.2.10-sp1-fp7-3.0.28
liferay.workspace.lcp.webserver.image=liferaycloud/nginx:1.16.1-3.2.1
liferay.workspace.lcp.jenkins.image=liferaycloud/jenkins:2.235.1-3.2.8
Once the gradle.properties file contains the updates, commit the changes to your Git repository.
git add gradle.properties && git commit -m "update dxp cloud stack to 2020.33.1"
After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.
Version 3 Change Log
Service Name | Service Version | Ticket Number | Description |
Database |
3.2.12 |
LCP-5063 |
Remove Proxy between Liferay and Database communication |
Liferay
|
3.0.28
|
LCP-5063 |
Remove Proxy between Liferay and Database communication |
LCPE-1646 |
Liferay Image for the workspace 3 based on the 7.2 FP7 |