Foreman Hardware Requirements

Folks,

Does anybody have any comments on what the hardware requirements for
Foreman are?

Something that could be put in the manual as the advice is only notable for
it's absence at the moment.

Stories like "I'm running Puppet Master/CA/Foreman/ENC for X hundred
machines with Y CPUs and Z Gb RAM" would be a great help.

I know the requirements won't exactly be stratospheric, but some guidelines
would be good.

Cheers

Duncan

P.S. I'm currently running Puppet Master, CA, Foreman, ENC for 200 hosts
on 1 vCPU and 1Gb RAM without much use of swap space.

We'll be increasing this, but interested in other stories.

The RedHat Satellite 6 Installation Guide
<https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/index.html> (RedHat
commercial packaging of Foreman/Katello/Pulp/Candlepin/Puppet) have some
good information about requirements and scalability:

> - There should be at least one networked host with the following
> minimum specifications:
> - 64-bit architecture
> - Red Hat Enterprise Linux 6.5 or later
> - A minimum of two CPU cores, but four CPU cores are recommended.
> - A minimum of 8 GB memory but ideally 12 GB of memory for each
> instance of Satellite. Use 4 GB of swap space where possible.
>
> see 1.5. Prerequisites
<https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html>

and

Puppet scalability within Satellite on Red Hat Enterprise Linux 6.5
> Capsules are as follows:
>
> 1. On the minimum amount of CPUs (two CPUs):
> 1. At 1 puppet class per host: Not tested
> 2. At 10 puppet classes per host: Maximum of 1020-860
> 3. At 20 puppet classes per host: Maximum of 375-330
> 2. On the recommended amount of CPUs (four CPUs):
> 1. At 1 puppet class per host: Maximum of 2250-1875
> 2. At 10 puppet classes per host: Maximum of 1600-1250
> 3. At 20 puppet classes per host: Maximum of 700-560
>
> see 5.1. Red Hat Satellite Capsule Server Scalability
<https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Capsule_Servers.html>

··· On Wednesday, February 11, 2015 at 3:11:58 PM UTC+1, Duncan Innes wrote: > > Folks, > > Does anybody have any comments on what the hardware requirements for > Foreman are? > > Something that could be put in the manual as the advice is only notable > for it's absence at the moment. > > Stories like "I'm running Puppet Master/CA/Foreman/ENC for X hundred > machines with Y CPUs and Z Gb RAM" would be a great help. > > I know the requirements won't exactly be stratospheric, but some > guidelines would be good. > > Cheers > > Duncan >

I'm running on a VM.

Foreman, Puppet Master, Puppet CA, Postgresql for PuppetDB+ForemanDB,
Smart-Proxy, Apache/Passenger, ISC dhcp, Puppet agent, Splunk agent, NRPE
agent on CentOS 6. The VM is configured for 12GB RAM, 2vCPUs, 4GB swap,
20GB of disk, it runs with a 5min load average of 1, about 6.5GB RAM used,
1.8GB cached, and 0 swap used. We have 5 puppet environments and are using
exported resources for about 2500 nagios checks, and I run trends on about
10 custom facts. The system seems to run fine now, though we started it 1
vCPU and 4GB of RAM when we had about 20 hosts on it. With 8GB, the trends
processing seemed to get hung up on a daily basis and the VM would run out
of swap eventually, so 12GB seems like the magic number for us.

··· On Wednesday, February 11, 2015 at 9:13:49 AM UTC-5, Duncan Innes wrote: > > P.S. I'm currently running Puppet Master, CA, Foreman, ENC for 200 hosts > on 1 vCPU and 1Gb RAM without much use of swap space. > > We'll be increasing this, but interested in other stories. >

Ha - for unknown reasons I didn't even think about looking up the Satellite
6 docs.

Thanks

> I'm running on a VM.
>
> Foreman, Puppet Master, Puppet CA, Postgresql for PuppetDB+ForemanDB,
> Smart-Proxy, Apache/Passenger, ISC dhcp, Puppet agent, Splunk agent, NRPE
> agent on CentOS 6. The VM is configured for 12GB RAM, 2vCPUs, 4GB swap,
> 20GB of disk, it runs with a 5min load average of 1, about 6.5GB RAM used,
> 1.8GB cached, and 0 swap used. We have 5 puppet environments and are using
> exported resources for about 2500 nagios checks, and I run trends on about
> 10 custom facts. The system seems to run fine now, though we started it 1
> vCPU and 4GB of RAM when we had about 20 hosts on it. With 8GB, the trends
> processing seemed to get hung up on a daily basis and the VM would run out
> of swap eventually, so 12GB seems like the magic number for us.
>
>
we hope to fix trends for 1.8, there is an open PR [1] that should reduce
the load greatly, if you are willing to give a try that would be great!

thanks,
Ohad

[1] https://github.com/theforeman/foreman/pull/2126

··· On Wed, Feb 11, 2015 at 4:36 PM, Sean Alderman wrote:

On Wednesday, February 11, 2015 at 9:13:49 AM UTC-5, Duncan Innes wrote:

P.S. I’m currently running Puppet Master, CA, Foreman, ENC for 200 hosts
on 1 vCPU and 1Gb RAM without much use of swap space.

We’ll be increasing this, but interested in other stories.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Cool! I'll take a look when we get there. I haven't looked at trends in a
while, but we don't seem to be having trouble with them at the current
resource allocation and Foreman 1.7.2.

··· On Wednesday, February 11, 2015 at 10:32:03 AM UTC-5, ohad wrote: > > > > On Wed, Feb 11, 2015 at 4:36 PM, Sean Alderman > wrote: > >> I'm running on a VM. >> >> Foreman, Puppet Master, Puppet CA, Postgresql for PuppetDB+ForemanDB, >> Smart-Proxy, Apache/Passenger, ISC dhcp, Puppet agent, Splunk agent, NRPE >> agent on CentOS 6. The VM is configured for 12GB RAM, 2vCPUs, 4GB swap, >> 20GB of disk, it runs with a 5min load average of 1, about 6.5GB RAM used, >> 1.8GB cached, and 0 swap used. We have 5 puppet environments and are using >> exported resources for about 2500 nagios checks, and I run trends on about >> 10 custom facts. The system seems to run fine now, though we started it 1 >> vCPU and 4GB of RAM when we had about 20 hosts on it. With 8GB, the trends >> processing seemed to get hung up on a daily basis and the VM would run out >> of swap eventually, so 12GB seems like the magic number for us. >> >> > we hope to fix trends for 1.8, there is an open PR [1] that should reduce > the load greatly, if you are willing to give a try that would be great! > > thanks, > Ohad > > [1] https://github.com/theforeman/foreman/pull/2126 > >> >> On Wednesday, February 11, 2015 at 9:13:49 AM UTC-5, Duncan Innes wrote: >>> >>> P.S. I'm currently running Puppet Master, CA, Foreman, ENC for 200 >>> hosts on 1 vCPU and 1Gb RAM without much use of swap space. >>> >>> We'll be increasing this, but interested in other stories. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >

Anybody else?

Would be better to have a broader view of Katello instances, but I'll base
figures on what Sean (thanks) has posted and my own experience.

D