- From: Lamont Granquist <
>
- To:
- Subject: [chef] Re: RE: Re: override argument
- Date: Tue, 17 Jun 2014 10:07:08 -0700
You can compose your roles such that you apply
'role[base],role[app1],role[app2]' to a server. The 'base' role
may install user accounts, security settings, resolv.conf,
logrotation for system logs, etc and other stuff not necessarily
directly about running the app. The application roles should
install the prerequisites for the app and deploy the app itself.
In order to immediately deploy 'app1' you can run "chef-client -o
'role[app1]'" which will only run the stuff necessary to deploy
app1 and will skip running the rest of the recipes in the base
role or for app2. That will allow chef to complete deploying app1
much faster.
You probably do not want to overuse override run lists. They're
for doing-a-piece-of-the-whole-run-list-right-now, and only doing
that occasionally on demand.
On 6/17/14, 9:47 AM, Florian Hehlen wrote:
"
type="cite">
HI,
Thank you Indra. I am aware of the feature. I
am just wondering if it’s safe to use –o or is it really
only for testing.
From: Indra k [
">mailto:
]
Sent: 17 June 2014 13:10
To:
">
Subject: [chef] Re: override argument
Hi Flo,
Ya, it gets run.
chef-client -o "recipe[something]"
the above command runs a chef-client with given runlist .
You can also refer this by
"chef-client -h" ---which shows a what are all
parameters we can run with chef-client.
Thanks,
Indra
From: Florian Hehlen <
">
>
To: "
">
"
<
">
>
Sent: Tuesday, 17 June 2014 3:42 PM
Subject: [chef] override argument
What
is the contract for the –o argument on
chef-client? Can I expect that the only
thing that changes between running
‘chef-client’ and ‘chef-client –o
“recipe[something]”’, is the recipes that
will get run?
LEGAL DISCLAIMER
This communication and any attached documents
are strictly confidential and/or legally
privileged and they may not be used or
disclosed by someone who is not a named
recipient. If you have received this
electronic communication in error please
notify the sender by replying to this
electronic communication inserting the word
"misdirected" as the subject and delete this
communication from your system.
LEGAL DISCLAIMER
This communication and any attached documents are strictly
confidential and/or legally privileged and they may not be used
or disclosed by someone who is not a named recipient. If you
have received this electronic communication in error please
notify the sender by replying to this electronic communication
inserting the word "misdirected" as the subject and delete this
communication from your system.
|
Archive powered by MHonArc 2.6.16.