bootstrap script changes

64 views
Skip to first unread message

Jesse Campbell

unread,
Jan 21, 2012, 11:50:28 AM1/21/12
to FrameOS Linux
I am using your bootstrap script, but I made two modifications, which
you may or may not want to incorporate back to your own:

1. change the yum call to include -q, I don't want quite that much
spam when i make a bootstrap call

2. just before the service chef-client start call, add "<%= start_chef
%> --once"
this causes the bootstrap to actually take in the run list specified
on the command line

#2 is the good one, imo

rubiojr

unread,
Jan 21, 2012, 12:13:28 PM1/21/12
to FrameOS Linux
Yah, that's correct Jesse. I should fix that link in the post since I
have fixed bootstrap templates in one of my github repos:

https://github.com/rubiojr/knife-bootstrap-templates

Thanks for noticing.

About the quiet yum param is all about taste I guess ;)

Rgds.

Jesse Campbell

unread,
Jan 21, 2012, 12:18:02 PM1/21/12
to frameo...@googlegroups.com
The way I have it is still different than what you have in your repo,
in your repo, you start chef daemon using the start_chef.
I do a run once using the start_chef call, then I use the regular init
script start procedure.

I'm not sure that using the start_chef method will cause it to log out
to /var/log/chef-client? Maybe it will?

-Jesse

rubiojr

unread,
Jan 21, 2012, 12:52:22 PM1/21/12
to FrameOS Linux
Yeh, I think you're right. It's better to delegate to the init script
I think. That will take into account custom settings in /etc/
sysconfig.

Awesome, thanks.
Reply all
Reply to author
Forward
0 new messages