Right after container’s creation, you can immediately proceed to its configuration. Below, we’ll show several basic actions that may be useful for you to get started:
1. For the most of the 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.
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.
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:
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).
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.
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.