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, configuring remote machines has become the stronghold of other tools - but a new feature of Chef changes the landscape fundamentally.
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
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
The new agentless collector for the Application Discovery Service can be used to collect data from VMware vCenter and thus is useful whenever the ADS agent cannot be installed on the servers. However, AWS “forgot to mention” how to ensure conn
The State of Target Mode in 2020 After my blog series on the agentless use of Chef dubbed “Target Mode” between August and October 2019, it is time to review what happened since. Updated 14th October 2020
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