[edit on Git Hub] A chef-client is an agent that runs locally on every node that is under management by Chef.
When a chef-client is run, it will perform all of the steps that are required to bring the node into the expected state, including: A physical node is typically a server or a virtual machine, but it can be any active device attached to a network that is capable of sending, receiving, and forwarding information over a communications channel.
Once created, the chef-client can be used to deploy, configure, and maintain those instances.
A network node is any networking device—a switch, a router—that is being managed by a chef-client, such as networking devices by Juniper Networks, Arista, Cisco, and F5.
Plugins are available for knife that provide support for external cloud-based services.
knife can use these plugins to create instances on cloud-based services.
In other words, a physical node is any active device attached to a network that can run a chef-client and also allow that chef-client to communicate with a Chef server.
A cloud-based node is hosted in an external cloud-based service, such as Amazon Web Services (AWS), Open Stack, Rackspace, Google Compute Engine, or Microsoft Azure.
A chef-client is an agent that runs locally on every node that is under management by Chef.
When a chef-client is run, it will perform all of the steps that are required to bring the node into the expected state, including: RSA public key-pairs are used to authenticate the chef-client with the Chef server every time a chef-client needs access to data that is stored on the Chef server.
This prevents any node from accessing data that it shouldn’t and it ensures that only nodes that are properly registered with the Chef server can be managed.
Ohai is a tool that is used to detect attributes on a node, and then provide these attributes to the chef-client at the start of every chef-client run.
Use Chef to automate common network configurations, such as physical and logical Ethernet link properties and VLANs, on these devices.Containers are an approach to virtualization that allows a single operating system to host many working configurations, where each working configuration—a container—is assigned a single responsibility that is isolated from all other responsibilities.