[chef] Re: Re: Low-memory chef servers

[Morgan Blackthorne < >]

So I tried setting this up, and ran into a snag... https://gist.github.com/stormerider/5656de72d29385249fcd

Basically, host_B should only run chef-solr, but chef-server-ctl reconfigure is unhappy about trying to notify erchef service when it hasn't been defined?

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Fri, Aug 2, 2013 at 1:39 PM, Daniel DeLeo < " target="_blank"> > wrote:

On Tuesday, July 30, 2013 at 2:11 PM, Morgan Blackthorne wrote:

Something I saw in the past was that a suggestion for low memory servers was to break apart the services so different pieces run on different boxes. Is that still viable under Chef 11, and if so, is there a guide to how to do so? Ideally, I want to shift some of the memory usage over to server_b but leave the CPU crunching on server_a.

Thanks!

--

~*~ StormeRider ~*~

Should be possible, but you're gonna have to roll up your sleeves a bit. The basic idea is to set the component['enable'] setting for each component as necessary, and use the component['vip'] settings to configure all the services to talk to each other.

http://docs.opscode.com/config_rb_chef_server.html 

-- 

Daniel DeLeo