Hi Philip,

open source puppet 3.x documentation seems to have stopped updating in
favour of PE documentation as per puppet support. that project is not
handled by me any longer, my colleagues have gone with foreman, it's
bootstrapping and scaling is very flexible, it is already a distributed
architecture using lightweight smart proxies, and have all  the components
maintained and documented better. also provides an escape from vendor lock,
you can use saltstack, Chef, and even there are ansible scripts on the net
floating around. not to mention we get the extra patching/life cycle
management workflow, openscap auditing, among other complementary features
out of the box. and an awesome foreman community over irc/mailing list, and
if you need commercial support you can go with Red Hat Satellite 6 which
will add the content management feature "Katello"  to your workflow.

On 10 September 2015 at 18:13, Philip Dixon <pdixon0b...@gmail.com> wrote:

> How has this been going for you. I have a similar situation. Am using
> "puppet server" version 1.1.1 (based on 3.8.2) and am seeing the same
> problem.
>
> On Saturday, August 29, 2015 at 12:48:11 AM UTC-7, Abu Yousef wrote:
>>
>> Hi,
>>
>> I have the requirement to manage thousands of nodes, I'm researching the
>> best effective way to scale Puppet 3.8.2 for now, later 4.2 with puppetserver
>> using haproxy to load balance more than 2-3 servers "compile only
>> masters" sharing a single CA, puppetDB, and possibly
>> puppetboard/puppetdbexplorer, the puppet  docs are outdated and do not
>> follow the PE enterprise split,  the interest is to use 3.x series so it
>> could be utilized by itself or as part of foreman smart proxy.  some
>> questions i can not see on the doc, is that can't puppetserver now handle
>> proxying CA certificate back to CA with no need for a webserver? with the
>> trapperkeepr, is it ready now to customize server functionalities to CA,
>> compile, file server, ..etc specific roles, how would one go about turing
>> on/off these features?
>>
>> whatever work done to achieve this should be easily ported to 4.x as it
>> is based on the puppetserver.
>>
>> TIA
>>
>> Abu Yuosef
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/641b6b40-5dda-4d19-8a81-55a3fbd3a4d6%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/641b6b40-5dda-4d19-8a81-55a3fbd3a4d6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN4dctomEEv%2Bz9kBBAKJazdLmYzYAyfEdqeko9X%3DsKa51maQVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to