DCImanager Administrator

DCImanager structure

ISPSystem

The architecture of DCImanager is based on the use of Docker. The Docker technology allows to create and manage containers. A docker container is an isolated environment in which the application is running. DCImanager uses the docker-compose service to manage all docker containers. The required environment is configured in the /opt/ispsystem/dci/docker-compose.yaml file.

DCImanager containers


The following docker containers are started on the DCImanager server: 

  • dci_dci_front_1 — main container of platform frontend;
  • dci_back — main container of platform backend;
  • dci_eservice_1 — HTTP service for managing equipment;
  • dci_ipmgr_1 — IP addresses management service;
  • dci_metric_collector_1 — metrics collection service;
  • dci_journal_1 — logging service;
  • dci_ipmi_proxy_v2_client_1 — client part of BMC proxy module;
  • dci_plugin_1 — plugin management container;
  • dci_msgsender_1 — service for email sending to users;
  • dci_updater_1 — DCImanager update service;
  • dci_notifier_1 — event tracking and notifications service;
  • dci_batch_1 — request sequence execution service;
  • dci_validator_1 — POST query content check service;
  • dci_consumer_1 — equipment management service;
  • dci_auth_back_1, dci_auth_back4_1 — backend user registration and authorization services;
  • dci_auth_front_1 — frontend user registration and authorization service;
  • dci_input_1 — nginx server for request processing;
  • dci_registrator_1 — new nginx containers registration service;
  • dci_dns_proxy_1 — container for working with PowerDNS module;
  • dci_graphite_1 — statistics aggregation and storage service;
  • dci_loki_1 — log file collection service;
  • dci_eservice_msg_queue_1 — message queue for equipment management service;
  • dci_grafana_1 — statistics visualization system;
  • mysql — container for working with MySQL;
  • dci_consul_1 — container for Consul service detection system. Read more about Consul in the official documentation;
  • dci_dci_backup_1 — platform backup service;
  • dci_ldap_1 — container for synchronization with the LDAP directory;
  • dci_dci_alert_wrapper_1 — notification tracking service;
  • dci_notice-center_1 — service for sending notifications to the platform interface;
  • alert — container for platform notifications settings service.

The following docker containers are started on the location server:

  • ipmi_proxy_v2_server — server part of BMC proxy module;
  • eservice_handler — service containing equipment handlers;
  • lweb — HTTP server;
  • tftpd — TFTP server;
  • smbd — SMB server;
  • redis — database and notifications system;
  • nfsd — NFS server;
  • kea_dhcp — DHCP server.

Product operation logic


How to manage containers


Connect to the DCImanager server via SSH and enter the command to view the list of running containers:

docker ps

To enter the required container, enter:

docker exec -it container_name sh

container_name — name of the running container

Thank you for your feedback!
Was the article useful?
Tell us why not:

it does not match the title

it was hard to understand

I didn't find the answer

recommendations from the article did not help

other

Tell us what you didn't like in the article: