Shared Storage Container

Jelastic Shared Storage Container is a special type of node, based on Docker centos7 image. Being developed specially for data storing, it provides a number of the appropriate benefits:
shared storage container logo
  • being delivered with the corresponding software (i.e. NFS & RPC) already pre-installed, so such a container can be used as a storage immediately after the creation without any additional configurations required
  • compared to other common-purposed Jelastic nodes, Shared Storage Container provides the enlarged amount of disk space, which allows to persist a comparatively bigger data volumes (herewith, the particular value depends on your service provider’s settings and can vary according to your account type).

Some tips on this container type usage and examples it can be leveraged in the best way are revealed within the corresponding use case description.

And below we’ll consider how to set up such Storage server inside jelastic PaaS and some tips on its management:

Storage Container Creation

So, in order to create a new Shared Storage Container (either for a new or the already existing environment), just enable the corresponding Storage section at the topology wizard. This option is available for all engines including Docker containers.

create environment with shared storage node

The exact amount of provided storage space will be shown in the middle part of the wizard next to the Disk Limit string. You can manually adjust container size up to your needs and, if the maximum value is not enough for you, please, contact your hosting provider’s support team and request the corresponding account limit enlargement.

Since this container type was specially developed to be used as a data storage server, you need to consider some specifics about its configuration:
  • the vertical scaling section is not disabled, as your storage will work over network, that presupposes usage of RAM & CPU (the particular amount depends on load)
  • this node’s exact pricing mainly depends on the amount of actually used disk space (but not on its limit) and external network traffic. You can check your provider’s costs for these resources within the Quotas & Pricing > Pricing > Disk Space (or Traffic) information frame

Storage Container Management

Right after creation, you can immediately proceed to the container configuration. Below, we’ll show several basic actions that may be useful for you to get started:

1. For the most common operations with your storage, the in-built configuration manager can be used. For example, its Root part gives access to container’s file system.

shared storage file manager

Tip: Additionally, with the Mount Points and Exports sections below, you can:

  • mount data from other Jelastic nodes and external servers
  • review the list of exported from the current node files and folders
2. For more complex operations, SSH access (either via web or local SSH client) may be required, where you get a full control over your storage server via console.

shared storage web ssh access

3. If you want to use your Shared Storage Container as an external server (i.e. not only within the current Jelastic installation) - just enable the Public IP option to make it accessible from outside and proceed with the dedicated NFS server configurations instruction.

Herewith, the attached to a node external IP address(es) can be checked through expanding the appropriate Shared Storage node in dashboard:

shared storage public IP address
4. In case you’ll try to stop your environment with storage, the corresponding notification will inform you, that all of the dependent mount points on other nodes will stop to respond (whilst being automatically restored once the environment is started again).

stopping shared storage component dependencies
Tip: You can perform the similar dependencies check up by clicking on the appropriate availability of the components link while migrating environment with mount points.

shared storage dependencies for migration
Herewith, live migration is not allowed for the Shared Storage node, so it will be transferred offline. Surely, data sharing will be automatically restored when the operation is finished.

That’s all! For now, as you know the main points on your Storage Container handling, feel free to proceed and fill it with the required content.

If you experience any problem with Shared Storage Container deployment, configuration or usage, feel free to appeal to our technical expert’s assistance at Stackoverflow.