Managing Environments

Note: This document is updated based on Jelastic version 3.3

The environments list represents information on the state of all environments, created by Jelastic users, and lets you effectively manage any environments issues that users may have reported.

The following environments’ information is available:

  • Domain name (including an alias if specified)
  • Hardnode Group an environment is located at
  • User ID in the system
  • Date of an environment’s creation

You can also click the value in the User ID column (environment’s owner) which is represented with a link. It leads to the Users JCA section, where the panel with full info about the chosen user (email, group, status, available environments etc) is shown.

The list of environments can be sorted using the set of fields at the top panel by:

  • Domain name (including the bounded external domain or an alias)
  • AppI(a unique Jelastic environment identifier)
  • User ID
  • Status (All, Running, Stopped, Launching, Sleeping, Suspended, Creating, Cloning, Exporting, Migrating, Broken)

For example, if you want to see the list and number of active environments, select the Running status and click Search.

The icons in the first row of the Environments’ table reflect the current state of each environment.

GreenEnvironment is running
BlueEnvironment is inactive at the moment for one of the following reasons:
  • user has stopped the environment; stopped environments are not charged
  • environment is provided free of charge and was not accessed during some time, thus, it was stopped automatically (this is defined by hoster)
RedEnvironment is stopped
BlackEnvironment is suspended for a paid user who can have balance overdraft
GrayEnvironment is broken because of an error, occurred during its creation

Environment Info

To view the details on a particular environment (such as nodes it consists of and used contexts), choose the required one by clicking on it. The detailed information will be shown in the right area.

There you can find the following environment data, divided into columns:

  • Name - name of the chosen environment with the expandable list of all instances it includes and deployed contexts
  • ID - unique ID value for each instance
  • IP address - all bound IP’s, both internal and external (if are any) ones
  • Hardware node - name and IP address of the hardware node, where a particular instance is located

Select a separate container in order to see its statistic or to migrate it to another hardware node.

Change Environment’s State

Select the required environment and click the Start/Stop/Sleep buttons accordingly.

View the Running Environment

Select the required environment and click Open.

The corresponding deployed application (under the ROOT context) will be loaded in a separate browser tab.

Note that if the environment you want to access is inactive, this will be initiated by Awakener.

Migrate (Relocate) an Environment

In order to migrate any environment to another hardware node group (regardless whether it belongs to the same or another region), select it and click on the Migrate button at the top pane.

Within the opened Migrate environment dialog frame, select the destination Hardnode Group and choose Migration type (if active - this depends on the chosen HN Group location) using the appropriate drop-down lists.

There are two migrations modes:

  • online - handled without containers’ restart or any manual adjustments needed, i.e. causing no downtime; available only upon relocation within the same region

  • offline  - during which all the containers are shut down for the whole relocation period; can cause changing of the binded IP(s) and/or environment domain name, thus some manual configurations may be required to restore the normal environment’s operability

Confirm your decision by clicking the Migrate button.

Note: In order to migrate a particular container to another hardware node, comprised within the same hardware node group, proceed to the corresponding section.

Delete Broken Environments

Sometimes, when an error occurs while creating the environment, this environment may not be visible at the user’s dashboard but is present in the Jelastic database list. In this case, there is the possibility to delete such failed environments through JCA.

For that perform the following:

  • choose those broken environments that you want to delete and click the Delete broken button;
  • if you want to delete all broken environments, choose the Delete all option (access it by clicking the down arrow on the Delete broken button).

Migrate (Relocate) a Container

You can migrate any container to another hardware node within the same hardnode group (i.e. which the chosen environment belongs to). To do that, click on the desired environment at the list and switch to the right-hand Info tab.

Then select a particular container from the expandable list and click Migrate at the toolbar above. You’ll see the Migrate node dialog opened, where you need to select a destination hardware node using the drop-down list and click Migrate once more.
Note: In order to learn how to migrate the whole environment to another hardware node group (within the same or different region), refer to this instruction. 

See Environment’s Statistics

Choose the required environment by clicking on it and select the node from the expandable topology list to the right.

The Statistics tab will be automatically shown in the lower area. It contains information about the amount of Memory, Processor and Network, consumed by the chosen node. You can also specify the Duration and Interval values using the corresponding drop-down lists to clearize the shown graphs, and apply these settings with the Refresh button.

Sleep Results

For the environments of trial accounts (only) a special 'sleeping' mode can be automatically applied. It is activated if such an environment was not accessed for some period of time and forces it into temporary sleep.

Note: This is just a trial limitation and does not apply to paying customers.

Sleeping environment will be awakened in the following cases:

  • A user starts it manually from the dashboard
  • Environment gets any http:// request
  • It is started manually via JCA

The statistics on the environments in sleeping mode can be seen at the JCA > Environments > Sleep results section.

State the dates you are interested in (Start/End date) and click on Refresh in the toolbar at the top. The following information will be listed:

  • Start and End Period (according to the date range you’ve specified within the Start/End date option)
  • Envs With HttpRequests - a number of active environments that received at least one HTTP request during the stated period
  • Envs Mentioned In Api Calls - a number of environments, called by API methods at least once during the stated period
  • New Active Envs - a number of environments, created during the stated period of time
  • Inactive Trial Envs - a number of trial account environments without any HTTP requests received during the stated period of time
  • Inactive Billing Envs - a number of billing account environments without any HTTP requests received during the stated period of time
  • Duration - a period of time between Start and End Period values

Note: if any parameter stays at zero or less, the line with the corresponding period will be highlighted in red.