CirrusGrid’s Platform-as-a-Service Cluster is targeted at a wide audience of developers and SMBs, enterprises and hosting providers. Each class of CirrusGrid customers has its own level of access and a specific way to interact with our platform.
There are three levels of access to the CirrusGrid Cluster:
The administrators of the CirrusGrid platform are operations departments of hosting providers or IT departments of enterprise companies. After the platform installation, they become the owner of the platform and begin to manage the overall performance via CirrusGrid Cluster Admin Panel by setting the main configurations (quotas, tariffs, customization etc.) and supporting all of the required aspects.
There are four main tasks performed by the administrators during the CirrusGrid Cluster lifecycle:
CirrusGrid provides a full set of analytics, documentation and required tools for performing the above mentioned tasks in an efficient and high quality way.
This group of CirrusGrid customers can create environments, deploy their applications and perform all the actions required for the successful lifecycle of their applications. Environment and application management is performed via CirrusGrid’s panel for developers CirrusGrid Dashboard.
The main activities available for developers or SMBs in the CirrusGrid platform are as follows:
While using CirrusGrid the typical developer might go from trial registration to features testing during the trial period. The major steps of this life cycle are represented in the diagram below:
At the end of the trial period developers decide whether to upgrade the account and reach the production or to get the account destroyed.
Enterprise installations do not have a trial period. In the enterprise private cloud developers can self-manage their application environments using the CirrusGrid dashboard relieving IT administrators from environment configuration and setup tasks.
The end-users are connected to the Jelastic Cluster indirectly by using applications deployed to the CirrusGrid environments created by developers or SMBs or enterprise developers. All of the incoming users’ requests are sent to the domain name of an appropriate application and are processed in one of the following ways:
via Global ResolversCirrusGrid uses several synchronized Resolvers for receiving requests simultaneously. As a result, there can be several entry points for environments used at the same time.
via Public IP if it is attached to the entry point of the environment (balancer, app server or database container). This solution provides less risk of being affected by other applications (as in the case with shared Resolvers) and is recommended for production applications. Also Public IP usage makes more features available such as remote debugging, remote backup, JMX, FTP, Custom SSL, websockets and polling etc.
Access levels make using and managing the CirrusGrid Cluster fully efficient, convenient and easy. Each type of customer is provided with their own range of rights and limitations making the system well structured and organized.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.