Operations | Monitoring | ITSM | DevOps | Cloud

The 2019.8.2 release of Puppet Enterprise has added a significant improvement to code deployment by enabling Puppet modules to be downloaded in parallel instead of serially. This functionality was added to the upstream r10k project almost a year ago and has now been added to Puppet Enterprise Code Manager.

I’m excited to announce the release of Puppet Enterprise 2019.8.3. This release builds on a number of important product enhancements based on customer feedback and delivers on the second phase of our highly requested Value Dashboard.

With only 49 days before this very long year comes to an end, we’re thrilled to announce the 2020 State of DevOps Report is finally here. We’re in our ninth year producing the State of DevOps Report; at this point, more than 35,000 technical professionals from around the world have contributed to this body of research, the longest-running and most widely referenced DevOps research in the industry.

In this blog, we will go through an example of how you can use the Cloudsmith Terraform Provider to provision resources in Cloudsmith, such as repositories and entitlement tokens. HashiCorp Terraform is an awesome Continuous Configuration Automation tool. It is used to provision, update and manage infrastructure resources such as Cloud instances, containers, physical machines and more. It is a firm favourite among developers, due to its brilliant community and mix of power and simplicity.

San Jose, CA, November 11, 2020 – A vast majority (84%) of companies considered “digital leaders” by IDC, a leading provider of global IT research and advice, are turning to a hybrid cloud approach as they adopt public cloud services to improve IT service delivery.

A few years ago, we realized that spending in our AWS product test environment had jumped significantly from one month to the next. We drilled down into the issue and traced it to some RDS database instances that had been spun up to test new product features. No one realized that these expensive instances were left running after the tests were complete, and subsequently racking up charges for several months.

By design and tradition, telecoms networks are built to last. But in a world where the rate of innovation seems to be accelerating, the end result is that a lot of legacy infrastructure needs to keep pace with, and accommodate, multiple ‘next generation’ phases. How long this can be maintained before the imperative to rip and replace becomes impossible to ignore is the multi-million-dollar question.

We created the Fleet Project to provide centralized GitOps-style management of a large number of Kubernetes clusters. A key design goal of Fleet is to be able to manage 1 million geographically distributed clusters. When we architected Fleet, we wanted to use a standard Kubernetes controller architecture. This meant in order to scale, we needed to prove we could scale Kubernetes much farther than we ever had.