Server Groups & Fleets

In enterprise architecture, servers are rarely treated as isolated individuals. They operate as clusters, swarms, and high-availability fleets.

RasnuOS natively supports this pattern through the Server Group abstraction.

Treating Servers as Cattle

If you need to deploy an updated Nginx configuration, you should not have to log into 20 different servers individually to apply the change.

By placing all 20 servers into a single Server Group (e.g., Frontend Web Servers), you can manage them as a single cohesive entity.

• When you push a deployment to a Server Group, the RasnuOS Control Plane places the Intent into the queue for all 20 agents simultaneously.
• The agents pull the Intent and execute the deployment in parallel.

Environment Segregation

Server Groups are the primary mechanism for isolating environments to prevent catastrophic human errors.

A standard best-practice architecture separates infrastructure into distinct groups:

1. Production Application Cluster
2. Production Database Cluster
3. Staging Environment
4. QA & Testing

Integrating with RBAC

Server Groups map directly to our Role-Based Access Control (RBAC) policies. You can confidently assign your junior developers the Operator role for the Staging Environment Server Group, while ensuring they possess only Viewer rights for the Production Database Cluster.

Fleet Auto-Scaling (Roadmap)

(Coming Soon)

Because Server Groups abstract the underlying infrastructure, they form the foundation for upcoming Auto-Scaling capabilities. In the future, the RasnuOS AI AutoPilot will be able to monitor CPU thresholds across a Server Group, dynamically provision new instances via your linked Cloud Credentials, and inject them into the Server Group to instantly handle traffic spikes.