Tag: devops

DevOps and Containers, On-Prem or in the Cloud

March 14, 2017

The cloud vs. on-premises debate is an old one. It goes back to the days when the cloud was new and people were trying to decide whether to keep workloads in on-premises datacenters or migrate to cloud hosts.

But the Docker revolution has introduced a new dimension to the debate. As more and more organizations adopt containers, they are now asking themselves whether the best place to host containers is on-premises or in the cloud.

As you might imagine, there’s no single answer that fits everyone. In this post, we’ll consider the pros and cons of both cloud and on-premises container deployment and consider which factors can make one option or the other the right choice for your organization. Read more


Top 5 challenges with deploying containers in production

February 24, 2017

 

Docker containers make app development easier. But deploying them in production can be hard.

Software developers are typically focused on a single application, application stack or workload that they need to run on a specific infrastructure. In production, however, a diverse set of applications run on a variety of technology (e.g. Java, LAMP, etc.), which need to be deployed on heterogeneous infrastructure running on-premises, in the cloud or both. This gives rise to several challenges Read more


Introducing Containers into Your DevOps Processes: Five Considerations

February 15, 2017

Docker has been a source of excitement and experimentation among developers since March 2013, when it was released into the world as an open source project. As the platform has become more stable and achieved increased acceptance from development teams, a conversation about when and how to move from experimentation to the introduction of containers into a continuous integration environment is inevitable.

What form that conversation takes will depend on the players involved and the risk to the organization. What follows are five important considerations which should be included in that discussion.

Define the Container Support Infrastructure

When you only have a developer or two experimenting with containers, the creation and storage of Docker images on local development workstations is to be expected, and the stakes aren’t high. When the decision is made to use containers in a production environment, however, important decisions need to be made surrounding the creation and storage of Docker images.

Before embarking on any kind of production deployment journey, ask and answer the following questions: Read more


Containers: Making Infrastructure as Code Easier

January 31, 2017

Containers and Infrastructure as CodeWhat do Docker containers have to do with Infrastructure as Code (IaC)?

In a word, everything.

Let me explain. When you compare monolithic applications to microservices, there are a number of trade-offs. On the one hand, moving from a monolithic model to a microservices model allows the processing to be separated into distinct units of work. This lets developers focus on a single function at a time, and facilitates testing and scalability. On the other hand, by dividing everything out into separate services, you have to manage the infrastructure for each service instead of just managing the infrastructure around a single deployable unit. Infrastructure as Code was born as a solution to this challenge.

Container technology has been around for some time, and it has been implemented in various forms and withvarying degrees of success, starting with chroot in the early 1980s and taking the form of products such as Virtuozzo and Sysjail since then. It wasn’t until Docker burst onto the scene in 2013 that all the pieces came together for a revolution affecting how applications can be developed, tested and deployed in a containerized model. Together with the practice of Infrastructure as Code, Docker containers represent one of the most profoundly disruptive and innovative changes to the process of how we develop and release software today. Read more


Accelerating DevOps adoption in the Nordics

January 20, 2017

EVRYLast week we announced a partnership with EVRY, one of the leading IT companies in the Nordics, to deliver Rancher’s container management platform as a service to EVRY customers.  This is an exciting moment for Rancher as the service will introduce our software to a new audience looking to embrace DevOps and transform how they deliver IT.

Not surprisingly, our relationship with EVRY began last year when a couple of their cloud architects downloaded Rancher and built a small test deployment. Like so many Rancher fans, they were looking for a simple way to use containers to accelerate the adoption of DevOps and continuous delivery for customers. Read more


Hidden Dependencies with Microservices

December 15, 2016

One of the great things about microservices is that they allow engineering to decouple software development from application lifecycle. Every microservice:

  • can be written in its own language, be it Go, Java, or Python
  • can be contained and isolated form others
  • can be scaled horizontally across additional nodes and instances
  • is owned by a single team, rather than being a shared responsibility among many teams
  • communicates with other microservices through an API a message bus
  • must support a common service level agreement to be consumed by other microservices, and conversely, to consume other microservices

These are all very cool features, and most of them help to decouple various software dependencies from each other.

But what is the operations point of view? While the cool aspects of microservices bulleted above are great for development teams, they pose some new challenges for DevOps teams. Namely:

Read more