The basic principles and introduction of the reproduction of DevOps

Reprint Original Address: The basic principle and introduction of HTTP://WWW.CNBLOGS.COM/WINTERSUN/P/3339047.HTMLDEVOPS

The term devops is a combined shorthand for developer and operations. Implementation and QA. DevOps describes and streamlines the software delivery process, which has begun to be widely used today. Emphasize rapid feedback learning from the production environment to the development life cycle. DevOps doesn't just get you to deliver software faster, it's more about helping you produce high-quality software that's consistent with your individual needs.

It is important to encourage operations engineers to work actively with development engineers. The DevOps principles are as follows:

L Cooperation with people :

Get up from your seat and talk to other OPS engineers or developers. Here you can't communicate by email or phone. Imagine trying to have a party with friends on the phone. Yes, now go and talk to someone about the next project, problem, solution, and you need to be like a team to them.

L wear their shoes to walk :

If you're ready to understand how software engineers and operations engineers work every day, how to work with tools, you'd better work with them in real-life scenarios. For example, if you are an OPS person, and you don't take the time to understand the source control system, and the developers are adamant that they are using git with subversion, then they need to stand up and think about the problem. Need more time to learn the system, because you can apply your skills to build tools to support the software development process.

L Work for others : Make everyone's work a little easier. Build tools for OPS, as well as build tools for you. As Tom Limconcelli, author of <<time Management for System Administrators>>, said, "We are programmers now." "Even we have the skill set to supplement the lack. No one can master everything, so building a new tool can help your OPS or developers automate the delivery process. It's not part of the formal environment, it's even a simple desktop tool. This is like a "swap tool" for increased efficiency while also consolidating relationships and enhancing collaboration between teams.

These basic principles can be applied to large companies of large-scale development and operations teams, as well as small-group companies with just a start.

Get closer to DevOps

More and more developers and operations staff learn from each other's expertise. More like they build a common vision of what needs to be done and how to do it. Developers need to learn some general high-level knowledge:

L Operating System

L Network Architecture

L Network Security

• Application Security

L Configuration Management

L Automation Practice

Operators working with developers need to build and maintain a complex online site that requires these skills:

L Communication

L Configuration Management

L Programming

L Software Design and architecture

Evolution

Let's take a look at the following diagram, assuming that some basic packaging has been implemented, the configuration management automation process

Developers have some collaboration with operations personnel, and developers may not understand the configuration of the management Web server, and it may not be clear how the command line configuration is used in a particular operating system. OPS personnel manages the server so that they can click on a button to complete the publishing application to the application server, implement the deployment, and provide the application server. The best environment is for developers and OPS to develop a new environment in a team. But once the new environment is launched, it takes some management costs to track and manage all of the new environments. Unfortunately, network management, configuration management, and more pressure for OPS to support the entire environment is running. See how the following diagram evolves:

In the above diagram we envision a more ideal scenario, which reduces the reliance on compilation, build, and deployment. The fact that the automation system provides a Web application server does not change, it is the Web server configuration that needs to interact with operations, the log configuration, and the deployment of application operations is done by the developer. Operational evolution to adapt to the continuous integration of developers, release management, testing, debugging source code. Developers need to learn about operating system core, network, configuration management and automation. Development and operations can take over the roles of each other, feeling like developers need two role skill sets, as well as the next level of demand for developers.

A 2013 research report on the 4000IT organization, the benefits of organizing DevOps are as follows:

We'll be here today, and we'll get to the next bit of information.

Hope to help you with your software development management.

For a devops update, you can refer to:

http://devopscafe.org/

DevOps is Everywhere

http://devops.com/

http://dev2ops.org/

The basic principles and introduction of the reproduction of DevOps