Jelastic PaaS 1.8.2 Release Notes

In this document you can find all the new features, enhancements and visible changes included in the Jelastic 1.8.2 release:

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

New Features

  • Elastic VDS with root access
    This feature lets the user have his own dedicated virtual server where the user can install his own software and perform mostly any system configurations and modifications which are needed. After creating VDS node user receives email with SSH credentials to log in remote secured shell. VDS template doesn’t have any huge applications preinstalled, only packet manager configured to use most of the popular repositories. Any software installation on VDS should be done by user. Also VDS has light build-in Ajax SSH server running. This lets the user connect secured shell directly using web-browser. More info.

  • Memcached node
    Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read. More info.

  • Ability to create environment without compute node
    This feature gives an opportunity to create environments without application logic nodes. For example one container with SQL or NoSQL database, or one VDS node etc.

  • Baloon system
    The prompts system, which allows users quickly to figure out with the dashboard interface.

  • Bandwidth limitation
    Ability to set guarantee traffic rate for customer’s container.
    More info.

  • QA Monitoring system
    System of monitoring of external Jelastic services which also contains subsystem of publishers and subscribers for notifying about monitoring events. Also it contains single subscriber that collects information to MySQL database. In addition it includes the Pentaho BI system with reports and analysis charts.

  • Add disk quota support in Jelastic as quota
    This feature provides the ability to use disk quota in container and configure this parameter according to the different groups of users.
    More info.

  • Tiered pricing for traffic
    This feature provides an opportunity to bill the network internal and external traffic.
    More info.

  • Upgrade system without downtime
    Update system without downtime - two in one feature. This feature lets hoster run two copies of Jelastic Platform, check health state of its internal infrastructure components, monitor health state and switch between infrastructure copies in case if any of active infrastructure components fails. Also this system allows to set any infrastructure hardnode to standby mode and perform the upgrade. When upgrade is finished it is possible to set upgraded node to standby and set update mode for another node. In such a way it is possible to perform system upgrade with minimum downtime.
    More info.

Changes

  • Topology UX modification (Simple/Expert modes)
    This feature provides the users with more flexible and simple way to create environments. New wizard now has two modes : Basic and Expert. In Basic mode you don’t need to think about complex environment topology, you can just select database and application server. That will be quite enough for the first-time user experience. In Expert mode you can select and cofigure balancing, application logic, storage (cache, SQL and NoSQL nodes) and addons (build node, VDS and SSL). More info.

  • Redesigned Hello World application
    HelloWorld.war is a demo application that user can deploy into Jelastic environment and see that everything works fine. Now it is not so boring like “Hello World!” text. It tells user what to do next and has social buttons to spread the World about Jelastic.

  • Sing-up block on blog
    Ability for users to register in the blogs pages.

  • Update templates to the latest versions
    The component templates are updated to the latest versions:

Tomcat 66.0.35
Tomcat 77.0.28
Jetty 66.1.26
GlassFish 33.1.2
Java 61.6.0u26
Java 71.7.0
MariaDB5.5.25
MongoDB2.0.5
MySQL5.5.25
PostgreSQL8.4.12
CouchDB1.2.0
nginx1.2.0
Maven3
Centos 55.8
Memcached1.4.13

More info.

Fixes

The following table lists the bug fixes in Jelastic 1.8.2.

ErrorDescription
JE-1200{“result”:99, “error”:“sh: /opt/tomcat /conf /tomcat-users.xml: Permission denied”, “source”:“JEL”, “out”:""}Error while trying to edit Tomcat’s configuration file: tomcat-users.xml
OB-743psql: FATAL: no pg_hba.conf entry for host X.X.X.XMissing parameter in pghba.conf file caused error during remote connection to PostgreSQL server using public IP.
JE-1324{“result”:0, “responses”: [{“result”:99,“error”: “bash: -c: command not found”, “source”: “JEL”,“out”:"”, “nodeid”:66008}]}Using not direct link to file while .war(.ear) files uploading.
JE-1406{“result”:99,“error”:“svn: OPTIONS of ‘https:// dmitryshnyrev%40bitbucket.org /DmitryShnyrev/quiz’: Could not resolve hostname dmitryshnyrev%40bitbucket.org’: Host not found (https://dmitryshnyrev%40bitbucket.org)"}Error appeared while trying to build git project via https://.
At that moment git projects’ building was available only via git://
JE-1406{“result”:99, “error”:“error: SSL certificate problem, verify that the CA cert is OK. Details: \nerror: 14090086:SSL routines: SSL3_GET_SERVER_CERTIFICATE: certificate verify failed while accessing https://……: HTTP request failed”}Error appeared while trying to build git project via https://.
At that moment git projects’ building was available only via git://
JE-2226{“result”:99, “error”: “sh: /opt /glassfish3 /glassfish /domains/domain1 /config /domain.xml: Permission denied”, “source”: “JEL”, “out”:""}There was a restriction to edit the mentioned file under GlassFish configuration
JE-2046{“result”:99,“source”:“JEL”}Error while resetting passwords for Databases or Glassfish instances
JE-1600External libs are not accessible from app deployed to GlassfishExternal libs are not accessible from app deployed to Glassfish
JE-160Maven: Create SVN project -> change to Git project, build it and got error “fatal: Not a git repository: ‘/root /maven /projects_src /123/.git’”This error took place while changing project type from SVN to GIT and then building this project

What’s next?