Configuration Tools

CirrusGrid PaaS provides a possibility to manage all main aspects of containers lifecycle directly through a dashboard. It supports a number of various tools, intended to help you to configure your environments:

Container Layer Settings Wizard #

CirrusGrid integrated the special Docker layer settings dialog frame to the topology wizard to adjust some of the most commonly required container settings without the necessity to access it via SSH. Simultaneously powerful and user friendly, it gives you the ability to configure your containers in the most easy and comfortable way.

So, to start with, you need to access the above-mentioned frame. There are two ways this can be done through:

  • via topology wizard – click on the New Environment button and add the needed container(s) or hit the Change Environment Topology button for the already created environment. topology wizard container settingsThen choose a container that needs to be tuned and select the appropriate Configuration section at the bottom (circled in the image above).

Tip: With CirrusGrid, any container can be preconfigured even before being created - the necessary data is automatically fetched from image manifest upon accessing the configuration wizard.

  • directly from the dashboard – hover over your environment layer, click on the gear icon and pick one of the quick access options from the expanded listdashboard layer settings

After that, the Docker layer settings window will appear:

layer settings window

As you can see, it contains 5 separate sections with the next settings options (follow the appropriate guide below for the section you are interested in):

Configuration File Manager #

The in-built CirrusGrid configuration file manager is designed to manage the files inside your container (including the ones, that are available and/or exported by means of Shared Storage Container functionality). The appropriate tab can be opened by clicking on the Config button next to the necessary node (or the whole layer):

configuration file manager

It includes 4 main sections:

  • Root (File Manager) – gives you an easy access to container local filesystem, where you can operate the comprised data and instance settings within the corresponding configuration files
  • Mount Points – list of folders, that are physically stored on a remote node but can be used at a current container through mounting the directories with required data
  • Exports – list of folders, which are shared with other nodes, i.e. are exported to be available at the remote instances whilst being stored locally
  • Favorites – commonly used files and folders to have a quick and simple access to (you can manually mark any custom ones as favorites)

Tip: In case the appropriate environment layer includes multiple same-type containers, you can easily switch between them directly inside the manager by choosing the required one within the corresponding drop-down list at the top pane (circled in the image above).

In such a way file manager, allows to take the full control over container file system with no extra tools required. However, be aware of what you are modifying, as in case something will get broken, the changes you’ve applied couldn’t be automatically reverted.

Log Files #

Another section of the CirrusGrid dashboard, which may help you to manage your projects, is Logs. Here, the data on all aspects of your containers lifecycle is gathered, which may come in handy while troubleshooting and/or debugging your applications or services.

node log manager

Note: The list of shown log files and directories depends on a particular software stack and can vary.

The log files inside a container are automatically rotated, so when any of them reaches the size of 50 MB, it is automatically compressed and moved to the dedicated rotated_logs directory. To view such archives (if necessary), you need to enter the appropriate container via SSH and download them for examining locally. The compressed logs are stored for 7 days, after which they will be automatically removed, being considered as an obsolete data.

Powered by BetterDocs