Evops is a very tall name, in fact, the simple point is that development and operation of itself is a team, to do things together to do well. No matter who has a problem, the website is not. As an architect, you have to be devops and know how to implement DevOps.
First of all to automate, for example Ali, Ali through the Aone system to achieve semi-automated deployment:
- Developers develop code to submit code to git after self-test pass.
- One-click deployment to the daily environment in Aone. Deployment is an automated scanning dependency conflict, system security and other issues.
- Test the notification to a successful deployment, test it, and if the test passes, approve it, and you can publish it online.
- On-line OPS personnel are deployed to the line with a single click, and deployment can be assigned to deploy for A/B testing. If a problem occurs, you can roll back one click.
Of course, this involves a lot of roles, in fact, if it is a company, the team should be one, equals. Each role in the team is a programmer and needs to be rotated every once in a while.
It's not just deployment that requires automation, testing, scaling, monitoring, analytics, and so on. Of course, this needs to be based on the actual situation of your company practice, the first need is actually deployment automation, how to achieve it:
- Using open source products git,hudson,ansible or puppet
- Develop appropriate specifications, automated deployment is normative, everyone must abide by, or the fault will appear immediately
- To make the whole system a whole,
- The above open source product is not a whole and needs to be coded to make it a system.
- Involves web system development, bottom-level scripting, Packaging specification development
- Continuous discovery of repetitive labor, making it automated
- To have a corresponding monitoring system, timely detection of anomalies
With this automated system, you can consider the automation of product installation, testing, expansion, monitoring, and analysis systems behind it.
In addition, continuous improvement is also at the heart of DevOps, with an eye to finding improvements. As long as there are things to repeat more than 3 times, consider whether automation is required.
If you don't do devops, as your business grows and your system grows, you will eventually need to transform it from beginning to end. It is better to start the construction of the pre-design considerations, in fact, these things if you understand, the beginning of the good, do not waste too much time, but can save a lot of time, why not.
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Why architects Express 7.3-devops is important