We are pleased to announce two new patch releases for CFEngine, version 3.12.6 and 3.15.3! These releases mainly contain bug fixes and dependency updates, but in 3.15.3 there are also some new enhancements in Mission Portal. The new cf-secret binary is also included in 3.15.3 packages.
Automation is everywhere in our day-to-day IT practices. Many of the processes that have been created for managing hardware and software components were designed, or at least initiated, in a time when managing only a few instances of an application was the norm. When we look at the work required to create, deploy, and maintain applications at a modern scale, the shortcomings of these processes become apparent.
In this blog we’ll share the journey we went on to solve a not-so-easy customer problem: a critical Windows services restart during Puppet agent upgrades. As with most software fixes, it starts with a customer ticket: component DHCP Server service restarts after an upgrade. This troubleshooting journey goes from analyzing Windows installer logs, to using undocumented Windows API calls, and back to the Windows installer logs, until we eventually found a solution.
Automation has evolved from being a management consultant’s go-to-advice to being a central part of every organization’s strategic plan. The biggest misconception about automation is that it is exercised in areas where the company wants to reduce human capital. Contradictorily, automation standardizes mundane processes and frees employees to focus on more value-producing activities that require their unique skills and knowledge.
Enterprises have relied on public cloud providers to shift and transform their legacy workloads using hyperscale infrastructure, but it is vital to ensure that business-critical services are running optimally. Cloud events help developers and operators understand how their workloads hosted on different cloud services are performing at any given time.
The StackStorm project is pleased to announce that the latest version of StackStorm, v3.3.0, is now publicly available! It has been approximately 5 months since our v3.2.0 release and we are releasing a new version containing important features and bug fixes that move the project forward.
When Puppet shows up red, don't panic! You need to figure out what's causing the error, so you can understand whether it's something fixable, or an actual bug. Generally, the first error in a Puppet run is the one you need to concern yourself with. Once the first thing fails, others that run after it or require it to succeed will also fail and could produce a LOT of red text! So scroll to the first red error on your Puppet run.
