Easy ad-hoc remote tasts and the future of Chef on the desktop
summary
A new Chef Workstation beta ships a command called chef run that uses train for ssh and winrm to run single resources, recipes or policyfile bundles on remote nodes; it auto‑installs Chef client, pins a policyfile bundle, and runs in local mode. Demo shows nginx and IIS deployed to six nodes and results appearing in Automate. Currently it requires Chef >14.1.1 on targets, limits parallel runs to 24 hosts, and emits user‑friendly error codes.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:29Agenda
- 3:22What's Chef Workstation
- 13:26Run a Recipe on the Target Node
- 16:17Policy File Bundle
- 18:57Specifying Multiple Nodes
- 19:23Arrange Syntax
- 21:05Windows Support
- 22:36Multi-Target Windows Hosts
- 23:17Set Up these Hosts as Iis Web Servers
- 24:47Automate Integration
- 28:06Limitations
- 29:43Auto Update
- 32:13Inventory Support
- 36:06Open Source
related talks
15mServerless Apps with Node.JS in OpenWhisk and Adobe I/O Runtime
05mBare Metal Provisioning With Tinkerbell
44mNode & Express as Workflow Tools
33mEasily expand your on-premises OpenShift cluster
42mBuild Better Desktop Apps with Ember
39m"Spinning up Node in the Browser"
24mNitro, the Server toolkit you probably need
18mvinxi: I needed a server