Regarding the orchestration vs config management reboots debate, the way I handle this is by using the schedule meta parameter. I define a reboot schedule and it is configurable via a Foreman parameter which allows ops to only reboot systems in the middle of the night and such. We also allow staging of large downloads (MSI) during the day without doing the install/rebooting. My focus is Windows desktop though.
at 14:26 there's a mistake. 0644 means the group "Users" can only read, not read/write (adminstrator can read/write). It would need to be 0664 for what is said/shown in the WIndows screen
at least with 2.7x, puppet preserves line endings in templates and puppet agent -t works fine. Run the puppet shell bat first and then you can use irb, fire off puppet runs, etc.
Shows how not to do it, doesn't show how to do it. Example: scheduled_taks { 'run_job': command => 'c:/jobs/run_job.exe', #fail ! } Then leaves us hanging. _should_ I do this: scheduled_taks { 'run_job': command => 'c:\jobs un_job.exe', } or this?: scheduled_taks { 'run_job': command => "c:\\jobs\ un_job.exe", } Well if I'm going to do something like this: command => '$path/executable', Then I MUST do this: command => "$path\\executable", And not this: command => '$path\executable', or maybe I should do this? command => "${path}\\executable", Discuss.
Could not agree more. Most people know what they're doing when they're thinking of using a config mgmt tool, so there's no need to speak to them like they were introduced to IT yesterday.
Regarding the orchestration vs config management reboots debate, the way I handle this is by using the schedule meta parameter. I define a reboot schedule and it is configurable via a Foreman parameter which allows ops to only reboot systems in the middle of the night and such. We also allow staging of large downloads (MSI) during the day without doing the install/rebooting. My focus is Windows desktop though.
at 14:26 there's a mistake. 0644 means the group "Users" can only read, not read/write (adminstrator can read/write). It would need to be 0664 for what is said/shown in the WIndows screen
at least with 2.7x, puppet preserves line endings in templates and puppet agent -t works fine. Run the puppet shell bat first and then you can use irb, fire off puppet runs, etc.
cool to see a couple of my windows puppet modules in here. nice talk good stuff :)
This looks odd: on puppet forge "addening/winntp" was deleted from puppet forge 2012, this video is dated 2013. forge.puppetlabs.com/adenning/winntp .
Can you deploy from Windows to Windows just by using the agent? I'm guessing no, but I don't want to install Linux to manage Puppet agents. :)
i use uac. don't see any reasons to disable it. i just know how to cook it ;)
Shows how not to do it, doesn't show how to do it. Example:
scheduled_taks { 'run_job':
command => 'c:/jobs/run_job.exe', #fail !
}
Then leaves us hanging.
_should_ I do this:
scheduled_taks { 'run_job':
command => 'c:\jobs
un_job.exe',
}
or this?:
scheduled_taks { 'run_job':
command => "c:\\jobs\
un_job.exe",
}
Well if I'm going to do something like this:
command => '$path/executable',
Then I MUST do this:
command => "$path\\executable",
And not this:
command => '$path\executable',
or maybe I should do this?
command => "${path}\\executable",
Discuss.
This guy is so pretentious, jeez.
Could not agree more. Most people know what they're doing when they're thinking of using a config mgmt tool, so there's no need to speak to them like they were introduced to IT yesterday.