As you probably are aware, Chef is a tool which is meant for automatic provisioning and configuring of systems. So if you have a particular problem falling outside of the regular use cases, both posts on the internet and support enquiries of any kind will probably result in one of two answers: “that is not possible” or “you are doing it wrong”. But - what if you really need this for a rather exotic task or even as an transitory solution?
AWS hat Chef als Technologiepartner. Da nicht nur AWS Chef in ihren Services wie OpsWorks oder OpsWorks Chef Automate nutzt, sondern auch wir, möchte ich eine kurze Einführung von Chef und Test-Kitchen geben. In diesem Teil werden wir feststellen, wie sch
Agentless Provisioning with Chef One of the main points of criticism about Chef I heard over the last few years has been the need to have an agent deployed at remote machines. Sometimes that is not desired, sometimes it is not even possible. Due to this,
ChefConf Online started this year with a big announcement for us. We have received the Chef Hartman award as “Partner of the year Financial Services”! This special award goes to companies that drove successful customer outcomes, developed spec
Target Mode with Chef Server and Chef Automate It is not sufficient to provision remote devices via Target Mode but we also want an overview of node attributes, run history and changed resources. In this post we have a look at how to connect agentless res
Currently, users of Chef are limited to working with the platforms supported by the Chef core. But with the advancements of Target Mode, the story could change quickly. Learn about the idea of a “Platform Support Pack” and what it could mean f