Operations | Monitoring | ITSM | DevOps | Cloud

Bare metal servers are a valuable option for all sizes of businesses, including small, medium, and startups companies. When designing infrastructure it is important to manage cost. However, the decision on whether to run your application on bare metal or cloud provider should not be driven by the size of your company but by your infrastructure needs. Each approach has its own tradeoffs and complexities, especially since it is difficult to find two clouds with the same parameters.

Over the past few months, we set out to drastically reduce the amount of time Code Manager takes to deploy code and sand down some rough edges to make it more stable and robust. In order to understand what we were able to achieve, we need a quick primer on how code is deployed to a Puppet Server in the first place. There are three parts to a Code Manager code deployment: We’ve improved each of these three parts of the Code Manager code deployment.

While Go provides a testing package and a go test command, the former only offers basic testing capabilities. The package also has some drawbacks, such as missing assertions and increasing repetition with large-scale tests. As a result, several Go testing frameworks have been created to augment it. Go testing frameworks consist of tools and resources for creating and designing tests. Some of these frameworks incorporate the testing package and go test command, while others take a different approach.

Pricing is a complex topic matter, and there’s no one-size-fits-all approach to pricing. Few things impact growth and revenue as much as your pricing. Finding the right balance between value and revenue will make or break your business. While most founders have a clear product vision and have thought through things like their go-to-market strategy or hiring plans, surprisingly, few have an idea about what their pricing should look like.

A CI/CD pipeline is the most fundamental component of automated software development. While the term has been used to describe many different aspects of computer science, at CircleCI, and within much of the DevOps industry, we use “pipeline” to illustrate the broad applications of behaviors and processes involved in continuous integration (CI).

Though you may be approaching SD-WAN with great anticipation, the old adage, ‘fail to prepare, prepare to fail’ has never been more relevant. Embarking on an SD-WAN project can be a complex process that requires a great deal of forward planning.

In regulated environments, some machines must adhere to strict cryptography requirements designed to protect systems from being cracked, altered, or tampered with. Using cryptographic modules that are FIPS certified or compliant ensure a systems’ encryption solutions adequately protect its digital assets. FIPS validated operating systems are a prerequisite for government agencies, their partners, and those wanting to conduct business with the federal government.

Whether running on the public cloud or a private cloud, the use of containers is ingrained in today’s devops oriented workflows. Having workloads set up to run under the mandated compliance requirements is thus necessary to fully exploit the potential of containers. This article focuses on how to build and run containers that comply with the US and Canada government FIPS140-2 data protection standard.

The focus of the 2.5 version was on expanding support for HAProxy configuration keywords, and that’s where most of the effort during this release cycle was spent. We will continue doing that during the next couple of versions to gain complete feature parity with both the HAProxy configuration and Runtime API so that you can use the Data Plane API as a full-featured way to configure HAProxy.