Sensu 2.0 and Habitat are both modern distributed systems, one for monitoring, the other for application packaging and deployment.

Audits are stressful. If your organization is subject to regulatory compliance rules, chances are you’ve experienced firsthand how time-consuming and painful they can be.

The world of application packaging and deployment can be viewed as a spectrum where at one end we have hand-crafted installation/run scripts on physical infrastructure and on the other are fully containerized applications making the most of cloud-native services.

Two years ago, Chef launched Habitat as a way to enable application teams to build, deploy, and manage any application in any environment.

On Wednesday, August 1, we presented a webinar on using InSpec with Cisco IOS network devices. Today, fewer than 10% of network teams are using any automation tools, yet through the NetOps 2.

Habitat can seem like magic – allowing you to deploy and manage any app, anywhere, in the same way. It’s not magic, however, it’s deliberate, very well thought out technology. In Habitat, the application itself is the unit of automation.

One of the best things about working at Chef is seeing how our customers use technology to create innovations and make a real difference through their work.

Here’s what happened in July across the Chef, Habitat, and InSpec open-source communities. Chef This month we released Chef Client 14.3, the newest release in the Chef 14 series. Chef 14.3 introduces the concept of preview resources, adds several new resources, and cleans up the shell_out API. What is a preview resource, you ask?

Chef, InSpec, and Habitat provide workflows for automating everything you manage, from infrastructure configuration to security auditing to application releases.