On Dec 15, 5:04 am, Patrick <kc7...@gmail.com> wrote: > I'm looking for a way to run more than one puppetmaster on the same server > under passenger. Most of the puppet CPU load is waiting for the catalogs to > compile. This also seems to be mostly what takes large amounts of RAM. I > have storedconfigs on. > > I want to be able to move the fileserver to a different pool of puppetmaster > processes. Is there an easy way to tell the client, either in the catalog or > in the config file, to get the files from a different port than the catalog?
You can write source => "puppet://<alternative_server>/..." instead of source => "puppet:///...". If <alternative_server> resolves to the same physical machine then apache can direct it to a different virtual host. (And if it resolves to a different physical machine then no worries on that level.) I'm not sure, however, whether you can run separate copies of Passenger in different vhosts. (But if not, then it would be a desirable feature.) > Is there a better way to do this? What I really want is for the cheap file > requests to stop being blocked by the expensive catalog requests and keep the > RAM usage low on the file serving processes. I don't know whether it's better, but since you're serving through Apache anyway, you could serve your files directly via http. That has implications on where you put said files on disk and on both client and file system security management, but it ought to be very fast, and it will scale as Apache itself does. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
