On Fri, Aug 22, 2014 at 10:38 AM, Charlie Baum <charlieb...@gmail.com> wrote:
> Running Puppet on Windows 2008r2 and 2012 in no daemon mode for a few > applications. Issue we are having is some tools/apps such as .net 4.5 and > some MSI files we are installing require a reboot. In no daemon mode, when > the system reboots and comes back up the puppet recipe doesn't continue > where it left off, so you have to run the puppet command again to kick it > off. If there's a couple reboots, there are multiple interactions here. > If this is on 10 systems, it's a little ridiculous. > > Any idea how we can get around this? How we can get the recipe to pick up > where it left off? Can't seem to find anything out there related to this > issue. > Puppet does need to be kicked back off. The agent runs when the system is booted, so it just picks back up and starts processing puppet again (the whole idempotent catalog, the net affect is that it picks up where it left off). To achieve the same with a no daemon mode you need to set up something to make puppet apply run when the box is first booted. The least fancy way is to just set up a script to run when the box is first turned on. The harder part is getting it to work without having to login. A scheduled task could achieve this with the trigger "At startup"[1]. Be aware that networking may or may not be available yet. Note that while "at startup" is a valid trigger and it is in the win32-taskscheduler[2] gem version that we use, it will likely not work with the scheduled_task resource[3] without changes to validation of win32_taskscheduler[4] and other areas to allow for at_startup to be considered a valid trigger schedule value. [1] http://technet.microsoft.com/en-us/library/cc748841.aspx [2] https://github.com/djberg96/win32-taskscheduler/blob/win32-taskscheduler-0.2.2/lib/win32/taskscheduler.rb#L110 [3] https://docs.puppetlabs.com/references/3.6.latest/type.html#scheduled_task-attribute-trigger [4] https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb#L347-L348 > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/1bdf4074-61a7-4a1f-892e-61f2f75b74f1%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/1bdf4074-61a7-4a1f-892e-61f2f75b74f1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Rob Reynolds Developer, Puppet Labs *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September 20-24 in San Francisco* *Register by September 8th to take advantage of the Final Countdown <https://www.eventbrite.com/e/puppetconf-2014-tickets-7666774529?discount=FinalCountdown> * *--**save $149!* -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMJiBK5mRFUh3zwDXcymBRpZcExL%3DYNgZHNszLPBYJ8DLY5c%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
