Establish and Enforce Minimum Requirements for Groups

[HttpMarco]

Motivation

Currently, the cloud system lacks well-defined minimum requirements for groups, which could lead to resource inefficiencies or system instability. This issue aims to introduce a structured approach to configuring groups with clear baseline requirements. By enforcing these guidelines, the system will achieve improved reliability and resource management.

Description

Each group in the cloud system should adhere to the following minimum configuration guidelines:

1. Name

   • Every group should have a unique and descriptive name to simplify identification and management.

2. Selected Platform

   • Groups must specify the platform they are designed to operate on (e.g., Spigot, Minestom). This ensures compatibility and proper deployment.

3. Memory Allocation

   • Minimum Memory: A baseline amount of memory should be allocated to ensure the group operates without issues.
   • Maximum Memory: A limit should be set to prevent over-allocation of resources and avoid conflicts with other groups.

4. Online Service Requirements

   • Minimum Online Services: Each group should maintain a minimum number of active services to meet operational needs.
   • Maximum Online Services: A cap should be set on the number of concurrent services to optimize resource usage and prevent overloads.

Tasks

• Define a group data structure including:
  • name
  • selectedPlatform
  • minMemory
  • maxMemory
  • minOnlineServices
  • maxOnlineServices
• Implement logic to validate that all groups meet the defined minimum requirements.
• Introduce a mechanism to monitor and flag any deviations from the defined requirements.
• Update system documentation to include these new configuration guidelines.

Acceptance Criteria

• Groups with incomplete or invalid configurations should not start.
• Clear error messages or logs should be generated when requirements are not met.
• Groups should run within the defined limits for memory and active services.