How companies plan DevOps floor and evolution?

DevOps is now the most popular IT development business model, according to a survey report DevOps research organizations Dora, practical DevOps has been in full swing in various industries, but in particular landing, the enterprises are still difficult, or deviated from the direction of DevOps, after years do not get anywhere, or small-scale trial success, but large-scale progress in the implementation of slow, ineffective, and so on.

Enterprise DevOps practices, methods of success are many, but failed way more fundamental reason is DevOps practice itself is a systematic project, for businesses, is feeling the stones, copy the successful experience of the existing high degree of difficulty . DevOps practices or business expectations in the short term bring considerable benefits sufficient return, or expected overnight transformation DevOps practices, ignoring the status of the foundation and objective process of enterprise DevOps practices, lack of content and DevOps practices evolutionary path in line with corporate status quo and characteristics of design.

So, exactly how to carry out enterprise DevOps practices in order to faster, better, more efficient propulsion floor, fully enjoy the DevOps practices bring business value of upgrading? DevOps practices through more planning involved, comparison of key factors influencing the landing DevOps practices of different enterprises raised floor, and based on this proposed landing path DevOps practices recommendations.


Factors

DevOps landing practice relating to business, from the development of the IT organization, operation and maintenance, operation service capabilities to enhance the appeal. Therefore, the transport capacity of IT research organizations in the DevOps is the practice of internal, while business change is an important external DevOps practices propulsion. Business relationship, IT organizations and DevOps as shown below.

Picture 1.png

DevOps for research and development to enhance the effectiveness, layer by layer can be passed through the ability to ultimately serve the business competition.

Picture 2.png

01 business factors

DevOps in practice, relatively speaking only external business factors, but in reality the process, which is often the first to promote the enterprises to carry out the core elements of DevOps practices. Because the current boom in the business of digital transformation, doing business more and more dependent on business systems, business systems and rapid iteration and high-quality delivery and rely on the IT organization's ability to transport research. The DevOps practices, is currently the most proven and effective way to promote capacity building direction of continuous delivery.

The business has the following characteristics, the stronger demand for its enterprise DevOps practices, the more urgent, more should be conducted as soon as possible of.

业务服务模式:业务服务模式以线上模式为主,或线上模式所占比重逐年上升。

用户群体:用户群里以C端用户为主,或以互联网方式的B端用户为主。

业务变化频率:受市场或政策影响,业务变化频繁,需及时调整应对。

业务连续性、可靠性:业务的连续性、可靠性要求高,任何业务中断都会带来较大的损失。

行业竞争性:行业竞争充分,持续的业务创新有利于提升企业竞争力。


02 IT因素

IT研发、运维服务能力现状是推动DevOps实践的内因。狭义的DevOps用于承载企业IT部门研发侧支持,而广义的DevOps则涵盖企业IT的研发、运维乃至技术运营等业务,当前DevOps的实践主要都集中在研发侧。

企业在研发侧的支撑能力、标准、质量,也并非白纸一张,现有企业大多仍是按需求、开发、测试、运维的划分阶段管理,长期以来研运支撑都是烟囱式建设,导致对于研发、运维的支撑一直难以形成合力,即使建设新的能力,也只是在树立新的烟囱,业务流、数据流难打通,难持续演进。

DevOps相对于IT来说,一方面是治理,另一方面是创新,IT的如下因素,对于DevOps的实践落地推动具有较大的影响。

  • IT现有与业务要求的研发效能差距,差距越大,越急需。

  • IT管控诉求,精细化管控诉求越高,越必要。

  • IT团队规模,规模越大,越有价值。

  • IT工具链缺少或烟囱式建设越明显,越必要。

演进路线

对于DevOps实践上,Dora曾经提出过五个阶段的指导,如下图所示:

Picture 3.png

其分别是:

  • Stage 1: 规范化技术栈

  • Stage 2: 推进标准化&降低不一致性因素

  • Stage 3: 扩展DevOps实践

  • Stage 4: 自动化基础框架交付

  • Stage 5: 提供自服务能力

该指导中特别强调构建标准的技术栈,认为它是Stage 1的关键因素,同时是Stage 2中的实践内容,也是Stage 3的关键因素,是一项需要持续实施的实践要素。

标准化的技术栈有利于降低DevOps实践的难度,但从企业的长期过程来看,实现的难度极大,不太现实;因此,我们建议DevOps的实践要基于异构体系,朝着一站式、企业级的方向,其更符合企业采用技术的演进现状。


DevOps实践演进建议

DevOps实践的演进要从目标定位、建设方式、实践过程等方面进行综合设计与推进,各方面的建议分别如下。


01 目标定位

DevOps实践是一个体系化、持续化的工程,不是一次性的项目建设,不可能一蹴而就。企业DevOps实践的阶段性目标规划既重要又必须,虽然不同企业的最终目标类似,但由于业务、IT的现状不同, DevOps实践的阶段性目标必然会有所差异。

企业DevOps实践的阶段性目标规划,需要依赖于企业的IT基础实力,例如组织、制度、协作模式、人员能力、研发模式等,结合业务保障与IT基础条件,合理的DevOps实践阶段目标。

一般来说,可将企业DevOps的整个实践过程划分为自动化数字化一体化三个大的阶段。

自动化阶段,构建DevOps的自动化过程工具链,着重实现DevOps意识提升、研发转型,以及初步的研发效率与质量提升,助力业务发展。

数据化阶段,构建面向业务和研发全过程的度量体系,形成持续改进机制,实现研发侧的DevOps的持续优化落地,提升业务竞争力。

一体化阶段,构建覆盖研发侧、运维侧,乃至运营侧的延展与闭环,实现应用系统的生命周期DevOps实践覆盖,推动业务持续创新,引领业务发展。


02 建设方式

DevOps的落地推进,部分企业采用的是来自研发团队的自下而上的方式,个别团队自主引入,效果出来后,再推广到其它团队;部分企业采用统一组织,自上而下推行的方式,企业统一规划,统一建设,应用与团队逐步迁移。

相对来说,自上而下的方式更有利于促进企业级的DevOps实践落地。因为对于自下而上的方式,成功经验带有较为浓厚的团队的特点,工具链以开源组件攒建,工具的体系化程度不够,团队级适用是其主要特点,DevOps的实践也常止步于“自动化”阶段。

基于此,经验复制、工具复用的方式难以落地,况且IT组织的核心职能是为企业业务提供服务与保障,IT服务业务如纳入IT组织自保障,必然分散IT组织的服务资源,短期内可能有一定的效果,长期看瓶颈明显,投入产出比不佳。

相对应地,自上而下的方式,从规划之初就会考虑到不同IT组织文化、团队技术栈、业务的特点差异,不同职能组织、不同角色的诉求支撑,产出可服务于企业不同团队的平台级的DevOps实践工具、方法与制度规范,避免实践中方向偏离。


03 实践过程

DevOps实践涉及工具平台、流程体系、规范制度、人员能力等方面建设。实践可采用先提升认知后落地实践、先试点验证后全面推开的过程进行。

DevOps的理解与认知

DevOps从2009年提出以来,其内涵一直在不断的丰富。因此,对于DevOps的理念与认知,在一定程度上决定了DevOps的执行程度。DevOps的定义演变过程如下:


Picture 4.png


DevOps的定义不断发展,内涵也在不断的演进。因此,企业的DevOps实践是一个长期过程,是一个会伴随企业业务发展、IT能力提升的长期过程,涉及企业的业务组织、IT组织的协作提升与持续优化。

DevOps实践平台

DevOps DevOps platform is the practice of corporate landing bearing, one-stop , enterprise-class , sustainable evolution should be the basic demands of the ability of the platform.

DevOps practices is not a day to complete, and similarly, DevOps practices support tools platform, also needs to continue to build and rich. Thick clouds thin end of the research station in operation mode, should be used as the sole direction of the platform, which can be an effective tool for precipitation general ability, but also enhance support the demands of enterprise DevOps scene changes through cost-effective manner.

DevOps practices in an orderly manner

DevOps practices in an orderly way, including two aspects, one means to promote the surface, that is, DevOps practices into other projects within the enterprise, other teams, the progressive realization of team agile, agile project, as well as business agility; another aspect DevOps is deepening application, which is based on the development of performance DevOps continuous optimization and upgrading, the establishment of learning-oriented, mission-oriented team, to promote the landing DevOps culture.

to sum up

Since the proposed DevOps, its meaning has been in constant development and rich. Accordingly, DevOps practices, will be a spiral process that requires companies continue to promote, and then injected into the continuing vitality of the enterprise business development.

Author: Huang in full

Other high-quality articles

ZooKeeper | installation deployment scenarios, the development of docking API

[Bank] landing platform operation and maintenance management, big step towards the Bank 4.0

Elastic (the Flex) Layout

Operation and maintenance transformation | O & M no longer just "as the light goes out."

Kerry was awarded the ITSS [2019 China Science and Technology Excellence intelligent operation and maintenance service provider]


Guess you like

Origin blog.51cto.com/11811406/2472058