On Wed, Nov 1, 2017 at 10:25 PM, ilya m. <[email protected]> wrote:
> Dear foreman users, > > I've recently joined foreman users group. > Welcome! > > 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? > Correct > > 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? > Kind of.. right now the only "supported" way is running all the services (apart from pgsql) is on a single node, [1] aims to change that. Most of the issues are based around the installer and the Puppet modules, your help testing and fixing issues would be amazing! > > My use case varies - but it will probably be 100k nodes in a year - and > upto 500k nodes in few years. > Exciting! I believe this will be one of the biggest deployment. > > It would be ideal if I can run foreman on kubernets with persistent > storage - is that a possibility? > Not for production. See [2] & [3] > > With that said - what challenges have you experienced in large scale? what > services are usual suspects and what can be done to mitigate it? > Lots of dragons.. off the top of my head: - Don't install katello-agent, instead try katello-host-tools and use Remote Ex/Ansible or something else to run 'yum update' on the clients. - Use lots of Smart Proxies, not register any clients to the Katello directly (apart from the Smart Proxies) - Are you using Puppet or any other Config Management tool? That can have a fairly big impact on scaling. - Use a separate DB server > 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. > Although that is an option, it'd prefer to have 1 and fix the issues as you come across them. > Thank you > -ilya > [1] http://projects.theforeman.org/issues/20850 [2] https://www.youtube.com/watch?v=mPjUvNAYp1c [3] https://groups.google.com/d/msg/foreman-dev/IVFkzDFAqSA/2TGa0E3sAQAJ > > -- > 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. > -- 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.
