I know of an 85k node deployment. It *really* depends on what services you expect to run.
With 10k hosts which run puppet every 30 minutes you will flatline a 24 cpu box. We have 11k so far with puppet checking in between 2 and 8 times a day depending on the environment and we run about 20% cpu (on said 24 cpu box (with 64G ram)). Our target will be ~25k servers and we expect to run roughly 50% cpu with that. We don't do a lot on publishes (we're satellite 6 users) but they add to cpu quite a lot. There is quite a bit of tuning you need to do out of the box: - apache (keepalive, spare / max servers) - passenger (workers and passenger limit - there are a few bugs which can cause passenger processes to explode) - postgres (connections, work mem and cache mem) - qpidd / qdrouterd (limits / aio limit) In terms of migrations, the registration process is painful (more than 10 / 15 simultaneous will cause you issues) - satellite has an old(er) version of candlepin which I understand has some serial limitations. Be careful with what you as expecting the capsules / smart-proxy to offload all the load from the master isn't as you might think. There are a lot of things which simply use the smart proxies as, well, a proxy hence just feed the request directly to the master (subscriptions, puppet fact / report / catalog processing etc). Hope this helps On Thursday, November 2, 2017 at 3:38:28 AM UTC-4, ilya m. wrote: > > Dear foreman users, > > I've recently joined foreman users group. > > Previously (4 years ago) i use to manage spacewalk - which was doing its > job well for 2k+ nodes - but i'd experience issues time to time with > stability + scalability. Also - postgres db left alot to be desired and > seemed a bit messy. This was 4 years ago - and i'm guessing alot has > changed since then - but it also seems like Spacewalk is on maintenance > mode and RedHat moved on to Foreman/Katello? > > I'm now tasked with new patching/management solution for linux - and i'm > exploring foreman as one of the alternatives. > > I'm curious how far foreman can scale and what services might be the > bottlenecks. Can i scale the bottleneck services? > > My use case varies - but it will probably be 100k nodes in a year - and > upto 500k nodes in few years. > > It would be ideal if i can run foreman on kubernets with persistent > storage - is that a possibility? > > With that said - what challenges have you experienced in large scale? what > services are usual suspects and what can be done to mitigate it? > > I'm guessing there arent too many solutions that work well in that scale - > so i'm open to splitting it up in smaller environments based on business > groups. I'd then create an aggregator and routing engine - if need be. > > Thank you > -ilya > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
