Jelastic 5.0.5/5.0.7

This document is preliminary and subject to change.

• Features & Updates
  

• Bug Fixes

For detailed information on using any of Jelastic features, please refer to the users’ documentation.

Back to the top

Cloud Scripting (CS) is a powerful Jelastic-developed solution for advanced automation of repetitive DevOps tasks, complex CI/CD flows and clustering configurations. Generally, it allows to predefine complex environments provisioning and their behaviour upon changeable conditions through interconnecting different Jelastic API methods into operation chains. In such a way,  Cloud Scripting represents a unique programming language that is optimised for Cloud hosting to simplify development and significantly reduce the implementation cost of managed services.

Representing a highly versatile tool, Cloud Scripting provides access to a wide range of automation options and tuning possibilities. They are implemented by composing a manifest file in JSON or YAML format, which describes the logic of what should happened during the application lifecycle or performed in response to a particular event. When prepared, CS code can be easily executed by importing it to the Platform and, upon the necessity, edited on a fly through the embedded JSON/YAML editor with auto formatting, errors review and debugging possibilities.

• Basic Configs - learn the minimum basis of any JSP manifest
• Actions - define the required environment configurations and application behavior with a set of prescribed procedures
• Events - automate application workflow by binding actions to particular application lifecycle events
• Custom Scripts - integrate your own scripts, written in either Java, Javascript or PHP, to subsequently execute them within containers
• Visual Settings - customize your package visual layout

• Placeholders - specify automatically substituted parameters to fetch the required data on environment topology, server settings, user account, etc during solution installation

Also, we recommend to examine Jelastic JPS Collection and get some real case examples on what you can achieve with Cloud Scripting.

Back to the list of Features & Updates

In the present 5.0.5 Platform version, Jelastic starts support of Docker Community Edition hosting, with full compatibility to native Docker ecosystem. This implies that a one can deploy any containerised Docker-powered application inside the Cloud, at the same time leveraging all the inherent Jelastic advantages like out-of-box automated scaling (both vertical and horizontal ones), pay-for-use pricing approach with granular resource allocation, ability to choose hardware and collaborate on a project with other team members, etc.

Within the current 5.0.5 Platform upgrade, Jelastic starts the process of certified software stacks transition to dockerized containers, following the global trend of this technology adoption. Such implementation does not limit any of the existing native templates’ functionality and even enlarges it with the inherent Docker containers support possibilities in Jelastic.

As one of the main advantages gained, this novelty simplifies delivery of new stack versions, which can be performed by a cluster administrator at any time by means of the corresponding Docker image tag addition. In such a way, availability of the most recent software is not bound to a particular platform upgrade anymore, whilst it’s developer who decides whether the update is required and when to perform it (by means of the inbuilt Docker container redeployment functionality). This allows to resolve any vulnerability or security issue almost immediately after the official fix is provided and ensures much more flexibility during development.

Currently, the following stacks were converted for being treated as Docker containers: NGINX load balancer, Maven, Memcached, Apache PHP, NGINX PHP, Tomcat 6/7/8, TomEE, MySQL 5.6/5.7, MariaDB 5/10 and Varnish. All such dockerized templates are packaged, proven and fully managed by Jelastic team. The remaining software stacks will be consequentially modified within future Jelastic releases.

• set of function icons for such instances was extended with the additional Docker-dedicated ones (i.e. to access redeployment option and list of configuration tools)
• list of engine versions in topology wizard was substituted with a number of appropriate template tags, allowing to select the required combination of software stack/engine version simultaneously (this approach was additionally improved within Jelastic 5.0.6)
• Docker configuration tools buttons were added to be shown when the corresponding servers are chosen within wizard frame

• new /etc/jelastic/redeploy.conf file, aimed to list files and folders that should be kept during redeploy, is automatically created and added to the Favorites section within container File Manager

Take into consideration that all abovementioned newly created containers will be built upon Dockerized templates for now, whilst the already existing servers will also remain fully operable due to backward compatibility.

Back to the list of Features & Updates

The Out-of-Memory (OOM) killer is a special job for Linux-based OS, aimed to suspend the currently unimportant processes in case of a strict lack of the free RAM memory and release it for more prioritized services. The selection of the process to be killed is made based on principles of losing the minimal amount of work done and simultaneous recovering larger amount of memory. Jelastic utilize OOM killer tool in all containers by default, allowing them to continue functioning even when the RAM limit is reached.

In the current 5.0.5 Platform release, the dedicated monitoring flow was implemented, which allows to track the OOM killer activity. This functionality is optional, thus its availability is controlled by a hosting provider. If enabled, all newly created containers will be supplied with the corresponding OOM killer load alert. It will track the running processes interruptions and send email notification with details to the corresponding user when such are observed. The default frequency for such notifications is one hour, but it can be manually tuned up to desired period (including immediate reports) within alert settings.

• Process Name
• Process ID
• Server
• Node ID

• Time

Also, it provides reference to the list of possible causes and advices on solving the occured issue. Generally, upon receiving the OOM killer notification, we recommend to consider optimization of your project memory consumption and/or attach more resources through the automatic vertical / horizontal scaling.

In addition, the Events History tab was updated to support the OOM killer monitoring implementation. Here, tools panel at top was moved into separate section in order to include the newly added filters (by Nodes and by Trigger), whilst details on the logged events are now shown upon hovering over a particular record.

More info

Back to the list of Features & Updates

Back to the list of Features & Updates

The component templates versions have been updated to their latest versions since the previous release:

Back to the list of Features & Updates

In the table below, you can see the list of bug fixes in Jelastic PaaS & CaaS 5.0.5, 5.0.6, and 5.0.7:

Back to the top