Revision a91625c5
Added by Benoît PECCATTE almost 7 years ago
| 10_installation/05_requirements/21_architecture_nodes.txt | ||
|---|---|---|
|
[[nodes_supported_OS, the list of supported Operating Systems for Nodes]]
|
||
|
|
||
|
==== Supported Operating Systems
|
||
|
|
||
|
===== For Rudder Nodes
|
||
|
|
||
|
The following operating systems are supported for Rudder Nodes and packages are
|
||
|
available for these platforms:
|
||
|
|
||
|
GNU/Linux:
|
||
|
|
||
|
* Debian 5 to 8
|
||
|
|
||
|
* RedHat Enterprise Linux (RHEL) / RHEL-like 3 and 5 to 7
|
||
|
|
||
|
* Fedora 18
|
||
|
|
||
|
* SuSE Linux Enterprise Server (SLES) 10 SP3, 11 SP1, 11 SP3, 12
|
||
|
|
||
|
* Ubuntu 10.04 LTS (Lucid), 12.04 LTS (Precise), 12.10 (Quantal), 14.04 LTS (Trusty), 16.04 LTS (Xenial)
|
||
|
|
||
|
Other Unix systems:
|
||
|
|
||
|
* IBM AIX 5.3, 6.1 and 7.1
|
||
|
|
||
|
Windows:
|
||
|
|
||
|
* <<install-on-windows, Microsoft Windows>> Server 2008, 2008 R2, 2012, 2012 R2
|
||
|
|
||
|
[TIP]
|
||
|
|
||
|
[[install-on-windows, Install on Microsoft Windows]]
|
||
|
|
||
|
.Windows and AIX Nodes
|
||
|
|
||
|
====
|
||
|
|
||
|
* On Windows, installing Rudder requires the commercial version of CFEngine (named CFEngine Enterprise)
|
||
|
* For IBM AIX, pre-built RPM packages are distributed by Normation only
|
||
|
|
||
|
Hence, as a starting point, we suggest that you only use Linux machines. Once
|
||
|
you are accustomed to Rudder, contact Normation to obtain a demo version for
|
||
|
these platforms.
|
||
|
|
||
|
====
|
||
|
|
||
|
[WARNING]
|
||
|
|
||
|
.Unsupported Operating Systems
|
||
|
|
||
|
====
|
||
|
|
||
|
It is possible to use Rudder on other platforms than the ones listed here.
|
||
|
However, we haven't tested the application on them, and can't currently supply
|
||
|
any packages for them. Moreover, some Techniques may not work properly. If you
|
||
|
wish to try Rudder on other systems, please get in touch with us!
|
||
|
|
||
|
A reference about how to manually build a Rudder agent is available on Rudder's
|
||
|
website here: http://www.rudder-project.org/foswiki/Development/AgentBuild
|
||
|
|
||
|
====
|
||
|
|
||
|
|
||
| 10_installation/05_requirements/21_supported_architecture.txt | ||
|---|---|---|
|
[[nodes_supported_OS, the list of supported Operating Systems for Nodes]]
|
||
|
|
||
|
==== Fully supported Operating Systems
|
||
|
|
||
|
Fully supported Operating Systems are systems that are frequently built and tested on our servers.
|
||
|
Partially suported Operating Systems are systems that have been built and tested at least once but that have not seen continuous flow of fixes.
|
||
|
|
||
|
===== For Rudder Nodes
|
||
|
|
||
|
The following operating systems are supported for Rudder Nodes and packages are
|
||
|
available for these platforms:
|
||
|
|
||
|
GNU/Linux:
|
||
|
|
||
|
* Debian 5 to 8
|
||
|
|
||
|
* RedHat Enterprise Linux (RHEL) / RHEL-like 3 and 5 to 7
|
||
|
|
||
|
* Fedora 18
|
||
|
|
||
|
* SuSE Linux Enterprise Server (SLES) 10 SP3, 11 SP1, 11 SP3, 11 SP4, 12, 12 SP1, 12 SP2
|
||
|
|
||
|
* Ubuntu 10.04 LTS (Lucid), 12.04 LTS (Precise), 12.10 (Quantal), 14.04 LTS (Trusty), 16.04 LTS (Xenial)
|
||
|
|
||
|
Other Unix systems:
|
||
|
|
||
|
* IBM AIX 5.3, 6.1 and 7.1
|
||
|
|
||
|
Windows:
|
||
|
|
||
|
* <<install-on-windows, Microsoft Windows>> Server 2008, 2008 R2, 2012, 2012 R2
|
||
|
|
||
|
[TIP]
|
||
|
|
||
|
[[install-on-windows, Install on Microsoft Windows]]
|
||
|
|
||
|
.Windows and AIX Nodes
|
||
|
|
||
|
====
|
||
|
|
||
|
* On Windows, installing Rudder requires the commercial version of CFEngine (named CFEngine Enterprise)
|
||
|
* For IBM AIX, pre-built RPM packages are distributed by Normation only
|
||
|
|
||
|
Hence, as a starting point, we suggest that you only use Linux machines. Once
|
||
|
you are accustomed to Rudder, contact Normation to obtain a demo version for
|
||
|
these platforms.
|
||
|
|
||
|
====
|
||
|
|
||
|
|
||
|
[[Server_supported_OS, the list of supported Operating Systems for Root server]]
|
||
|
|
||
|
===== For Rudder Root Server
|
||
|
|
||
|
The following operating systems are supported as a Root server:
|
||
|
|
||
|
GNU/Linux:
|
||
|
|
||
|
* Debian 7 and 8 (Debian 9 will be supported when it will be released)
|
||
|
|
||
|
* RedHat Enterprise Linux (RHEL) / RHEL-like 6 and 7
|
||
|
|
||
|
* SuSE Linux Enterprise Server (SLES) 11 SP1 and SP3, 12 SP1
|
||
|
|
||
|
* Ubuntu 14.04 LTS (Trusty), 16.04 LTS (Xenial)
|
||
|
|
||
|
|
||
| 10_installation/05_requirements/22_architecture_root_server.txt | ||
|---|---|---|
|
[[Server_supported_OS, the list of supported Operating Systems for Root server]]
|
||
|
|
||
|
===== For Rudder Root Server
|
||
|
|
||
|
The following operating systems are supported as a Root server:
|
||
|
|
||
|
GNU/Linux:
|
||
|
|
||
|
* Debian 7 and 8
|
||
|
|
||
|
* RedHat Enterprise Linux (RHEL) / RHEL-like 6 and 7
|
||
|
|
||
|
* SuSE Linux Enterprise Server (SLES) 11 SP1 and SP3
|
||
|
|
||
|
* Ubuntu 14.04 LTS (Trusty), 16.04 LTS (Xenial)
|
||
|
|
||
|
==== Hardware specifications for Rudder Agent
|
||
|
|
||
|
Rudder agent has a very small footprint, and only consumes:
|
||
|
|
||
|
* 10 to 20 MB of RAM during an agent run
|
||
|
* a few kB on the network to check or update its policies
|
||
|
* a few kB on the network to report
|
||
|
* around 100 MB of disk space for the installed files and the workspace
|
||
|
|
||
|
These figures will vary depending on your configuration (backup retention,
|
||
|
number of configured components to check, etc...).
|
||
|
|
||
|
==== Hardware specifications and sizing for Rudder Root Server
|
||
|
|
||
|
A dedicated server is strongly recommended, either physical or virtual with at least one dedicated core.
|
||
|
Rudder Server runs on both 32 (if available) and 64 bit versions of every supported Operating System.
|
||
|
|
||
|
===== Memory
|
||
|
|
||
|
The required amount of RAM mainly depends on the number of managed nodes. A general rule for the minimal value is:
|
||
|
|
||
|
* less than 50 nodes: 2GB
|
||
|
* between 50 and 1000 nodes: 4GB
|
||
|
* more than 1000 nodes: 4GB + 1GB of RAM by 500 nodes above 1000.
|
||
|
|
||
|
When managing more than 1000 nodes, we also recommend you to use a multiserver
|
||
|
installation for Rudder as described in chapter <<multiserver-rudder, Multiserver Rudder>>.
|
||
|
|
||
|
For large installations, you should also tune the amount of RAM given to:
|
||
|
|
||
|
* the web application, as explained in the section
|
||
|
<<_configure_ram_allocated_to_jetty, about webapplication RAM configuration>>
|
||
|
* PostgresSQL, as explained in the <<_optimize_postgresql_server, Optimize PostgreSQL Server>> section
|
||
|
|
||
|
===== Disk
|
||
|
|
||
|
The PostgreSQL database will take up most disk space needed by Rudder. The storage
|
||
|
necessary for the database can be estimated by counting around
|
||
|
150 to 400 kB by Directive, by Node and by day of retention of node's
|
||
|
execution reports (the default is 4 days):
|
||
|
|
||
|
----
|
||
|
max_space = number of Directives * number of Nodes * retention duration in days * 400 kB
|
||
|
----
|
||
|
|
||
|
For example, a default installation with 500 nodes and an average of
|
||
|
50 Directives by node, should require between 14 GB and 38 GB of disk space for PostgreSQL.
|
||
|
|
||
|
Follow the <<_reports_retention, Reports Retention>> section to configure the
|
||
|
retention duration.
|
||
|
|
||
| 10_installation/05_requirements/22_unsupported_architecture.txt | ||
|---|---|---|
|
==== Partially supported Operating Systems
|
||
|
|
||
|
Fully supported Operating Systems are systems that are frequently built and tested on our servers.
|
||
|
Partially suported Operating Systems are systems that have been built and tested at least once but that have not seen continuous flow of fixes.
|
||
|
|
||
|
===
|
||
|
|
||
|
[WARNING]
|
||
|
|
||
|
.Partially supported Operating Systems
|
||
|
|
||
|
====
|
||
|
|
||
|
It is possible to use Rudder on other platforms than the fully supported ones.
|
||
|
However, we haven't tested the application on them, and can't currently supply
|
||
|
any packages for them. Moreover, some Techniques may not work properly. If you
|
||
|
wish to get Rudder support on those systems, please get in touch with us!
|
||
|
|
||
|
A reference about how to manually build a Rudder agent is available on Rudder's
|
||
|
documentation here: <<_building_the_rudder_agent, Building the Rudder Agent>>
|
||
|
|
||
|
====
|
||
|
|
||
|
===== For Rudder Nodes
|
||
|
|
||
|
The following operating systems have had an agent built using <<_building_the_rudder_agent, Building the Rudder Agent>>:
|
||
|
|
||
|
* FreeBSD
|
||
|
|
||
|
* Slackware
|
||
|
|
||
|
* Solaris 10 and 11
|
||
|
|
||
|
* Raspbian, based on jessie (via dpkg)
|
||
|
|
||
|
* Debian 8 on ARM (armhf version) (via dpkg)
|
||
|
|
||
|
* OpenSUSE (via rpm)
|
||
|
|
||
|
|
||
|
You can also follow the documentation instructions to build and install Rudder Agent locally on your favorite linux distribution.
|
||
|
Even if this distribution has not been tested by us, it has a reasonable chance of success.
|
||
|
|
||
|
|
||
|
===== For Rudder Root Server
|
||
|
|
||
|
We advise against using an unsupported OS for Rudder server because the server contains
|
||
|
much more code than the agent. This code is tailored against specific OS versions
|
||
|
to work around many system limitations and specificities.
|
||
|
|
||
| 10_installation/05_requirements/23_cloud.txt | ||
|---|---|---|
|
==== Cloud compatibility
|
||
|
|
||
|
The agent provides an abstraction that permits a high level management of the infrastructure.
|
||
|
This abstraction is independant of the underlying hardware. This also works for the cloud -
|
||
|
we can define configuration rules in Rudder that will be applied as well inside a cloud instance as in a virtual server or in a physical machine of a datacenter.
|
||
|
|
||
|
Any cloud instance based on one of the supported operating system is automatically supported.
|
||
|
|
||
| 10_installation/05_requirements/30_hardware_specifications.txt | ||
|---|---|---|
|
==== Hardware specifications for Rudder Agent
|
||
|
|
||
|
Rudder agent has a very small footprint, and only consumes:
|
||
|
|
||
|
* 10 to 20 MB of RAM during an agent run
|
||
|
* a few kB on the network to check or update its policies
|
||
|
* a few kB on the network to report
|
||
|
* around 100 MB of disk space for the installed files and the workspace
|
||
|
|
||
|
These figures will vary depending on your configuration (backup retention,
|
||
|
number of configured components to check, etc...).
|
||
|
|
||
|
==== Hardware specifications and sizing for Rudder Root Server
|
||
|
|
||
|
A dedicated server is strongly recommended, either physical or virtual with at least one dedicated core.
|
||
|
Rudder Server runs on both 32 (if available) and 64 bit versions of every supported Operating System.
|
||
|
|
||
|
===== Memory
|
||
|
|
||
|
The required amount of RAM mainly depends on the number of managed nodes. A general rule for the minimal value is:
|
||
|
|
||
|
* less than 50 nodes: 2GB
|
||
|
* between 50 and 1000 nodes: 4GB
|
||
|
* more than 1000 nodes: 4GB + 1GB of RAM by 500 nodes above 1000.
|
||
|
|
||
|
When managing more than 1000 nodes, we also recommend you to use a multiserver
|
||
|
installation for Rudder as described in chapter <<multiserver-rudder, Multiserver Rudder>>.
|
||
|
|
||
|
For large installations, you should also tune the amount of RAM given to:
|
||
|
|
||
|
* the web application, as explained in the section
|
||
|
<<_configure_ram_allocated_to_jetty, about webapplication RAM configuration>>
|
||
|
* PostgresSQL, as explained in the <<_optimize_postgresql_server, Optimize PostgreSQL Server>> section
|
||
|
|
||
|
===== Disk
|
||
|
|
||
|
The PostgreSQL database will take up most disk space needed by Rudder. The storage
|
||
|
necessary for the database can be estimated by counting around
|
||
|
150 to 400 kB by Directive, by Node and by day of retention of node's
|
||
|
execution reports (the default is 4 days):
|
||
|
|
||
|
----
|
||
|
max_space = number of Directives * number of Nodes * retention duration in days * 400 kB
|
||
|
----
|
||
|
|
||
|
For example, a default installation with 500 nodes and an average of
|
||
|
50 Directives by node, should require between 14 GB and 38 GB of disk space for PostgreSQL.
|
||
|
|
||
|
Follow the <<_reports_retention, Reports Retention>> section to configure the
|
||
|
retention duration.
|
||
|
|
||
|
|
||
Also available in: Unified diff
Fixes #10679: Document fully and partially supported OS