Rudder

While we prepare the documentation here are a few guidelines to help new users get started:

CPU/VPU: At least 1 cpu core dedicated to Rudder.

32/64bit: your preference, Rudder Server is available on both 32 and 64 bit versions of every supported Operating System.

Memory: at least 1GB though 2GB is better. 4GB preferred if the server is managing other tasks.

Bandwidth: bandwidth utilisation is very small, it will rarely exceed 0.005% of bandwidth on a 10GB net, dependent on agent density which is usually 100%.

Local storage (deployment): Rudder will need about 300MB.

Local storage (logs): Every action taking place in the Rudder web interface and all agent logs are stored in the PostgreSQL database. If logs are localised it will be prudent to allow at least 5GB. When deploying to production with weekly log rotation then 5GB is sufficient for most cases though the number of reports that are generated and thus archived suggests at least 20GB+ will be required.

Postgres: it is worth optimizing this -> http://www.rudder-project.org/rudder-doc-2.7/rudder-doc.html#_server_optimization

As each and every site configuration is different these are very much guidelines. We will strive to provide greater clarity in the upcoming addition to our documentation based on this user request.

New pull request: https://github.com/Normation/rudder-doc/pull/50

Applied in changeset commit:bdbebdd8bc48f9189fd8bc5055320ab2c3d46c3b.