Question about chef server as a node


#1

Hello,

I am just learning the ropes with chef - I have setup a chef server and some nodes under VirtualBox to get familiar a bit, and one question I have is whether it’s common to have your chef server also be a node. Let’s say I also want to install munin for monitoring my nodes, and I want munin server to run on the same machine as chef server, and I want to use the munin opscode recipe to do so….can I make my chef server a node and install it that way, or is it preferable to have a dedicated machine just for chef and not try to put other monitoring or utility processes on that machine?

Thanks for listening!

Greg


#2

This is what we do - I have a role for our Chef server which sets up a
backup cron and handles other base role stuff. The chef server is
self-contained, so you can safely install and bootstrap the Chef client
just as you would on any other node.

On Sat, May 4, 2013 at 7:13 PM, Greg Lappen greg@lapcominc.com wrote:

Hello,

I am just learning the ropes with chef - I have setup a chef server and
some nodes under VirtualBox to get familiar a bit, and one question I have
is whether it’s common to have your chef server also be a node. Let’s say
I also want to install munin for monitoring my nodes, and I want munin
server to run on the same machine as chef server, and I want to use the
munin opscode recipe to do so….can I make my chef server a node and install
it that way, or is it preferable to have a dedicated machine just for chef
and not try to put other monitoring or utility processes on that machine?

Thanks for listening!

Greg


#3

Thanks for the reply! Can you expand on what you mean by “base role stuff”?
Is monitoring included in that?

On Saturday, May 4, 2013, Christopher Armstrong wrote:

This is what we do - I have a role for our Chef server which sets up a
backup cron and handles other base role stuff. The chef server is
self-contained, so you can safely install and bootstrap the Chef client
just as you would on any other node.

On Sat, May 4, 2013 at 7:13 PM, Greg Lappen <greg@lapcominc.com<javascript:_e({}, ‘cvml’, ‘greg@lapcominc.com’);>

wrote:

Hello,

I am just learning the ropes with chef - I have setup a chef server and
some nodes under VirtualBox to get familiar a bit, and one question I have
is whether it’s common to have your chef server also be a node. Let’s say
I also want to install munin for monitoring my nodes, and I want munin
server to run on the same machine as chef server, and I want to use the
munin opscode recipe to do so….can I make my chef server a node and install
it that way, or is it preferable to have a dedicated machine just for chef
and not try to put other monitoring or utility processes on that machine?

Thanks for listening!

Greg


#4

Yep, we have a base role which includes configurations that are common
across all nodes. That’s where monitoring is setup, as well.

On Sat, May 4, 2013 at 8:09 PM, Greg Lappen greg@lapcominc.com wrote:

Thanks for the reply! Can you expand on what you mean by “base role
stuff”? Is monitoring included in that?

On Saturday, May 4, 2013, Christopher Armstrong wrote:

This is what we do - I have a role for our Chef server which sets up a
backup cron and handles other base role stuff. The chef server is
self-contained, so you can safely install and bootstrap the Chef client
just as you would on any other node.

On Sat, May 4, 2013 at 7:13 PM, Greg Lappen greg@lapcominc.com wrote:

Hello,

I am just learning the ropes with chef - I have setup a chef server and
some nodes under VirtualBox to get familiar a bit, and one question I have
is whether it’s common to have your chef server also be a node. Let’s say
I also want to install munin for monitoring my nodes, and I want munin
server to run on the same machine as chef server, and I want to use the
munin opscode recipe to do so….can I make my chef server a node and install
it that way, or is it preferable to have a dedicated machine just for chef
and not try to put other monitoring or utility processes on that machine?

Thanks for listening!

Greg