In a previous publication we announced our collaboration with OpenShift in order to support their cartridge standard in Jelastic’s Cloud. Now, we’d like to explore more about why we’ve decided to adopt this technology, the goals we are pursuing and what problems we have solved. We will also highlight the difference between a basic cartridge and one that is customized for Jelastic’s Cloud, as well as additional benefits experienced while running your cartridge on Jelastic.
Jelastic Platform-as-Infrastructure supports OpenShift’s cartridge model to make it easier for independent software vendors (ISVs) offering core services in multiple platforms and for a wider array of cloud ecosystems and marketplaces.
Cartridge standardization is an essential element for next-generation cloud infrastructures and enables ISVs to focus on providing real value to customers, instead of spending resources coding for multiple platforms. This results in a broader choice of tools and applications.
ISVs want to offer customers the broadest possible access to their technologies and services, but the cost of achieving this in a variety of public and private cloud environments, can present a significant barrier to entry. This cartridge specification will enable ISVs to rapidly and seamlessly offer their services to a broader array of enterprise customers and leading-edge cloud users.
This open standard for technology packaging and deployment enables ISVs and end-users to integrate their own middleware, databases, and services into the platform and make them available to PaaS developers building applications. It reduces the need for companies to repackage their technology for different cloud platforms, making it easier and quicker to offer their solutions to PaaS users and developers.
Jelastic Cartridge Differences
A cartridge is an advanced packaging format. In our case, it is represented with existing OpenShift cartridge specifications, extended with Jelastic configurations, to provide more complex functionality and the ability to make adjustments it in Jelastic. This additional tuning is required based on the difference between the architectures of the two platforms (Jelastic and OpenShift).
Such configuration is quite easy – you just need to fork a basic cartridge and add custom settings. Most of them are connected with our UI which is very rich and targeted to simplify the usage of the Jelastic Cloud. So, in this case you need to specify node and engine types, also add paths to the required icons and other specs like that. Except that, you can add specific automation scripts for extra functionality.
All of this data should be placed to the cartridge in a separate jelastic folder. After that, this cartridge will work on top of Jelastic as well as on top of OpenShift’s platform.
By running your cartridge on the Jelastic Cloud, you gain these additional benefits:
- Automatic vertical scaling and automated horizontal scaling
- High-level isolation of each stack in a separate container
- Visual topology builder
- Files and configs management via UI
- Easy .war-drop-deploy
- Reset DB password via UI
- Flexible management of resources (RAM, CPU, network, storage)
- Ability to attach Public IP to the cartridge
There are a number of already prepared cartridges customized for using in the Jelastic Cloud (note that they will be fully available for usage starting with the next release). Examples of this proven technology with Jelastic cartridges can be uploaded from the Template repository:
Also, you can package and configure your own cartridge, upload it to the repository and then make it available for your users.
In our next post we’ll provide detailed instruction on how to compile a jelastic folder in the cartridge with all custom configurations. In addition, you’ll get information on how to add this cartridge and make it available for your Jelastic users.
And now, you can delve deeper into the world of cartridges from the Jelastic Cloud perspective by watching the video with our CTO Ruslan Synytsky presenting the details.