Yunyuanyuan (VIII) | Devops in depth Devops

​ thorough Devops

One 、

DevOps What is it?

Development and Operations The combination of the words

​

​

DevOps: Development  and  Operations  The combination of

• DevOps  As the development of （ Software Engineering ）、 Technical operations and quality assurance （QA） The intersection of the three .

• Emphasize the communication and cooperation between software developers and operation and maintenance personnel , By automating processes to make software build 、 test 、  Release faster 、 Frequent and reliable .

• DevOps  What we hope to achieve is in the process of software product delivery  
  IT  Opening of tool chain
  , Make each team reduce time loss   Consumption , Work together more efficiently . The experts summed up the following  DevOps  Capability map , A good closed loop can greatly   Increase overall output .

Two 、

CICD What is it?

continued

Integrate  

continued

Deploy

1、

Basic idea

​

1.1、 Continuous integration （Continuous Integration）

Continuous integration refers to the delivery of the part of software personal development to the whole part of software , Integrate frequently to discover more quickly   The mistake .“ Continuous integration ” From extreme programming （XP）, yes  XP  The original  12  One of the practices .

CI  You need to have these ：

• Comprehensive automated testing .
  This is continuous integration of practice & The foundation of continuous deployment , meanwhile , Choose the right one   Automated testing tools are also extremely important ;

• Flexible infrastructure . Containers , virtual machine
  The existence of allows developers and  QA  People don't have to go through a lot of trouble ;

• Version control tools .
  Such as  
  Git
  ,CVS,SVN  etc. ;

• Tools for automated build and software release processes
  , Such as  
  Jenkins
  ,flow.ci;

• feedback mechanism .
  Such as building / The failure of the test , Can quickly feedback to the relevant person in charge , To get a more stable version as soon as possible .

1.2、 Continuous delivery （Continuous Delivery）

Continuous delivery is based on continuous integration , Deploy the integrated code to

Closer to the real operating environment

「 Class production environment 」 （production-like environments） in . Continuous delivery takes precedence over software deployment throughout the product lifecycle , establish   On top of high-level automation and continuous integration .

The advantages of continuous delivery and continuous integration are very similar ：

• Fast release .
  Be able to respond to business needs , And realize software value faster .

• code -> test -> go online -> deliver
  The frequent iteration period is shortened , And get quick feedback ;

• High quality software release standards
  . Standardize the whole delivery process 、 repeatable 、 reliable ,

• Visualization of the progress of the whole delivery process ,
  Make it easier for team members to understand project maturity ;
  A more advanced way of teamwork .
  From demand analysis 、 The user experience of the product is interaction   Design 、 Development 、 test 、 O & M and other roles cooperate closely , Compared to the traditional waterfall software team , Less waste .

1.3、 Continuous deployment （Continuous Deployment）

Continuous deployment

When the delivered code passes the review ,

Automatically deploy to the production environment

. Continuous deployment is the highest stage of continuous delivery .  It means , All changes that have passed a series of automated tests will be automatically deployed to the production environment . It can also be called “Continuous Release”.

“ Developer

Submission code

, Continuous integration server to get code , Perform unit tests , Decide whether to deploy to the rehearsal environment based on the test results , If successfully deployed to the rehearsal environment , Conduct the overall acceptance test , If the test passes , Automatically deploy to the production environment , 

The whole process is automatic and efficient .

The main benefits of continuous deployment are , New capabilities can be deployed relatively independently , And can quickly collect feedback from real users .

“You build it, you run it”, This is a  

Amazon 

It can be done in a year  

5000 

Ten thousand deployment ,  On average, each engineer deploys more than  50  The core secret of the times .

5000/365 = 15  Ten thousand times

The developer has finished typing the code . Sure release When , Submission code ,  All the rest are done automatically in one stop

2、 Best practices

2.1、 Internal circulation and external circulation

• Inner loop （ Development to do ）：

                 code 、 test 、 function 、debug、 Submit

• Push the code to the code warehouse （svn,git）【 Code rollback 】

• Conduct CI The process （ Continuous integration ）, Everything can be containerized . Pack it into a Docker Mirror image

• The image is pushed to the image warehouse

• test

• Continuous deployment process （CD）, Get the previous image , Conduct CD. How to put it in various environments .uat、test、prod

• Outer loop

                 Run time monitoring

                 Management of production environment   

                 monitor

                 Online feedback to development

• Then to internal circulation

2.2、 Practice process

new function ,bug Repair , How should we operate ？

• Create a branch to do this （ Development function ）

• Commit branch code changes

• Enter the continuous integration process

• The current branch code functionality is built and tested automatically

• Automated tools push this submission

• Automated integration testing

• You can see the effect

• Manually confirm whether the function is released to the production environment

• Code merge

• Enter the continuous deployment process

        

structure 、 test 、 Release ......

2.3、CICD LandSpace

CICD The blueprint