Is the reboot resource idempotent? To extend Joshua’s answer one can run chef-client as a daemon on a node and run this recipe.
# Put resources that need to converge before a reboot here
resource1 “Some resource”
resource2 “Some resource”
# Reboot the machine
reboot “Need to reboot for kernel changes to take effect”
# Put resources that need to converge after a reboot here
Resource3 “Some resource”
Resource4 “Some resource”
What will this recipe do after the reboot? I know it will not converge resource1 and resource2, but will it converge the reboot resource? You can put guards against it but just wondering what the vanilla behavior will be.
Chris
From: Joshua Timberman [mailto: " target="_blank"> ]
Sent: Monday, August 10, 2015 9:56 AM
To: " target="_blank">
Subject: [chef] Re: Does Chef have support for multi-boot install
You are correct in that Chef doesn't have a "resume after reboot" option. However, Chef is both idempotent and convergent. Rerunning chef after reboot will result in NOT configuring the system resources that are in the state declared by the recipes. For example, if your recipes manage a config file and install a package, those won't change when chef reruns. However if the reboot made a change to a file chef manages then it will be updated by chef after the reboot.
Make sense?
Cheers,
Joshua
On Sunday, August 9, 2015, Jubal Kohlmeier < " target="_blank"> > wrote:Hello,
I am new to chef, and have gone the effort to port a few cookbook recipes to the AIX operating system. In one of my recipes, i update kernel parameters. However, on AIX, the parameters
require a reboot of the OS for them to come into effect. Does CHEF have multi-boot support? I suspect not. Ive found recipe's for shutting down the os, but nothing for support the
chef kitchen for 'waiting for the os to come back up' and continue installation.
Do i have it correctly?
Jubal Kohlmeier
503-747-1333 503-502-7733 cell
IT Specialist Oracle Applications Benchmark
Archive powered by MHonArc 2.6.16.