Shulou(Shulou.com)06/01 Report--

What this article shares with you is about the five O2O thoughts you should have. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article. Let's take a look at it with the editor.

In many recent customer exchanges, I have repeatedly stressed that operation and maintenance should have the following thinking: "three points offline, seven points online; three points operation and maintenance platform, seven points technical architecture". Operation and maintenance need to "go from offline to online, from offline to online", in short, it is a kind of O2O operation thinking. How to understand the specific O2O thinking? (there is a four-quadrant capability extraction of O2O at the end of the paper)

Offline thinking in 1.O2O

This is part of the three-point operation and maintenance platform, that is, offline content. The construction of the operation and maintenance platform should grasp the main line, with the CMDB platform as the core, which is divided into two parts: one is the continuous delivery platform, which is called automation, which is used to improve the efficiency and quality of delivery while reducing dependence on people; the other is a data platform, which covers end-to-end monitoring system and data analysis system.

Recently, what I think about most is whether the operation and maintenance automation platform should be called automation. Later, my thinking was to remove this operation and maintenance automation from our platform, which is no longer called automation. I carefully looked at many products, including traditional enterprise automation solutions, such as bmc automation, are not bad, because in essence is a process engine plus actuator, does not reflect the difference in capability. What makes Internet operation and maintenance automation different from tradition? my answer is delivery capability. Delivery is a verb that connects many objects, delivers value, delivers services, delivers resources, delivers capabilities, delivers configurations, delivers applications, right? In fact, automation is only a requirement of delivery capability, the most important thing is the quality and efficiency of delivery. We need to have the global thinking ability of continuous delivery, and construct different delivery capabilities according to roles, scenarios and IT maturity, so that the product can bring real value.

Not long ago, I saw a financial application release process, which involved dozens of links, and many people were shocked to see it. I said that precisely this process exposed a problem that many internal platforms lacked service capabilities. For example, a machine acquisition is artificially divided into multiple processes, rather than a complete resource delivery. But when I ask for a device, I need to get a physical machine, and then install the operating system and turn on the firewall according to the KS file. In fact, these should be package into a service that delivers the machine.

These two platforms, finally based on CMDB business information management, can achieve platform closed loop and interoperability. The capability of the tool platform can be used by the monitoring platform to improve the ability of automatic fault handling; the data analysis results and pattern discovery of the data analysis platform can be used as the input of the scheduling decision of the continuous delivery coupled platform.

Online thinking in 2.O2O

This is part of the seven-point technical architecture, that is, online content. I think the improvement of the quality / efficiency of operation and maintenance and the reduction of cost deeply depend on the service capability of this online technical architecture. But when we racked our brains to think about how to improve the automation of continuous delivery and reduce the complexity of application release, we never thought about making some efforts online. The specification of an application can reduce the dependence on cmdb automatic discovery; the reporting of a service relationship call can reduce the dependence on log monitoring; the automatic encapsulation of F5 and DNS capabilities can reduce the dependence on human changes; once the service call passes through the firewall or F5, your service scheduling is no longer simple.

Why do I talk to you about lean operation and maintenance? we should know that the stringent requirement of the Japanese on the production line is to stop all production activities once quality problems are found in the production line. Lean point of view is to face the operation and maintenance with a critical attitude!

OO interworking thinking in 3.O2O

Without a good platform to support, the online capacity cannot be further enhanced; without the cooperation of online capabilities, the offline platform can not be simple enough, the two complement each other and promote each other.

Don't go further and further on the wrong road! Connect offline and online in order to complete the mission. Take our own current start-up projects, for example, we have set high requirements for online capabilities from the very beginning, and he regards operation and maintainability as a strict standard (maybe it has something to do with our background in operation and maintenance. CTO is designed and implemented by Tencent "Zhi Yun"). We access the unified scheduling, use the name service, with the help of automated testing; also use the unified interface specification to facilitate the automatic generation of interface description documents, but also convenient to test; unified packaging, easy to change. With the realization of these capabilities, we reduce our dependence on human flesh operation and maintenance. We need to expand the capacity of a node in the future. Just tell the customer to join a node instead of writing complex documents.

Continuous Operation thinking in 4.O2O

When communicating with customers, customers will inevitably say that many of the ideas you have put forward are very good, but it is very difficult to change on our side. In fact, I also know that change is very difficult. I said I could try some operational ideas. Didn't I always tell you that the operation and maintenance is actually the operation of IT?

First of all, we need to have grayscale thinking, the grayscale process is from non-core business to core business, from good relationship R & D to general relationship R & D, from technology enthusiasm R & D to technology enthusiasm general R & D. You have to master this path, you can't Cover everything in the first place, let all people and business follow your way of thinking, and you are bound to fail.

Second, you must be able to systematically describe your ideas and the benefits you achieve. Many operators only describe their ideas and plans in a few words, which is very bad. We need such a systematic language to communicate with developers / tests and even business units about the benefits of this operable solution. Make a PPT, communicate every month, in UC9 Tour, they have a planning communication meeting, the department spent a few days, pull the parties together, everyone in turn to talk about their own plan, the effect is very good. In fact, there is no wall between R & D and operation and maintenance. If there are more people, there will be a wall!

* you must have a platform to host and visualize your ideas. Even when you don't have business access, you need a visual platform to present your Idea and let the other person see the effect, which is often the most touching. People are rational, but also visual, directly see the visual presentation of the intuitive benefits, there is no reason to refuse.

The rest is for the operation and maintenance staff to identify the target and get to work. Everything is difficult at the beginning, and when you connect to * services, the progress of other services will be greatly improved. I have always thought that R & D is not the enemy of operation and maintenance. In fact, they take their applications or programs more seriously and want them to have higher usability. They just often suffer from time and no operation and maintenance ideas. But we must be careful that this trick is not spoiled, that is to say, a shot must be successful!

The thinking of "subsidy" in 5.O2O

In fact, you can see that there are just a few tricks for developers to reject OPS requirements. * * tricks: if the performance of your solution degrades, more machines will be needed; second, if the demand of OPS is launched in this period, the progress of product launch will be affected. To deal with * points, it is very simple to subsidize some of their resources. This strategy was adopted before when UC promoted the MySQL high availability solution. When building a dual-center, we said that we needed twice as many machines. I said that we could bring a breakthrough in the operation and maintenance of the dual-center, so give it to the machine. But the second point, I think the strategy to break the situation is that operators need to go out, go to the R & D side, go to the front of the R & D process, R & D stage-"design stage -" demand stage, do more time subsidies, and constantly promote.

The thinking of O2O is to make operators aware of the ability not to be too infatuated with the platform. Tools are tools that can never surpass the energy behind the idea of technical architecture design. O2O thinking is also a kind of DevOps thinking, O to understand the operation and R & D, do not understand the R & D operation and maintenance is not a good operation and maintenance. Today, I would also like to emphasize that if I do not understand the R & D of operation and maintenance, I do not think it is a good R & D. O2O thinking is a kind of operational thinking, without continuous iteration and optimization, operation and maintenance can not get out of the predicament.

Appendix reference:

The O2O four quadrants of operation and maintenance are summarized as follows:

These are the five O2O thoughts you should have. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.