Luke has mentioned a few times that people are fairly quiet about numbers, so I thought I''d help out there. Our production Puppet server currently has 75 signed certificates, and I believe essentially all of those systems are active. We have an extremely diverse environment; there are rarely more than three or four systems that can use the same set of classes. So that represents quite a few different classes and different system models. Our long term goal is to manage every system we support via Puppet except for the legacy Solaris environment, which means that we''re slowly scaling up to about 450 hosts. If we get into supporting grid computing and similar large compute clusters the way that we hope and therefore deploy large numbers of identical systems, that number will increase significantly. So far, we''re only running a handful of production systems via Puppet; most of the systems currently in Puppet are test/dev systems. We will, however, begin managing some of our production Kerberos KDCs using Puppet this coming weekend. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
Why won''t you support your legacy solaris environment via puppet?
Russ Allbery <rra@stanford.edu> wrote:
Luke has mentioned a few times that people are fairly quiet about numbers,
so I thought I''d help out there.
Our production Puppet server currently has 75 signed certificates, and I
believe essentially all of those systems are active. We have an extremely
diverse environment; there are rarely more than three or four systems that
can use the same set of classes. So that represents quite a few different
classes and different system models.
Our long term goal is to manage every system we support via Puppet except
for the legacy Solaris environment, which means that we''re slowly
scaling
up to about 450 hosts.
If we get into supporting grid computing and similar large compute
clusters the way that we hope and therefore deploy large numbers of
identical systems, that number will increase significantly. So far,
we''re
only running a handful of production systems via Puppet; most of the
systems currently in Puppet are test/dev systems. We will, however, begin
managing some of our production Kerberos KDCs using Puppet this coming
weekend.
--
Russ Allbery (rra@stanford.edu)
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
---------------------------------
Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Brent Clements <brent_puppet_ml@yahoo.com> writes:> Why won''t you support your legacy solaris environment via puppet?It''s not clear it''s worth the effort to port our modules to Solaris. Our legacy Solaris systems are set up much differently than our Linux systems, they have a maintenance setup that works for them right now, and they''re being slowly phased out anyway. If I thought we were still going to have any noticable number of Solaris systems in five years, I might do something different, but I think that by the time we get all of our Linux systems on-line, we''ll be down to a small handful of systems run in "never change anything except security updates" mode. For example, we''re running mostly Solaris 8 and a bit of Solaris 9 and have no plans to ever install anything newer. In other words, it''s for internal reasons only, not due to any deficiency in Puppet. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
OK great. I''m glad to hear that there are no issues with puppet on Solaris. We actually use solaris alot in production. While it''s a small number(only 40 servers or so compared to 350 linux boxes), we do alot of configuration changes on the systems due to their nature. We have alot of Oracle Boxes and Data Warehouse Systems that need configuration changes regularly such as sudo file mods, etc. Russ Allbery <rra@stanford.edu> wrote: Brent Clements writes:> Why won''t you support your legacy solaris environment via puppet?It''s not clear it''s worth the effort to port our modules to Solaris. Our legacy Solaris systems are set up much differently than our Linux systems, they have a maintenance setup that works for them right now, and they''re being slowly phased out anyway. If I thought we were still going to have any noticable number of Solaris systems in five years, I might do something different, but I think that by the time we get all of our Linux systems on-line, we''ll be down to a small handful of systems run in "never change anything except security updates" mode. For example, we''re running mostly Solaris 8 and a bit of Solaris 9 and have no plans to ever install anything newer. In other words, it''s for internal reasons only, not due to any deficiency in Puppet. -- Russ Allbery (rra@stanford.edu) _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users --------------------------------- Now that''s room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Russ Allbery wrote:> Luke has mentioned a few times that people are fairly quiet about numbers, > so I thought I''d help out there.I''ll add our numbers to this thread. We''re currently converting our entire serverpark to puppet. Right now roughly half is done. I''m counting 376 signed certs and growing. Grtz Ramon