This is the second post in a four-part series on why Open Source Puppet users have made the decision to move to Puppet Enterprise. If you’re considering making this change, read on for pros and cons! As more and more businesses are moving from Open Source Puppet (OSP) to Puppet Enterprise (PE), they are experiencing multiple benefits. In this blog series, we’re exploring the biggest benefits we hear from customers about their experience moving from OSP to PE.

Whether it's in classrooms or on Zoom calls, the kids have headed back to school! Bright-eyed students are gearing up to study new subjects and test their brains. Hopefully on their report cards, failure isn’t inevitable. Before the first day, parents load up their kids’ backpacks with everything they’ll need. Being well equipped with good supplies is the best way to stay focused and educate “reliably”. Likewise, SREs need the right tools and practices for the job.

Kubernetes has what you may consider an aggressive release cycle. There have been three to four releases per year since 1.0 was released in July of 2015. Perhaps you’ve found it all too easy to get behind a couple of versions. Running the latest, or nearly latest release will help protect your organization from security issues. This is because releases are deprecated once they fall three minor versions behind the latest. Staying current isn’t just about security though!

Earlier this year StackStorm established a partnership program with some first partners that supported StackStorm in its Open Source journey when the project joined the Linux Foundation. The Partners Program was created to recognize companies and organizations that provide ongoing assistance to the StackStorm Open Source project. Because of the substantial support provided by these partners, we have been able to expand and improve StackStorm.

Welcome to the Civo update for September 2021. In case you missed the big news... this week we successfully launched our first region in Frankfurt, Germany. Plus we announced our new strategic partner, THG Ingenuity, who invested $2 million into the company. This will allow us to quickly invest in our infrastructure, including more regions across the globe throughout the next 12 months.

Open RAN or ORAN is a game-changing Radio Access Network (RAN) evolution combining RAN functionality with cloud-native design, scale and automation. Legacy RAN was and is still intentionally designed using closed and proprietary architectures that locked operators to a particular vendor, for both radio and supporting hardware (baseband units). Now with ORAN, operators can not only decouple vendors, but also software from hardware, facilitating the migration to a cloud-native model.

JFrog Artifactory and JFrog Xray recently underwent a rigorous hardening process to earn accreditation for inclusion in the U.S. Department of Defense’s Iron Bank, a centralized repository of digitally-signed and hardened container images. In this blog post, we’re pulling back the curtain on the process, in order to share our insights and lessons learned with our customers and with the DevOps community at large.

On June 2, 2019, Google Cloud Platform had a major network outage that disrupted the services of Discord, Spotify, and Snapchat, among many others. The root cause was a benign misconfiguration coupled with a software bug that caused the loss of configuration data. The issue was resolved almost four hours later after the lost configuration data was rebuilt and redistributed.

It is a super exciting day! Finally, you can invite your friends/team/colleagues (pick one) via the web console.

With companies expecting software products to handle constantly increasing volumes of requests and network bandwidth use, apps must be primed for scale. If you need resilient, resource-conserving systems with rapid delivery, it is time to design a distributed system. To successfully architect a heterogeneous, secure, fault-tolerant, and efficient distributed system, you need conscientiousness and some level of experience.