→ Applies to: SynetoOS 5.x

All commands in this article are intended to be executed via SynetoOS CLI.

Pods: Roles and Responsibilities

Minerva - Hypervisor Integration

Minerva is responsible for managing the integration between SynetoOS and hypervisors, enabling seamless VM lifecycle management. It handles:

• Provisioning of virtual machines.
• Power management of VMs.
• Hardware management for virtualized environments.
• VM migration across different hosts.

Marte - Task Execution

Marte is responsible for executing all tasks on the platform, ensuring efficient automation and system operations.

Mercurio - Cloud Connection

Mercurio enables seamless communication between on-premise Syneto HYPER appliances and Syneto Central cloud services, facilitating remote management and integration.

Chronos - Time Manager

Chronos is responsible for task scheduling and automation within the SynetoOS environment. It handles:

• Task scheduling to optimize system operations.
• SLA policy management, including protection tasks and data retention.
• Recovery point scheduling to ensure regular and reliable backups.

Aurora - Monitoring & Metrics

Aurora manages the monitoring and performance metrics of Syneto appliances. Its key functions include:

• Collecting performance metrics for system optimization.
• Log collection to provide insights into system health.
• Alerting and notifications for proactive issue resolution.
• Integration with SerenITy or third-party platforms for comprehensive monitoring.

Doorman - Authorization and Access Control

Doorman manages the authentication and authorization across the entire Syneto platform:

• Session management with multi-factor authentication (MFA) support.
• Programmatic access tokens with granular permissions and network restrictions.
• TLS certificate generation and management for secure communications.
• Account creation and management with role-based access control (RBAC).
• Fine-grained permission control and continuous authentication for sensitive operations.

Hercules - Bandwidth Allocation

Hercules manages bandwidth allocation and prioritization across processes:

• Evaluates the priority of each request and determines how much bandwidth to reserve from other processes.
• Allocates bandwidth to the requesting process based on calculated needs.
• Reduces bandwidth consumption of other processes to guarantee resources for critical tasks.
• Continuously communicates updated bandwidth availability to running processes.
• Monitors how much bandwidth each process consumes in real time.
• Frees bandwidth when a process finishes and redistributes it to speed up other processes.

List pods and statuses

kubectl get pods -A

EXAMPLE of output

To be operational, the value in the Ready column for each pod must be a fraction equal to 1 (e.g. 1/1, 2/2, 3/3, 4/4, 5/5).
If a different status is detected, it means the pod did not start properly.

Restart a pod

kubectl delete pod <pods_name>

EXAMPLE

kubectl delete pod mercurio-54cf975dfd-vv2bp

The correct pod name must be taken from the Name column in the pod list.

Access pod logs

kubectl logs -f <pods_name>

EXAMPLE

kubectl logs -f mercurio-54cf975dfd-vv2bp

The correct pod name must be taken from the Name column in the pod list.