- From: Stephen Corbesero <
>
- To: "'
'" <
>
- Subject: [chef] RE: chef-client , apply role
- Date: Tue, 7 Jan 2014 14:32:18 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
There were many responses to this, but I want to get back to the original
question.
Is there a way to just get a node into a role, but not have go through that
role's run list?
The use case I am thinking of is provisioning a new node. Sometimes the very
first chef run fails. If we could get the node into its correct role, and
chef-client running as a cron job or service, the node will eventually
converge.
Cfengine used to provide something like this. It was a failsafe
configuration that a cfengine run would fall back to if the main
configuration failed. It was a way to minimize the risk of disconnecting
your infrastructure from configuration management if you accidentally
deployed a bad main configuration.
--
Stephen Corbesero, Performance Engineer
-----Original Message-----
From: Sam Darwin
[mailto:
Sent: Thursday, January 02, 2014 5:29 AM
To:
Subject: [chef] chef-client , apply role
is there a way to run:
chef-client -o "role[abc]"
that is, to apply a role without running the entire run_list ?
this should not be ephemeral and have little effect... it should cause all
the results that having the role in the real run_list would have, update the
chef-server with attributes in a persistent way and everything else. I
would also add the role to the real run_list . But I don't want to run all
recipes on the client at that moment.
Archive powered by MHonArc 2.6.16.