VMmanager structure

VMmanager has following docker containers:

• vm_box — the main container with the services for the platform;
• vm_input_1 — container with nginx web server. Provides access to all platform services;
• vm_auth_back_1, vm_auth_back4_1 — services for user registration and authorization in VMmanager. They process profile settings and SSH-keys;
• vm_validator_1 — POST query content check service;
• carbon_clickhouse — aggregator of VM and cluster node usage metrics;
• clickhouse_server — database of VM and cluster node usage metrics;
• graphite_clickhouse — service for converting metrics to graphite format;
• carbonapi — API service for transferring metrics to Grafana and platform interface;
• mysql — the container for the database management system MySQL;
• vm_ipmgr_1 — IPmanager service container;
• plugin — plugins container;
• registrator — the container for dynamic creation of new containers for nginx;
• consul — the container for Consul service detection system. Read more about Consul in the official documentation;
• vm_metric_collection_1 — VMmanager metrics collection service;
• grafana — grafana monitoring visualization container;
• vm_dns_proxy_1 — PowerDNS integration plugin container;
• alert — container for platform notifications settings service;

• scheduler — container for VMs backup schedule;

• telegram-srv — container responsible for sending notifications to Telegram messenger;
• vm_msgsender_1 — container for sending emails to VMmanager users. E.g., after the virtual machine is successfully created or the operating system is reinstalled;
• vm_ldap_1 — container for synchronization with the LDAP directory.
  

Container management

To view the list of running containers connect to the server with VMmanager via SSH and enter:

docker ps

To go to the container, enter:

docker exec -it containerID bash

Services of the vm_box containers

Services

The main services of the vm_box container: 

• supervisord — the service management system. It restarts the services automatically when they fail. For more information please refer to the official documentation; 
• nginx — the webserver for displaying the web interface; 
• novnc — this service supports VNC of virtual machines; 
• vm6 — this service supports the operation of VMmanager;
• notifier — monitors running events and shows pop-up notifications when their statuses are changed;
• taskmgr — tasks processing service that collects, keeps, and outputs information in the Tasks section;
• monitor — collects and displays the current status of the virtual machine and cluster nodes;
• gostat — VM usage statistics processing service. It receives information from the graphite container and displays it in Virtual machines → VM card → Statistics;
• collector — collects VMmanager usage and error statistics and sends them to the metrics server;
• alert-wrapper — this service monitors notifications and transmits them to the notice_center service;
• grafana_proxy — this is the service for proxying platform requests to grafana;
• notice_center — this service sends notifications to the platform interface.

• hawatch — service for interaction with a high availability cluster; 

• ifacewatch — service for tracking network interfaces, bonds and bridges on cluster nodes; 

• mon_proxy — platform monitoring service; 

• updater — VMmanager update service; 

• vmwatch — VM status tracking service; 

• nodewatch — service for tracking the status of cluster nodes; 

• task-alert — service for tracking notification status;

• user_syncer — user data synchronization service; 

• rdns_syncer — reverse DNS records synchronization service.

To display a full list of running services:

1. Go to the container vm_box: 

   docker exec -it vm_box bash

2. Open the list of active services: 

   ps ax

Logs

The log files of all VMmanager services are kept in the vm_box container in the directory /var/log. The name of the log file matches the service name. E.g., the name of the log file of the taskmgr service is taskmgr.log.