Reproduced DevOps Mid-year inventory: 10 most popular technical articles abroad

In this paper, according to the efficient operation and maintenance series Group of Friends to organize the contribution. The "Efficient operation and maintenance" public number as the official only public number of this series group, original and exclusive debut.

Welcome to the "efficient operation and maintenance" of the public number, free to participate in the "Operation and Maintenance forum" Monthly offline communication activities, and the first surely dry full of all kinds of original articles (see article at the end).

Edit

• Wang Peng (translator)

• Gao Hao Miao (Finishing & Publishing)

Introduction

"Editor's note" Recently, foreign technical experts in the SEI grasping the text of the current popular DevOps ideas and tools, including fabric, Ansible, Docker, Chaos Monkey and so on. In this paper, ONEAPM and efficient operation and maintenance are combined to compile and organize:

At the end of 2014, SEI Blog published a series of blog posts about Devops① , providing guidance, practical advice and tutorials. These posts are targeted at a growing number of DEVOPS-based businesses (up to 26% since 2011).

According to recent research ②, these organizations deploy change codes 30 times times faster than traditional methods .

While the benefits of DevOps are obvious, many companies are still afraid to adopt DevOps, which requires a shift in mindset, culture, and technical requirements, and is a big challenge for traditional businesses.

Given these hurdles, CERT researchers ' articles focused on successful cases of Amazon③ and Netflix④ DevOps, as well as tutorials on some of the devops popular technologies, such as Fabric⑤, Ansible⑤ and Docker⑥.

We'll cover 2015 years of the past six months, with 10 of the most popular DevOps-related articles (sorted by number of visits). This article introduces the first 5 articles, followed by the introduction of the following 5 articles. Click "Read the original text" at the end of the article to enjoy the English source.

1. DevOps Technology: Fabric and Ansible

In this blog post, the authors highlight scenarios related to using the DEVOPS deployment process, including assessing resource requirements, designing production systems, configuration and production server configuration, synchronizing code, and so on.

The following is an excerpt:

The workflow for deploying code is almost as old as the code itself. There are many use cases associated with the deployment process, including evaluating resource requirements, designing a production system, configuring and configuring production servers, synchronizing code, and so on.

In this blog post, I will focus on configuring a software package on a remote server and the necessary software to execute your code. This use case can be accomplished using a number of different, competing technologies:

such as: Chef, Puppet, Fabric, Ansible, Salt, Foreman, these are just a few of the technologies you may have heard about the path to DevOps automation.

All of these technologies have a repository that can submit scripts to the warehouse and complete the task. This article explores the fabric and Ansible in more depth. To learn more about other infrastructure as code solutions, check out the article on Docker ⑥ or about Vagrant article ⑦.

One difference between fabric and Ansible is that fabric lets you see results in a matter of minutes, and Ansible requires more effort to understand them. Generally speaking, Ansible is more powerful:

Because it provides the semantics of a deeper and more complex multilayer architecture model, such as WEB and database host arrays.

From an operational perspective, Fabric has a more direct and basic API that can be written in Python, and Ansible uses YAML to provide a rich operation (I'll discuss this later). We will use the examples in this article to illustrate.

Read the full article,DevOps technology: Fabric and Ansible, please visit
Http://blog.sei.cmu.edu/post.cfm/devops-technologies-fabric-or-ansible

2. The DevOps Docker

Read the full article,DevOps Docker, please visit
http://blog.sei.cmu.edu/post.cfm/devops-docker-015

3. Using Docker for development

Docker these days in the DevOps community are quite hot, for good reason. Docker containers enable the development and deployment of application software to achieve a controlled, isolated, flexible, and highly portable infrastructure.

In this article, author ⑧ describes the scalability, resource efficiency, and resiliency of using Docker to develop and deploy software applications.

The following is an excerpt:

Linux Container Technology (LXC) provides the foundation for Docker creation, but this is not a new idea. LXC has already appeared in Linux kernel 2.6.24, when the control group (or cgroups) is formally integrated.

Google has actually used Cgroups technology as early as 2006, because Google has been looking for ways to isolate and run resources on shared hardware.

in fact, Google admits to launching 2 million containers a week, using its own published LXC container Imctfy⑨.

Unfortunately, this technique is not easy to adopt until Docker simplifies container technology and makes it easier to use.

In the absence of Docker, it is difficult for developers to access, let alone understand the merits of LXC. Dotcloud⑩ founder and current CTO Solomon Hykes discovered the potential of Docker, which was released as an open source project in March 2013.

the ease of use of Docker is due to its high-level abstraction of APIs and documentation. This makes the DEVOPS community powerful and creates Docker tutorials, official applications, and many other technologies. By lowering the threshold for entering container technology, Docker has changed the way developers share, test, and deploy applications.

use Docker Development in this article? , Yankel describes how to start using Docker to develop the appropriate software in a common software development environment by launching a database container (MongoDB), a Web Services container (Python Bottle APP), and configuring them to access each other. This is a multi-container application.

To read the full article, using Docker development , please visit
Http://blog.sei.cmu.edu/post.cfm/development-with-docker

4.DevOps Example: Amazon AWS

Readers who regularly read the DevOps blog will find recurring themes in this series:

In essence, DevOps improves quality by carefully building organizational processes, strengthening communication, and working with processes.

In this article? , the experience of Amazon DevOps is shared primarily.

Read the full article, DevOps example: Amazon AWS, visit
http://blog.sei.cmu.edu/post.cfm/devops-casestudy-amazon-aws-036

5.DevOps Example: Netfix's Chaos Monkey

DevOps is often used in areas such as agile development, automation, and continuous delivery, and the spirit of DevOps can be applied in many ways. In this blog post, the author shares another groundbreaking DevOps case study,Netflix? Some way out of the box .

The following is an excerpt:

Netflix is a fascinating case study, as their DevOps software engineering process demonstrates an understanding of the nature of DevOps and focuses on achieving quality requirements through the DevOps Automation assistance process.

DevOps practitioners embrace a drive to focus on quality attributes to meet business needs and leverage automated processes for consistency and efficiency.

Netflix's streaming service is a large distributed system hosted on AWS. As so many components work together to provide reliable video streaming for customers in each region, Netflix engineers need to focus on the reliability and robustness of the quality attributes of the server-side component.

In short, they conclude that the only way to deal with failure is through continuous practice failure.

To achieve such a trustworthy, quality-compliant level, using a DevOps style, Netflix engineers began using automated failure scenarios.

Read the full article,DevOps example: Netfix's Chaos Monkey, please visit
Http://blog.sei.cmu.edu/post.cfm/devops-case-study-netflix-and-the-chaos-monkey

Description

The next 5 articles are also very exciting oh. Please look forward to it.

Every two weeks, SEI publishes a new blog that provides guidance, practical advice, and tutorials for organizations that try to adopt DevOps. We welcome your feedback on this series of articles, as well as suggestions for future content. Please feedback in the comments section below.

①http://blog.sei.cmu.edu/post.cfm/what-is-devops-324
②http://readwrite.com/2014/02/11/devops-future-diy-it-gartner-nosql
③http://blog.sei.cmu.edu/post.cfm/devops-casestudy-amazon-aws-036
④http://blog.sei.cmu.edu/post.cfm/devops-case-study-netflix-and-the-chaos-monkey
⑤http://blog.sei.cmu.edu/post.cfm/devops-technologies-fabric-or-ansible
⑥http://blog.sei.cmu.edu/post.cfm/devops-docker-015
⑦http://blog.sei.cmu.edu/post.cfm/devops-technologies-vagrant-345
⑧http://www.sei.cmu.edu/about/people/profile.cfm?id=yankel_15790
⑨https://github.com/google/lmctfy
⑩https://www.dotcloud.com/
? Http://blog.sei.cmu.edu/post.cfm/development-with-docker
? http://blog.sei.cmu.edu/post.cfm/devops-casestudy-amazon-aws-036
? http://aws.amazon.com/
? http://www.netflix.com/

How to develop happily together

"Efficient operation and maintenance" of the public number (the following QR code) worthy of your attention, as an efficient operation and maintenance series group (the leading operation and maintenance of vertical community) the only official public number, weekly published a number of dry goods full of original Good article: from the series group of discussion essence, operation and maintenance forum wonderful sharing and group Friends original. "Efficient operation and maintenance" is also the Internet column, "Efficient operation and maintenance of best practices" and Operations 2.0 official public number.

Tip: At present, efficient operation and maintenance of two major groups only a small number of precious seats, if you wish, you can add Shida personal number Xiaotianguo as friends, to apply, or to join our technology Exchange Group (technical discussion-oriented, no main group so many rules, more lively).

Important: Unless previously authorised, you can reprint this article 2 days after the public number is published. To respect the knowledge, please reprint the full text, and include the bank and the following QR code.

Reproduced DevOps Mid-year inventory: 10 most popular technical articles abroad