Operations | Monitoring | ITSM | DevOps | Cloud

Puppet and Government: Maintaining compliance in complex hybrid cloud environments

This blog is the third in a four-part series about how Puppet can help government agencies meet compliance and security requirements. Read the second post here. Government agency IT departments know that migrating applications to the cloud can improve efficiency, increase visibility, and reduce costs. They also recognize the value in keeping some operation resources on-premises.

Change in behavior: multiple cf-execd processes

Recently we introduced new feature where you can trigger agent runs and report collection from the Mission Portal UI. This required our daemon cf-execd to behave a bit differently when periodic agent runs occur. Previously the daemon would create a new thread in which to run cf-agent, capture output, wait for completion and move on. We changed the behavior so that the daemon forks itself and then fork/execs cf-agent as before, with the forked cf-execd processing agent run output.

CFEngine Build System version 2

A while back we released version 2 of cfbs, and even though we release versions of this tool quite frequently, without announcing it on the blog, we thought this was a good opportunity to talk a bit about the tool, what’s new and our direction with it in the future. The reason why we called this the “2.0” release is that we are trying to follow semantic versioning, and there were some big new features in the release which could be considered breaking changes.

Improved Design Interface. Less Code. Runbook Studio 5.0 Makes Runbook Automation a Cinch

Kelverion Runbook Studio V5.0 makes it even easier for organizations to automate IT service desk requests and reduce IT burden. In its fifth iteration, The Runbook Studio has undergone a significant design overhaul. The Studio’s technical capabilities have always been exceptional and now it has a user interface to match. On top of that, this version takes Kelverion’s low code/no-code design environment to the next level.

Puppet and Government: DevSecOps in government environments

This blog is the second in a four-part series about how Puppet can help government agencies meet compliance and security requirements. Read the first post here. Zero Trust is a strategy created to combat system intrusions through a “never trust, always verify” model. DevSecOps is a collaborative software development strategy that integrates development, security, and operations practices into a continuously evolving lifecycle.

Sponsored Post

4 Database Access-Control Methods to Automate

Regardless of which role a person has in an organization, they will always need access to one or more databases to be able to perform the functions of their job. Whether that person is a cashier at McDonald's or a technical account manager supporting a Fortune 500 company, data entry and retrieval is core to the services they provide.